CORDnn messages are issued by the Adabas System Coordinator daemon.
CORD01S | CORD02S | CORD03E | CORD04I | CORD05E | CORD06E | CORD07E | CORD08E | CORD09I | CORD10E | CORD11I | CORD12I | CORD13E | CORD14I | CORD15I | CORD16S | CORD17E | CORD18E | CORD19E | CORD20E | CORD21I | CORD22E | CORD23I | CORD24I | CORD25E | CORD26E | CORD27S | CORD28E | CORD29E | CORD30E | CORD31E | CORD33S | CORD34E | CORD35S | CORD36S | CORD37S | CORD38S | CORD39I | CORD40S | CORD41S | CORD42S | CORD43S | CORD44I | CORD45E | CORD46I | CORD47S | CORD49I | CORD50E | CORD51S | CORD52I | CORD53I | CORD56E | CORD57I | CORD58I | CORD59I | CORD60S | CORD61I | CORD62E | CORD63I | CORD64S | CORD65S | CORD66S| CORD01S | CAS 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 | CAS 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 |
| Action |
Add the required |
| CORD07E | MPM FAILURE - FUNCTION: ## ERROR ## |
| Explanation |
An error occurred when trying to:
|
| 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. |
| CORD09I | SHUTDOWN REQUESTED |
| Explanation |
The daemon has received a shutdown request. |
| Action |
None. This message is for information only. |
| 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 ##### ### CIB=######## |
| 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. |
| CORD17E | PRODUCT ### DUPLICATED |
| Explanation |
The daemon has detected multiple copies of the PRODUCT= card for a single product. |
| Action |
Remove the duplicate entries and restart the daemon. |
| CORD18E | TOO MANY PRODUCTS SPECIFIED |
| Explanation |
The daemon has detected too many copies of the PRODUCT= card. |
| Action |
Correct the PRODUCT= cards and restart the daemon. |
| CORD19E | PRODUCT ### - WORK AREA CANNOT BE ALLOCATED |
| Explanation |
This is an internal error. |
| Action |
Contact your Software AG technical support representative for assistance. |
| CORD20E | INVALID PARAMETERS - TERMINATING |
| Explanation |
The daemon has detected invalid parameter cards and has shut down. |
| Action |
Correct the parameter cards and restart the daemon. |
| 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. |
| CORD23I | PARAMETERS FOR THIS RUN: |
| Explanation |
The parameters in use in this instance of the daemon. |
| Action |
None. This message is for information only. |
| CORD24I | ################ = ################ |
| Explanation |
Along with CORD23I gives details of the parameters in use in this instance of the daemon. |
| Action |
None. This message is for information only. |
| CORD25E | ### IS AN INVALID PRODUCT NAME |
| Explanation |
The daemon has detected invalid an invalid product name. |
| Action |
Correct the product name and restart the daemon. |
| CORD26E | PROXY MODULE ######## WAS NOT FOUND, PRODUCT ### WILL NOT BE CALLED |
| Explanation |
The daemon has been told to run with PRODUCT=nnn but cannot find nnnPXY. |
| Action |
Ensure the daemon has access to all the products required and restart the daemon. |
| CORD27S | INVALID PRODUCT TABLE ENTRY FOR ### |
| Explanation |
This is an internal error. |
| Action |
Contact your Software AG technical support representative. |
| CORD28E | CAS PROXY MODULE ######## FOR PRODUCT ### IS INVALID (BAD EYECATCHER) |
| Explanation |
The requested module could not be located or loaded. |
| Action |
Contact your Software AG technical support representative. |
| CORD29E | CAS PROXY MODULE ######## FOR PRODUCT ### IS NOT SUPPORTED BY THIS VERSION OF CAS |
| Explanation |
This is an installation error. |
| Action |
Ensure that all product libraries used in the daemon are the same version. |
| 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 IN MODULE SYSCORU |
| Explanation |
A memory allocation failed during the initialization of the daemon. |
| Action |
Increase the region specification for the job. |
| CORD33S | APPEND OF PRODUCT V-CON LIST FAILED. |
| Explanation |
Explanation This is an internal error. |
| Action |
Contact your Software AG technical support representative. |
| CORD34E | ASA ALLOCATION ERROR IN MODULE SYSCORU |
| 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 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. |
| CORD36S | SVC/NODE DDCARD INPUT IS INVALID WITH PRODUCT=CAS |
| Explanation |
This is an internal error. |
| Action |
Contact your Software AG technical support representative. |
| 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. |
| CORD41S | CSECT ######## ENTRY ######## OFFSET ######## |
| Explanation |
Additional information to CORD40S. |
| Action |
Contact your Software AG technical support representative. |
| CORD42S | MODULE ######## ENTRY ######## OFFSET ######## |
| Explanation |
Additional information to CORD40S. |
| Action |
Contact your Software AG technical support representative. |
| CORD43S | REGS ##### ######## ######## ######## ######## |
| Explanation |
Additional information to CORD40S. |
| Action |
Contact your Software AG technical support representative. |
| CORD44I | PROXY ######## LOADED AT ######## |
| Explanation |
The address of the named proxy module. |
| Action |
None. This message is for information only. |
| 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 |
| Action |
Check that the target database is operating correctly. If the problem
persists, try increasing the |
| 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. |
| CORD49I | PRODUCT COMPONENT ENDED - ### |
| Explanation |
The named product has ended. |
| Action |
None. This message is for information only. |
| 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. |
| CORD51S | XCF CQ OVERFLOW – RESTART DAEMON(S) |
| Explanation |
There has been an overflow in the XCF command queue. |
| Action |
A restart of all daemons using XCF communications is required. |
| CORD52I | Configuration file: database / 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 : database / 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. |
| CORD56E | Latency file error: ###### - #################### rc=######## |
| Explanation |
A latency file error has occurred in the Adabas System Coordinator daemon. |
| Action |
Contact your Software AG technical support representative. |
| CORD57I | Recovery for ######## found ######## sessions at rest |
| Explanation |
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. |
| Action |
This message is for information only, no action is needed. |
| CORD58I | Service AbTerm resource manager termination-type term |
| Explanation |
The System Coordinator daemon resource manager was invoked at address-space (termination-type indicates AddrSpc) or task (termination-type indicates Task) termination . |
| Action |
None. This message is for information only. |
| CORD59I | Resource manager activation failed, rc=hhhhhhhh |
| Explanation |
The System Coordinator daemon was unable to activate its resource manager. hhhhhhhh indicates a reason for the failure. |
| Action |
The daemon continues without its resource manager. Contact Software AG support to establish the reason for the failure. |
| CORD60S | Failure: Continuous Operation has been initiated for ### |
| Explanation |
A failure has occurred in the component identified in the message. Continuous operation processing has been invoked to restart the appropriate component(s). |
| Action |
None. This message is for information only. |
| CORD61I | ### STORAGE AREA RELEASED |
| Explanation |
This is an information message during continuous operation recovery. |
| Action |
Report it to your Software AG technical support representative. |
| CORD62E | Continuous operation error: ################### rc=####### |
| Explanation |
The System Coordinator daemon was attempting to recover following a failure but an error occurred trying to do so. |
| Action |
Contact your Software AG technical support representative. |
| CORD63I | Continuous operation recovery for ######## found ######## sessions at rest |
| Explanation |
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. |
| Action |
None. This message is for information only. |
| CORD64S | Shutdown activated owing to recursive failure |
| Explanation |
There has been more than one failure in a period of 30 minutes. Continuous operation is abandoned and the daemon terminates. |
| Action |
None. This message is for information only. |
| CORD65S | SHARED MEMORY ANCHOR AT ######## |
| Explanation |
Issued at startup of a Coordinator daemon, this message displays the address of the daemon’s shared memory anchor. |
| Action |
None. This message is for information only. |
| CORD66S | SHARED MEMORY GETMAIN FAILED |
| Explanation |
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. |
| Action |
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. |
