Moving to release 5.2 of the Tape Management System (TMS)

The tape management system installed on OS/390 is release 5.2 of CA-1. This release of the tape management system is certified by its vendor, Computer Associates, as its year 2000 compliant release.

Release 5.2 has some differences from the 5.0 code now running on MVS, mainly because in the past CAS has added local features to the tape management code by modifying code shipped by the vendor. However, because in release 5.2 the vendor ships only operational code and not source code, CAS can no longer modify the code. Features in the tape management sustem running on MVS which were locally written will not be available on OS/390.

This document gives a brief overview of tape management and then outlines changes between the current release containing local code and the new release running on OS/390. You should look through this document before running jobs on OS/390 to see if you need to make any changes.

A brief overview of tape management

Using JCL to say how long you want to keep a tape

You 'check out' a tape or make it yours the first time you write on it. The tape will be in your control for a time specified by you either by taking the default ownership period of 7 days, by using the JCL parameters EXPDT= or RETPD=, or by providing a pattern data set from which the expiration date is copied. When using EXPDT= you may provide real dates or one of five reserved dates, called 'keyword dates', which have special meanings to the tape management system. The meaning of keyword expiration dates set by EXPDT= are:
```
  99000 - keep tape as long as data set is cataloged in the MVS
          system catalog
  98000 - non-resident (formerly called alien) tape from outside
          SMC library
  99ccc - keep the most recent ccc cycles of this data set name
  99365 - keep this tape permanently
  98ddd - keep tape ddd days after last used
```
There are two possible meanings for all dates in 1998-1999: 1998/041 could be interpreted as a real date (the 41st day of 1998) or a keyword date (keep the tape 41 days after last used). Therefore the tape management system observes the convention that it will consider the date you provide in EXPDT= as a keyword date UNLESS you provide an override. The override in the current release is a TMNOKEY DD statement in the step. The presence of a TMNOKEY DD statement tells the tape management system not to interpret all EXPDT= dates in the step as keyword dates. EXPDT=98041 will be interpreted as the keyword 41 days-since-last-used if you don't include a TMNOKEY DD statement and the real date of the 41st day of 1998 if you do.

A keyword override is also necessary for any tape whose expiration date is set by RETPD=, when the computed expiration date falls in 1998 or 1999. In the current release you must put a TMNOKEY DD DUMMY statement in any step which contains a RETPD= tape. (You can continue to use TMNOKEY in release 5.2 but the 'new features' section later in this document describes how you can replace the step-level TMNOKEY override with a more flexible DD-card-level override.)
Using utilities to report on or update information about tapes

Information about tapes is kept in a tape management catalog, which is separate from the MVS system catalog. This information is used by the tape management system to enforce tape ownership and security. Several utilities are available for querying the tape management catalog about your tapes or for updating information about them (such as changing the expiration date.)

Using TMS 5.2 on OS/390

Most JCL for reading/writing tapes runs unchanged

Protection of tape data sets is based solely on RACF protection of the data set name. Although the old method of protecting tapes with passwords is gone, you needn't change JCL because JCL which used the TMSDSS DD data set to manipulate passwords will be ignored. You should use data set names for your tape data sets (like those which you use for disk data sets) which are protected by RACF. Usually this means the high level qualifier will be Jnnnnnn, where nnnnnn is the account code of your office.

Jobstreams which include UCCGRW require change:

The batch utilities UCCUPDTE, UCCBINQ and UCCGRW have been replaced: see later section on tape utilities for how to accomplish the same tasks. (nb. Testing indicates that while UCCGRW does not work and must be replaced, UCCUPDTE seems to work and UCCBINQ displays tape information except for TACCT, JPGMR and JPROJECT.)

Some utilities for managing tapes have changed

TAPELIST
The page headers for TAPELIST have changed slightly. You should check any programs or CMS execs which depend on the format of the header pages.
UCCBINQ and UCCUPDTE are replaced by ISPF TIQ
If you now use batch programs UCCBINQ and UCCUPDTE to display and update tape records you must change to the online utility TIQ, which is on the ISPF Local panel. The password field on the initial screen is 'INQ' for inquiry and 'UPD' for update. You may update the EXPDT and COMMENT fields for tape records which have data set names for which you have RACF UPDATE authority.
the COMMENT field
You can no longer use the TMSDISP DD card to put information in the COMMENT field of a tape record. You must use ISPF TIQ instead. Unfortunately, TIQ only works for a previously written tape; we no longer have the ability to put information in the COMMENT field at the time you check a tape out. Existing JCL with a TMSDISP DD card for the COMMENT field will be ignored.
The batch reporting program UCCGRW is replaced by EARL or by TMSGRW. TMSGRW is very much like UCCGRW except that it does not automatically limit its report to tapes on the account code where the job is run. Your current UCCGRW jobs will run as before if you change EXEC UCCGRW to EXEC TMSGRW and add to your control cards
```
 in the CONTROL section:  DEFINE vblname HX 'nnnnnn' where
                          nnnnnn is the account code you want to
                          select for.  'nnnnnn' must be 6 numeric
                          digits.
 in the PROCESS section:  WHEN TACCT NE vblname REJECT
```
The vendor says that the TMSGRW program is frozen at its current level and recommends you use the reporting program Earl. You must change the format of your input to use Earl. The vendor's documentation of Earl is available on the Enterprise Systems Team's Bookmanager server.

