Utilities › TMSXTEND Utility—Dynamic TMC Extend Process Control Program › Control Statement Specifications › Control

Control

Control statements for the SYSIN DD statement

Note: The control statements are parsed thru column 80. Do not use sequence numbers on these statements in columns 73 - 80.

ADDDSNB nnnnnnn

Requests that nnnnnnn additional DSNB records be added to the new TMC.

ADDVOL

Lowvol-Highvol DEN=nn ROBTY=nn TRTCH=nn VENDOR=cccccccc DELETE specifies that the volume range lowvol-highvol be added to the new TMC. Optional parameters are provided to initialize the volume records with a density (DEN), robot type (ROBTY) recording technique (TRTCH) and vendor (VENDOR). For the DEN, ROBTY and TRTCH parameters, nn should be replaced with hexadecimal values. For a list of these values see the Programming Guide. The DELETE parameter simply indicates the volume(s) are added in DELETE status in the new TMC. VENDOR is an 1-8 character string that is used to identify the media manufacturer. In addition to a range, a single VOLSER may also be specified on the ADDVOL statement.

Notes:

• The dash ("-") is required between lowvol and highvol.
• VOLSERs shorter than six characters are supported. They are left justified and padded with blanks. The volumes added will be in SCRATCH status if you do not use the DELETE keyword in the control statement.

REMDSNB nnnnnnn

Requests that nnnnnnn free DSNB records be removed from the new TMC. Only DSNBs from the end of the free chain that have never been used can be removed.

REMVOL lowvol-highvol

Specifies that all volumes in the range lowvol-highvol be removed from the TMC. All volumes in this range must be in DELETE status, otherwise the entire range is not removed. A single VOLSER may also be specified on a REMVOL control statement.

UNIQUE_RNAME=[YES|NO]

Specifies if UNIQUE_RNAME is used with this TMC. If you want to code this statement, code it as the first statement in the SYSIN DD.

Control statements for the CPULIST DD statement

When all systems sharing the TMC have tape processing performed on them at least once a day, there is no need for any CPUs to be included in the CPULIST control statements. However, if there are some CPUs that have NO tape processing performed on them, or when the tape processing is very sporadic that can go for days at a time without any tape processing, it would be recommended to use the INCLUDE type of CPULIST control statement.

The EXCLUDE control statement should only be used when there is a CPU that shares the TMC AND that CPU will not be active when TMSXTEND is running AND that CPU is 100% guaranteed to be at the correct maintenance level applied. If that CPU will be active, but there will not be any tape jobs running on it, it should not be excluded using the EXCLUDE control statement.

You cannot exclude the CPU that TMSXTEND is running on itself. If the SMF ID of the CPU that TMSXTEND is running on is listed on the EXCLUDE statement, it will be automatically included and shown as forced on Report-81.

INCLUDE smf id

This control statement defines the SMF ID of a system running CA 1 that should be included in the list of systems to process when performing an extend function. INCLUDE must begin in column 1 followed by a blank and then the SMF id. Only one SMF id may be specified per control statement.

EXCLUDE smf id

This control statement defines the SMF ID of systems running CA 1 that should be excluded from processing by TMSXTEND. EXCLUDE must begin in column 1 followed by a blank and then the SMF id. Only one SMF id may be specified per control statement. Note that failure to find a system specified on an EXCLUDE statement is not considered an error.

Comments identified by an asterisk in column 1 may be specified in both CPULIST and SYSIN DDs but are not listed in any report.