TRICKY GDG QUERY

useit · Active User Joined: 05 Oct 2006 Posts: 152

hi,
is there any way we can find out what was the last generation(generation number). and we can start reading from the next generation number?

say example

before my execution (first run) of job gdg had 2 generation.

g001
g002

in the next run say other jobs created 2 more generations.

g001
g002
g003
g004

so in my job i just have to process only g003, g004, since g001 and g002 i have proceseed before the first run.

i, e
some point of time i have to find out what was the latest generation number. and next time onwards i have to process from the next generation number onwards.

note: i cant delete the genearation numbers.

i would be really thankful to you if you can help me on this.

Regds,
useit

Escapa · Posted: Tue Aug 30, 2011 3:21 pm

I would have done like this...

Create two GDG bases.. like

HLQ.GBASE.MAIN and
HLQ.GBASE.TEMP

Whenever your job adds new generation to MAIN would have added to TEMP also...

While you want to process generation... process only generations from TEMP and delete all once processing is done.

useit · Active User Joined: 05 Oct 2006 Posts: 152

escapa,

i dont think your solution would work for me.

in my case.

my gdg file creation jobs run at 4pm, 5pm, 6pm,7pm

and my new file creation job run can vary from 4pm to 6pm

suppose if my new file creation job runs at 5.30. then whatever the gdgs created before 5.30 shouldnt be considered
for processing.(should consider only the generation created from 6pm, 7pm jobs)

if it runs at 6.30pm.(then process only generation created by 7pm job)

please help me regarding the same.

Escapa · Posted: Tue Aug 30, 2011 4:28 pm

Clear as mud.... + confusing

useit · Active User Joined: 05 Oct 2006 Posts: 152

hi,

sorry for bothering you again

actually there is one more update job which would run at around 8.30.

here i have to see which all generations needs to be processed.

suppose if new file creation jobs run at 4.30. my 8.30 update job should use(generation created by 5pm, 6pm, 7pm job)

Regds,
useit

superk · Posted: Tue Aug 30, 2011 4:47 pm

I've used two approaches in the past:

- Maintain a logfile. When you use a generation, log it to the log file. On the next batch cycle, check the current existing generations against the log file. If you find a new one, process it, add it to the log file, and continue the processing cycles.

- Rename the used GDG. I'd rename the version number (V00) to (V01) as the indicator that it has been processed. This can really be handy if you have a need to re-process an older generation. Just rename it back to (V00) and let the batch process pick it up on the next cycle.

Robert Sample · Posted: Tue Aug 30, 2011 4:52 pm

Either set up individual files for each time the job creating the file can run, or have your job process AND DELETE all members of the GDG . If you need to retain data, you would need a second generation data group defined to retain the data.