Daemon Runtime Parameters

#### Search Results

Search

# Daemon Runtime Parameters

The following parameters can be entered using DDCARD input. The PRODUCT parameter is mandatory. All other parameters are optional.

Parameter | Usage
--- | ---
CT | Command timeout limit.
DSPSCOPE | Specify the type of dataspaces used by Adabas System Coordinator and Adabas Fastpath.
ENCRYPTION | Support encrypted daemon datasets.
FORCE | Overwrite ID table entry.
LOCAL | Define an isolated daemon.
LU | Length of intermediate user buffer.
MPMWTO | Display information messages.
NABS | Number of attached buffers.
NC | Number of command queue elements.
NXC | Number of sysplex command queue elements
PRODUCT | Identify the services to be made available. Mandatory.
START– Cold start feature | Delete shared memory from previous execution.
ZIIP | Activate zIIP support for the System Coordinator Daemon.

## CT – Command Timeout Limit

Parameter | Use | Mimimum | Maximum | Default
--- | --- | --- | --- | ---
CT | The maximum number of seconds (more precisely, units of 1.048576 seconds) that can elapse from the time a daemon request is completed until the results are retrieved by the sender through the interregion communication. | 1 | 16,777,215 | 60

This parameter is used to prevent a request queue element (RQE) and attached buffer from being held indefinitely when a user with an outstanding request terminates abnormally.

Possible causes of a command timeout are

- address space is swapped out or cannot be dispatched;

- the task is cancelled or ABENDed;

- the task has low priority in a high-activity system.

## DSPSCOPE – Dataspace Scope

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
DSPSCOPE | Specify the type of dataspaces used by Adabas System Coordinator and Adabas Fastpath. | ALL | COMMON | ALL

From z/OS 2.4 and above, DSPSCOPE must be set to ALL to enable the continued use of dataspaces due to z/OS enforcing the DIAGxx parmlib statement ALLOWUSERKEYCADS(NO).

This parameter is used by:

- The Adabas System Coordinator daemon when it is defined to use a dataspace for its shared memory latency/pulse services (refer to Daemon latency/pulse services).

- The Adabas Fastpath buffer when it is defined to use a dataspace (refer to the Dataspace Name Adabas Fastpath buffer parameter).

#### Important Note:

The following fixes must be applied and active in all components (client, daemon, database) across all systems (LPARs) before the use of `DSPSCOPE=ALL` is considered for any daemon within a group involving those systems:

Product | Version | Fix Number
--- | --- | ---
Adabas System Coordinator | 8.6 SP1 | None
8.3 SP1 | MI831003, MI831004
Adabas Fastpath | 8.6 SP1 | None
8.2 SP2 | AW822058

## ENCRYPTION - Activate Support for Encrypted Datasets

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
ENCRYPTION | Specify whether to activate support for encryption. | YES | NO | NO

The `ENCRYPTION` parameter controls whether the Adabas System Coordinator Daemon supports encrypted datasets.

Note
At ADA85 encryption requires the Adabas Encryption (AEZ) modules from the AEZ load library to be included in the Adabas System Coordinator (COR) Daemon STEPLIB concatenation above the Adabas modules. At ADA86 and above the Adabas Encryption modules are included in the Adabas load library. Adabas Encryption requires its license module (AEZLIC) or file (DD-name DDLAEZ). If `ENCRYPTION=YES` and the AEZ license are missing or invalid, the COR Daemon will refuse to start.

If `ENCRYPTION=NO` is specified (the default), the Adabas System Coordinator Daemon does not support encrypted datasets. In this case, if a dataset is encrypted, the Adabas System Coordinator Daemon will terminate with an error when it attempts to open the dataset.

Setting `ENCRYPTION=YES` is required if one or more of the datasets accessed by the Adabas System Coordinator Daemon are encrypted (such as the Adabas Transaction Manager TMRFI recovery file).

If multiple daemons share an encrypted dataset in a group, then `ENCRYPTION` must be set to `YES` for all daemons in the group.

## FORCE – Overwrite ID Table Entry

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
FORCE | Specify whether or not this daemon is to force an entry into the active node list. | YES | NO | NO

Possible values:

- `FORCE=YES`: Force an active entry, if one is available.

  `FORCE=YES` is usually not required. However, it may be needed if the previous daemon session ended abnormally, leaving the old entry in the active node list. Use this setting carefully.

- `FORCE=NO`: Causes an error if the node used by this daemon already appears in the active node list.

## LOCAL - Define an Isolated Daemon

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
LOCAL | Specify whether or not a daemon is to be isolated from other Entire Net-Work nodes. | YES | NO | NO

Possible values:

- `LOCAL=YES:` Isolates this daemon from other Entire Net-Work nodes.

- `LOCAL=NO:` The daemon can receive calls from other Entire Net-Work nodes.

## LU – Length of Intermediate User Buffer

Parameter | Use | Mimimum | Maximum | Default
--- | --- | --- | --- | ---
LU | Set the size of the intermediate user buffer area. | 4000 | 65,535 | 65,535

The size specified must be large enough to accommodate all control information for commands passed to the node.

An error occurs if the `LU` parameter specifies a value greater than the byte count implied by the `NAB` parameter. If you change either parameter value, you may have to change them both.

