Re: WRKJOBSCDE, library lists, and user ids.

["Richard B Baird" <rbaird@xxxxxxxxxxxxxxxxxxxxx>]

Rob,

Thanks, I think changing the call to a submit is the ticket.  that should
work nicely for us.

I really wonder why, since the jobscde is simply a glorified sbmjob, they
don't include ALL of the sbmjob command parms in the addjobscde and
chgjobscde, etc.

thanks again,

Rick


------original message----------
1)  We've gotten out of the habit of using 10-Submit Immediately.  It
often will use many of the features of your current environment.  Instead
we'll just change the entry to a time about 30 seconds into the future.
Don't know how many times we use 10 and it worked great only to find it
failed when ran during the night.  Therefore 10 is not a valid test.

2)  On an addjobscde, and NOT on submit immediately, it should use the
library list of the job description listed in the JOBD portion of
ADDJOBSCDE.  If you find this not to be true, then there is one way to
gain some more insurance.  Instead of putting a call directly on the
command, have it do a SBMJOB.  Sample:
ADDJOBSCDE JOB(RICHARD)
           CMD(SBMJOB CMD(CALL PGM(MYPGM)) JOB(RICHARDJS)
               JOBD(MYLIB/MYJOBD) PRTDEV(*JOBD) OUTQ(*JOBD)
               USER(*JOBD) INLLIBL(*JOBD))
           FRQ(*WEEKLY)
           SCDDATE(*NONE)
           SCDDAY(*MON)
           SCDTIME('08:00')
Remembering to prompt on the SBMJOB command and override numerous of the
defaults away from *CURRENT, *USER, etc.