I experimented with this a while back and I believe the results bore out what you stated.
As I remember, the displaced GDS ended up cataloged though not as a GDS. ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Peter Hunkeler <[email protected]> Sent: Tuesday, November 17, 2015 4:23 PM To: [email protected] Subject: AW: Re: Fastest way to read OLDEST GDG entry > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
