On Tue, 17 Nov 2015 22:05:27 -0600, Joel C. Ewing <[email protected]> wrote:
>After several decades of using MVS I finally ran into a case where I >thought GDS/GDG versioning might be useful and used it to create a >corrected version of a GDS generation using V01 to make it obvious it >was a corrected version. > >I was lucky and didn't shoot myself in the foot. Somehow I was thinking >there would be an opportunity to verify things were cool before trashing >the GnnnnV00 version, but the instant the GnnnnV01 version is cataloged >the corresponding Gnnnnv00 version scratches! I haven't done it, so I can't verify what the doc says, but Using Data Sets has this to say under the topic Absolute Generation and Version Numbers: <quote> You can catalog a new version of a specific generation automatically by specifying the old generation number along with a new version number. For example, if generation A.B.C.G0005V00 is cataloged and you now create and catalog A.B.C.G0005V01, the new entry is cataloged in the location previously occupied by A.B.C.G0005V00. The old entry is removed from the catalog, to make room for the newer version, and may or may not be scratched depending on what limit processing options are specified for the GDG base. </quote> So you might want to make sure the GDG is defined with NOSCRATCH before doing this. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
