MVSFORUMS.com

[prabhutp]

My query is:
A production job got abended with JCL error in a step with the error message 'Dataset Reservation Error'.

I searched if the dataset used in this step was being accessed by another job or proc at that time. But could not find the reason for this??

is it something related with the system catalog backups??

Any help in this regard will be appreciated.

Thanks in advance!!!
_________________
tp

[expat]

That is a new message for me, so perhaps you have a software package that will cancel any jobs that are waiting for non available datasets.

Please post your output showing this message, along with any message ID that is shown.
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

[Mervyn]

I just had one of these:

[code:1:244b6cb449]
Item ==> * MVS/QuickRef 6.5 *
Command ==>
IEF211I DEMCG04 STEP010 A CSR5FIL1 - DATA SET RESERVATION UNSUCCESSFUL
------------------------------------------- V=IBM P=Z/OS SYSTEM MSGS R=V1R7 I=IEF211I ---
********************* Text Below Copyright (c) 2007, IBM *********************

IEF211I jobname ^procstep] stepname ddname^+ xxx] - DATA SET RESERVATION
UNSUCCESSFUL

Explanation: The system could not reserve a data set for a job. The type
of data set requested and the problem are as follows:

o The DD statement requested a non-VIO, temporary, direct access data
set. The data set name is the same as an existing system-generated
data set name.

o The DD statement specified an alias name. After locating the real data
set name in a catalog, the system found that the data set is already
reserved by another user.

o The DD statement requested a generation of a generation data group
(GDG). After locating the catalog-generated name for the generation,
the system found that the data set was already reserved by another
user.

o The DD statement requested all levels of a GDG. When checking the
individual levels, the system found that one of the levels is already
reserved by another user.

In the message text:

jobname The name of the job.

procstep The name of the step in the procedure.

stepname The name of the job step.

ddname The name of the DD statement.

+ xxx The relative position of a data set within a concatenation of
data sets, including all data sets implicitly concatenated
(through GDG ALL or OPTCD=B requests). See z/OS MVS JCL User's
Guide for more information on GDG ALL or OPTCD=B requests when
used within a set of concatenated data sets. The first data set
of a concatenation would be +000, but the value +000 is never
shown.

System Action: The system ends the job to avoid impacting the
availability of critical system resources.

Application Programmer Response: Change the DD statement. Resubmit the
job for processing.

System Programmer Response: If the system programmer wants to allow jobs
to wait for the requested resource rather than to fail, add the following
statement into the ALLOCxx member of SYS1.PARMLIB: SDSN_WAIT
WAITALLOC(YES). See the z/OS MVS Initialization and Tuning Reference,
ALLOCxx, SDSN_WAIT for additional information on WAITALLOC(^NO
_________________
The day you stop learning the dinosaur becomes extinct

[expat]

Well, that's a new one for me.

Thanks for the heads up on the data Merv
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

[Mervyn]

It's pretty new for me, too.
_________________
The day you stop learning the dinosaur becomes extinct

[prabhutp]

Mervyn, that was really helpful..Thank u

actually, that step was trying to delete all the versions of a GDG created for the day.

From the JESYSMSG of the job, the relative position of the dataset was given as +137.

If possible, also let me know how to locate the real data set name in a catalog??

also, we have a member ALLOC00 in SYS1.PARMLIB: with the statement SDSN_WAIT WAITALLOC(YES). but still the job has abended with jcl error.

thanks in advance
_________________
tp