WLM managed classes are queued by RDR-TIME, (to the 1/100th of a second). Assuming they all resolved to the same service class, Ceterus parabus, they *should* run in the order submitted. However, job2 may not wait for the completion of job1. Obviously there are a number of "exception" criteria.
I have a job class set up for "single threading" via $TJOBCLASS(x),XEQCOUNT(MAXIMUM=1) This applies sysplex wide. Only one job can be in active execution in class x. <snip> Maybe. But if the class is managed by WLM, there is at least some chance jobs may not run in the order they were submitted. At least I think that's the case (perhaps someone more familiar with WLM can confirm or deny that understanding). </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
