Daemon Parameters

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.

Single
Multi-XCF
Multi-Net-Work

Indicates whether a common daemon latency file is to be used to store session-related information when sessions are at rest.

For more information, refer to Multi-system Dynamic Transaction Routing in the Adabas System Coordinator Operations and Programming Guide.

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

The job name under which this daemon executes.

This is the name of the job or started task as known to the operating system.

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.

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

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, IMS and/or UTM) 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 may optionally be allocated within a dataspace of the specified name.

For BS2000, this shared memory is taken from the daemon shared memory pool as defined by the daemon parameter Pool settings for BS2000.

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.

Refer to The Daemon Unified Trace in the Adabas System Coordinator Operations and Programming Guide.

Specify the name, virtual address and size of the daemon shared memory pool. Required on BS2000.

This shared memory pool is used to hold latent session-related information for UTM services and also activity information for jobs defined to use activity pulsing as well as internal daemon control information.

Note:
You must also set the "Shared memory area size (k)" in the Daemon Group parameter Daemon latency/pulse services.

Name :

The name of the daemon shared memory pool.

Address:

The virtual start address of the daemon shared memory pool. The start address (and size) must be valid for the daemon, all UTM services managed by the daemon, and any jobs defined to use activity pulsing.

Size(mb)

The size (in megabytes) of the daemon shared memory pool.

This shared memory pool size must be large enough to contain the "Shared memory area size" defined within the Daemon Group parameter Daemon latency/pulse services plus 1 megabyte for control information.