Parameter Types

For a batch job, or a standard (single-job) TP monitor, this is the name of the job. If the value ‘*’ is specified, the control will be used for all jobs that do not have a specific control defined.

For a multi-job TP monitor service, this is a unique name for the service. Individual jobs within the service are defined as Service Member Names, using the runtime control Expand function.

The name of a job that runs as part of a multi-job TP monitor service. This control is maintained with the runtime control menu Expand service.

Indicate operation mode for COR

Auto-Detect

Enable COR even if no products

Disable all products including COR

This parameter is used to determine the approximate size of the Adabas System Coordinator user pool where

• type "a" represents batch, TSO, CMS, and TIAM jobs

• type "b" represents Com-plete, CICS, CICSplex, IMS, and UTM jobs

type a: 2
type b: 1000

Indicates whether controls can be dynamically overridden at runtime via a customised API call to COR.

Determines the initial size of all fixed memory pool extents managed by the Adabas System Coordinator.

Enables calling of additional installation exits (IEXIT1, IEXIT2) before and after the Adabas command. Refer to Before You Install in the Installation section for information about installing additional exits.

The group name of a System Coordinator daemon that is to manage the job.

Indicates a time limit after which terminal sessions are eligible for timeout termination if no activity has occurred.

Indicates a time limit after which non-terminal sessions are eligible for timeout termination if no activity has occurred.

Indicates a time limit for sessions that are timed out to receive response code 9, subcode 79 if they are re-activated.

Y|N (enable or diasble RSP0009/0079 setting)

0-nnnnnnnnnn (time limit for setting RSP0079/0009

Y

0

Used to define up to 256 bytes of alphanumeric data, which is stored with the runtime control definition and may be retrieved at runtime using the site information API.

Used to define runtime overrides of the basic control for the job. After definition the override can be modified with the Modify menu option.

Depending on Job Type, Stepname, Login or Transaction overrides can be defined.

Indicate whether session cleanup is required when a session override is activated (Cleanup at Start) or deactivated (cleanup at End).

The identifier for a daemon group.

In a sysplex environment, this is the XCF group name.

The router (SVC) number that is used for communicating with the group. This must be the same in all parts of a cluster.

Type of coordination to be performed by the daemon group

Possible values are:

• Single: A single system is to be coordinated.

• Multi - XCF: Multiple systems are to be coordinated with no dynamic transaction routing support across the systems. XCF is used for cross-system communications.

• Multi - Net-Work: Multiple systems are to be coordinated with no dynamic transaction routing support across the systems. Entire Net-Work is used for cross-system communications.

• Sysplex: Multiple systems are to be coordinated with dynamic transaction routing support across the systems.

Single
Multi-XCF
Multi-Net-Work
Sysplex

The name of the coupling facility cache structure defined in the installation process. This name is only required when using a sysplex environment.

Indicates whether or not automatic pool recovery is to be in effect. Automatic pool recovery ensures that, should a Adabas System Coordinator daemon fail for any reason, existing client sessions will continue to operate. When the daemon is restarted, it will recover the user pools from the failing daemon.