CORD* - Adabas System Coordinator Daemon Messages

The Adabas System Coordinator cannot initialize because of a memory shortage.

Increase the region specification for the daemon job.

The daemon failed to locate or load the runtime kernel module CORKRN.

Ensure that the load library containing the kernel module is available to the job.

The DDCARD control file could not be opened.

Ensure that the daemon job has a DDCARD file containing the required control cards.

The input parameters contained in the DDCARD file are echoed in the job message output file.

None. This message is for information only.

An invalid input parameter was found in the DDCARD file. The daemon terminates.

Correct or delete the invalid parameter.

There was no PRODUCTparameter in the DDCARD file. The daemon does not know which product(s) to load.

Add the required PRODUCT parameter and restart the daemon.

An error occurred calling ADAMPM when trying to:

• initialize a target (Function=00)

• sign off from the Adabas SVC (Function=20)

• sign on to the Adabas SVC (Function=24)

For a sign on error, navigate to the Daemon Group Parameters in the System Coordinator Online system and ensure that the correct SVC and Node ID have been specified for the Adabas System Coordinator group.

A sign-off error indicates an internal problem with the System Coordinator Daemon. Contact your Software AG technical support representative for assistance.

No action is required in the Coordinator Daemon.

An error occurred during an ADAIOR service call.

Contact your Software AG technical support representative for assistance.

The daemon has received a shutdown request.

None. This message is for information only.

The daemon cannot acquire memory for the command queue.

Increase the region specification for the Adabas System Coordinator daemon task.

The daemon successfully signed on to the Adabas SVC and is ready for communication. The message indicates the node and SVC number used.

None. This message is for information only.

The operator entered a console command to the daemon. The command is echoed back to the message output file.

None. This message is for information only.

The command entered is not valid.

Correct the command and enter it again.

The daemon is terminating because of operator request or unrecoverable error.

None. This message is for information only.

The daemon terminated normally as a result of an operator request.

None. This message is for information only.

The daemon terminated abnormally as a result of a previous error.

A previous message will identify the cause of the abnormal termination. Examine the message and take appropriate recovery action.

The daemon has detected multiple copies of the PRODUCT= card for a single product.

Remove the duplicate entries and restart the daemon.

The daemon has detected too many copies of the PRODUCT= card.

Correct the PRODUCT= cards and restart the daemon.

This is an internal error.

Contact your Software AG technical support representative for assistance.

The daemon has detected invalid parameter cards and has shut down.

Correct the parameter cards and restart the daemon.

An operator command completed successfully.

None. This message is for information only.

The requested module could not be located or loaded.

Ensure that the requested module is available to the Adabas System Coordinator daemon task.

The parameters in use in this instance of the daemon.

None. This message is for information only.

Along with CORD23I gives details of the parameters in use in this instance of the daemon.

None. This message is for information only.

The daemon has detected invalid an invalid product name.

Correct the product name and restart the daemon.

The daemon has been told to run with PRODUCT=nnn but cannot find nnnPXY.

Ensure the daemon has access to all the products required and restart the daemon.

This is an internal error.

Contact your Software AG technical support representative.

The requested module could not be located or loaded.

Contact your Software AG technical support representative.

This is an installation error.

Ensure that all product libraries used in the daemon are the same version.

A memory allocation failed during the initialization.

Increase the region specification for the job.

A memory allocation failed during the initialization of the daemon.

Increase the region specification for the job.

Explanation This is an internal error.

Contact your Software AG technical support representative.

A memory allocation failed during the initialization of the daemon.

Increase the region specification for the job.

The configuration module cannot be loaded. This module contains the SVC, DBID, and file number for reading the configuration file. The daemon will not function correctly without this module.

Refer to the Adabas System Coordinator Installation documentation for information about assembling a configuration module.

This is an internal error.

Contact your Software AG technical support representative.

The named Adabas System Coordinator group member was not found in the group in the configuration file. Every daemon must have an equivalent group member parameter.

Add the member entry for this daemon to the appropriate Adabas System Coordinator group.

The named group cannot be located.

An error occurred while searching for the Adabas System Coordinator group parameters. Define the Adabas System Coordinator group. If the problem persists, contact your Software AG technical support representative.

