Intro to the UTCC Tape Management System, U01-0509-16

The UTCC Tape Management System uses the CA-1 software package for managing tape data sets. Information about tapes under control of CA-1 is stored in a Tape Management Catalog (TMC) data set. At tape open time, CA-1 performs validity checking prior to allowing any processing by the user program. When a tape is opened for input, CA-1 compares the data set name specified in the DD statement with the corresponding 44 character data set name for the volume stored in the TMC. If the data set names are identical, processing is allowed to continue; otherwise the job is ABENDED. The check by CA-1 is performed after the normal operating system verification of the 17 character data set name in the header record of a labeled tape. When a tape is opened for output, CA-1 verifies that the output tape has SCRATCH status in the TMC. This means that the tape has been released through CA-1 and is available for reuse. Tape expiration is controlled completely by CA-1, and expiration dates in the tape header will be ignored. Tape retention through CA-1 is under user control. All tapes managed by CA-1 will be assigned a retention period based upon the EXPDT or RETPD subparameters provided when the tape is first used, or "checked out." Keyword parameters unique to CA-1 allow user specification of other retention criteria, such as retention based on the number of cycles required, and permanent hold. A system default period of seven days will apply if no retention parameters are supplied. CA-1 examines the TMC daily and marks for release those tapes having expired retention conditions. These tapes are then released to a scratch pool for reuse in other jobs.

Introduction

This document introduces the CA-1 Tape Management System. This system was designed primarily for tapes used on the IBM/MVS machine, but modifications have been made so that VAXcluster and VM/CMS tapes may be managed by CA-1. The following sections describe general information about CA-1 and the use of CA-1 on the IBM/MVS machine. Modifications for the VAXcluster are described in the section entitled VAXcluster Considerations. For the IBM many of the examples assume that data sets are cataloged and that DCB information is supplied by the job. CA-1 requires standard JCL for the use of tapes except for certain exceptions pointed out in this document. Most of the document describes single file, single reel, or single cartridge data sets. If you are working with multifile, multireel, or multi-cartridge tapes please read those sections first for the differences. The default density for writing on tapes is 38K BPI for a cartridge tape and 6250 BPI for a reel tape. Users who do not catalog their tape data sets or who want new data sets created on reels instead of cartridges MUST code the UNIT= parameter to match the desired type of tape. The UNIT names are listed below. UNIT and DCB are parameters on a DD statement. Note that UNIT=TAPE prior to August 3, 1985 requested a 3420 tape drive supporting 1600 and 6250 BPI. Now UNIT=TAPE will request a 3480 tape drive supporting 38K BPI.

   OLD   CURRENT

   Unit  Tape     DCB
   Type  Density  DEN=  UNIT= UNIT=

   3420-6   1600  3  TAPE  TAPE1600
   3420-6   6250  4  TAPE  TAPE6250
   3480     38K   -    -   TAPE

All 3480 drives attached to MVS are IDRC-capable. Using UNIT=TAPE with DCB=TRTCH=COMP to write the first file on a tape will result in all files on that tape being in IDRC-compact format. Compact format tapes may hold up to 5 times more data than non-compacted cartridges. Cartridges in compacted format can be read on any IDRC-capable drive with no special instruction from the user. Users who intend to transport data to systems which do not have IDRC-capable drives should not use TRTCH=COMP when preparing tapes. To write on a 1600 bpi tape DCB=DEN=3 must be specified. To use a 1600 bpi tape the UNIT parameter in JCL should say UNIT=TAPE1600. To use a 6250 bpi tape, the UNIT parameter in JCL should say UNIT=TAPE6250.

Tape creation and retention using MVS JCL

CA-1 uses the expiration date (EXPDT) or the retention period (RETPD) of the LABEL parameter in JCL to save tape data sets. If no EXPDT or RETPD is specified and a valid DSN is specified, the tape data set will be kept seven days. Expiration dates in the range 98000-99365 have special meanings to the tape library system, as follows:

98000  Alien tape (not stored in tape library).
98nnn  Retain tape nnn days after last access.
99000  Retain tape as long as dsname is cataloged on MVS.
99nnn  Retain tape for nnn cycles.
99365  Retain tape permanently; read access only.

Because dates in the year range 1998-1999 have special meanings, you must, if you want your tape to have an EXPDT in 1998-1999, include an extra DD statement, ddname //TMNOKEY in your JCL to show that the EXPDT you have specified should NOT be interpreted as a keyword date.

