DSM/Tape Catalog User's Guide

Tape Library Control Path Configuration Guidelines
DSM/Tape Catalog User’s Guide — 520233-008
7 - 15
User Request Operations

ADD DEFINE =FUPOUT, CLASS TAPE, LABELS ANSI, &
VOLUME (ANSI01,ANSIO2)
FUP COPY FILE1, =FUPOUT

ADD DEFINE =FUPOUT2, CLASS TAPECATALOG, LABELS IBM, &
VOLUME IBM001, COMPRESSION OFF, USE OUT, CATALOG OFF
FUP COPY FILE2, =FUPOUT2

ADD DEFINE =FUPIN, CLASS TAPE, LABELS IBM, VOLUME IBM001
FUP COPY =FUPIN, FILE3
User Request Operations
These examples use both TAPE DEFINEs and TAPECATALOG DEFINEs as they
might be specified for typical user requests:

ADD DEFINE =OUT, CLASS TAPE, LABELS IBM, &
VOLUME (IBM123,IBM124), FILEID OUTTEST
Because a TAPE DEFINE was used, the default value specified for compression is
used. Also, the OPEN request is specified somewhere in the user application.

ADD DEFINE =OUT2, CLASS TAPECATALOG, LABELS ANSI, VOLUME
ANSI98, & USE OUT, CATALOG OFF
Because compression is not specified, the system default is used.

ADD DEFINE =OUT3, CLASS TAPE, LABELS OMITTED, DEVICE $SILO00
Because labeled tapes are not being used, the operator must use the ACSLS
library server to mount the tape cartridge from the tape library.

ADD DEFINE =OUT4, CLASS TAPECATALOG, LABELS OMITTED, 
& DEVICE $SILO00, CATALOG OFF, COMPRESSION IDRC
Because labeled tapes are not being used, the operator must use the ACSLS
library server to mount the tape cartridge from the tape library. Also, because
compression is specified, the system default is not used.
TMF Operations
TMF automatically creates a TAPE DEFINE and selects tapes as needed. All these
examples are executed from a TMFCOM prompt:

DUMP FILES $DATA.*.*, BLOCKSIZE 28,...
TMF chooses which scratch tapes to use.

DUMP FILES $DATA1.*.*, TAPEMEDIA (TMF001,TMF002),...
If too few tape volumes are specified, TMF automatically chooses more.

NEXT AUDITTRAIL $DATA3.TMFTRAIL.MA