Version 8.2.5
 —  Messages and Codes  —

CORD* - Adabas System Coordinator Daemon Messages

CORDnn messages are issued by the Adabas System Coordinator daemon.

Overview of Messages

CORD01S | CORD02S | CORD03E | CORD04I | CORD05E | CORD06E | CORD07E | CORD08E | CORD10E | CORD11I | CORD12I | CORD13E | CORD14I | CORD15I | CORD16S | CORD21I | CORD22E | CORD30E | CORD31E | CORD34E | CORD35S | CORD37S | CORD38S | CORD39I | CORD40S | CORD45E | CORD46I | CORD47S | CORD49W | CORD50E | CORD52I | CORD53I

CORD01S COORDINATOR CANNOT INITIALIZE, GETMAIN ERROR
Explanation

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

Action

Increase the region specification for the daemon job.


CORD02S COORDINATOR CANNOT INITIALIZE, KERNEL LOAD ERROR
Explanation

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

Action

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


CORD03E DDCARD OPEN ERROR: ## - TERMINATING
Explanation

The DDCARD control file could not be opened.

Action

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


CORD04I INPUT PARAMETER: #############
Explanation

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

Action

None. This message is for information only.


CORD05E INVALID PARAMETER: ###########
Explanation

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

Action

Correct or delete the invalid parameter.


CORD06E PRODUCT PARAMETER NOT SPECIFIED
Explanation

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

Action

Add the required PRODUCT parameter and restart the daemon.


CORD07E MPM FAILURE - FUNCTION: ## ERROR ##
Explanation

An error occurred when trying to:

  • sign on to the Adabas SVC (Function=24 - x'18')

  • sign off from the Adabas SVC (Function=20 - x'14')

  • Post command completion to caller (Function=12 - x'0C')

  • get the command queue element (CQE) (Function=8 - x'08')

Action

For a sign on error, ensure that the correct SVC and Node ID have been specified in the Adabas System Coordinator group member.

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

A Get CQE error or a Post error indicates a problem with the daemon caller. This will be accompanied by an Adabas "User Gone" message (ADAM91 or ADAM92), 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.


CORD08E IOR FAILURE - FUNCTION: ## ERROR ##
Explanation

An error occurred during an ADAIOR service call.

Action

Contact your Software AG technical support representative for assistance.


CORD10E GETMAIN FOR COMMAND QUEUE FAILED
Explanation

The daemon cannot acquire memory for the command queue.

Action

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


CORD11I CORD11I SYSCO IS ACTIVE ON NODE ##### ###
Explanation

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

Action

None. This message is for information only.


CORD12I OPER TYPEIN: #################
Explanation

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

Action

None. This message is for information only.


CORD13E INVALID OPERATOR COMMAND
Explanation

The command entered is not valid.

Action

Correct the command and enter it again.


CORD14I TARGET ##### TERMINATION IN PROGRESS
Explanation

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

Action

None. This message is for information only.


CORD15I TARGET ##### ENDED NORMALLY
Explanation

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

Action

None. This message is for information only.


CORD16S TARGET ##### ENDED ABNORMALLY
Explanation

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

Action

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


CORD21I OPERATOR COMMAND PROCESSED SUCCESSFULLY
Explanation

An operator command completed successfully.

Action

None. This message is for information only.


CORD22E LOAD FOR MODULE: ######## FAILED
Explanation

The requested module could not be located or loaded.

Action

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


CORD30E GETMAIN FOR PRODUCT PARM BLOCK FAILED
Explanation

A memory allocation failed during the initialization.

Action

Increase the region specification for the job.


CORD31E CAB ALLOCATION ERROR
Explanation

A memory allocation failed during the initialization of the daemon.

Action

Increase the region specification for the job.


CORD34E ASA ALLOCATION ERROR
Explanation

A memory allocation failed during the initialization of the daemon.

Action

Increase the region specification for the job.


CORD35S CONFIGURATION MODULE CORCFG CANNOT BE LOCATED
Explanation

The configuration module CORCFG 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.

Action

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


CORD37S SYSCO DAEMON member-name NOT FOUND IN CONFIGURATION FILE, RESPONSE=nnnn, SUBCODE=nnnn
Explanation

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.

Action

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


CORD38S GROUP group-name NOT FOUND IN CONFIGURATION FILE, RESPONSE=nnnn, SUBCODE=nnnn
Explanation

The named group cannot be located.

Action

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.


CORD39I SHUTDOWN PENDING
Explanation

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.

Action

None. This message is for information only.


CORD40S ABEND #### PSW ######## ########
Explanation

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.

Action

Contact your Software AG technical support representative.


CORD45E THREAD ######## TIMEOUT, TARGET=#####, USER=########
Explanation

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.

Action

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.


CORD46I ######## Start pending, configuration file (dbid ##### fnr #####) not active
Explanation

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.

Action

Start the database that contains the configuration file.


CORD47S Halt-Load library is not Authorized
Explanation

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

Action

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


CORD49W (jobname) shutdown rejected, configuration file (dbid ddddd fnr fffff) not active
Explanation

A daemon shutdown request was made, but either the primary or the alternate configuration file is not active.

This message appears only when Alternate Configuration File support is specified.

Action

Make the required Configuration File available and re-issue the shutdown request.


CORD50E Shutdown rejected
Explanation

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

Action

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


CORD52I Configuration file: ##### / #####
Explanation

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

Action

None. This message is for information only.


CORD53I Alternate file : ##### / #####
Explanation

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.

Action

None. This message is for information only.


Top of page