Examples

To save a tape for three days

RETPD=yy, where yy is the number of days the tape is to be held, 3 in this case.

   //FILEB DD DSN=J999991.PUTTER8.OUTPUT,UNIT=TAPE,
   // DISP=(NEW,KEEP),LABEL=RETPD=3

To save a tape data set until January 1, 1996

EXPDT=yyddd, where yy is the year, 95 in this case, and ddd is the Julian day of the year, 001 in this case.


   //TESTOUT DD DSN=J999991.PUTTER8.DATA79,DISP=(NEW,CATLG),
   // UNIT=TAPE,DCB=(RECFM=FB,LRECL=100,BLKSIZE=6400),
   // LABEL=EXPDT=96001


To save a tape data set until January 1, 1998

EXPDT=yyddd, where yy is the year, 98 in this case, and ddd is the Julian day of the year, 001 in this case. The presence of the TMNOKEY DD statement tells the tape management system NOT to interpret the date as a keyword date.


   //TESTOUT DD DSN=J999991.PUTTER8.DATA79,DISP=(NEW,CATLG),
   // UNIT=TAPE,DCB=(RECFM=FB,LRECL=100,BLKSIZE=6400),
   // LABEL=EXPDT=98001
   //TMNOKEY DD DUMMY

If a valid DSN is given and no EXPDT or RETPD is specified, the tape data set is kept seven days.


   //FILEB DD DSN=J99991.FUDGE8.SHORT,
   // DISP=(NEW,CATLG),UNIT=TAPE

Retention based on the catalog (EXPDT=99000)

Indicates that the tape data set is to be held as long as the data set is cataloged.

To save


   //OUTPUT DD DSN=J999991.PUTTER8.JUNE,UNIT=TAPE,
   // LABEL=EXPDT=99000,DISP=(NEW,CATLG)

To release, do one of the following

1. The last time the dataset is used code:

//ZONK DD DSN=J99991.FUDGE8.JUNE,DISP=(OLD,UNCATLG)

2. Run UCCUPDTE to set expiration date to TODAY (see section entitled TAPE RELEASE). The next time the tape management utility to return expired tapes to the scratch pool is run, the tape will be set scratch and entries for any data sets on the tape (except generation data group data sets) will be removed from the MVS system catalog. The expiration utility is normally run early each morning.

