Re: Job Date

Jim Langston wrote:
> 
> There is a certain procedure that runs in a batch job that
> uses the job date for a lookup.  I did not write this procedure,
> but there is now a problem with it.
> 
> Before, our users would type in // DATE 12/24/99 and the job
> date would change to 12/24/99 when the sbmjob was ran, and
> everything went fine.
> 
> But, someone came to me today and said he ran this job to get a
> report and it came out 0.  I did the procedure myself, changed the
> jobdate to 12/24/99 with // date 12/24/99 and ran it, then looked at
> the job when it was running and it has a job date of 01/03/2000.
> 
> I then went to find out where else I could change the job date and
> did a CHGJOB and prompted, hit F9, scrolled down and saw a
> jobdate field, that already had the value 122499 in it.
> 

As you proably know, this is a S/36 command, and I just tested it on
a V4R3 machine.... It works normally... 

The // date xx/xx/xx changes the "session" date in a S/36EE....

What release are you on ????
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---