ARC0309I
TAPE VOLUME volser REJECTED, {VOLUME ALREADY CONTAINS VALID DFSMSHSM DATA | VOLUME RACF-PROTECTED BUT DOES NOT APPEAR IN DFSMSHSM.’S TAPE VOLUME SET | VOLUME IS A BACKUP VOLUME, MIGRATION VOLUME REQUIRED | VOLUME IS A MIGRATION VOLUME, BACKUP VOLUME REQUIRED | VOLUME IS A DUMP VOLUME, MIGRATION VOLUME REQUIRED | VOLUME IS A DUMP VOLUME, BACKUP VOLUME REQUIRED | VOLUME IS A BACKUP VOLUME, DUMP VOLUME REQUIRED | VOLUME IS A MIGRATION VOLUME, DUMP VOLUME REQUIRED | DUMP CLASS CONFLICT | VOLUME HAS ALREADY BEEN USED FOR OUTPUT ON ALLOCATED DEVICE | WORM MEDIA IS NOT VALID FOR THIS FUNCTION | TTOC TYPE CONFLICT }

Explanation

The DCB volume verification exit was invoked by OPEN or end-of-volume (EOV) processing for the tape volume whose volume serial number is volser. The tape volume is rejected by the DFSMShsm volume verification exit for one of the following reasons:
  • The tape volume mounted already contains valid DFSMShsm data.
  • The tape volume mounted is RACF-protected, but does not appear in DFSMShsm’s RACF® tape volume set of HSMHSM or DFHSMx (where x is the last nonblank character of the tape volume’s volser).
  • The tape volume mounted is defined to DFSMShsm as a backup volume and a migration volume is required.
  • The tape volume mounted is defined to DFSMShsm, as a migration volume and a backup volume is required.
  • The tape volume mounted is defined to DFSMShsm as a dump volume, but a migration volume is required.
  • The tape volume mounted is defined to DFSMShsm as a dump volume, but a backup volume is required.
  • The tape volume mounted is defined to DFSMShsm as a backup volume, but a dump volume is required.
  • The tape volume mounted is defined to DFSMShsm as a migration volume, but a dump volume is required.
  • The dump class to which the volume is currently assigned does not match the dump class to which it is dumped.
  • A volume is mounted for output on an allocated device after a previous mount for output during the processing of the same function.
  • The media which is mounted is WORM and this function is not supported for WORM.
  • The tape volume mounted is defined to DFSMShsm with TTOC type which does not match the current SETSYS EXTENDEDTTOC(Y|N) setting.

System action

A keep message is sent for the tape volume. The tape volume is rewound and unloaded by OPEN or EOV processing and a mount message is sent for another tape volume. If the SELECTVOLUME option is SPECIFIC, and it is OPEN processing, DFSMShsm attempts to select another tape volume already defined to DFSMShsm. If there are three consecutive specific volumes mounted and rejected with an ARC0309I message, the operator receives a nonspecific (PRIVAT) mount request. If it is EOV processing, DFSMShsm attempts to select another tape volume already defined to DFSMShsm without regard to the number of rejections occurring with an ARC0309I message for this mount. If DFSMShsm is able to select another tape volume, the operator receives a specific mount request. If DFSMShsm is unable to select another tape volume or the SELECTVOLUME option is SCRATCH, the operator receives a nonspecific (PRIVAT) mount request. If the message indicates that WORM media is not valid for this function then the system will end OPEN processing.

Operator response

The tape operator should respond to the specific mount request by mounting the requested tape volume on the requested tape drive.

The tape operator can respond to the nonspecific (PRIVAT) mount request by mounting a scratch tape or a tape volume already defined to DFSMShsm on the requested tape drive. If the tape operator mounts a scratch tape, the tape should not be RACF-protected by another user nor used previously for output by the DFSMShsm function issuing the message. If the tape operator mounts a tape volume already defined to DFSMShsm, the tape volume should not contain any valid DFSMShsm data (it should be empty) and should not be RACF-protected by another user. Also, the type of tape volume mounted (backup, migration, or dump) should be the same as the type of tape volume that encountered the EOV condition. To resolve a TTOC conflict, the tape operator can mount a tape volume with a compatible TTOC type.

Programmer response

The system programmer determines what valid DFSMShsm data already exists on the tape volume by entering the DFSMShsm space manager LIST command. For level 2 migration tape volumes and backup and SPILL tape volumes, issue the LIST command with the TTOC parameter. For dump volumes, issue the LIST command with the DUMPVOLUMES parameter.

If the message indicates the tape volume does not appear in one of DFSMShsm’s RACF tape volume sets, see z/OS DFSMShsm Implementation and Customization Guide topics "Authorizing and Protecting DFSMShsm Resources" and "Implementing DFSMShsm Tape Environments" for a description of how to add tape volumes to DFSMShsm’s RACF tape volume sets.

If the message indicates the dump classes are in conflict, use the DELVOL command with the UNASSIGN parameter for the dump volume so the volume can be used in any other dump class for subsequent dumps.

If the message indicates the tape volume is RACF-protected by another user, the system programmer should request the RACF security administrator look into the matter. The RACF security administrator can determine if the tape volume is RACF-protected, and by whom, by entering the following RACF command:

RLIST TAPEVOL volser ALL

The sender of the command must have a certain level of access authority to the resource depending on the information requested. For additional information, see z/OS Security Server RACF Command Language Reference.

Source

DFSMShsm

Parent topic: ARC messages