z/VM: CP Commands and Utilities Reference - z/VM - IBM

If you do not receive this response during a LOAD or SCAN operation, then
SPXTAPE is not reading the tape. Possible reasons are:
v One or more tape drives are in “WAITING” state (identified by response 4 or 10),
waiting for another SPXTAPE LOAD or SCAN command.
v One or more tape drives are in mount-pending state (identified by response 5),
waiting for additional tapes to be mounted.
v One or more tapes are in intervention-required state.
v You placed your virtual machine in CP READ state.
Response 8:
Each tape drive on which an SPXTAPE operation is initiated is reported with the
following response written in the command summary log and displayed on the
screen.
SPXTAPE {DUMP } INITIATED ON VDEV vdev
{LOAD }
{SCAN }
{CANCEL}
{END }
DUMP
LOAD
SCAN
CANCEL
END
is the SPXTAPE operation that was started.
vdev
is the virtual device number of the tape drive on which the SPXTAPE operation
is running.
Response 9:
When a file is dumped with the PURGE operand, or when a file is loaded, the
following response is sent to the file owner, if currently logged on. For DUMP, the
response is issued after the tape is “closed” (trailers and tape marks have been
successfully written), because files are purged in groups that correspond to a tape
volume that has been successfully completed. For LOAD, the response is issued
after each individual file has been placed on the queue.
{RDR} FILE spd1 SENT {{TO } userid {RDR}} AS spd2 RECS {nnnn}
{PRT} {{FROM} {PRT}} {nnnK}
{PUN} { {PUN}} {nnnM}
{**** PURGED **** }
CPY [*]nnn c {HOLD } {KEEP }
{NOHOLD} {NOKEEP}
RDR
PRT
PUN
identifies the virtual device on which the file is being created or read.
spd1
is the spool ID of the file associated with the command user.
userid
is the user receiving the file.
RDR
SPXTAPE
Chapter 2. CP Commands 1475