Daemon Parameters

#### Search Results

Search

# Daemon Parameters

Daemon parameters are used to define the environment and operational requirements for Adabas System Coordinator daemons. Daemon Group Parameters apply to all daemons in that group. Daemon Group Member Parameters and Daemon Runtime Parameters apply to individual daemons and may differ from one daemon to another in the group.

- Daemon Group Parameters

- Daemon Group Member Parameters

- Daemon Runtime Parameters

## Daemon Group Parameters

Daemon group parameters are used to define the Adabas System Coordinator daemon environment.

Daemon Group Parameters
`Daemon Group Name`
`Daemon SVC`
`System Type`
`Full crash recovery disk file`
`Messages - database`
`Messages – daemon`

### Daemon Parameters Descriptions

This section describes the daemon parameters.

#### Daemon Group Name (Daemon Group Parameter)

Parameter Type | Use | Default
--- | --- | ---
Daemon Group | The daemon group name is used to control communication between Adabas System Coordinator daemon peers in an operating system cluster. For example, the peer daemons communicate using an XCF group with this name in an IBM parallel sysplex. | none

#### Daemon SVC

Parameter Type | Use | Default
--- | --- | ---
Daemon Group | The router (SVC) number that is used for communicating with the group. This same number must be used by all daemon group members. | none

#### System Type

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group | Type of coordination to be performed by the daemon group Possible values are: Standard single-system: A single system is to be coordinated. This system type includes support for: Adabas Fastpath Adabas Transaction Manager Single-seat current activity displays Single-system dynamic transaction routing Standard multi-system using XCF: Multiple systems are to be coordinated using XCF for cross-system communications. This system type includes support for: Standard single-system (see above) Adabas Fastpath in a distributed system environment Adabas Transaction Manager in a distributed system environment Multi-system dynamic transaction routing Standard multi-system using Net-Work: Multiple systems are to be coordinated using Entire Net-Work for cross-system communications.This system type includes support for: Standard single-system (see above) Adabas Fastpath in a distributed system environment Adabas Transaction Manager in a distributed system environment Multi-system dynamic transaction routing Note Entire Net-Work should only be used for multi-system coordination if XCF is not available. | Single Multi-XCF Multi-Net-Work | none

#### Full Crash Recovery Disk File

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group | Indicates whether session-related information for client jobs managed by this daemon group can be optionally maintained in the COLAT daemon latency disk file This feature enables appropriately defined client sessions, at rest at the time of a daemon failure, to resume processing after the daemon has restarted. Refer to the client runtime control Latency Controls for information on how to enable a client job to use this option. | Y | N | N

#### Messages – database

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group | Indicates the destination for database messages written by the Adabas System Coordinator component in the database (including messages written by products which use its services). Database messages, by default, are written to the console. Additionally, or instead of, these messages may be directed to a disk file by selecting the DDSMG file option. The DDMSG file must be specified in the database execution control script and 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 all messages not to be seen until the database terminates. | Console message job log Local DDMSG file in the database job | Console

#### Messages – daemon

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group | Indicates the destination for messages written by the Adabas System Coordinator daemon (including messages written by products which use its services). Daemon messages, by default, are written to the console. Additionally, or instead of, these messages may be directed to a disk file by selecting the DDSMG file option. The DDMSG file must be specified in the daemon execution control script and 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 all messages not to be seen until the daemon terminates. | Console message job log Local DDMSG file in the daemon job | Console

## Daemon Group Member Parameters

Daemon Group Member Parameters
`Daemon job name`
`Node id`
`Recovery`
`Daemon latency/pulse services`
`Unified trace settings`
`Debug settings`

### Daemon Job Name

Parameter Type | Use | Default
--- | --- | ---
Daemon Group Member | The job name under which this daemon executes. This is the name of the job or started task as known to the operating system. | none

### Node id

Parameter Type | Use | Default
--- | --- | ---
Daemon Group Member | Daemons sign on as targets to the Adabas router. Specify the node id to be used by the daemon. This node id must be unique across all your systems. | none

### Recovery

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group Member | Setting Continuous Operation to "Y" causes the daemon to intercept failures, react by automatically terminating and restarting the appropriate component(s) and then continuing. Setting Continuous Operation to "N" causes the daemon to react to a failure by terminating. You are recommended always to set Continuous Operation to "Y". | Y | N | N

### Daemon latency/pulse services

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon Group Member | Defines the shared memory limits for holding at-rest session-related information and also activity information for jobs defined to use activity pulsing. Shared memory is mandatory if you want to use activity pulsing (see Client Runtime control Activity pulse) and is recommended for dynamic transaction routing (DTR) systems (eg. CICS/MRO, CICS/PLEX or IMS) that require daemon latency for performance and resilience (see Client Runtime control Latency controls). The required shared memory area size depends on the number of sessions, the installed product mix and configuration, and the nature of the application workload and also on how extensively you use activity pulsing. If the shared memory area is not large enough, the daemon will transparently use its own local memory for DTR systems latency. You should monitor the shared memory area usage with the DRES daemon operator command which shows the maximum, current and highwater-mark allocations for Shared Memory. This shared memory will be allocated as a dataspace of the specified name. For more information on shared memory requirements, refer to Considerations and Configuration for using a Daemon in the Adabas System Coordinator Operations and Programming Guide. | 0 – 2097151 Valid dataspace name. | none

### Unified trace settings

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon | Define unified trace settings. For more information, refer to the section Using the Unified Trace in the Adabas System Coordinator Operations and Programming Guide. | Refer to The Daemon Unified Trace in the Adabas System Coordinator Operations and Programming Guide. | None

### Debug settings

Parameter Type | Use | Possible Values | Default
--- | --- | --- | ---
Daemon | `CORDUMP` for transient situations…Some internal communications (for example) may suffer intermittent, transient failure. System Coordinator automatically tolerates and recovers from these issues without problem. However, sometimes support may ask that diagnostics are taken when investigating a problem by requiring this setting to be Y. | N | Y | N
Number of outputs…when diagnostics are being taken it is possible (and wise) to limit the number of times diagnostics are taken using this number. | 0-65535 | 0

### On this page

- Daemon Group Parameters
- Daemon Group Member Parameters