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.
It is also my understanding that this is initiator business and
therefore works the same way in either JES2 or JES3 environments.
(I don't talk about main device secheduling in JES3, which only
handles devices, not DSN ENQs).
Peter, you are 100% correct.
I seem to recall that in the "old days", before OCO, there were USERMODs
that changed this. Heck, I think I wrote one myself for SVS. But these
have never been standard IBM operation.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
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
