IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

GDG version number


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
PANDU1

New User


Joined: 16 Nov 2016
Posts: 7
Location: india

PostPosted: Sat Mar 04, 2017 8:28 pm
Reply with quote

HI All,

Could any one help with below question.

How edit/create GDG version files ending with current date instead of version number.

For example:
MYFILE.GDG.00V01 should replace with MYFILE.GDG.currentdate

Thanks in advance
Pandu.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 895
Location: The Universe

PostPosted: Sat Mar 04, 2017 10:33 pm
Reply with quote

You can't do this. All GDG data sets must end with .GnnnnVnn. Period. End of story.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Sat Mar 04, 2017 10:44 pm
Reply with quote

Well, there are several problems with your post.

The low-level qualifier (LLQ) that you specify is invalid. A generation data set's LLQ will be of the form GnnnnVmm, where nnnn, the generation number, varies from 0001 to 9999. A GDS is generally referred to by a relative generation number; the JCL might specify something like:
Code:
//OUT1    DD DSN=FOO.BAR(+1),DISP=(,CATLG,DELETE),...

where "(+1)" is interpreted "one greater than the highest existing generation". Thus, a given run of this job might find FOO.BAR.G0100V00 to be the highest existing generation and create FOO,BAR.G0101V00; the next run, of course, finding G0101V00, would create G0102V00. A GDS created in this way always has a version number (the "Vmm" part) of V00; only if the GDS is referred to with an absolute generation number (E.G., as FOO.BAR.G0102V01) will be the version number be different; this is often (but not invariably) done to indicate that the data set was recreated in a restart or rerun.

Now, given that z/OS provides this sophisticated mechanism, why do you want to replace it with a RYO naming scheme? This might be appropriate in a more primitive OS as Unix or Windows where GDGs are unavailable, but I do not see what you hope to gain from it in a mature environment such as z/OS provides. Please explain your reasoning, and we'll see if we can't come up with a realistic alternative.
Back to top
View user's profile Send private message
PANDU1

New User


Joined: 16 Nov 2016
Posts: 7
Location: india

PostPosted: Sat Mar 04, 2017 11:02 pm
Reply with quote

Thank you Steve and Akatsukami icon_biggrin.gif
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Sat Mar 04, 2017 11:06 pm
Reply with quote

FTR, I've moved this thread to the JCL & VSAM forum, which more appropriate than DB2.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts how to convert and use 1 bit hex-numb... COBOL Programming 10
No new posts Merge a variable number of records fr... DFSORT/ICETOOL 5
No new posts total number of bytes PL/I & Assembler 10
No new posts Chained RPL - How to get RRN number. JCL & VSAM 0
No new posts XMITIP Latest Version JCL & VSAM 2
Search our Forums:

Back to Top