View previous topic :: View next topic
|
Author |
Message |
anuradha
Active User
Joined: 06 Jan 2004 Posts: 247 Location: Hyderabad
|
|
|
|
HI ,
I HAD A DOUBT ON GDG VERSION FROM SO MANY DAYS.NO ONE IS ABLE TO CLEAR MY DOUBT.MY DOUBT IS HOW CAN WE INCREMENT THE VERSION OF A GDG.PLEASE CLARIFY THIS.
THANKS AND REGARDS
ANURADHA |
|
Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003 Posts: 1592
|
|
|
|
Hi ANURADHA,
When you say "version" I'm assuming you mean the Vnn portion of the
GnnnnVnn extension of the full GDG name.
To change the V00 to V01 you must create a new version of the dataset and code the full DSN using the same Gnnnn, but changing the Vnn. When this is done the old (V00) version is deleted and replaced by the new (V01) version. The new version will assume the same position in the GDG as the original version.
Only pne version of a generation is allowed to exist at any given time.
HTH, Jack. |
|
Back to top |
|
|
anuradha
Active User
Joined: 06 Jan 2004 Posts: 247 Location: Hyderabad
|
|
|
|
hi jack,
Still i had some doubt on that.If i need to keep the old version details where can I keep.I mean to ask if I require to maintain all details how can I . Even though we have 99 versions we can maintain only one version at a time for a gdg .Then wats the fun of having 99 versions .please clarify my doubt.
THANKS AND REGARDS
ANURADHA |
|
Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003 Posts: 1592
|
|
|
|
Hi ANURADHA,
1 - I guess you can copy it first to an "error stuff" dataset. Don't blame me, I didn't design it.
2 - Yes, the idea is (I guess) that the Version is used for correcting errors in the previous version and replacing it with the clean version. That means that you're limited to 99 mistakes. 8)
3 - Who said dataprocessing was fun?
Regards, Jack. |
|
Back to top |
|
|
anuradha
Active User
Joined: 06 Jan 2004 Posts: 247 Location: Hyderabad
|
|
|
|
hi ,
thanks a lot jack.hey,i am not blaming any one.how can i? i myself is a beginner in this. but i am very sincere learner in this.so out of curiosity iam asking all this doubts.anyway thanku again for clearing JACK.
THANKS AND REGARDS
ANURADHA |
|
Back to top |
|
|
Sharan
New User
Joined: 22 Dec 2003 Posts: 6 Location: Banaglore
|
|
|
|
Hi Jack and Anuradha,
I just have a couple more questions to this thread of conversation.
Now let us assume there are 5 versions of a GDG that are created ,the final one being FILE1.G0005V00. Now I wish to change my version from 00 to 01 to the last version, changing which the last/latest version would be FILE1.G0005V01.If this is the case what would be the version of the next subsequent GDG that is created? would it be FILE1.G0006V01 or FILE1.G0006V00.
Lets assume that while creating a GDG base the attributes were NOSCRATCH and NOEMPTY ,so when the limit is reached the oldest generation is Uncataloged and not deleted.Now if I wish to access the uncataloged GDG Memeber would it be possible for me, if I explicitly mention its absolute number.
Thanks in advance,
Sharan |
|
Back to top |
|
|
sandip_datta
Active User
Joined: 02 Dec 2003 Posts: 150 Location: Tokyo, Japan
|
|
|
|
I think using CYC(+) we can increament the GDG version;at least in our shop we do this in this way. It would also keep the older versions. no of versions depend on how the GDG is defined ?
Regards,
Sandip. |
|
Back to top |
|
|
anuradha
Active User
Joined: 06 Jan 2004 Posts: 247 Location: Hyderabad
|
|
|
|
hi sharan,
if iam not wrong, you will get FILE1.G0006V00 when you create next subsequent gdg.you can change the version of this generation only by hardcoding it.so for one generation there are 99 versions(limited to 99 mistakes ).
Thanks,
Anu |
|
Back to top |
|
|
Sharan
New User
Joined: 22 Dec 2003 Posts: 6 Location: Banaglore
|
|
|
|
Hi,
Thanks for the answer, but I am not sure about the syntax or how to use CYC(+). It would be great if you could illustrate CYC(+) with an example. I was'nt able to find any information about CYC in the "quick refernce" either.Does this mean that CYC(+) is shop specific????
Thanks,
Sharan |
|
Back to top |
|
|
gowtham_srgp
New User
Joined: 09 Jun 2005 Posts: 38
|
|
|
|
anuradha wrote: |
HI ,
I HAD A DOUBT ON GDG VERSION FROM SO MANY DAYS.NO ONE IS ABLE TO CLEAR MY DOUBT.MY DOUBT IS HOW CAN WE INCREMENT THE VERSION OF A GDG.PLEASE CLARIFY THIS.
THANKS AND REGARDS
ANURADHA |
hai anuradha. i hope that this late mail do help you. you need not change the version of the gdg on your own. once we've reached the g9999voo, i.e the maximum limit for the gdg, the version for the first generation i.e for g0001v00 will be incremented to g0001v01. this is the automatic process. also do remeber that we can've at a time only 255 generation cataloged.
even if you need to change the version no for the gdg, you can perform as one of our fellow team member suggested. just override the version number to v01....
corrections welcomed......
gowtham |
|
Back to top |
|
|
senti
New User
Joined: 18 Aug 2005 Posts: 19
|
|
|
|
Hey Goutham, I have few questions,
- As u said, you can have only upto 255 gdgs.So, After gen# G9999V00 you will not find gen# G0001V00 to change its version number.So not sure how the version number will be automatically changed.
- When i tested, i saw that u get G0001V00 after G9999V00 ( as expected tho )
Please refer to comments by 'mmwife' which i think is correct. |
|
Back to top |
|
|
die7nadal
Active User
Joined: 23 Mar 2005 Posts: 156
|
|
|
|
Sharan,
Quote: |
Lets assume that while creating a GDG base the attributes were NOSCRATCH and NOEMPTY ,so when the limit is reached the oldest generation is Uncataloged and not deleted.Now if I wish to access the uncataloged GDG Memeber would it be possible for me, if I explicitly mention its absolute number.
|
Yes, u can access this uncatalogued GDS by using its absolute name and by mentioning its Volume serial number. |
|
Back to top |
|
|
ashwinreddy
Active User
Joined: 16 Sep 2004 Posts: 106 Location: Hyderabad
|
|
|
|
Hi all,
I have some doubts after all the coversation on version.
As Jack had sent that we can change the version by changing V00 to V01 with full DSN name but when we do this we can increase the version of only one generation.
Eg: My GDG name is JLL.ALLOC.PATTERN.BACKUP
and if i want to increase the version i can do JLL.ALLOC.PATTERN.BACKUP.G0001V00 to JLL.ALLOC.PATTERN.BACKUP.G0001V01.
but i may have a lot of generations in a single version.
Do i have to change them seperatly.
I feel when the limit of the gererations is reached i.e 9999 the version is automatically increased
This happens when we give GDG parameters as EMPTY and SCARCH
and go on increasing the generations until you reach 9999 limit.
but i never faced any situtations of increasing the version and i never seen a GDG with Version V01
This is only a guess and i am not confident.
If any corrections welcome.
Thanks & Regards
Ashwin |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
Ashwin, take a look at the "z/OS V1R6.0 DFSMS: Using Data Sets" manual, Chapter 29 "3.10 Chapter 29. Processing Generation Data Groups":
publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dgt2d430/CCONTENTS
This is a copy of the text:
Quote: |
3.10.2 Absolute Generation and Version Numbers
An absolute generation and version number is used to identify a specific generation of a GDG. The generation and version numbers are in the form GxxxxVyy, where xxxx is an unsigned 4-digit decimal generation number (0001 through 9999) and yy is an unsigned 2-digit decimal version number (00 through 99). For example:
A.B.C.G0001V00 is generation data set 1, version 0, in generation data group A.B.C.
A.B.C.G0009V01 is generation data set 9, version 1, in generation data group A.B.C.
The number of generations and versions is limited by the number of digits in the absolute generation name; that is, there can be 9,999 generations. Each generation can have 100 versions.
The system automatically maintains the generation number. The number of generations kept depends on the size of the generation index. For example, if the size of the generation index permits ten entries, the ten latest generations can be maintained in the GDG.
The version number lets you perform normal data set operations without disrupting the management of the GDG. For example, if you want to update the second generation in a 3-generation group, replace generation 2, version 0, with generation 2, version 1. Only one version is kept for each generation.
You can catalog a generation using either absolute or relative numbers. When a generation is cataloged, a generation and version number is placed as a low-level entry in the GDG. To catalog a version number other than V00, you must use an absolute generation and version number.
You can catalog a new version of a specific generation automatically by specifying the old generation number along with a new version number. For example, if generation A.B.C.G0005V00 is cataloged and you now create and catalog A.B.C.G0005V01, the new entry is cataloged in the location previously occupied by A.B.C.G0005V00. The old entry is removed from the catalog, to make room for the newer version, and may or may not be scratched depending on what limit processing options are specified for the GDG base. For system-managed data sets, if scratch is specified, the older version is scratched from the volume. If noscratch is specified, or if the attempt to scratch the DSCB fails, the older version is not scratched and the generation data sets is recataloged as a non-VSAM data set with the GnnnnVnn name not associated with the GDG base. For non-system-managed data sets, the older version is also governed by the GDG base limit processing options. If noscratch is specified for the base, the older GDS version is not scratched. To scratch the old version and make its space available for reallocation, include a DD statement, describing the data set to be deleted, with DISP=(OLD,DELETE) when the data set is to be replaced by the new version.
|
|
|
Back to top |
|
|
|