>What happens if the program that employs such a product was fetched from
a
>program object with the (newfangled?) deferred/incremental load protocol?
This is only one of the reasons that reallocating STEPLIB (and perhaps any
other system-allocated DD) is not supported.
The operating system cannot prevent an authorized program from doing
whatever it wants, but you won't get any sympathy if something bad
happens.
And of course in this case the system actually did prevent this specific
reallocation. The message seems pretty clear, as does the documentation
for the dynamic allocation code associated with the IKJ56236 message.
0364
(868)
Meaning: JOBLIB/STEPLIB specified as a ddname,
or associated with specified dsname or
pathname. These ddnames are allowed only for
special data sets. The accompanying message
IKJ56236I identifies which of the above ddname
types is in error. (dsname allocation, ddname
allocation, unallocation, concatenation,
deconcatenation)(1)
Application Programmer Action: Use a different
ddname, or consult your system programmer for
the proper ddname to use.
Corresponding Message: IKJ56236I
If you don't like the STEPLIB that you're running with, then you ought to
design your application to run under a subtask that you can attach with a
TASKLIB that you open, so that module fetches will use the tasklib first.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
