retired mainframer wrote:
If the dataset in question is not SMS managed, CAMLST/RENAME makes no effort
to update the catalog. Therefore your UNCAT and CAT steps are necessary and
should succeed.
If the dataset in question is SMS managed, coordinates the required changes
to the VTOC, the VTOC index, and the catalog. Therefore your UNCAT and CAT
steps are not only unnecessary but bound to fail.
I expect this is why you are seeing "random" failures.
Yes - I was wondering about the SMS managed question. But,
the documentation for CATALOG with an UNCAT CAMLST says
this:
Restriction:
The CAMLST UNCAT or UCATDX function is not supported for
system-managed
data sets. These are ignored. The function is not performed and
the return
code is 0.
so while I expect the unCATALOG to "fail" for an SMS-managed file, I also
thought it would fail "gracefully" and give me a return-code of 0. It
seems to
be giving me a return code of 8 (with a reason code of 8.)
Perhaps the documentation is in error?
Is there a programattic mechanism for determining if a data-set is SMS
managed?
I'm wondering if an SVC 99 asking for the data-set's management-class is
sufficient
(albeit expensive.)
- Thanks -
- Dave Rivers -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
