When you say "a file in the VTOC," did you deliberately mean to distinguish that from a case where you rename a dataset in the catalog? Did the rename command specify a volume? Was the old DSN catalogued on the volume whose VTOC you are updating? Is the new DSN catalogued correctly? Did the new DSN exist in the catalog prior to this activity?
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Thomas David Rivers > Sent: Tuesday, April 11, 2017 1:24 PM > To: [email protected] > Subject: unCATALOG after a RENAME > > I've got some old code here that is doing a strange > thing trying to rename a non-VSAM file. > > After invoking the DFSMS RENAME service; which > has met with success (return-code is 0) to rename > a file in the VTOC from the "old" name to the "new"name; > it then goes on to un-CATALOG the "old" name. > > What is surprising is that the un-CATALOG mysteriously > succeeds... but only sometimes. > > Trying to track down two questions with this: > > 1) Is the un-CATALOG of the "old" name (which presumbly > is no longer there since RENAME has succeeded) necessary? > > 2) Why would this un-CATALOG succeed if the RENAME > has worked? Shouldn't it always fail??? (Presumably > with a return-code of 8?) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