## MPMWTO – Display Information Messages

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
MPMWTO | Specify whether or not to display information level (l-level) messages. | YES | NO | NO

By default, information level (I-level) messages are suppressed.

## NABS – Number of Attached Buffers

Parameter | Use | Mimimum | Maximum | Default
--- | --- | --- | --- | ---
NABS | Specify the number of attached buffers to be used. | 0 | 500,000 | 16

An attached buffer is an internal buffer used for communication with the daemon.

For Adabas System Coordinator, this is an optional parameter that defines the number of attached buffers to be used for receiving requests from clients or from other daemon peers.

An attached buffer pool is allocated with a size equal to the value of the `NABS` parameter multiplied by 4096 bytes.

## NC - Number of Command Queue Elements

Parameter | Use | Mimimum | Maximum | Default
--- | --- | --- | --- | ---
NC | Set the maximum number of command queue elements. | 20 | 32,767 | 100

The maximum number of command queue elements (CQEs) that can be processed simultaneously by this daemon.

## NXC - Number of Sysplex Command Queue Elements

Parameter | Use | Mimimum | Maximum | Default
--- | --- | --- | --- | ---
NXC | Set the maximum number of queue elements in the sysplex messaging command queue. | 1 | 4096 | 256

This parameter is used only for multi-system daemons using XCF messaging, or for full Parallel Systems daemons using dynamic transaction routing (DTR). Although the default value will be sufficient for most sites, the number will dynamically expand as required when there is a high volume of XCF messages.

## PRODUCT - Identify the Services to be made Available

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
PRODUCT | Specifies which product services are to be made available by Adabas System Coordinator: AAF: Adabas SAF Security AFP: Adabas Fastpath Asynchronous Buffer Manager ATM: Adabas Transaction Manager AVI: Adabas Vista daemon component DTR: Dynamic Transaction Routing Service | AAF AFP ATM AVI DTR | none

This parameter is used once for each service that is to be made available by the daemon.

Possible values:

- `PRODUCT=AAF`:

  Enable the daemon services necessary to support Adabas SAF Security for the protection of online administration of COR-based Add-on products.

- `PRODUCT=AFP`:

  Enable the daemon services necessary to support the Adabas Fastpath Asynchronous Buffer Manager. This is mandatory for sites using Adabas Fastpath.

- `PRODUCT=ATM`:

  Enable the daemon services necessary to support Adabas Transaction Manager. This is mandatory for sites using Adabas Transaction Manager.

- `PRODUCT=AVI`:

  Enable the daemon services necessary to support Adabas Vista daemon-managed jobs such as those defined to use activity pulsing or those defined to run in dynamic transaction routing systems (eg. CICS/MRO, CICS/PLEX, and IMS).

- `PRODUCT=DTR`:

  Note
  `PRODUCT=DTR` previously replaced `PRODUCT=CAS` but parameter support for `PRODUCT=CAS` has been retained for backward compatibility.

  This is an optional dummy parameter used simply to identify that dynamic transaction routing systems (eg. CICS/MRO, CICS/PLEX, and IMS) are being managed by this daemon.

## START– Cold start feature

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
START | Normally, the daemon inherits and reuses shared memory allocations from a previous execution. Specify `START=COLD` to skip this recovery processing. Note `START=COLD` is normally only used when advised by support to avoid start-up problems related to auto-recovery from previous executions. If there is a risk of daemons unnaturally terminating across an IPL then `START=COLD` should be used when restarting them. | COLD | none

## ZIIP – Activate zIIP support for the System Coordinator Daemon

Parameter | Use | Possible Values | Default
--- | --- | --- | ---
ZIIP | Specify whether or not zIIP support is to be activated for this Daemon. | YES | NO | No

Possible values:

- `ZIIP=YES:`

  zIIP support for the Daemon is activated. The Daemon offloads CPU time from the general processors to System z Integrated Information Processors (zIIP). The purpose of this configuration is to reduce the CPU consumption on the general processors.

- `ZIIP=NO:`

  The default setting.

  The Daemon runs without the option to offload CPU time to zIIPs.

Note
The use of ZIIP=YES requires the availability of the Adabas for zIIP license file (AZPAD). If the AZPAD license file is missing or found invalid, the Daemon will start but will run as if ZIIP=NO had been specified.

#### Dynamic Modification

If the Daemon was started with ZIIP=YES, the setting of the ZIIP parameter can be changed at runtime - that is, set to NO and subsequently back to YES - using the ZIIP= command from the operator console. If the Daemon was started with ZIIP=NO, the setting of the ZIIP parameter cannot be changed to YES later in this session.

Refer to Daemon Operator Commands for more information on the ZIIP= operator command.

### On this page

- CT – Command Timeout Limit
- DSPSCOPE – Dataspace Scope
- ENCRYPTION - Activate Support for Encrypted Datasets
- FORCE – Overwrite ID Table Entry
- LOCAL - Define an Isolated Daemon
- LU – Length of Intermediate User Buffer
- MPMWTO – Display Information Messages
- NABS – Number of Attached Buffers
- NC - Number of Command Queue Elements
- NXC - Number of Sysplex Command Queue Elements
- PRODUCT - Identify the Services to be made Available
- START– Cold start feature
- ZIIP – Activate zIIP support for the System Coordinator Daemon