A shutdown request was entered. One or more of the subcomponents of the Adabas System Coordinator daemon suspended the request until it completes its own shutdown processing. The daemon should terminate when this is completed.

None. This message is for information only.

An error occurred in the Adabas System Coordinator daemon. The registers, PSW, and failing module at the time of the error are displayed. The Adabas System Coordinator writes additional diagnostic information to the CORDUMP file, deletes any common memory pools in use, and terminates.

Contact your Software AG technical support representative.

Additional information to CORD40S.

Contact your Software AG technical support representative.

Additional information to CORD40S.

Contact your Software AG technical support representative.

Additional information to CORD40S.

Contact your Software AG technical support representative.

The address of the named proxy module.

None. This message is for information only.

The Adabas System Coordinator daemon sent an Adabas command to the indicated target, and has not received a response within the timeout interval as specified by DDCARD parameter CT.

Check that the target database is operating correctly. If the problem persists, try increasing the CT timeout value. If there is still a problem, contact your Software AG technical support representative.

An Adabas System Coordinator daemon has been started, but the required configuration file is not active. The daemon will wait for 60 seconds and try again. If the configuration file is still not active after 60 minutes the daemon will terminate.

Start the database that contains the configuration file.

z/OS only. An Adabas System Coordinator daemon has been started from a load library that is not APF-authorized.

Ensure the specified load library is authorized and restart the daemon.

The named product has ended.

None. This message is for information only.

A daemon shutdown request was made, but there are active client DTR jobs connected to the daemon.

This message will be preceded by message CAS004I, identifying the names of the active DTR job(s).

Terminate the active client jobs and re-issue the shutdown request.

There has been an overflow in the XCF command queue (see NXC parameter) of the current daemon resulting in a daemon restart.

None. This message is for information only and indicates an exceptionally high volume of XCF messages in this System Coordinator group.

This message shows the database ID and file number of the configuration file in use by this System Coordinator daemon.

None. This message is for information only.

This message shows the database ID and file number of the alternate configuration file in use by this System Coordinator daemon. The message only appears if an alternate configuration file has been specified.

None. This message is for information only.

An Adabas System Coordinator daemon has been instructed to terminate, but an alternate configuration file is in use and one or both configuration files is not active. Both configuration files must be available at daemon termination.

Ensure that the configuration file database(s) are active.

A latency file error has occurred in the Adabas System Coordinator daemon.

Contact your Software AG technical support representative.

The Adabas System Coordinator daemon has been restarted after a failure and full crash recovery was active at the time of failure for the job/service indicated. This message identifies the number of sessions recovered for the services/job so they can continue without interruption if possible.

This message is for information only, no action is needed.

The System Coordinator daemon resource manager was invoked at address-space (termination-type indicates AddrSpc) or task (termination-type indicates Task) termination .

None. This message is for information only.

The System Coordinator daemon was unable to activate its resource manager. hhhhhhhh indicates a reason for the failure.

The daemon continues without its resource manager. Contact Software AG support to establish the reason for the failure.

A failure has occurred in the component identified in the message. Continuous operation processing has been invoked to restart the appropriate component(s).

None. This message is for information only.

This is an information message during continuous operation recovery.

Report it to your Software AG technical support representative.

The System Coordinator daemon was attempting to recover following a failure but an error occurred trying to do so.

Contact your Software AG technical support representative.

The Adabas System Coordinator daemon was restarted following a failure and has recovered the job/service indicated. This message identifies the number of sessions recovered for the services/job so they can continue without interruption.

None. This message is for information only.

There has been more than one failure in a period of 30 minutes. Continuous operation is abandoned and the daemon terminates.

None. This message is for information only.

Issued at startup of a Coordinator daemon, this message displays the address of the daemon’s shared memory anchor.

None. This message is for information only.

Issued at startup of a Coordinator daemon, when it has been configured to use shared memory for latency/pulse services but the attempt to allocate shared memory failed.

The daemon continues, using private memory for latency services (pulse services are disabled). Review the daemon’s shared memory definitions and ensure that sufficient shared memory is available. Consider using a dataspace in preference to standard shared memory.