The pseudo-label in JES2 JOB LOG section of batch output is gone

A label-like set of informational messages showing the volser, data set name and other information about a tape will no longer be printed in the JOBLOG section of your batch job at the time a tape is first written on. You will still have most of the information in the IECTMS9 and IEC705I messages in the JOBLOG section.

There are a few changes in checking tapes out-of-area

If you check a tape you have used in your job out-of-area by including a TMSDISP DD data set in the last step of a job as in this example:
```
  //OUTTAPE1 DD DSN=NEWTAPE,UNIT=TAPE,....
  //TMSDISP DD *
  OUTTAPE1XF OUT=USER,John Smith;BINS
  1.......9...
```
where USER is the outcode, John Smith is the username and BINS is the deliveryid, release 5.2 will display the username/deliveryid information for the operator but will no longer store the information in the COMMENT field for the tape or print it on the gummed label.
If you now check already-existing tapes out-of-area by changing the outcode using the batch utility UCCUPDTE, you should changed to use the batch program TMSDISP. Notice that although the program TMSDISP is new and is different from the DD card TMSDISP discussed above, the syntax of the input is almost the same. For the DD card TMSDISP the TMS locates tape volume information from the ddname you provide; for the program TMS uses the data set name on the DSN= input statement you provide to query the MVS system catalog for the volume serial of your tape. Therefore the 'ddname' in columns 1-8 in the following input statement can be any characters.
```
  //CHECKOUT PGM=TMSDISP
  //TMSDISP  DD *
  DSN=J1234.MY.DATA.SET,LABEL  <- ',LABEL' is required
  ddname  XF OUT=USER,John Smith;BINS
  1.......9...                 <- exact columns required
```
Notice that the TMSDISP program only works for data set names catalogued in the MVS system catalog; if you want to check out of area a tape whose data set name is not in the system catalog you must ask the tape librarian to do it.

New features may make tape management easier
1. ISPF TIQ
  You may use the Tape InQuiry program, found on the ISPF local panel, to display and update tape information. When you start TIQ you must provide a password, which is INQ to display tape information and UPD to update information and to use the utilities which update tape information.
  
  Option 2, 'utilities', allows you to expire or to reset or extend the expiration date for any tape with a data set name you have RACF UPDATE authority for. Option 1,'display/update', allows you to update the comment field or the expiration date if you have RACF UPDATE authority for the data set name.
  
  If your tape data set name is NOT protected by a RACF profile then you must be connected to the RACF group under which the tape is held to be able to update the record of a tape. For example, a data set named MYTAPE is not protected by a RACF profile, so only users connected to group J1234 can update the record of a tape with data set name MYTAPE created by a job running on account J1234.
  
  You can see more information about TIQ at
  http://utkvm1.utk.edu/tiq.html
2. An additional JCL parameter, ACCODE, can now provide keyword/real date interpretation overrides on an individual tape basis, so that you have a way of making the expiration dates of multiple tapes created in one step be interpreted differently. This is more flexible than the TMNOKEY override which applied to all tapes in a job step.
  
  ACCODE is documented in IBM JCL manuals as 'an accessibility code for ansii labeled tapes... which is ignored for standard label (SL) tapes', but if you include it for the standard label (SL) tapes you normally use, the tape management system will use the value you use for ACCODE as an expiration date indicator. The values of ACCODE TMS honors are:
```
ACCODE=xCAEXPDT - the value specified by EXPDT=
                  is a true expiration date and not
                  a keyword
ACCODE=xCAKEYWD - the value specified by EXPDT=
                  is a keyword
ACCODE=xCACATLG - same as EXPDT=99000: keep
                  while cataloged
ACCODE=xCANORES - same as EXPDT=98000: non-resident
                  or alien tape
ACCODE=xCAPERM  - same as EXPDT=99365: keep
                  permanently
```
  where 'x' can be any character
  examples:
```
ACCODE=ZCACATLG - keep a tape while its data set name is cataloged
  in the MVS system catalog
EXPDT=98335,ACCODE=ZCAEXPDT - keep the tape until Dec.1,1998 (the
  ACCODE value says interpret the EXPDT value as a real date)
EXPDT=98338 - keep the tape for 338 days after last used
```
  A special note on using RETPD= : When you set a tape expiration date using RETPD= you should also include either the step-level DD card TMNOKEY or the DD card parameter ACCODE=ACAEXPDT to get a good expiration date.