In
<[EMAIL PROTECTED]>,
on 07/28/2006
at 10:42 AM, "Hunkeler Peter (KIUB 34)"
<[EMAIL PROTECTED]> said:
>Is is my understanding and experience that the initiator will ENQ on
>all data sets referenced in the JCL (all steps) at job initiation
>time. The job will not start even the first step before all ENQs
>have been granted. So a job might be "WAITING FOR DATASETS" even if
>the one not yet available is only referenced in step nn (nn > 1).
>At step end, the initiator will DEQ any DSNs that are no longer
>needed, i.e. those which are not referenced on a DD in any later
>step.
Correct.
>It is also my understanding that this is initiator business and
>therefore works the same way in either JES2 or JES3 environments.
Yes.
>(I don't talk about main device secheduling in JES3, which only
>handles devices, not DSN ENQs).
MDS serializes data sets; unlike the Initiator, it takes volume serial
numbers into account.
>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.
I'm sure that he was told that. The ISV was wrong.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
