Explanation
The system issues this message under either one
of the following conditions:
- The OPEN tape mount verification function, detected a RACF® volume conflict with the volume
being opened; the system can not use the volume.
- The end of volume (EOV) tape mount verification function, detected
a RACF volume set conflict
(1) between the current volume and the previous volume or (2) on the
current volume. In either case, the system cannot use the current
volume.
A RACHECK macro is issued for tape volumes that are write
enabled, and not file protected. An error occurred while the system
was processing the scratch tape volume for input or output in either
OPEN or EOV.
- Reason Code
- Explanation
- 1
- OPEN processing found either one of the following conditions to
be true:
- PROTECT is specified for a tape volume that is already RACF protected.
- An open was issued for a RACF protected
tape volume, but the caller was not authorized.
- 2
- The EOV processing of a concatenated tape volume encountered either
one of the following conditions:
- PROTECT is specified for a tape volume that is already RACF protected.
- At EOV, the user is not authorized to use the data set on the
new volume.
- 3
- During EOV processing of a tape volume (1) for output that was
not concatenated, and (2) the previous volume was not RACF defined, the system encountered either
one of the following conditions:
- The RACF definitions are
inconsistent. The system is processing a previously allocated tape
volume for output. One of two conditions may exist. The first volume
is not RACF defined while the
current volume is defined as such or the first volume was previously RACF defined, but currently is
not defined as such.
- At EOV, the caller is not authorized to use the new tape volume.
- 4
- During EOV processing of a tape volume (1) for output that was
not concatenated, and (2) the previous volume was RACF defined, the system encountered one of
the following conditions:
- PROTECT is specified for a tape volume that is already RACF protected.
- The RACF definitions are
inconsistent. The system is processing a previously allocated tape
volume for output. The current volume being processed at EOV is
defined to RACF, but this current
volume is not a part of the same RACF volume
set as the previous volume.
In the message text:
- rsnc
- The reason code.
- ser
- The volume serial number.
- dev
- The device number.
- jjj
- The jobname.
- sss
- The stepname.
System action
The system issues messages IEC502E and IEC501A.
These messages request that the operator mount a new scratch volume.
Operator response
If PROTECT was specified, either mount a scratch
volume that is not RACF protected
or remove the PROTECT specification. If the user is not RACF authorized to use the volume, mount a scratch
tape volume that is not defined to RACF.
If
message IEC089I contains a reason code of either 3 or 4 you can take
following additional steps:
- If the reason code is 3 and the current volume is defined to a RACF volume set, but the previous
volume was not defined to a RACF volume
set mount a scratch tape volume that is not defined to RACF. If you want RACF protection for the dataset being created,
the volumes must be manually defined to the same RACF volume set at a later time.
- If the reason code is 4 and the current volume and the previous
volume are defined to different RACF volume
sets then you have two choices. You can make sure that either (1)
the scratch tape volumes are defined to the same RACF volume set or (2) none of the volumes are
defined.
Source
Module