How to validate the currect generation of GDG reached max no

palas_08 · New User Joined: 26 Feb 2007 Posts: 9 Location: kolkatta

hi,

GDG name : xx1.xap.temp.tran

Limit : 5

How to validate the currect generation of GDG reached max no
i.e. current generattion of GDG is the 5 th generation ?

murmohk1 · Posted: Fri Aug 03, 2007 3:26 pm

Palas,

If the # of existing generations are 5 or more.......

palas_08 · New User Joined: 26 Feb 2007 Posts: 9 Location: kolkatta

hi,

limit can be max 255.

Generally we are giving limit when we are creating gdg.

I want to say that limit.

----------------------------------------------------------------------------------
Regards
Palas

shankar.v · Posted: Fri Aug 03, 2007 4:06 pm

If LIMIT=5 means, the maximum available generations in catalog are -4, -3, -2, -1 and 0.

Run a JSCAN(JOB SCAN) batch job to check that whether -4 is cataloged or not for the JCL code as the following one.

palas_08 · New User Joined: 26 Feb 2007 Posts: 9 Location: kolkatta

hi,

max limit can be variable .
max limit can be 5,6,7 ,8
that u don't know properly .

Regards
palas

shankar.v · Posted: Fri Aug 03, 2007 7:07 pm

If LIMIT=N means, the maximum available generations in catalog are -(N-1), -(N-2), -(N-3), -(N-4), . . . . . . . -4, -3, -2, -1 and 0.

Run a JSCAN(JOB SCAN) batch job to check that whether -(N-1) is cataloged or not for the JCL code generated by the following one.

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi Palas,

If i understood u correctly

we dont have any way to (as per my knoweldge) to find out that it has reached to it limit and now its will revolve back to generation zero.

This scnarion becomes more complex when we already have 5 version and our job creates new one so it drops the oldest generation. So if we need to keep more version or more backups we copy the current GDG into date qualified files.

Correct me if i lack somthing

dick scherrer · Posted: Fri Aug 03, 2007 7:46 pm

Hello,

It is not the design of GDG processing to reach the limit and start over.

As new +1 versions are created, the generation increases. When the limit is reached, the early generations are "rolled off", retaining the most current "limit" generations. It is very likely that as processing continues, the generations in the catalog will be far from the 1st-5th generations. Even though the generations increase, they are still processed using (0), (-1), etc up to (-4).