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

Normal autodetect

COR detects other products and switches itself off if none are found

Enable without products

COR remains active, even if no other products are detected

Disable all

COR switches itself off and disables any other active products

You can use a System Coordinator daemon to enable "single-seat" display of session activities in any client job. To enable a client job for this feature, specify:

• The group in which the daemon runs. When you choose to make these statistics available externally a daemon is required. During periods when the daemon is unavailable (planned or unplanned outage) statistics are unavailable.

• The frequency at which statistics are pulsed to the daemon:

  • Every nnnnnnn Adabas calls and/or

  • Every nnnnn seconds

Set both to zeroes to disable the refresh.

The statistics are held in shared memory, so you must configure your daemon to use shared memory (refer to the section Daemon latency/activity services for information on configuring the daemon to use shared memory).

Note:
For dynamic transaction routing (DTR) systems (CICS/MRO, CICS/PLEX, IMS/TM, UTM) you must always specify a group, even if you do not want to make use of "single-seat" activity displays. This is because the System Coordinator daemon is also responsible for managing DTR client sessions while they are at rest.

Indicates whether or not the client job should issue information messages when it connects (message COR060I) or disconnects (message COR061I) from the daemon.

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

This parameter is only applicable to runtime controls of type CICS and CICS/DTR and specifies whether or not the System Coordinator client environment runs in CICS threadsafe mode.

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.

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.

Specifies a number of seconds after which response code 9, subcode 79 will no longer be returned to re-activated sessions that were previously timed out. 0 means that response code 9, subcode 79 is always returned to sessions that were previously timed out, no matter how much time has passed since they were timed out.

Y|N (enable or disable RSP009/79 setting)

0-nnnnnnnnnn (time limit for setting RSP009/79

Y

0

Specify where context information is stored when sessions are at rest. For standard jobs (local mode, the default) all context usually resides in local memory. Specify Y for Latency – Local. In CICS jobs, a temporary storage queue is used to expedite context operations and you can specify a prefix for that queue.

Note:
If you use the Client Versioning feature, be sure to specify a different prefix for each System Coordinator version active in the CICS job.

Daemon latency is normally used by dynamic transaction routing (DTR) systems (CICS/MRO, CICS/PLEX, IMS and/or UTM). These options require the job runs with a local daemon. For these jobs, Y is enforced for Latency – Daemon. You can additionally choose whether or not context information is written to disk to provide crash-recovery. If you choose not to write to disk, the information is stored in shared memory if the daemon is configured to use shared memory or in daemon local memory if the daemon is not configured to use shared memory. Shared memory provides better performance.

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).

Indicates where messages are written.

If you elect to use a DDMSG file, you must select "Forward to the Daemon DDMSG file" for TP systems because sequential files are not suited to TP.

If you select "Local DDMSG file" for batch type systems, you must add the Adabas load library to the job’s loading environment.

The DDMSG file should be defined as fixed records of length 133, with an appropriate blocksize. It is possible that operating system factors (such as blocking, caching) may cause messages not to be seen until the job terminates.

Console message job log
Local DDMSG file
Forward to the Daemon DDMSG file

Allows automatic retry of Adabas commands that receive the specified response codes. You can also

• restrict retry to particular sub-codes

• restrict it to certain database ids and file numbers

• specify the number and frequency of retry attempts

• specify whether or not command retry should cause a console message to be issued

• specify whether or not retried commands should be shown to user exits

• in-memory trace size

• trace collection

• dynamic tracing options for capturing non-zero response codes

Specify the virtual address and size of the common memory pool for this UTM service.

Pool address, this fixed address will be used by both the System Coordinator daemon and all the jobs in this UTM service.

Size(mb)

Indicates whether or not a disk file is used by daemons in this group to provide full crash recovery for client sessions.

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.

Indicates where messages are written for databases.

The DDMSG file should be defined as fixed records of length 133, with an appropriate blocksize. It is possible that operating system factors (such as blocking, caching) may cause messages not to be seen until the database terminates.

Console message job log

Local DDMSG file in the database job

Indicates where messages are written for daemons.

The DDMSG file should be defined as fixed records of length 133, with an appropriate blocksize. It is possible that operating system factors (such as blocking, caching) may cause messages not to be seen until the database terminates.

Console message job log

Local DDMSG file in the daemon job

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

Setting this to Y causes the daemon to intercept failures, react by automatically terminating and restarting the appropriate component(s) and then continuing.

Setting this to N causes the daemon to react to a failure by terminating.

Shared and local memory limits for holding activity display and latent session information and optional dataspace name.

Note that the daemon only uses local memory for latent session information. If you want to enable "single-seat" display of client job activities, you must define a shared memory maximum size. Shared memory minimum size and dataspace name are optional.

0 - 2097151

Valid dataspace name

Size of in-memory trace buffer

Whether to use a trace file

Whether to go back to the beginning of the trace file when it fills

Name

The fixed address will be used by both the System Coordinator daemon and all the jobs in this UTM service.

Size(mb)