|
View previous topic :: View next topic
|
| Author |
Message |
shanth555
New User
Joined: 17 Aug 2012
Posts: 35
Location: India
|
|
|
|
Hi All,
I have a base file and it contains 14 GDG versions. The GDG versions are creating daily basis, since the limit is 14 we are losing the before 14 days files.
Note: i dont want to increase the GDG limt.
Whenever the JCL runs, it needs check the GDG limit. if its 14 we need to NDM the oldest file ( Means the first file in GDG) to DB.
Is there any way to check the GDG limit in JCL?
i would be thankful for your help.
Regards,
Iniyavan |
|
| Back to top |
|
 |
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
GDG Generations Vs Versions?
Ok. IDCAMS LISTCAT on GDG Base. |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
Again, if GDG base's LIMIT is 14, LIMIT from LISTCAT is always 14 only.
You may need to check ASSOCIATIONS information from LISTCAT listing, to know the number of active generations as well as the oldest generation DS name. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
I wonder why people like to make things more difficult that they should be.
for what reason You don' t just NDM the file as soon as it is created and let the older generations vaporize at rolloff time ??? |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| enrico-sorichetti wrote: |
I wonder why people like to make things more difficult that they should be.
for what reason You don' t just NDM the file as soon as it is created and let the older generations vaporize at rolloff time ??? |
Thinking is a tough business business under the sun, perhaps, that's why very few people indulge in it.
shanth555 - The idea from Enrico seems best for what you've described. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Your process sounds like it will be problematic.
If the process runs one day and there are 14 generations the oldest would be "sent". If the process is run the next day and nothing has changed, the oldest will be sent again. Is this ok? What is to prevent this?
Why is the data not sent until it is the oldest?
I do not understand what this is to accomplish. The places i support typically want the most current info in the database. They do not want it to "age" before loading.
Possibly i am missing something. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
even if the approach is clumsy I guess that the TS wants
( before the rest of the <procedure> runs )
<RUN WHATEVER PROCESS> on the <gdg_base_name>(-13) if it exists |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
You could listcat the gdg, then strip the names from that result. Run that through another listcat with a count(14). Based on that result, run the NDM with the -13.
I would add a step to delete the -13 so that you don't end the same one multiple times.
Not the craziest requirement I've ever heard. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
But still crazy though not craziest !  |
|
| Back to top |
|
|
|
|
