Not just your shop, John. Access to actually create or modify a job schedule here is restricted to operations personnel. IMHO, a real production scheduler is usually way overkill for a programmer wanting to set up a few ad-hoc job sequences, not to mention that (in my experience) companies don't usually bother to teach programmers how to use production schedulers anyway.
The comment earlier in this discussion (or the other similar thread) about changing the DUPEJOB setting for JES2 to allow duplicate-named jobs to execute simultaneously would be entirely counter-productive here, since submitting your series of 10 compile and link jobs (all with the same job name) would entirely flood the few initiators permitted for this purpose, locking out all the other hundreds of programmers from that scarce resource. One duplicate at a time measures out a very scarce resource in the fairest manner, or at least in *a* fair manner. Still, it would be nice to have the JES3 job networking capability. Not likely to go JES3 here though. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Wednesday, May 01, 2013 10:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Check whether job still running I don't know if it is a general "problem" or only one around here (due perhaps to ignorance), but in most cases, a programmer cannot _easily_ add an "ad hoc" series of jobs to our CA7 system and schedule them. Not to mention that the programmers don't generally have that level of knowledge any way. I am not very JES3 literate, but I've heard that it solves this problem with DJC (Dependent Job Control). And, of course, not letting a job into an initiator when it would cause a "JOB WAITING FOR DATA SETS" message. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
