-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Cole Sent: Friday, May 23, 2008 1:17 PM To: [email protected] Subject: Re: Controlling the execution sequence of dependant jobs in JES2 (a suggested fix)
As noted in my prior post, I think it is a shame that the IBM-JES2 folks make it so difficult to serialize a thread of jobs. It seems to me that this is such an obvious thing to want to do, but when JES2 is started with CNVTNUM=>2 (and there are strong reasons for must shops to want to do this), such serialization becomes problematic. The thing is, a JES2 supported solution, it seems to me, would be both ideal and easy to implement. Here's my idea: (1) support a //card option or a /*card option by which a user could provide an arbitrary serialization name. Example: /*JOBPARM THREADNAME=xyz. Use this name on each job in the thread. <SNIP> How about getting IBM to support //*NET in the JES2 world? Wouldn't that get you what you are after (assuming you have used JES3 and know about NETWORKED JOBS). Regards, Steve Thompson -- All opinions expressed by me are my own and may not necessarily reflect those of my employer. -- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
