Job Control Statements

Utilities › TMSTPNIT Utility—Initialize Tape Volumes › Report Description › Job Control Statements

Job Control Statements

//stepname EXEC PGM=TMSTPNIT
//             [,PARM='[DATEFMT=(fmt)][,TEST][,VERIFY=(opt)]']
//STEPLIB  DD  DSN=CAI.CTAPLINK,DISP=SHR
//* NOTE - THE ABOVE LIBRARY MUST BE IN IEAAPFxx or PROGxx
//SYSPRINT DD  SYSOUT=A
//LABELDD  DD  UNIT=(tape,,DEFER)
//SYSIN DD  *
(control statements here)
/*

Parameter Definitions

DATEFMT=(fmt)

Specifies the date format to be printed on TMS Report 41. The date pattern indicated by (fmt) is limited to 10 bytes and must be enclosed in parentheses. This parameter is optional. For more information on valid date formats, see Overriding the Preferred Date Pattern.

TEST

The TEST parameter allows you to simulate the execution of TMSTPNIT without actually modifying the contents of the tapes or the TMC. This can be done with or without operator intervention. Operator intervention is determined by the presence of a DD card for LABELDD. (In round tapes, the operator intervention can occur only when the OLDTAPE command is requested. This is because of problems opening a blank round tape for input.)

When there is no LABELDD DD statement present, no operator intervention is required and console messages are kept to a minimum. Control statements are read, checked for syntax and valid operands. The SER operand is checked against the contents of the TMC (except when OUTTAPE is specified), and the user exit is called.

When the LABELDD DD statement is present in the JCL, the requested tapes are actually mounted (except for round tapes which are not mounted unless OLDTAPE is specified) and additional edits are performed using the label information contained on the tape. All console messages including those requiring responses are issued.

VERIFY=(opt)

The VERIFY parameter determines when, and if, label verification messages are issued for cartridges. It is valid for all cartridges, ignored for reels unless the OLDTAPE command is used, and not applicable when the test option is specified without a DD card for LABELDD. The verify command can have one of the following values:

ERROR: (Default) - the CAL0TN01 message is issued only for tapes not containing a VOL1 record (NL).
CHANGE: The CAL0TN01 message is issued whenever a tape containing data is having its VOLSER changed or for tapes not containing a VOL1 record (NL), *NL*.
ALWAYS: A CAL0TN01 message is always issued. Reels will always display '******' for the VOL1 record's volser if OLDTAPE is not specified. For example, no attempt is made to read the VOL1 record. New tapes will display '*NEW*' for the VOL1 record's VOLSER (cartridges only, OLDTAPE is not valid for new reels and will run the tape off the end of the reel if specified for a never used tape).
ABEND: Task will abend after issuing a CAL0TN02 or CAL0TN03 message without waiting for an operator response.
ROBOT: Operator is not prompted for volume verification (CAL0TN01 message) for NL tapes.

JCL Considerations

LABELDD: This defines the tape drive that is used to initialize volumes.
tape: Specifies a tape device used to initialize tape volumes. The DEFER keyword is required.

Completion Codes

Possible completion codes and their meanings are listed below.

0

Successful completion.

4

Successful completion with operator intervention. For example, a live tape was mounted for initialization, it was rejected and a valid tape was mounted and successfully initialized. Another example would be a write-protected tape was mounted, rejected, and non-write-protected tape was mounted and successfully initialized. You should check the console log for specifics.

8

All tapes were not successfully initialized. For example, a specific SER was not in the TMC or had the wrong status. You should check the TMS Report 41 (and possibly the console log) for specifics.

12

Invalid input, such as a syntax error or invalid JCL parameter. You should check the TMS Report 41.

16

Missing DD statement.

Note: The return code is the highest code encountered, and does not preclude the existence of errors having lower return codes, (RC=12 does not mean that there were no errors that would not have produced an RC=8). For example, if you receive an RC=8 you should also check the console for RC=4.