I have a scenario ,where one of our jobs is failing with "Dataset reservation Unsuccessful" .
1. Job1 creates a file ,which triggers another job say Job2.
2. This Job2 is submitted with the same name Job1.
3. Job2 is getting failed with "Dataset reservation unsuccessful" when it trying to check if the file created in the previous Job1 has any data or not.
4. This file is nothing but a GDG version.
5. Job1 creates a GDG version and Job2 checks if the GDG base has any data or not.
6. Job1 using GDG version with DISP=(new,cat,del) & DISP=SHR
whereas Job2 is using DISP=OLD.
Joined: 22 Apr 2006 Posts: 6258 Location: Mumbai, India
I agree with Enrico, however look for the explanation for IEF211I and see if something matchs for your scenario.
This file is nothing but a GDG version.
Are you really talking about "version" and not "generation". If yes and you've allocated something like HLQ.SLQ.G0001V01 and your job has HLQ.SLQ(+1), possibly you might run in to this error: http://ibmmainframes.com/post-60435.html
Thanks Guys for responding. And apologies for being so vague in explaining.Let me try to explain what I am encountering.
We have a job which runs daily in Production.From last 1 month this job is failing with "Dataset reservation Unsuccessful" (not everyday though).
This job creates a file ( next generation of a GDG) .As soon as the next generation is created ,another job is triggered which is submitted with same name as the triggering job. The triggered job gets failed in the first step itself where it is checking if the base GDG has any data or not.
Now , the issue is we are not sure as in why the jobs are failing with this error,because both the jobs are submitted with the same name .Unless and until first job is completed , eventhough the second job is triggered , it won't start executing until first one is completed , so there should not be any dataset contention issue.
Joined: 06 Jun 2008 Posts: 8319 Location: Dubuque, Iowa, USA
Now , the issue is we are not sure as in why the jobs are failing with this error,because both the jobs are submitted with the same name
Depending upon your site, this may not prevent the two jobs from running at the same time. And if they run at the same time, the first job still has an ENQUEUE on the GDG base (assuming you used (+1) for your generation). You need to look at the start / stop times of the first and second jobs (and where each is running) to verify that they really are not running at the same time.
The restriction is that every job running on an LPAR have a unique name -- if your site is set up to allow batch jobs to run on more than one LPAR, then you can have more than one job with the same name running simultaneously.
If the start time of the second job is after the end time of the first job, then you have an issue which needs attention from IBM.