Date Last Reviewed:
03/15/2007
------------------------------------------------------------------
The Tape Management System (TMS) was a product originally marketed as UCC-ONE. It is also known as CA-1 but is referred to by Enterprise Systems Support (ESS) and this document as TMS.
TMS is designed to provide a secure means of tape management, by providing absolute data set protection against inadvertent destruction of tape files.
All production files must be under TMS control and will therefore be in the Tape Management Catalog (TMC). Exceptions must be processed as outside volumes (i.e. NL tapes, imported data files and exported nonproduction files). See Storage Librarian for assistance.
It is the purpose of the ESS Storage Librarian to manage, store, and protect all University data entrusted to the Computer Operations Center. The ESS Storage Librarian is also available to assist all users in the use of the automated Tape Management System and Disk Management System to ensure that data is not unintentionally destroyed nor needlessly kept past its' useful life.
------------------------------------------------------------------
TMS provides tape protection by gathering and maintaining current information in the Tape Management Catalog (TMC) and by performing validity checks before allowing the tape to be overwritten. TMS gains control at every OPEN, CLOSE and EOV (End Of Volume). All necessary information for the volume is captured at that time and immediately stored in the TMC.
Input tape validation is extended beyond OS header record checking. The 44-character data set name check is performed between the DD statement,in the JCL and the data set name in the TMC.
(Note: Only the last 17-characters of the data set name are recorded in the OS header label of the physical tape.)
All output tapes are checked against the TMC, those which do not meet specific requirements are immediately unloaded and a mount for a new scratch tape is requested.
NOTE: An outside tape (not entrusted in the University library) cannot be used for output unless the expiration date 98000 is used.
A record is maintained in the TMC for each data set on a volume. The volume is retained and therefore not eligible for scratch until the highest expiration date among all files on the volume has expired. The expiration date in the first file record is the highest date of all files. Multi-data sets on a volume must be created in sequence and incremented by one using the label parameter. Multi-data set volumes also require write access to the data set in order to create subsequent files/data sets.
The TMC record for a multi-volume data set contains pointers to the previous volume and next volume in the set, as well as a pointer to the first volume. This prevents volumes from being mounted out of order for input or remounted for output during creation.
The operator does not have the ability to override and permit writing on an unexpired TMS tape. A tape is not qualified for scratch use until the scratch flag in the TMC has been turned on. Only the TMS program, TMSCLEAN (run Monday-Saturday during System Maintenance (SMT)), can turn the scratch flag on. The scratch flag can be turned off by using an expired TMS volume for input (since the TMC entry is unchanged and the data is still on the volume) if it has not already been used as a TMS scratch volume. TMS allows a data set to be recreated on a volume if the data set name is exactly the same, it is the last data set on the volume, and DISP=OLD is specified in the JCL.
Every time a tape data set is created, the expiration date is automatically stored in the TMC. The expiration date must be specified through the EXPDT or RETPD operand of the DD statement LABEL parameter or the default keyword of 99000 may be assumed. The EXPDT operand may contain normal Julian dates or unique TMS keywords. These keywords indicate specific hold criteria (see 1.03 F. Expiration Dates).
The Vault Management System (VMS) under TMS allows the automatic routing of critical tapes to and from an offsite storage location (see 1.05 Vaulting).
A back up copy of the TMC is written daily and an Audit data set keeps track each time a record is updated in the TMC. In the event the TMC is lost (disk pack failure) TMS provides the capability of recovering, using the last backup and the current Audit data set.
Activity reports are available from the Audit data set. Likewise, various reports are available from the TMC (The E.S.S. Storage Librarian will be able to provide requested information).
------------------------------------------------------------------
Although JCL changes are not normally required for TMS, users should examine the five DD statement parameters with which TMS is concerned, as these have expanded functions with TMS. Note that ownership of the volume is determined by the higher level qualifier in the data set name of the first file.
All new data sets on disk and tape volumes (except for outside tape volumes) must adhere to the standard ACF2 data set naming convention. That is, the highest level of the dsname must correspond to a Logonid or a special rule set (e.g. SYS1, SCT). Normally, users will create datasets beginning with their own Logonid or a Department Logonid (e.g. logonid.data.set.name).
NOTE: Department Logonid would be one used when the file would remain in the department if for some reason an individual were to leave that department. Individual Logonid would be used when the file is not used as a department file and could be deleted if the individual left the department.
For any tape created under TMS, the same data set name must be specified when reading a tape for input as was used when the tape was created. Upon input, TMS compares the data set name specified in the JCL to the data set name in the TMC record. An unequal compare will terminate the job.
Volume information can be supplied in JCL or retrieved from the OS catalog. Do not specify a volume serial when creating the first file/label on a tape volume or when a data set name is to be cataloged.
VOLSER must be specified when creating the second or subsequent files on a volume. Note that ACF2 WRITE access to the first file is required to write any secondary files on the volume.
NOTE: If writing a temporary dataset to a cartridge volume (which is not recommended), you should use VOL=PRIVATE (non-specific volume mount).
The UNIT= parameter is required during creation of an OS cataloged data set. Thereafter, the OS catalog should be used and UNIT or VOLUME should not be specified.
The number of tape devices that can be requested by any one job step is limited to four (4).
Tape data sets MUST be cataloged (DISP=(,CATLG)). The default TMS keyword is EXPDT=99000 when a data set is cataloged.
All tapes in the tape library will have standard labels, so be sure to specify LABEL=(...,SL) or leave the default which is SL. Required NL tapes must be processed as outside volumes.
If either expiration date (EXPDT) or retention period (RETPD) is specified as a subparameter of LABEL when the tape is created, that hold criterion is used to protect the data set. There are also several TMS keywords which may be specified in the EXPDT parameter. However, EXPDT/RETPD types can not be intermixed on a multi-data set volume. Although not recommended, several tapes could contain the same data set name but only one can be cataloged. These locally accepted and recommended values are described below.
If the jobstep creating any tape abends (except for S222, S522, S80A, or Sx13 abends), the file will be retained for only one day after its last use (abend changes EXPDT to 98001).
RETPD=nn - A tape may be created with a short term retention period of up to thirty days. Any data which is needed longer should be cataloged and retained with EXPDT=99000 as above. nn is any value between 01 and 30.
EXPDT=980nn - Another option, frequency control, is to indicate a tape, that is to expire nn days after the last day it is used (read or write). nn is any value between 01 and 30.
EXPDT=98000 - Indicates an outside tape not under the control of TMS. This may be used ONLY on non-TMS controlled tapes to override TMS control and is needed only when writing.
EXPDT=99000 - This is the default. Keeps tape from expiring as long as it contains at least one cataloged data set. The file is under OS Catalog control and will only be scratched if and when it becomes uncataloged from the OS Catalog.
NOTE: If at the end of the day, a tape with EXPDT=99000 has no cataloged data sets, it will be returned to the scratch pool.
Only the ESS Storage Librarian can alter an expiration date in the TMC. A written request from the user will be required.
Example 1: To create a data set which will be kept until it is uncataloged:
//ddname DD DSN=logonid.filename,UNIT=CART,
// DISP=(,CATLG),DCB=dcbinfo,LABEL=(n,SL)
Example 2: To create a data set to be kept for one week:
//ddname DD DSN=logonid.filename,UNIT=CART,
// DISP=(,CATLG),DCB=dcbinfo,LABEL=(n,SL,RETPD=7)
Note that when the tape expires after seven days, TMS will uncatalog the data set automatically (since it no longer exists).
Example 3: To create a data set to be kept for two weeks after its last use; for example programmer testing:
//ddname DD DSN=logonid.filename,UNIT=CART,
//DISP=(,CATLG),DCB=dcbinfo,LABEL=(n,SL,EXPDT=98014)
EXPDT is limited to thirty days and can not be expired by the user earlier (EXPDT 99000 can be expired simply by uncataloging).
Example 4: To create a data set on an outside (non-TMS) tape, possibly for export to another site:
//ddname DD DSN=anything,UNIT=3480,VOL=SER=xxxxxx,
// DISP=(,KEEP),DCB=dcbinfo,LABEL=(n,xx,EXPDT=98000)
The volser MUST NOT fall within a TMS range (any volser with alphabetic characters, for example, is not in TMS).
Note: Cataloging data sets on outside tapes is not permitted.
------------------------------------------------------------------
Several tools are available to provide TMC/volume information and aid in the copying of TMS controlled and outside volumes.
There is a Superwylbur macro that will generate an 'express' batch job to provide a listing of the information contained in the TMC for a specific volume.
Note: The inquirer must have ACF2 read access to the special DSN crule.$SHOWDSN (crule=creating rule or high level index of DSN).
1) Call from &PUBLIC.MACROS:CMDS
2) Enter: TMS
3) Provide: VOLSER (volume to be listed) "or" Cataloged DSN (determines volume to be listed)
4) Select an output format:
L = long - all fields (DEFAULT)
S = short - only major fields (volser, fileseq, expdt, DSN, and DSNB)
D = dump - entire record in character and hexadecimal
When there is a need to see the header label information of a physical tape volume contact the ESS Storage Librarian for controlled access (BLP) TAPEMAP.
The OUTMAP program will list the label contents of an OUTSIDE tape. The following JCL should be used:
1) Call from &PUBLIC.MAC1:OUTMAP
2) Provide VOLSER
3) Verify that is is the correct volser
4) Do you want to see the Job (Y/N)?
5) Type R to run the Job or a Temp Name to HOLD it.
Note: If the volume serial is in the TMC, OUTMAP will terminate prior to mounting of tape.
TAPECOPY, a cataloged procedure, can be used to copy outside or TMS tape volumes. It consists of 4 steps:
1) Call From &Public.Mac1:Outmap
2) Step COND - PGM=IEFBR14 sets condition code zero; this is needed only in case the subsequent READ step is to be bypassed.
3) Step READ - PGM=TAPECOPY reads the tape and creates control cards for the subsequent COPY step. Contrary to the name of the program, this step only reads the input tape to determine file names and does no copying.
4) Step COPY - PGM=IEHMOVE copies the input tape to a TMS scratch tape according to the control cards created in the READ step.
The following is a complete definition of the TAPECOPY procedure symbolics; most of the values shown will not normally be used.
//TAPECOPY PROC CCOND=0, COND FOR COPY STEP
// CTLDISP=PASS, DISPOSITION OF CONTROL FILE
// CTLFILE='&&SYSIN', DSNAME OF CONTROL FILE
// CTLUNIT=DISK, UNIT FOR CONTROL FILE
// CTLVOL=, VOLSER FOR CONTROL FILE
// DSN1='&&INPUT', INPUT DATA SET NAME
// INEXP='98000', INPUT EXPIRATION DATE
// OPT=PREFIX, OUTPUT DSNAMES START WITH LID
// OUTDEV=CART, OUTPUT DEFAULT DEVICE
// RCOND=0, COND FOR READ STEP
// VOL= VOLSER TO BE COPIED
The TAPECOPY procedure may be used to copy TMS volumes. However the following two rules apply.
a) For nonoutside tapes, TAPECOPY must be invoked with INEXP= '00000', since EXPDT=98000 is permitted on outside tapes only.
b) For active TMS tapes, the TAPECOPY program will verify that the user has ACF2 READ access to the first file on the tape.
Example 1: To insert the LID of the job as high level index of the DSN.
//stepname EXEC TAPECOPY,VOL=volsertobecopied
All files on the input tape will be copied to a TMS scratch tape, renaming each file to start with the user's LID.
Example 2: Use if a prefix other than the users LID is desired. OPT= option must be overridden.
//S1 EXEC TAPECOPY,VOL=ABC001,
// OPT='PREFIX=Z00USR1.FILES'
Example 3: Use if renaming of selected files is desired. Each output data set name must be specified in an input file using SYSIN. The SYSIN control statement general format (semicolon required) is:
FILE=n,DSNAME=new.data.set.name; ( where 'n' is the file sequence number). For example:
//S1 EXEC TAPECOPY,VOL=ABC999
//READ.SYSIN DD *
FILE=8,DSNAME=Z00USR1.FILE8; FILE=1,DSNAME=Z00USR1.FILE1; FILE=4,DSNAME=Z00USR1.FILE4; FILE=12,DSNAME=Z00USR1.FILE12; FILE=2,DSNAME=Z00USR1.FILE2;
Note the control statements need not be in sequential order and not every file name need be specified. Those file names not specified will be handled as determined by OPT.
Example 4: Use if LID of job is not to be inserted as high level index of DSN.
//S1 EXEC TAPECOPY,VOL=ABC001,
// OPT=NOPREFIX
Example 5: It may be desirable to edit the control cards generated by the READ step before they are processed by the COPY step. An understanding of IEHMOVE is required before proceeding.
1) Use the READ step to generate the control cards and save them on ACA004 as a permanent data set to be edited using Wylbur:
//S1 EXEC TAPECOPY,VOL=ABCDEF,
// CCOND=4095, STOP COPY STEP FROM EXECUTING
// CTLDISP=KEEP, KEEP THE CONTROL FILE
// CTLFILE='logonid.filename', NAME THE CONTROL FILE
// CTLVOL=ACA004, SAVE CONTROL FILE ON ACA004
// OPT='PREFIX=Z00ABC1' RENAME ALL FILES
2) After execution of the above job, edit the control file as desired and resave it (must be in CARD format so do not change attributes).
3) Submit the following job to do the actual copy:
//S1 EXEC TAPECOPY,VOL=ABCDEF,
// RCOND=4095, STOP READ STEP FROM EXECUTING
// CTLFILE='logonid.filename', FIND THE CONTROL FILE
// CTLVOL=ACA004 WHERE IT MAY BE FOUND
Example 6: Use if a tape reel is required:
// EXEC TAPECOPY, VOL=ABCDEF,OUTDEV=TAPE
In all cases, users should verify the COPY step (IEHMOVE) ends with condition code zero. Caution should be taken when copying cataloged data sets; consult MVS UTILITIES MESSAGES, GC26-3920.
See Storage Librarian (Lead Operator after office hours) for complete listing of TMS MESSAGE/ERROR CODES.
------------------------------------------------------------------
1.05 VAULTING a copy of critical tape files (e.g. historical data or backup generation/cycle) should be stored in an offsite location for protection in case of fire or disaster. The Vault Management System (VMS), a facility of TMS, provides the control and routing of these files. This may not be necessary if the Automatic Backup and Recovery (ABR) files can be used.
VMS processing is scheduled during SMT (Monday-Saturday) to automatically produce picking, distribution and inventory lists for offsite tape data sets. The actual vaulting and return of volumes is done daily (Monday-Saturday except holidays).
Vaulting is controlled by data set name; whenever a data set is created with a data set name that matches a predetermined pattern, that volume will automatically be moved to the vault where it will remain until expired. VMS control is based on the first data set on a tape volume even if there are multivolume, multi-data set aggregates.
The Storage Librarian maintains the vault pattern description data set and approves all vaulting requests. The user must determine appropriate routing and retention criteria for each file to be vaulted as follows: (see Storage Librarian)
1) Data set name or index (partial data set name) to be vaulted (DSN=)
2) Creating JOBNAME (JOB=) - optional
3) Vault code - VALT, LIBR or LIB (V=)
'VALT' is the offsite storage location/vault (OUTCODE=VALT).
'LIBR' is a pseudo vault name used for storage of volumes in the CC library with the protection and features of VMS. Since it is in OFFSITE status (OUTCODE=LIBR), the dataset cannot be recreated without intervention by the Storage Librarian. (Initiated by a written request.)
'LIB' also allows the tape to remain in the CC library (OUTCODE= LIB) however, the volume may be recreated.
4) Vault retention:
a) number of cycles of a specific data set (C=nn)
b) number of days to remain in the vault (VR=nn)
c) number of days since creation to remain in the vault (CR=nn)
d) specific Julian date to return from the vault (E=yyddd)
e) hold until the tape dataset expires (EXP)
Note: Volume is retained in the vault for the specified retention period even if data sets are expired.
Example pattern 1:
DSN=logonid.dataset
V=LIB,C=2
V=VALT,EXP
The most recent copy of the data set named logonid.dataset will remain in the Computer Operations Center library for two cycles under VMS control so that it may be recreated if necessary. It will then be retained in the offsite vault until it expires according to the TMC record.
The vaulting example above, is recommended for generation data groups. The current file (0) as well as the next most current (-1) file are available for immediate processing, the second most current (-2) file is in offsite storage if required for disaster recovery and the need for redundant copies/backup is eliminated.
Example pattern 2:
DSN=logonid,INDEX
V=LIBR,C=1
V=VALT,VR=30
The most recent copy of all data sets with the high level qualifier/index of 'logonid' will remain in the E.S.S. library for one cycle but can not be recreated. They will then be retained in the offsite vault for 30 days.
Example pattern 3:
DSN=logonid.xyz,JOB=abcjob
V=VALT,E=91365
The data set logonid.xyz when created by the job abcjob, will be routed to the offsite vault and retained until December 31, 1991.
A vaulted tape can be retreived from the offsite storage location for input only processing and subsequently returned to the vault. This process however, is under the manual control of the Storage Librarian and will only be initiated by a users written request.
To request vaulting for existing data sets, see Storage Librarian. (For outside tape vaulting see 1.07 OUTSIDE TAPE HANDLING).
------------------------------------------------------------------
Out-of-area codes may be assigned to keep track of tape volumes that are sent out of the ESS tape library for 'read only' purposes. The use of these codes is limited to files created by administrative production jobs processed under the control of JOBTRAC.
Whenever a data set is created that matches a predetermined pattern, the volume will automatically be routed to the appropriate department. Volumes with OUTCODES are not eligible for use as scratch tapes. When these tapes are returned to the Computer Operations library, the outcode in the TMC must be manually updated by the Storage Librarian.
All requests for out-of-area assignment (V=nnnn, where nnnn=numeric value) must be coordinated through the Storage Librarian. (Tape cartridges can be handled on an exception basis.)
------------------------------------------------------------------
Outside tapes used for the purpose of importing and exporting data are allowed in the Computer Operations for a period of seven (7) days in accordance with the following policies.
1) A Tape Control Form must be submitted to the Computer Operations Storage Librarian (Lead Operator after office hours) with the tape volume. The user is required to obtain proper authorization and the pink copy/receipt.
2) The tape VOLSER must be outside the TMS range.
a) VOLSER should contain at least one (1) nonnumeric character. Exceptions will be handled manually by the Computer Operations Storage Librarian.
b) EXPDT=98000 is required when a data set is created. (Do not catalog data sets written on outside volumes.)
3) IMPORT - volumes submitted for importing data will be available for use after one (1) hour.
4) EXPORT - volumes submitted for exporting data must be certified and initialized (all existing labels and data will be destroyed) by the Computer Operations prior to use. Specific volsers will be available for use after 8:00 a.m. the following calendar day. If the tape does not pass certification, a replacement volume will be substituted and the user will be billed accordingly. Preferably a prelabeled (nonspecific volume serial) tape may be obtained from Computer Operations and used after one (1) hour.
5) The users signature and University identification may be required when an outside tape volume is released from Computer Operations.
6) Outside tapes should be removed from Computer Operations within the authorized seven (7) day period . A 30 day grace period will be granted. At the end of the grace period users will be contacted to determine the disposition of the outside volume.
7) Header label information on all OUTSIDE volumes (except nonlabelled, unblocked, 80 byte records) is to be obtained by using the OUTMAP program (see 1.04 C. OUTMAP).
8) Assistance, if required, will be provided by either the Computer Operations Storage Librarian and/or the Customer Service Center (CSC).
9) Generally outside volumes owned by individual users, departments and other agencies are tape reels, however, tape cartridges can be handled on an exception basis.
------------------------------------------------------------------