----- Original Message -----
From: "Chris Craddock" <[email protected]>
Newsgroups: bit.listserv.ibm-main
Sent: Wednesday, July 07, 2010 10:12 AM
Subject: Re: ENQ trap for dynamic allocation
>
Perhaps I'm missing something here, but couldn't this be nicely done in
IEFDB401?
Some code would be necessary to rattle through the dynamic allocation
parameter
list, but on an allocation request, find the DSN (if present) and DISP
(if
present)
and then, do the actual ENQ on SYSDSN (whatever). If you get it, DEQ and
proceed,
otherwise use the logic you presently have.
Testing "can I get the resource" by obtaining and then releasing it
doesn't
do anything productive, but it DOES drive up resource contention and
overhead. The problem with any such approach is that the state of the
resource is quite likely to be different the moment you release it, so a
subsequent attempt to obtain it would block anyway. There IS a conditional
form of ENQ you can use if you don't want to become trapped in amber while
some paleolithic production job runs all day.
Well, yes. But the OP has an existing ENQ screen, and existing logic
and an expectation that this continue. If I were in his situation, IEFDB401
is where I would look. I did look at PC screening once, and it was scary.
So, given the situation at hand, is there a better place to look than
IEFDB401?
--
This email might be from the
artist formerly known as CC
(or not) You be the judge.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
