View previous topic :: View next topic
|
Author |
Message |
smita V
New User
Joined: 05 Nov 2007 Posts: 11 Location: hyderabad
|
|
|
|
Hi,
I want to know the how the limit and retention period for GDG datasets works in relation to each other.
I am assuming that by retension period we are meaning the numbers of days each GDG version of a particular cluster will be available and Limit as the number of GDG versions that we can have for max. Correct me if I am wrong.
If I am keeping the Limit as 3 and Retension period as 10 days using FOR parameter while defining a cluster and creating a new version each day.
Then on 4th day will the fourth generation will be created since the limit is 3? and if it happens what will happen to the first version of the GDG, the retention period of which is not met on 4th day.
Iam using SCRATCH option while defining the cluster.
Thanks,
Smita |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
1) I assume that by CLUSTER that you really mean GDG base
2) I also assume that you mean to say generations rather than versions. Generations and versions are both valid terms in GDG parlance, but have totally different meanings
What happend to gen 0001 when 0004 is created - well to be real picky this is a site specific question as what happens to gen 0001 will depend on how your storage people have set up the SMS environment.
They may have set it up to honor your 10 day retention by retaining the deleted gens in ROLLED OFF status, or they may have set it up to ignore user supplied retention (I always do )
Also there may be backups available which will honour the 10 day retention of each generation. Either that or actually try it yourself and see what happens.
The very best bet is go talk to your storage people to get the info that you require. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
Trying to take the exapt's legacy little more ahead -
Quote: |
I am assuming that by retension period we are meaning the numbers of days each GDG version of a particular cluster will be available and Limit as the number of GDG versions that we can have for max. Correct me if I am wrong. |
Term "Retention period" is not limited to GDGs only, this is equally applicable to a sequential data set, a PDS, or a VSAM data. The MGMTCLAS parameter provides the management class to be used for a sequential data set, a PDS, or a VSAM data set that you are creating. And yes given an individual GDG, it has all the qualities of an QSAM.
Quote: |
Then on 4th day will the fourth generation will be created since the limit is 3? and if it happens what will happen to the first version of the GDG, the retention period of which is not met on 4th day. |
This is not the concept on which GDGs were build up, they say, if limit is "3" then at a given instant there will be 3-different generations (Expat sir, I recall something.. ) in the catalog, if on "4th" day a new generation forces to come in existance the most old GDG has "to die little younger"; alas, they are GDGs..& here retention period is not the enemy. Instead if 4th generation will be created on 11th day then very first GDG would be found "migrated"; this migration is because the retention period limit of "10 days". |
|
Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006 Posts: 1702 Location: Australia
|
|
|
|
Hi,
usually GDG's are rolled off when the max limit has been reached and the expiry date has not passed, the job creating the new GDG will normally throw up a message of the GDG that was not able to be scratched.
As far as the GDG would be found to be migrated is up to the MGMTCLAS and nothing to do with the retention period.
Gerry |
|
Back to top |
|
|
|