To Check the previously ran GDG no.

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi,
I have a requirement in which I have to:
1.) Have a check where we have to check if a new GDG generation is created or not. If not we have to send a empty file.
If yes we have to carry on with the business processing.

Is there a way out for how to check whether a new GDG has been created since the last run ??

Thanks.

superk · Posted: Tue May 03, 2011 6:43 am

Keep a logfile, and update it on the last run. For the current run, check against the logfile, and see if they match or not. Or, use it to see if there is more than one generation in between the runs.

Nic Clouston · Posted: Tue May 03, 2011 10:59 am

Or create an empty GDG dataset at start of cycle which will then be filled with data - if data exists for it. When the send job comes along it will find the GDG with or without data.

Phrzby Phil · Posted: Tue May 03, 2011 5:44 pm

Run IDCAMS LISTCAT report to a file and analyze it programatically.

Escapa · Posted: Tue May 03, 2011 6:22 pm

Or maintain control flag... set the flag when gdg generation is created...

Before processing your business logic check for flag if set do business process and reset the flag....
Else send empty file....

expat · Posted: Tue May 03, 2011 6:31 pm

Why not use a fixed file name and then check on the contents of a name that will not change.

If the file is populated then create the GDS from that file, else send that empty file.

daveporcelan · Posted: Tue May 03, 2011 8:41 pm

I vote for expat's solution.

Very strait forward and easy to implement.

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi,
Thanks All for the suggestions...
Expat : I see that could be a easier one...Could you explain a littele more to help me with the implementation part...

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi Sambhaji,
Could you please explain, how can we implement this....

Thanks.

superk · Posted: Wed May 04, 2011 4:37 am

Saurabh, do you think that maybe you could explain the situation a little more clearly, what happens betwen runs that causes a problem? Why do you send an empty file and not the one with actual data in it?

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi,
Sure I would like to explain more….

We have a job which runs daily, now there is something happening on our source system which causes the Input file to be irregular , i.e it won't come on daily basis and might come irregularly. So we plan to have a check on the GDG generation, i.e if a new GDG generation is created by the source, we would do the processing or else send an empty file.

I hope this clarifies.

Thanks.

expat · Posted: Wed May 04, 2011 12:50 pm

Has your shop not heard of dataset triggering, although a GDS is probably not the best type of dataset to use for this.

When a dataset is created, the scheduling software can submit a job for processing that dataset.

vasanthz · Posted: Wed May 04, 2011 2:30 pm

I agree with Expat,
CA7(I strongly believe other schedulers also have this) tracks the creation of GDG generations once the GDG is defined on CA7. And CA7 can be made to trigger a job when a new GDG generation is created.

kratos86 · Posted: Wed May 04, 2011 4:11 pm

If you want it to be simple follow this procedure,

1. Delete all the GDG generations after the file is sent
2. Create an empty GDG generation.

Next day when the process starts
Even though the file is not received we have an empty GDG entry and would be sending the empty file. If the file is received we anyways send the latest generation.

This is always a safe handling. In case you have restriction to use only GDG files.

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi,
I do agree with EXPAT...
But not sure of whether the Schedular thing is applicable in our case as while scheduling a job I am not getting any such option in our interface.

kratos86: Nice Simple solution, Nice logic. BUT I really CANNOT Either Create or DELETE the Source GDG, So won't be able to implement that.

I would relly love to implement EXPAT's earlier solution

kratos86 · Posted: Thu May 05, 2011 8:19 am

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi kratos86 :

I did this

kratos86 · Posted: Thu May 05, 2011 10:07 am

Saurabh Pune · New User Joined: 26 May 2009 Posts: 23 Location: USA

Hi,

kratos86 · Posted: Thu May 05, 2011 12:03 pm

Nic Clouston · Posted: Thu May 05, 2011 3:48 pm

Or change the job that creates the GDG by adding a step that will copy the new dataset to another dataset (not a GDS) which your job can empty after transmission.

And you should be able to change a feeder job as part of the project.