Actually, allocation does the ENQ, not the initiator. And both names will
be ENQed, so the real point here is that your alias suggestion won't work.
Mark, I think you are wrong. The initiator ENQs on all dataset names
that appear in the JCL during job initiation, long before any allocation
of datasets takes place.
However, in the case of an alias, I think that step initiation (and this
may actually be in the allocation component) will ENQ on the true name.
I am not certain on this and I haven't tested.
Similar processing occurs for GDG relative generations (e.g., +1). Job
initiation doesn't know what the true absolute name will be, so it ENQs
on the GDG base name. Step initiation ENQs on the absolute name
(.GnnnnV00).
It used to be that if step init could not get the ENQ, it would fail the
step and job, but now there is a parmlib option allowing installations
to control what happens (failure or warning)
--
Bruce Black
Senior Software Developer
Innovation Data Processing
----------------------------------------------------------------------
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
