We have installed a job in production.It is loaded onto the jobtrac and executed as soon as the GDG file is recieved from our upstream.The issue is we are receiving the files from our upstream in a gap of time interval i.e. in seconds. When we received the first file the job is loaded onto the jobtrac and starts executing in mean time we received 2nd file, as we are referring latest file generation in the job the job picked the 2nd file as latest generation and processed it. So the first file was not processed.
We spoke to our upstream to send each file in delay of 5-10 min but they are not making any changes. Could you please let me know how to handle this issue in my Jcl
Joined: 26 Apr 2004 Posts: 4650 Location: Raleigh, NC, USA
Probably not the best use of GDG's. If the processing order of the inbound datasets was really important, I'd ask the application that was creating them to somehow serialize them so my job would know the proper order.
Anyway, dealing with similar situations in the past, I always made the process work by not using the relative generation number for the GDG. I'd always keep a master log of all generations used, check the new generation against the log, verify that it was the next in sequence, then use it in the job by it's absolute generation (i.e. the GnnnnVnn number).
Now, I don't know a lot about JobTrac, but if it can trigger a job on the event of a catalog of a new generation, can it also pass on to that job through a variable WHAT that generation number was?