Hmm...
Now I have examples of SMS-managed un-CATALOG failing, and non-SMS-managed
un-CATALOG failing. But, I can't seem to reproduce the failure in-house.
I thought perhaps that my order-of-operations was wrong?
Here's what the code is doing:
RENAME (rename the file on the VTOC)
CATALOG UNCAT (uncatalog the old name)
CATALOG (catalog the new name)
Is that not the proper order to do things?
If it is the proper order, what is expected of that CATALOG UNCAT step?
Should a failure simply be ignored?
I've spent a few days reading thru DFSMS books and looking for
examples; but
haven't found a definitive answer to these questions. The documentation
for RENAME in DFSMS Advanced Services doesn't seem to indicate that the
un-CATALOG/CATALOG would be needed for non-SMS files, but seems like
it would be?
If someone has a pointer to some definitive doc on "this is the proper way
to rename a non-VSAM file" it would be much appreciated.
- 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
