I suppose you could set some job classes to allow the NODELAY, and have automation look for a particular JOBPARM which would result in moving the job to those classes. Don
On Fri, Oct 2, 2009 at 3:14 PM, Howard Brazee <[email protected]>wrote: > On 2 Oct 2009 11:55:07 -0700, [email protected] (McKown, > John) wrote: > > > This "one at a time" has persisted to this day as a primitive way to try > to ensure that jobs run in a specific sequence. Programmers especially think > that if "n" jobs are submitted in the same job class, then they are > guaranteed to run in the order submitted. They really aren't guaranteed, but > it happens in 99% of the time. And is usually set up to try to guarantee it. > > I do this all the time. It would be nice to keep this ability with a > job parm while changing the default behavior. > > > ---------------------------------------------------------------------- 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
