>From a vague memory, the Vnn was to be used if you had to do a "file fix" type 
>operation and recreate a specific generation. The system did not help with a 
>way to do this, but if you did it yourself by deleting the V00 version and the 
>cataloguing a V01 (and now-a-days do a ROLLIN), you could access the V01 
>version using the same relative generation. Or you could do something like:

//FIXFILE EXEC PGM=FILEFIX
//INPUT DD DSN=GDG.G0127V00,DISP=(OLD,DELETE,KEEP)
//OUTPUT DD DSN=GDG.G0127V01,DISP=(NEW,CATLG,DELETE),
// ... OTHER PARAMETERS
//*

then the GDG.G0127V01 would replce GDG.G0127V00 as GDG(-n). And it would be 
documented that this was a different version, in records such as SMF. I don't 
remember anybody ever doing it. Personally, I sort of like the UNIX way where I 
put the ISO date & time (ISO 8601 / RFC 3339  format) as the last node. Wish I 
had a simplier way to do it. Note that it is exactly difficult. Just "fiddly" 
to me.

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
[email protected] * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:[email protected]] On Behalf Of Roberts, John J
> Sent: Monday, June 11, 2012 2:59 PM
> To: [email protected]
> Subject: Re: Weird thought on misuse of a GDG.
> 
> > But in today's world, without SCRATCH in the definition, 
> the oldest GDG does not get scratched. It gets "rolled off" 
> the GDG base and becomes a "normal" cataloged dataset entry. 
> So it stays in the catalog, and can be referenced by absolute 
> name. I wonder if this would ever be of some use to anyone.
>  
> What happens when you hit G9999V00?  Does it wrap to G0000V00 
> or G0001V00?  If so, you could be attempting to catalog a 
> name that already exists.  Not a problem for most generation 
> datasets, but I would guess that someone would trip over this 
> someday. Especially if z/OS lasts another 50 years ;-)
> 
> Also, what is the significance of the V00 part of the 
> qualifier?  I was always led to believe that it was a vestige 
> of something that was never implemented.
> 
> ----------------------------------------------------------------------
> 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

Reply via email to