MODET

Control‑M/Tape global operation mode.

• Mandatory

Valid values are:

• TEST – Control‑M/Tape is working in test mode. Information is recorded in the Media Database, but Control‑M/Tape does not intervene in any way, that is, prompts are not issued, data sets that have not expired are not protected, mount messages are not modified, and so on. Default.
• PHASED – Control‑M/Tape is working in production mode parallel to other tape management systems.
• PROD – Control‑M/Tape is working in production mode, that is, data sets that have not expired are protected, mount messages are modified, and so on.

DYNINTR

Whether Control‑M/Tape dynamically creates operating system interfaces during Control‑M/Tape initialization.

• Mandatory

Valid values are:

• Y – Operating system interfaces are dynamically created during initialization and removed upon termination. Default.
• N – Control‑M/Tape does not dynamically create operating system interfaces during initialization. It is necessary to perform the static installation as described in Step 7.2 – TLPE Static installation (optional)).

DYNSVC

Whether Control‑M/Tape dynamically defines its SVC during initialization.

• Mandatory

Valid values are:

• Y – Control‑M/Tape dynamically defines its SVC during initialization and removes it upon termination. Default.
• N – Control‑M/Tape does not dynamically define its SVC during initialization. How to define the SVC is described in Step 6 – Control-M/Tape SVC installation.

SVCNUM

Control‑M/Tape SVC number.

• Mandatory
• Valid values are: 200 through 255
• Default: 242

Note: Find an available SVC number for Control‑M/Tape. Various products, such as OMEGAMON, LOOK, and RESOLVE, enable identification of available SVC numbers.

TSSALLOC

The action to be performed by Control‑M/Tape if the Control‑M/Tape subsystem is not yet defined in the operating system.

• Mandatory

Valid values are:

• Y – If the CTTH subsystem does not exist, Control-M/Tape automatically creates one. Default.
• N – If the CTTH subsystem does not exist, Control-M/Tape fails during initialization.

SMSINTR

Whether to activate the Control‑M/Tape to DFSMS interface. For details, see the organization and administration chapter of the Control‑M/Tape User Guide.

Valid values are:

• Y – Activate the Control‑M/Tape to DFSMS interface.
• N – Do not activate the Control‑M/Tape to DFSMS interface. Default.

If YES is specified for the SMSINTR installation parameter and the current data set is managed by DFSMS, the STKUNIT parameter is ignored for this data set and the data set is dynamically stacked only if it belongs to a storage group whose type is TAPE. For information about stacking DFSMS data sets, see the organization and administration chapter of the Control‑M/Tape User Guide.

PARALLEL

Whether Control‑M/Tape version 7.0.xx is to work in parallel with another version of Control‑M/Tape. Version 7.0.xx can either be run as the primary Control‑M/Tape (the default), meaning in production mode, or as a secondary Control‑M/Tape, meaning in test mode.

• Mandatory

Valid values are:

• N – No other version of Control‑M/Tape should be run in parallel with this Control‑M/Tape. Default.
• S – Run the current Control‑M/Tape as the secondary Control-M/Tape while another Control‑M/Tape installation is running in PROD mode.

For information about how to run two Control‑M/Tapes in parallel, see the INCONTROL for z/OS Installation Guide: Upgrading.

ABENDACT

Enables user to abend jobs that were started while Control‑M/Tape was down. When an active job uses a tape, Control‑M/Tape checks whether Control‑M/Tape was active from the beginning of the job.

Mandatory

Valid values are:

• Y – jobs that were started while Control‑M/Tape was down are abended. Default.
• N – jobs that were started while Control‑M/Tape was down are not abended

Note: You cannot currently use ICE to set a value for the ABENDACT parameter. You can only set this parameter value after installation, by manually editing the CTTPARM member in the IOA.PARM library.

HCHECKT

Whether Control-M/Tape should employ the IBM Health Checker interface to control the functionality of Control-M/Tape vital components.

Valid values are:

• Y – Health Checker interface is enabled. Control-M/Tape will communicate with IBM Health Checker. Default.
• N – Health Checker interface is disabled. Control-M/Tape will not communicate with IBM Health Checker.