DSM/Tape Catalog User's Guide

DSM/TC Tape Processing
DSM/Tape Catalog User’s Guide — 520233-008
3 - 11
How $ZSVR Manages Tape Requests
b. $ZSVR sends a mount message to the event message collector and any
terminal acting as the tape console. The message tells the operator which
tape to mount on a tape drive.
c. After the operator mounts the tape, $ZSVR uses AVR to find the drive on
which the tape is mounted and to make sure the tape name is the same as
the one in the mount message.
d. When $ZSVR locates the correct tape drive, it connects it to the application
so it can use the tape.
$ZSVR also generates operator messages to indicate when a user requests an
unlabeled tape or to bypass labeled tape processing entirely.
Example
This DEFINE requests a scratch tape for FUP by name:
5> ADD DEFINE =OUTFILE, CLASS TAPECATALOG,&
5> & LABELS ANSI,&
5> & FILEID TEST_DATA_12,&
5> & VOLUME TAP046,&
5> & POOL TEST_TAPES,&
5> & USE OUT
6> FUP COPY $DATA.OPER.RECDS, =OUTFILE
To satisfy this request, after $ZSVR receives the DEFINE information:
1. $ZSVR asks DSM/TC to verify that TAP046 is cataloged in pool TEST_TAPES with
a state of scratch.
2. DSM/TC confirms that TAP046 is a scratch tape in TEST_TAPES.
3. $ZSVR cannot find TAP046 on any of the t
ape drives, so it issues a mount
message to the operator, part of which looks like:
... $ZSVR : 0009 *MC* MOUNT TAP046 WITH RING
4. The operator mounts TAP046 on tape drive $TD03. $ZSVR detect
s this and
connects FUP to $TD03 to complete the request, which lets FUP write data to
TAP046.