|
On 2/7/06, Yivi <nardus@xxxxxxxxx> wrote: > On 2/7/06, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote: > > > > > > This sounds like it should work to me! The job schedule entry is calling > > your program directly, right? It's not running the SBMJOB command or > > anything like that, is it? > We use a lot of job schedule entries here, and had lots of troubles such as described here. We have found it much more effective to actually put a SBMJOB in the job schedule entry. This allows us to force the job description, library list, subsystem, etc. Such as ... Display Job Schedule Entry Details System: CFP Job: SLS_QUOTA Entry number: 000098 Status: SCD Next submit date . . . . . . . : 02/09/06 Command . . . . . . . . . . . : SBMJOB CMD(CALL PGM(UR2500C)) JOB(SLS_QUOTA) JOBD(BPCSUSR/BPCS) JOBQ(MIS) INLLIBL(*JOBD) LOG(4 00 *SECLVL) Job queue . . . . . . . . . . : *JOBD Library . . . . . . . . . . : -- Tom Jedrzejewicz tomjedrz@xxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.