<snip> My colleague claimes that he once was told by an ISV that in a JES2 environment two jobs can be serialized on a certain step by coding a DISP=OLD/MOD DD for a data set in the step to be seriallzed. The jobs would then execute in parallel until they come to that specific step. They also said that this will not work in a JES3 environment because JES3 behaves as I described above. This contradicts my understanding (and experience). </snip>
This is indeed true. However, it is not the initiatior that does the enqueues it is allocation. The step will not proceed until all enqueues are granted. Yes two jobs can be serialzed on a single resource(dataset) by coding disp=old/mod On one or both of the jobs. However, the 1st one wins. Given JOBA and JOBB, there is no guarantee that JOBA will always be the first to obtain the enqueue. This can be extened to any number of jobs. The jobs will execute using the serialized resource in the order the reached the point of serialization. Again, there are no guarantees that the jobs will process in JOBA, JOBB, JOBC,.... Order. I am not familiar enough w/JES3 to make a useful comment. ---------------------------------------------------------------------- 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
