If you specify the volser for a non-sms dataset, the catalog is not accessed, and the rename does not update the catalog, and you need to manually update the catalog.
On Tue, Apr 18, 2017 at 10:18 AM, Thomas David Rivers <[email protected]> wrote: > retired mainframer wrote: > >> Run some test cases, at least one for an SMS volume, at least one for a >> non-SMS volume: >> List the catalog entry for the old DSN >> List the catalog entry for the new DSN (expect failure) >> List the VTOC for the old DSN >> List the VTOC for the new DSN (expect failure) >> Rename the dataset >> List the catalog entry for the old DSN (expect failure for an SMS >> dataset) >> List the catalog entry for the new DSN (expect failure for a non-SMS >> dataset) >> List the VTOC for the old DSN (expect failure) >> List the VTOC for the new DSN >> Uncatalog the old DSN (expect failure for SMS dataset) >> List the catalog entries for both old and new DSNs >> Catalog the new DSN (expect failure for SMS dataset) >> List the catalog entries for both old and new DSNs >> Draw conclusions about who does what to whom. >> >> Are any of the datasets VSAM in disguise, such as PDSE or ZFS? >> >> >> > Hi! > > That's not a bad idea - except that in-house, I get no errors; this is at > a customer site (and the errors are strange - return-code=8 and > reason-code=8 > from the unCATALOG; that reason-code is undocumented for that return-code.) > > The data sets are not VSAM - just a "flat" sequential file. > > It's interesting that I can't seem to arrive at a _definitive_ "This is the > proper > way to rename a non-VSAM file" statement. I can't find anything in the doc, > etc... > and while an act-of-discovery will probably get me something that "mostly > works", > one is not assured it would be guaranteed to work into the future, etc... > > I find this situation strange of such a venerable operating system, and it > makes me > think that I must not be understanding something fundamental... because > surely such an operation as renaming a file must be well defined and well > understood > and easy to communicate. > > But - no answer has been forthcoming here, and my scouring of DFSMS > documentation hasn't yielded anything fruitful; so... looks like > experimentation > is what is left... > > Unless, another pair of eyes has seen some kind of documentation or example > of "this is the proper way to rename a non-VSAM file." > > - Dave R. - > > -- > [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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