CORD70I messages are displayed in response to a DRES operator command and show allocated size, current usage and high-water mark for various daemon resources.

None. This message is for information only.

This is a one time only warning message that the XCF command queue is 80% full, potentially a sign of an imminent overflow.

Use the DRES operator command to monitor the XCF command queue. If a high percentage continues to be in use, this may indicate a high number of updates to files being optimized by Adabas Fastpath . This is not recommended and should be investigated. Note that if the number continues to increase then an overflow will occur when the maximum XCF command queue entries is reached, resulting in a CORD51S message and daemon auto-restart.

An error occurred calling ADAMPM when trying to:

• Get the command queue element (CQE) (Function=08)

• Post command completion to caller (Function=12)

• Timeout (Function=36)

This message indicates a problem with the daemon caller. The message identifies the calling Job and Session ID. It may also be accompanied by an Adabas "User Gone" message (ADAM91 or ADAM92), also identifying the calling Job and Session ID. Examine the calling job to determine the reason for the failure. Probably the job has abnormally terminated.

No action is required in the Coordinator Daemon.

The use of this operator command requires zIIP support to have been activated in the Daemon.

In order to activate zIIP support for the Daemon, set ZIIP=YES in the Daemon runtime parameters.

In response to the operator command DZSTAT, these messages display the zIIP-related statistics of the Daemon.

The first line shows the current execution mode: "SRB" (execution on zIIP enabled) or "TCB" (execution on zIIP disabled).

The following statistics correspond, and are equivalent to, the zIIP-related statistics at the end of the Daemon session statistics. Refer to Monitoring zIIP Usage in section "Adabas System Coordinator for zIIP"in the Adabas System Coordinator documentation for detailed information about the various statistical figures.

None. This message is for information only.

In response to the operator command ZIIP=NO, this message indicates the Daemon is now executing in TCB mode (disabling the use of System z Integrated Information Processors). The ZIIP parameter value was changed to NO, from YES.

None. This message is for information only.

In response to the operator command ZIIP=NO, this message indicates the Daemon was already executing in TCB mode (disabling the use of System z Integrated Information Processors). The ZIIP parameter value was not changed; it was already NO.

None. This message is for information only.

In response to the operator command ZIIP=YES, this message indicates the Daemon is now executing in SRB mode (enabling the use of System z Integrated Information Processors). The ZIIP parameter value was changed to YES, from NO.

None. This message is for information only.

In response to the operator command ZIIP=YES, this message indicates the Daemon was already executing in SRB mode (enabling the use of System z Integrated Information Processors). The ZIIP parameter value was not changed; it was already YES.

None. This message is for information only. .

The command entered is not executable.

This message should be preceded by another message which explains the reason why this command could not be executed.

An internal error has occurred during license validation processing.

First verify that the LICMAIN (MLC) module is available in the STEPLIB, otherwise increase the region size available to the Adabas System Coordinator Daemon..

An error occurred opening the license file specified by the DDLAZPAD statement.

Omit the DDLAZPAD statement and use the load module method of licensing instead.

An empty file or invalid record structure was detected.

Verify that the license file has been copied correctly to the license data set. The file should not be empty and the data should not have been converted to EBCDIC (it should be in ASCII format).

The license being read is larger than expected.

Verify that you are using the original license file obtained from Software AG.

An unexpected error occurred while performing the Adabas System Coordinator for zIIP license check. The license function (fx), subfunction (sfx) and return code (err) are given in the message.

Examine the Adabas System Coordinator Daemon JCL and verify that the AZPAD license is available as load module AZPADLIC or is assigned with the link (DD) name DDLAZPAD.

The license check completed successfully and the Adabas System Coordinator Daemon is started.

None. This message is for information only.

The license file is physically correct, but some license property was found that did not match your Adabas System Coordinator Daemon execution environment. This is a final message, accompanied by another message specifying details of the failure. The Adabas System Coordinator Daemon is started but will execute in TCB mode (disabling the use of System z Integrated Information Processors). The ZIIP parameter value was changed to NO, from YES.

Check the accompanying message(s) for the details of the failure. If necessary, contact your Software AG technical support representative.