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. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Thomas David Rivers > Sent: Tuesday, April 11, 2017 4:43 PM > To: [email protected] > Subject: Re: unCATALOG after a RENAME <snip> > The operations appear to be: > > Ensure the "to" data set doesn't exist. > Do a LOCATE on the "from" DSN to determine the source volume list > Do a RENAME with that volume list > unCATALOG the "from" name > CATALOG the "to" name > > I have the hope those last two steps are not necessary... I don't know > why they are there - seems like the RENAME would have done it's job > (assuming all the return-codes are appropriate.) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
