Previous Topic: Status in TAPE DATABASE MessagesNext Topic: User Exit


TLMSNITT - Initialize Tape Volumes

TLMSNITT initializes tape volumes as SL, NL, or AL. TLMSNITT checks the VMF and the tape label to verify your request to initialize a tape volume.

Important! Nonlabeled tapes and tapes not written to can still be initialized.

Standard OPEN and CLOSE are issued to process the tapes. SMS, CA Top Secret Security, RACF, CA TLMS, and any other components or products receiving control during OPEN and CLOSE processing may be invoked.

For any tape cartridges where a VOL1 record is present (this includes AL and SL labeled tapes), the volser is obtained from the tape. For round tapes, the VOLSER can be obtained only when the tape is known to contain data (OLDTAPE), since any attempt to read a blank tape causes the drive to search the entire reel for data. In all cases (except where the hardware indicates the tape contains no data), when a VOLSER cannot be obtained from the tape, you are prompted to provide one. To determine if the mounted tape is valid for initialization, the status of the obtained VOLSER in the VMF, the input command (INTAPE, NEWTAPE, OLDTAPE or OUTTAPE), and user exit (if any) will be checked.

TLMSNITT opens tapes with BLP input. Some security packages software protect the device if the user does not also have BLP write authority to issue a CCW = x'7782??80'. This CCW causes the device to treat the tape as write protected resulting in a write protect error message from TLMSNITT. In the case of when the user does not have BLP read authority, the system (without any indication or warning) treats BLP as NL. This can manifest itself either by successive mount/dismounts when the tape is blank or unreadable or in CAT9702P messages. TLMSNITT must be executed under a USERID which has read/write BLP authority.

The method of volume verification for TLMSNITT differs depending on the request and type of device. The overriding rule is that the operator is prompted any time the TLMSNITT cannot obtain sufficient information from the device to ensure that a 'live' tape is not being over written. The procedure differs depending upon whether the tape is being opened for input or output. Cartridges are always opened for input; reels are opened for output unless OLDTAPE is specified (opening up a blank reel for input will scan off the end of tape for data).

When a tape is opened for output with BLP, TLMS intercepts the open and issues a CAT9702P WTOR. It prompts you for the volser of the mounted tape to ensure that a live tape is not over written. Once a tape is opened for output, closing it results in an end-of-file mark which destroys data. When OLDTAPE is specified for a reel, you indicate that the tape contains data; thus, the tape can be opened for input and the software can attempt to read an 80 character VOL1 record from the tape. If this read is successful, then the software determines the true volser of the tape and the VMF is checked to ensure that this is not a live tape. If there is no VOL1 record (NL) on the tape, TLMS issues a CATLTN01 WTOR. When a cartridge is processed, the device recovers from attempting to read a blank tape (new, not erased) and provides sense data from the device to indicate that this is a blank tape not a live tape and issues no verification message. In most cases, when attempting to read a valid tape which cannot be processed by this device (such as a 3480 with a 36 track tape), the device returns the volser in the format 24 sense data and the VMF can be checked using this volser without your intervention. In all other cases when an error occurs attempting to read the VOL1 record (such as may be the case with a bulk erased tape) or no VOL1 record is present, TLMS issues a CATLTN01 WTOR.

TLMSNITT uses both BLP and 98000 processing. Therefore, the proper security access must be set up to run TLMSNITT. When the process updates a VMF record, the data set name and other information appears as if a temporary data set was written by program TLMSNITT. This always leaves the volume in scratch status and available for reuse.

CA TLMS must be active to run TLMSNITT.