CBR6400D   Unable to allocate tape drive for volser in SG storage-group-name. Reply 'C' to cancel, 'R' to retry, 'N' to nowait retry.

Explanation

Start of changeA failed tape drive allocation attempt by OAM has been retried for the time duration specified by the ALLOCRETRYMINUTES keyword on the SETOAM statement in the CBROAMxx PARMLIB member and all allocation attempts failed because no acceptable tape drive was available. An acceptable tape drive is one which is compatible with the media to be mounted: in the case of tape volumes that are not in a tape library, the tape drive must belong to the TAPEUNITNAME to which the tape volume volser has been assigned; in the case of library-resident tapes, the tape drive must be in the same physical library as the tape to be mounted.End of change

Before more attempts are made to allocate the tape drive, the operator is being prompted to indicate whether or not the tape drive allocation request could be satisfied. The OBJECT or OBJECT BACKUP storage group storage-group-name and the VOLSER of the tape volume volser to be used for the pending request are provided in the message text. An associated CBR6425I message was previously issued. Message CBR6425I lists the object name and collection name associated with the request which requires this tape drive allocation.

System action

If the operator replies 'R' (meaning retry), OAM will retry the tape drive allocation. If the allocation request cannot be satisfied immediately, MVS™ Allocation Recovery will issue message IEF238D. Once this message has been issued, other dynamic allocations and all dynamic deallocations, in the OAM address space, cannot be processed until this allocation completes or is canceled.

Start of changeIf the operator replies 'N' (meaning retry with NOWAIT) to the CBR6400D message, OAM will repeat the retry process from the beginning: OAM will issue the dynamic allocation every 10 seconds for a specified time duration (see paragraph below on time duration). If after the specified time duration OAM does not successfully allocate the required device, OAM issues message CBR6425I indicating to the operator that OAM has not allocated a tape drive. OAM continues to retry dynamic allocation every 10 seconds, until a suitable tape drive is allocated or until the number of minutes specified in the ALLOCRETRYMINUTES keyword have elapsed. During this period of time (up to five minutes if ALLOCRETRYMINUTES is set to 5) that OAM is trying to allocate a tape drive, z/OS® allocation recovery processing is disabled and OAM is retrying the dynamic allocation.End of change

Start of changeThe time duration prior to issuing the CBR6425I message is determined by the value specified via the ALLOCRETRYMINUTES(minutes) keyword in a SETOAM statement within the CBROAMxx Parmlib member. The ALLOCRETRYMINUTES value represents the maximum number of minutes OAM will attempt allocation retries prior to issuing the CBR6400D message that gives the operator an opportunity to cancel the request. Valid values for ALLOCRETRYMINUTES are 0-5. The default value is 5 if ALLOCRETRYMINUTES is not specified in the CBROAMxx Parmlib member. A value of 0 results in a time duration of 0 seconds before CBR6425I is issued. A value of 1-5 results in a time duration of 1 minute before the CBR6425I message is issued.End of change

If the operator replies 'C' (meaning cancel), OAM will fail the tape drive allocation and its associated OAM request.

Any other reply will cause OAM to issue this message again, along with its previously issued corresponding CBR6425I message.

Operator response

Determine if there are any tape drives which could be used to satisfy this request (either online or offline) prior to responding to this message.

If this message has an imbedded VOLSER that is not SCRTCH then:
  • Determine if this tape volume is in a tape library. If the tape is in a tape library, make sure that there is a device in that library which can be used for the pending request. (You can determine if the tape is in a tape library by doing a DISPLAY VOLUME command using the volser in this message.)
    Note: If this is a scratch allocation (volser is SCRTCH), the display command will not return any volume location information for this tape.
  • If this tape volume is not in a tape library, make sure that there is a tape drive, with the same TAPEUNITNAME as this tape volume, which can be used for the pending request. (The TAPEUNITNAME might be an ESOTERIC or GENERIC. To determine the TAPEUNITNAME associated with a tape volume retrieve the row for this tape volume volser from the TAPEVOL table.)
    Note: If this is a scratch allocation (volser is SCRTCH), there will not be a row in the TAPEVOL table for this tape.
Once you know the type of tape drive that is required:
  • If all potentially usable tape drives are already allocated to OAM, then respond 'C' or 'N' to this message.
  • If none of the potentially usable tape drives are available, and it is unlikely that one will soon become available, then respond 'C' to this message.
  • If there is at least one potentially usable tape drive available, and it is offline, then vary the tape drive (or the tape library in which it resides) online and respond 'R' or 'N' to this message.
  • If a potentially usable tape drive is available, then reply 'R' or 'N' to this message.

Source

Object Access Method (OAM)

Routing Code

2,3,5

Descriptor Code

2