3. Run IEHPROGM (See chapter 10, UTCC IBM User's Guide ) to uncatalog the data set. The next time the tape expiration utility runs it will set the tape scratch.

Note: Do not provide a DD statement for the tape which is to be uncataloged

Note: Although CA-1 recognizes a date of 99000, MVS expects the day portion of the date to be between 001 and 365. Therefore, in response to an EXPDT of 99000, MVS will print the message "IEF604I EXPDT SUBPARAMETER OF LABEL KEYWORD SPECIFIES ZERO DAYS VALUE." This is, however, only an informatory message, and the data set will be properly cataloged.

Retention since last used (EXPDT=98aaa)

The "aaa" designates the number of days after the last use of the tape data set for which the tape is to be saved. The value of "aaa" can be between 001 and 365.

To save


   //FT08F001 DD DSN=J99991.FUDGE8.DATA,DISP=(NEW,KEEP),
   // LABEL=EXPDT=98005,DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400),
   // UNIT=TAPE

To release (automatic)

Since "aaa" was 005 release will take place five days after the last time the tape is used. If you wish to alter the expiration date or change the last date used, use UCCUPDTE (see section entitled TAPE RELEASE).

Permanent retention (EXPDT=99365)

EXPDT=99365 indicates that the tape data set is to be held permanently.

To save


   //FILEB DD DSN=J99991.FUDGE8.EASYOUT,UNIT=TAPE,
   // LABEL=EXPDT=99365,DISP=(NEW,CATLG)

In order to release a permanent tape data set, Form U01-0510 can be completed and returned to the I/O Clerk, SMC M1; or UCCUPDTE can be used to modify the expiration date so that the tape may be released (see section entitled TAPE RELEASE).

Cycle retention (EXPDT=99ccc)

The "ccc" indicates the number of cycles to be saved. A cycle is defined as all volumes with the same data set name and creation date. The value of "ccc" can be between 001 and 364.

To save


   //OIRIPS DD DSN=J99991.FUDGE8.INVENT,DISP=(NEW,KEEP),
   // UNIT=TAPE,LABEL=EXPDT=99003,DCB=(RECFM=FB,
   // BLKSIZE=13000,LRECL=130)

To release (automatic)

Since "ccc" is 003 in this example, whenever more than 3 cycles exist, the oldest one will be released. Since a cycle is based on date and data set name, there will never be less than 3 cycles, although there could be more than one tape per cycle. The data set name must follow the UTCC convention, for example, J99991.node.node, where 99991 is the user IBM project code number and node names may be chosen by the user.

Saving tapes into the 21st century

Use the yyyy/ddd form of date in your EXPDT in JCL.

   //OIRIPS DD DSN=J99991.FUDGE8.INVENT,DISP=(NEW,KEEP),
   // UNIT=TAPE,LABEL=EXPDT=2001/015,DCB=(RECFM=FB,
   // BLKSIZE=13000,LRECL=130)

Recreate

CA-1 will allow a tape data set to be rewritten onto the same tape only if DISP=OLD and the DSN is the same as when it was originally created. Note that if EXPDT=99365 was originally coded the file cannot be recreated. When you rewrite a tape data set, the EXPDT is updated to reflect the new EXPDT. Only the last file on a multi-volume tape can be rewritten. Multi-volume data sets may not be recreated nor can an alien tape whose volume serial number falls in the range of tapes managed by CA-1


   //REWRITE DD DSN=J99991.FUDGE8.ITG,DISP=OLD,
   // LABEL=EXPDT=98001

MOD

A DISP of MOD is valid with CA-1. When a DISP of MOD is used when writing a tape, the tape is positioned at the end of the data which already exists on the tape, thus appending the new data to already existing data. On a multifile tape a DISP of MOD can only be used for the last file.


   //APPEND DD DSN=J99991.FUDGE8.DATA,DISP=MOD

Tape release

To release a tape that has an expiration date or retention period greater than the present day, do one of the following:

1. Use the CA-1 Utility, UCCUPDTE described on Form U01-0527.


   //ZAP JOB ,DELANEY,GROUP=J999991,USER=P999998,PASSWORD=FUDGE
   /*ROUTE PRINT RMT0
   //STEP1 EXEC UCCUPDTE
   //SYSIN DD *
   VOL 109652
   VER DSN=J999991.OLD.STUFF
   REP EXPDT=TODAY

VOL Indicates the Volume Serial Number (VSN) of the tape for which to modify the expiration date.

VER Verify the data set name for the first file (may be omitted for a pre-TMC tape that has not been used under CA-1).

REP Replace the expiration date. TODAY indicates present date.

2. Fill out Form U01-0510 and return it to the I/O Clerk, SMC M1.

3. Uncatalog the tape data set if saved with EXPDT=99000. (See Section entitled RETENTION BASED ON THE CATALOG)

Alien tapes

Any tape which is not managed by the CA-1 system is an alien tape. If the volume serial number is outside the range of 000000 through 029999, the system will automatically recognize it as an alien tape and allow it to be read. If a tape has a volume serial number within this range but is from another site, then EXPDT=98000 must be coded to read the tape. To write on an alien tape an EXPDT=98000 must be coded, except that in no case can an alien tape be written if the volume serial number falls in the range of 0 through 29999. In order to write to a standard labeled alien tape that has an expiration date which is greater than the present date and other than 98000, a /*MESSAGE statement must be included in the JCL. For example:

   /*MESSAGE OK TO WRITE ON DATE-PROTECTED DSN J999991.NODE1.NODE2

JES2 Message statement

If an alien tape VSN does not match the external label, a JES2 MESSAGE statement must be supplied following the JOB statement.

/*MESSAGE internal=external where "internal" is the volume number of the tape and "external" is the external U number

UCCUPDTE

UCCUPDTE is a utility program that permits users to release SMC tapes, check SMC tapes out-of-area, or modify information in the CA-1 data base. The tape does not have to be mounted for the change to take place.

Note: Tapes out-of-area should not be updated and if a tape is checked out of the area the expiration date should be such that the tape will not expire until after the tape is returned.

UCCUPDTE control statements

Three UCCUPDTE control statements are used to specify tape information to be modified in the CA-1 data base:

VOL Specifies volume about which information is to be modified.

VER Specifies the data set name of the first file, and may specify the current values of other fields, to verify that the proper tape is accessed

REP Specifies fields to be modified

Note: Each control statement must begin in column one. Column four is always blank. Any number of VER or REP statements may be specified, but neither a VER nor REP statement may extend beyond column 72 or be continued. The CA-1 fields described below may be coded on the VER and REP statements, beginning in column 5.

DSN data set name (always required on the VER statement except for tapes created before the use of the CA-1 tape management system).

EXPDT expiration date (yyyy/ddd) or CA-1 keyword. Use yyyy/ddd if you want a 'real' date and keyword if you want special retention criteria.

PASSWRD password

LDATE last date used (yyyy/ddd or "TODAY")

OUTCODE out-of-area code (ENTX, FICH, AHT, or USER. If USER is specified, see COMMENT)

TACCT responsible project code (always specified as six digits, including leading zeroes if necessary)

COMMENT comments (1-31 characters. If USER is specified on the OUTCODE statement, the name and destination to which the tape is sent must be coded as comments.)

Note: These fields apply to the first or only file on the tape. Information about other files on the tape may not be modified. In the case of a multi-volume data set or a multi-volume, multi-data set aggregate, information may be changed for the first volume only. This information, however, is then applied to all volumes containing the data set or data set aggregate.

Note: "HEXZERO" may be used to indicate hexadecimal zeroes for any field.

Note: If the DSN or COMMENT field contains special characters or blanks, the data set name or comment must be enclosed in apostrophes.

JCL for UCCUPDTE


   //jobname JOB ,name,GROUP=J999991,USER=P999998,
   // PASSWORD=current
   /*ROUTE PRINT dest
   /*JOBPARM ROOM=BINS
   //stepname EXEC UCCUPDTE
   //SYSIN DD *
      (control statements)

Note: The project code on the JOB statement must be the project code responsible for the tape.

Examples of UCCUPDTE control statements


Releasing a tape

VOL 999999
VER DSN=J999991.DATA
REP EXPDT=TODAY


Modifying the expiration date

VOL 999999
VER DSN=J999991.COBOL.SOURCE
REP EXPDT=1998/030

Changing Expiration Date to "30 days since last used" and Changing Last Date Used to today


VOL 999999
VER DSN=J99991.TEST
REP LDATE=TODAY,EXPDT=LDATE/030

Checking a tape out-of-area to
 user

VOL 999999
VER DSN=J999991.ZINC
REP OUTCODE=USER,COMMENT='BINSzJOHN DOE'

Note: Destination and user name must be specified in the comment field.

Checking a tape out-of-area to Entrex

VOL 999999 VER DSN=J999991.FUNPACK REP OUTCODE=ENTX

Adding a password

VOL 999999
VER DSN=J999991.CASH.COLLECT
REP PASSWRD=ABCDEF (ABCDEF is the new password)

Removing a password

VOL 999999,PASSWORD=SECRET (SECRET is the old password)
VER DSN=J999991.DATA
REP PASSWRD=$REMOVE$ ($REMOVE$ is a keyword which removes
                      the old password)

Note: The spelling of the password keyword differs on the VOL (PASSWORD=) and the REP (PASSWRD=) control statements.


Changing a password

VOL 999999,PASSWORD=FUDGE (FUDGE is the old password)
VER DSN=J999991.DSATE
REP PASSWRD=THUD (THUD is the new password)

Note: The old password (FUDGE) on the VOL statement must be specified to change the password to THUD.


Releasing a password protected
 tape

VOL 999999,PASSWORD=R2D2
VER DSN=J999991.MASTER
REP EXPDT=TODAY

Note: The password is required on the VOL statement to modify any information about a password protected tape.

Assigning a tape to another project code

VOL 999999 VER DSN=J999994.TEST REP TACCT=999994

Adding or replacing a comment about a tape

VOL 999999 VER DSN=J999994.ZAP REP COMMENT='FIX OF JUNE DATA'

Note: The new comment is added if there is not a previous comment; otherwise the old comment is replaced.

Removing a comment about a tape

VOL 999991 VER DSN=J999991.OLD REP COMMENT=' '

Note: The blank character in single apostrophes (' ') causes the old comment to be replaced by blanks.


Several tasks combined

VOL 999991
VER DSN=J999991.OLD
REP EXPDT=TODAY
VOL 999992
VER DSN=J999991.GOOD
REP EXPDT=CATALOG,COMMENT='OLD 999991'

Changing the expiration date of a
 pre-CA-1 tape

VOL 999999
REP EXPDT=99365

Temporary tape data sets

CA-1 will recognize a tape data set as temporary if no EXPDT is specified and any of the following is true:


   1.  No DSN is specified
   2.  DSN starts with &&
   3.  DISP=(NEW,DELETE)
   4.  LABEL=RETPD=0

NL tapes

When a NL tape is generated under CA-1, the data set name is stored for validity checking when the tape is used subsequently. Therefore, when a NL tape is read under CA-1, the DSN that was used at creation time must be specified. The retention procedures are the same as for SL tapes.

To save, using the catalog, with EXPDT=99000


   //TSTAE DD DSN=J99991.FUDGE8.TIMECARD,UNIT=TAPE,
   // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400),
   // LABEL=(1,NL,EXPDT=99000),DISP=(NEW,CATLG)


To read the above NL tape data set

   //INTSTAE DD DSN=J99991.FUDGE8.TIMECARD,DISP=SHR,
   // LABEL=(,NL),DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)


To release the last time it is used

   //ZAP DD DSN=J99991.FUDGE8.TIMECARD,DISP=(OLD,UNCATLG),
   // LABEL=(,NL),DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
   (or use IEHPROGM to uncatalog the tape data set
    or use UCCUPDTE (see section entitled TAPE RELEASE))

Generation data groups

There are three steps in creating a generation data group (GDG):

1. Create a disk data set with the attributes required by the GDG.


   //GDGDISK JOB ,FRED.GRIMM,GROUP=J999991,USER=P999998,
   //  PASSWORD=SECRET
   /*ROUTE PRINT RMT15
   //SA EXEC IEFBR14
   //A DD DSN=J999991.MODEL.DCB,DISP=(NEW,CATLG),
   // UNIT=ONLINE,SPACE=(TRK,(0)),LABEL=EXPDT=99000,
   // DCB=(RECFM=FB,LRECL=400,BLKSIZE=6400)

DSN - any permanent data set name; cannot be the same as your tape GDG data set name

DISP - catalog

UNIT - can be any online disk pack

SPACE - only the attributes are needed so no space is required

LABEL - sets GDG up to rely on the catalog as the means of scratching old generations

DCB - DCB attributes for the tape generations

2. Build the GDG index using IDCAMS:

   //GDGDISK JOB ,FRED.GRIMM,GROUP=J999991,USER=P999998,
   // PASSWORD=SECRET
   /*ROUTE PRINT RMT15
   //START EXEC PGM=IDCAMS
   //SYSIN DD *
DEFINE GDG (NAME(J999991.PUTTER8.MASTER) LIMIT(5))

DEFINE GDG - tells IDCAMS to build a GDG index

NAME(DSN) - tells the qualified name of the GDG

LIMIT(#) - tells how many generations are to be contained in the GDG

3. Add data sets to the GDG:

//OUTTAPE DD DSN=J999991.PUTTER8.MASTER(+1), // DISP=(NEW,CATLG),DCB=(J999991.MODEL.DCB), // UNIT=TAPE

ABEND

If a job has an abnormal termination before a tape data set is closed, the retention period specified is overridden and is set to seven days.

Multifile tapes

Expiration date types should not be mixed on a tape volume. A warning is issued if this is done. (MIXEXP=WARNING). When multifile tapes are used the tape will not be scratched until the expiration date of all tape data sets has passed. CA-1 will only allow recreation or DISP=MOD for the last file of a tape. A new data set can be added only after the last file of a tape.

TAPELIST

A list of all tapes checked out to a project can be obtained by executing the procedure TAPELIST. The project code on the job statement is the key for selection. To get a tape list for project code 999991 the following may be used:


   //LIST JOB ,FRED.SMITH,GROUP=J999991,USER=P999998,
   // PASSWORD=SECRET
   /*ROUTE PRINT RMT0
   /*JOBPARM ROOM=BINS
   //SA EXEC TAPELIST

TAPELIST will sort on one major and up to nine minor CA-1 keywords. You simply add a //SYSIN DD * statement and then a line with the verb: SORTDSNB keyword1,keyword2,...,keyword10. The first keyword listed is the major keyword; any others are considered minor keywords for this jo A complete listing of CA-1 keywords is given in the section entitled CA-1 Keywords in the; IBM User's Guide For example SORTDSNB DSN will give a listing sorted by DSN rather than by the default of VOLSER.

//SORTLIST JOB ,'FRED.SMITH',GROUP=J999991,USER=P999998, // PASSWORD=SECRET /*ROUTE PRINT RMT0 /*JOBPARM ROOM=BINS //SA EXEC TAPELIST //SYSIN DD * SORTDSNB DSN

Tape label listing

To print the tape labels on a 38K BPI tape cartridge execute the procedure TLABELS as follows.


   //LABEL JOB ,FRED.SMITH,GROUP=J999991,USER=P999998,
   // CLASS=T,PASSWORD=SECRET
   /*ROUTE PRINT RMT0
   /*JOBPARM ROOM=BINS
   //SA EXEC TLABELS,VOLID=999999

To print the tape labels on a 1600 BPI tape execute the procedure TLABELS as follows.


   //LABEL JOB ,FRED.SMITH,GROUP=J999991,USER=P999998,
   // CLASS=T,PASSWORD=SECRET
   /*ROUTE PRINT RMT0
   /*JOBPARM ROOM=BINS
   //SA EXEC TLABELS,VOLID=999999,UNIT=TAPE1600

To print the tape labels on a 6250 BPI tape execute the procedure TLABELS as follows.


   //LABEL JOB ,FRED.SMITH,GROUP=J999991,USER=P999998,
   // CLASS=T,PASSWORD=SECRET
   /*ROUTE PRINT RMT0
   /*JOBPARM ROOM=BINS
   //SA EXEC TLABELS,VOLID=999999,UNIT=TAPE6250

CA-1 password protection

Access to any tape can be restricted through the use of the CA-1 password. This password is assigned, in the step using or creating the tape, by using a DD statement with the DDNAME TMSDSS. This DD statement indicates where information is to be read which assigns a password for a particular data set. Failure to supply a password in a job step using a password protected tape results in the job ABENDING and in a record being written to the audit data set. The passwords may be in-stream or stored in any sequential data set. Users must be aware that if a password is assigned to a tape, that password is encrypted in the CA-1 TMC. UTCC cannot provide this password to a user once it has been stored by CA-1.

A. Syntax of password control statement

COLUMNS REQUIRED INFORMATION

1-8 DDNAME of DD statement that password is to be associated with.

10-17 1 to 8 character password


   COLUMNS  OPTIONAL INFORMATION

   19-80 Keyword options, each option separated by a
      comma.


KEYWORD OPTIONS:

READ=YES Tape can be read without password.

READ=NO (DEFAULT) Tape cannot be read without password.

WRITE=NO Tape cannot be written on.

NEW=new password  Assign new password to this tape.The old password in
columns (10-17) must match the old password to change a password.

NEW=REMOVE  Remove password protection from this tape.  Old password must
match.

DSN=dsname  Fully qualified data set name of a concatenated data set.
This is used only for the concatenated data sets.
The DDNAME (1-8) is left blank.

B. Creating a password protected tape

   //ZINGER DD DSN=J99991.FUDGE8.SECRET,DISP=(NEW,CATLG),
   // UNIT=TAPE,LABEL=EXPDT=99000
   //TMSDSS DD *,DCB=BLKSIZE=80
   ZINGER   FUDGE


C. Using a password protected tape
 
   //INPUT DD DSN=J99991.FUDGE8.SECRET,DISP=OLD
   //TMSDSS DD *,DCB=BLKSIZE=80
   INPUT    FUDGE


D. Changing the password of a password protected
 tape
 
   //FILEA DD DSN=J99991.FUDGE8.SECRET,DISP=OLD
   //TMSDSS DD *,DCB=BLKSIZE=80
   FILEA    FUDGE    NEW=THUD

Tape check out

CA-1 allows users to automatically check a tape out and supply a destination for the tape. The control statements to check out a tape can be instream or on a disk data set. A DD statement with the DDNAME of TMSDISP must be supplied as part of the JCL if you want to check a tape out of area.

Note: Tapes out-of-area should not be updated and if a tape is checked out of the area the expiration date should be such that the tape will not expire until after the tape is returned.

Syntax of tape check out control statement

Columns Required Information

1-8 DDNAME associated with the tape
9 the letter "X"
10 the letter, "F"
12-15 OUT=
16-19 Route to one of the following:

OUT=AHTb Tape is to be sent to the librarian at AHT P204.

OUT=ENTX Tape is to be sent to the Entrex system operator at 101 AHT.

OUT=FICH Microfiche tape is to be picked up.

OUT=USER

If USER is used as the route code then the following additional information is required:

Columns Required Information

20 Comma ","

21-50 user name; destination
provide a name and destination where the tape is to be sent.

Note: When columns 20 through 50 are used, the comment information about the tape is replaced with the name and destination information. See the section entitled COMMENTS FIELD.

Example to check out a tape


   //TIMEDATA DD DSN=J99991.FUDGE8.DATA,DISP=OLD
   //TMSDISP DD *,DCB=BLKSIZE=80
   TIMEDATAXF OUT=USER,FRED GRIMM;BINS

Comments field

UTCC has modified CA-1 to allow users to store a 31 character comment about the tape being used. The format for supplying a comment is as follows:

Columns Required Information

1-8 DDNAME associated with the tape 10 * 12-16 COMM= 17-47 Comment

The control statement for the comment can be instream or a disk data set. A DD statement with the DDNAME of TMSDISP must be supplied in the job step using the tape. To store a comment:


   //TIMERPRT DD DSN=J99991.FUDGE.DATA,DISP=OLD
   //TMSDISP DD *,DCB=BLKSIZE=80
   TIMERPRT * COMM=TIME REPORT FOR JUNE AND JULY

Note: If you use the Tape Check Out procedure to check a tape out of the area with OUT=USER in columns 12-19, the comment field will be changed to contain the user name and the destination supplied in the tape check out statement.

Multireel data sets

Multireel data sets, data sets that span more than one physical reel, cannot be read out of order.

IBM messages and codes

DDD designates the tape drive unit on which the job was run.

IECTMS1 DDD, ,ENTER VSN

Operator verifies VSN for NL tape

IECTMS2 DDD,bbbbbb,VERIFY FROM OUTSIDE LIBRARY

Job cancelled if not an alien tape and LABEL=EXPDT=98000

IECTMS3 DDD bbbbbb IS NOT aaaaaa

Operator responded tape number bbbbbb when user requested tape number aaaaaa

IECTMS3 DDD bbbbbb IS NOT SCRATCH(XX)

(XX) 04 Tape is not an alien tape 08 Tape is alien and LABEL=EXPDT=98000 not coded 12 Permission denied to write on an alien tape. (See IECTMS4) 16 Operator did not reply a specific NL VSN. (See IECTMS1) 20 TMC EXPDT=99365 24 Volume marked out of area 28 TMC DSN does not match tape DSN 32 Volume has not expired 36 Same volume re-mounted for EOV output request 40 Volume part of a valid multi-volume chain 44 Specific VSN required 48 Volume has DSNB's 52 Trying to create file 'N' and 'N-1' does not exist 56 Trying to create file 'N' and 'N+1' already exists 60 Trying to create file 'N' but 'N' already exists 64 Trying to recreate a data set with DISP=NEW 68 Label check occurred at open on file >1 72 Label check occurred at open on password protected tape 76 An attempt has been made to recreate a data set with RETPD=0.

80 The volume that was mounted is not a member of the scratch pool requested.
84 A tape has been mounted from a defined scratch pool for a job which requested no specific scratch pool.
88 An unauthorized label type or density change has been attempted.
92 An attempt has been made to use a tape for output that has been marked BAD by CA-1.
96 DISP=OLD has been specified in the JCL, but the data set name in the TMC does not match the data set name in the JCL.

IECTMS4 DDD,bbbbbb IS UNEXPIRED

If an alien tape has an unexpired expiration date except (EXPDT=98000) the system will not write on the tape without permission.

To write on the tape the user must supply the following MESSAGE statement:

/*MESSAGE OK TO WRITE ON DATE-PROTECTED DSN J999991.NODE1.NODE2

IECTMS9 DDD,bbbbbb,WORK TAPE

Work tape not saved.

IECTMS10

Warning, a mixed expiration was issued for a multifile tape, retention is questionable. Mixed expiration types should not be used.

IECTMS9 DDD,bbbbbb,WORK FILE

Temporary file created on a multifile tape.

IEFTMS50 Nyy-rc,jobname,stepname,ddname

** UCC1-ABEND..Refer to UTCC document 0509

(Nyy) 1D9 Invalid data set name. The DSN in JCL does not match the DSN in the TMC.

2D9 Invalid secondary data set. For input probably wrong file number. For output see rejection code in IECTMS3 message.

3D9 Invalid TMC record. Contact the Tape Librarian.

4D9 Invalid multi-volume data set. Make sure volume being mounted is part of the multi-volume data set.

5D9 Mixed expiration date disallowed.

6D9 Invalid password. Use the correct password.

7D9 DISP=MOD rejected. See rejection code in IECTMS3 message.

9D9 No output to alien tape in CA-1 range.

ED9 Invalid alien output tape or tape mounted as scratch.

FD9 Invalid SVC. See IBM messages and codes manual.

1D8 IPL required. Contact the Tape Librarian.

2D8 All DSNB's are allocated. Contact the Tape Librarian.

3D8 Invalid DSNB record. Contact the Tape Librarian.

4D8 Invalid parameter list. Contact the Tape Librarian.

FD8 Invalid SVC. See IBM messages and codes manual.

VAXCLUSTER CONSIDERATIONS

On the VAXcluster, interaction with the Tape Management System (TMS) is through the TMOUNT command. The TMOUNT command is used to mount a tape volume and make it available for processing. It is also used to check out a scratch tape, and to display and update tape status information.

Expiration date

The /RETAIN qualifier on the TMOUNT command is used to specify the tape expiration date. The expiration date tells when the tape is to be released from the tape library back into the scratch tape pool. All tapes handled by the Tape Management System have an expiration date. When a scratch tape is first checked out and mounted by TMOUNT it will be given the expiration date specified on the TMOUNT command. If no expiration date is specified, the tape will expire in seven days. The expiration date will remain in effect until it is explicitly changed using the /RETAIN qualifier on the TMOUNT command.

Syntax for /RETAIN Qualifier

The /RETAIN qualifier on the TMOUNT command supports the following options:

/RETAIN=UNTIL=date Retain tape until specified date. The date may be specified as:

dd-mmm-yyyy VMS date format: day-month-year
yyyy.ddd Julian date: year.day

/RETAIN=DAYS=nnn Retain until nnn days from today.

/RETAIN=LDATE=nnn Retain until nnn days after last date used.

/RETAIN=CYCLE=nnn Retain nnn most recent tapes with this dataset name.

/RETAIN=PERMANENT Retain the tape permanently. NOTE: Tapes retained permanently cannot subsequently be mounted for writing.

/RETAIN=RELEASE Release the tape into scratch pool.

The /RETAIN qualifier may be used when mounting a scratch tape, when mounting a tape for writing, or when the /TMS_UPDATE_ONLY qualifier is specified. The /RETAIN qualifier may not be used with alien tapes.

Example - Check out and mount a scratch tape

This command will check out and mount a scratch tape. The tape will be retained in the tape library until December 31, 2001.

$ TMOUNT * SCRTCH mytape: /DSN=EXAM /RETAIN=UNTIL=31-DEC-2001

Example - Mount a tape and update the expiration date

This command mounts a tape for writing. Because the /RETAIN qualifier has been specified, the tape expiration date will be changed: the tape will be released from the tape library 100 days after the last date it is used. If the /RETAIN qualifier had not been specified, the expiration date would have remained unchanged.

$ TMOUNT * 001234 mytape: /DSN=EXAM /WRITE /RETAIN=LDATE=100

Example - Update the expiration date without mounting the tape

This command modifies the tape expiration date so that the tape will be released from the tape library in 30 days. The tape is not actually mounted.

$ TMOUNT * 001234 mytape: /DSN=EXAM /RETAIN=DAYS=30 /TMS_UPDATE_ONLY

Example - Display tape status information

This command displays current tape status information. The tape is not actually mounted.

$ TMOUNT * 001234 mytape: /DSN=EXAM /TMS_INFO_ONLY

Documentation

For a more thorough discussion of the TMOUNT command consult the online help facility by using the command

$ HELP TMOUNT

For comprehensive documentation of magnetic tape usage on the VAX/VMS system, see the Guide to VAX/VMS Disk and Magnetic Tape Operations VAXcluster User's Guide , Form U01-0572 is available in the UT Bookstore and provides details on the use of magnetic tape on the VAXcluster at UTCC. For a description of the MOUNT command, see the VAX/VMS Mount Utility Reference Manual