----- Original Message ----- From: "Mark Zelden" <mzel...@flash.net>
Newsgroups: bit.listserv.ibm-main
Sent: Wednesday, July 07, 2010 2:32 PM
Subject: Re: ENQ trap for dynamic allocation


On Wed, 7 Jul 2010 11:30:08 -0600, kopplin <kopp...@earthlink.net> wrote:


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?


Yes - covered early in the thread along with a pointer to the
manual.  GRS exits.

Mark

It looks like we have different definitions of "better".  We run a GRS exit
(for Bronzeplex) written when we had a lot more Systems Programming horsepower
than we do today.  Given the same (Priceplex) situation today, I would swear
up and down that MIM is an absolute requirement. From a business perspective,
I really do think that's true.  Things are obviously changing.

Given a "No money, code something up" situation I would work a dynamic
allocation front-end with GRS Exit as a distant second choice.  But that's
a personal pucker factor at play.

Mileage varies, there's more than one way to skin a cat etc.

Lance
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:mzel...@flash.net
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to