Explanation
The dynamic allocation protection key was specified
or the PROTECT keyword was coded on the DD statement. The request
did not meet the requirements as follows:
- If PROTECT was specified for a DASD data set, the data set must
be a new, non-temporary data set. That is, the status of the data
set is ‘NEW’ or ‘MOD’ treated as ‘NEW’.
Normal and abnormal dispositions if specified are other then DELETE,
and the data set has a non-temporary data set name.
- If PROTECT was specified for a tape volume, the tape label specification
must be SL, AL, SUL, AUL, or NSL. Both the file sequence count and
volume sequence count must be set to one (except for NSL), or must
default to one, and the tape volume must have a volume use attribute
of PRIVATE. If the file sequence count or the volume sequence count
is greater than one, the RACF® TAPEDSN option must be active
for successful processing.
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
Programmer response
Correct the data set or volume description
on the DD statement. Resubmit the job.
Source
Module
Routing code
Descriptor code