I forgot to add, the reason would be that DSN(0) would never know which Version 
to pull in should there be more than one version.

That is why many shops want a different process for getting dates and times 
into data set names.

Lizette



>
>My understanding is that you would only have ONE verions number at any given 
>time.
>
>I have not seen a case where you would have G0001V00, and G0001V01 and 
>G0001V02.  Only the G0001V02 would be in the catalog.  Any other versions 
>would not.
>
>Though I could be wrong, but that is currently my understanding.  Version only 
>allows you to replace the current Gen Number without losing the oldest GDG 
>(due to roll off).
>
>
>Lizette
>
>
>-----Original Message-----
>>From: J R <[email protected]>
>>Sent: Jan 20, 2009 1:49 PM
>>To: [email protected]
>>Subject: Re: GDG Question
>>
>>> The Version numbers are ascending (00 to 99). I have not known 
>>> of a case where you would create a descending version (99 to 00).  
>> 
>> 
>>Well, I can't imagine needing to create up to 99 replacement versions either. 
>> 
>> 
>>However, if I were to use this feature, I could well imagine making 
>>the version number meaningful.  Examples might be day-of-week, 
>>month-of-year, etc.  In such a scenario they could well end up 
>>going backwards ... V06 (Friday) to V02 (Monday) maybe.  
>> 
>>So, the question stands:  May version numbers be created out 
>>of sequence and randomly?  
>> 
>> 
>>> Date: Tue, 20 Jan 2009 13:29:56 -0500
>>> From: [email protected]
>>> Subject: Re: GDG Question
>>> To: [email protected]
>>> 
>>> The Version numbers are ascending (00 to 99). I have not known of a case 
>>> where you would create a descending version (99 to 00).
>>> 
>>> Lizette
>>> 
>>> 
>>> 
>>> >
>>> >> The Vyy is the Version Number ... (allowing you to replace it up to 99 
>>> >> times). 
>>> > 
>>> > 
>>> >Are you saying that replacement versions may only be created in ascending 
>>> >sequence? 
>>> > 
>>> >
>>> >> 
>>> >> >So what your saying is the the LOCATE/CAMLIST macros (and others I 
>>> >> >suppose)
>>> >> >never even look at the Vxx part of the DSN.
>>> >> >Your usage of it is interesting, never thought of it myself, but lord 
>>> >> >knows
>>> >> >I could have used it!
>>> >> >
>>> >> >Thank You,
>>> >> 
>>> >> They look at and use it. It is just that when you catalog a GxxxxVyy 
>>> >> it will replace an existent GxxxxVyy entry. The Vyy is the Version 
>>> >> Number of the Gxxxx dataset (allowing you to replace it up to 99 
>>> >> times). There can be only one version of each generation. To do this 
>>> >> you must use an Absolute Dataset Name (GDGBASE.GxxxxVyy) not the 
>>> >> GDGBASE(x) Relative type name.
>>> >> 
>> 
>> 
>> 
>> 
>> 
>>_________________________________________________________________
>>Windows Liveā„¢ HotmailĀ®: Chat. Store. Share. Do more with mail. 
>>http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_hm_justgotbetter_explore_012009
>>----------------------------------------------------------------------
>>For IBM-MAIN subscribe / signoff / archive access instructions,
>>send email to [email protected] with the message: GET IBM-MAIN INFO
>>Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to