areas and allowing a programmer to choose to enable a feature may
have effects that the installation needs to control.
Regards, Steve
Steven B. Jones
z/OS BCP Development - Allocation/Scheduler/SMF
--
For IBM-MAIN subscribe
A little plug for z/OS V1R11:
It contains a new setting in ALLOCxx to tell Allocation to not recall a
data set before deletion, when the program name is IEFBR14 and the
DISP=(OLD,DELETE) or DISP=(MOD,DELETE). Look for the
IEFBR14_DELMIGDS(NORECALL) setting in Initialization and Tuning
Well, I disagree about the kluge part, (it solves the problem for which
the requirements were written), but disgarding that ...
How often does this very big hole occur? Does it make the function
unusable? (I'm really curious, not being argumentative). When the data
set is not deleted and
I am out of the office until 12/07/2009.
Thanks,
Steve
Note: This is an automated response to your message IBM-MAIN Digest - 2
Dec 2009 to 3 Dec 2009 (#2009-337) sent on 12/4/09 0:00:03.
This is the only notification you will receive while this person is away.
It's true that IEFBR14 will now get special treatment for the purposes of
batch allocation. I don't know if I would call that a reserved word.
We thought about the steplib case. If a programmer writes his own
IEFBR14, he can expect the system to behave as if it were the real
IEFBR14 shipped
5 matches
Mail list logo
