-----------------------------<snip>---------------------------
Paul Gilmartin wrote:
Ouch! So it updates the element's SYSLIB (or whatever) subentry in
the element's target zone entry without even determining whether
it can allocate the data set? And then when the user supplies
a corrected SYSMOD it attempts to allocate the data set before
updating the SYSLIB subentry? I could imagine a more robust
design.
Could the user recover by providing a DD statement in JCL for
the bogus DDNAME for one APPLY which would correct the CSI for
the future?
-- gil
-----------------------------<unsnip>----------------------------------
Supplying the bogus DD name (probably) won't correct anything; just
bypass the real problem.
If you list all the elements of the SYSMOD in the target zone, you
should be able to find the bogus
DD name and correct it with UCL. But be VERY CAREFUL, lest you get
results you hadn't
planned on getting.
----------------------------------------------------------------------
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
