RE: Job Date

["Jewel, Jerry" <jerry.jewel@xxxxxxxxxxxxxx>]

You mentioned you are doing a SBMJOB.  The options for the DATE parm of
SBMJOB command is:

Job date . . . . . . . . . . . .   *JOBD         Date, *JOBD, *SYSVAL

Most job descriptions are set to *SYSVAL.  The submitted job will use the
system date.  There is no *CURRENT for job date special value.

I believe your CL or OCL will need to retrieve and substitute the current
job date in the DATE parm.

Regards,
Jerry

Better living through fine code and hot coffee!


> -----Original Message-----
> From: Jim Langston [SMTP:jlangston@conexfreight.com]
> Sent: Monday, January 03, 2000 1:47 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      Job Date
> 
> 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.
> 
> Is this a Y2K bug?
> 
> Is there a work around?
> 
> Regards,
> 
> Jim Langston
> 
+---
| 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
+---