On Tue, Nov 17, 2015 at 3:23 PM, Peter Hunkeler <[email protected]> wrote: > > What makes "V00" ever Vnn, where N<>0? > > > IIRC, the system does not really care for the version number. When a new > GDS is allocated using relative numbering, the version is always V00. If > you want to replace a GDS with a specific generation number while keeping > the place in the GDG, you cataloge the new data set using the fully > qualified DSN but replace the V00 with whatever version you like. The new > data set will become a GDS in place and at the place of the V00 GDS. This > new GDS will be treated as any other GDS, i.e. aged and eventually rolled > off. > > > I don't see practical use for this. > > > -- > Peter Hunkeler > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN >
Vnn came in very handy when transferring data to a new location when a business unit was spun off to another company. Copies of catalogs were sent to the other data center. Historic generational data was FTPed to the remote site to fully qualified "V01" versions, saving shipping and copying of tapes. The business applications could refer to relative GDG and find the data cataloged to their own tape volsers. This was several years and two employers ago, so the specific details have gotten a bit fuzzy. I just know both parties involved were quite satisfied, and it was a unique learning experience crafting that solution. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
