At 10:48 -0300 on 05/24/2007, Shmuel Metz (Seymour J.) wrote about
Re: Why is there JOB scope for DSN ENQ's anyway?:
>Just make it a private/undocumented interface (as has been done with
other internal functions such as SuperLocate and others) and
restrict its use to ONLY the Initiator (and possibly other IBM
routines that could be more efficient by its availability).
That is an unnecessary and insufficient condition. I see no risk in
making it a GUPI, while making it private does not resolve the problem
of a GRSplex with some members not having the functionality. By all
means submit a requirement, with a sound business case, but don't ask
for an early implementation; if you got one you'd be sorry. It will
undoubtedly take IBM some serious work to get the GRS aspect right.
I may be missing something but I do not see how GRS comes into play.
Lets say that I have two systems in my GRSplex. System A has the
enhanced ENQ while System B does not. If I run a job on System B, the
EXC ENQ gets keep until the last DISP=SHR step terminates (like now).
When run on System A, the EXC ENQ gets downgraded and propagated to
System B (with all the waiting SHR ENQs on both systems getting
released). Remember that the fix is done in the Initiator so that
fact the System B Initiator (and ENQ) does not have the fix does not
affect anything.
My 2 step implementation method (first private interface and then
later GUPI when the downlevel system issues get addressed) is to
allow it to be available to the Initiator (and other IBM routines)
NOW with code that is Guaranteed to be at the minimal support level
needed to make use of it without running into the GOTCHA situation of
a user program that is using the GUPI (or assuming that the support
exists due to being assembled with a ISGENQ [ENQ due to being
depreciated does not need to be updated just like GETMAIN was not to
support STORAGE-Only functionality] macro that supports it) and then
run on a downlevel system without the support (assuming that the
current ENQ/ISGENQ routine can not spot the "bad" parmlist and either
ABEND or return a Non-Zero RC as appropriate).
----------------------------------------------------------------------
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
