COR* - Adabas System Coordinator Kernel Messages

#### Search Results

Search

# COR* - Adabas System Coordinator Kernel Messages

CORnnn messages are issued by the Adabas System Coordinator kernel.

### Overview of Messages

`COR001S | COR002S | COR003S | COR004S | COR005E | COR006S | COR007E | COR008S | COR009S | COR010S | COR011I | COR012S | COR013I | COR014E | COR015S | COR016S | COR017I | COR018E | COR019E | COR020I | COR021S | COR022S | COR023S | COR024E | COR025E | COR026E | COR027E | COR028E | COR029E | COR030I | COR031I | COR034S | COR035S | COR036S | COR037I | COR038E | COR039S | COR040S | COR041I | COR042I | COR043W | COR045I | COR046S | COR047S | COR048S | COR049S | COR050S | COR052I | COR053I | COR054S | COR055I | COR060I | COR061I | COR064I | COR065I | COR066E | COR067E | COR069I | COR072I | COR073I | COR074I | COR075I | COR076I | COR077E | COR078E | COR079E`

COR001S | RUNTIME ENVIRONMENT CANNOT INITIALIZE, KERNEL LOAD ERROR
Explanation | The Adabas System Coordinator client (CORSnn) failed to locate or load the runtime kernel module CORKRN.
Action | Ensure that the load library containing the kernel module is available to the TP monitor or batch job that issued the message.

COR002S | RUNTIME ENVIRONMENT CANNOT INITIALIZE, CONFIGURATION FILE RESPONSE=nnnn, SUBCODE=nnnn
Explanation | A configuration module (CORCFG) has been located that indicates the SVC, DBID, and file number of the Adabas System Coordinator configuration file. An error occurred when trying to read this configuration file.
Action | Refer to the Adabas Messages and Codes documentation to determine the reason for the error.

COR003S | FAILED TO REGISTER JOB WITH COR DAEMON, ERROR=nnnnnnnn. SERVICE CONTINUING IN LOCAL MODE
Explanation | The job is defined to run in daemon-mode, but an active local daemon could not be found.
Action | The job continues in local mode. COR daemon services are not available. If daemon-mode is critical to the correct operation of the job or service you should designate one or more add-on products with the “CRITICAL” specification in the COR configuration module (CORCFG). See message COR040S for further information.

COR004S | GROUP group-name NOT FOUND IN CONFIGURATION FILE RESPONSE=nnnn, SUBCODE=nnnn
Explanation | An error occurred when attempting to read the defined group parameters.
Action | If the Adabas System Coordinator group parameters have not been defined, use the SYSCOR online application to define them and resubmit the job.

COR005E | RUNTIME CONFIGURATION MODULE CORCFG NOT LOCATED – INITIALIZATION RETRY LATER
Explanation | The configuration module CORCFG cannot be loaded, without it System Coordinator and related products are unable to operate. The job continues without Coordinator but it will periodically try to find CORCFG so it can activate.
Action | Refer to the Adabas System Coordinator Installation documentation for information about assembling a configuration module.

COR006S | NO MEMBERS DEFINED FOR DAEMON GROUP ########
Explanation | A job is defined to expect an Adabas System Coordinator group. The group has been defined but no daemon members have been defined within the group.
Action | Use the SYSCOR online application to define required daemon members in the group.

COR007E | DAEMON NOT RUNNING FOR GROUP ########, JOB ######## CANNOT INITIALIZE
Explanation | A job is defined to expect an Adabas System Coordinator group, but none of the Coordinator daemons defined in the group are active on this system.
Action | After ensuring that the local Coordinator daemon is started, restart the job.

COR008S | CANNOT LOCATE ID TABLE FOR SVC nnn
Explanation | A job is defined to expect an Adabas System Coordinator group, but no ID table was found for the Adabas SVC number specified in the group definition.
Action | Use the SYSCOR online application to enter the correct SVC number in the group record.

COR009S | ################ IXLCACHE READ ERROR, RC=##, RSN=###
Explanation | The Coordinator daemon is running in an IBM sysplex environment and is using the coupling facility. An error occurred when trying to access data from the coupling facility cache memory. The coupling facility may be improperly set up or defined.
Action | Ensure that the cache structure is defined correctly in the Adabas System Coordinator group.

COR010S | ################ IXLCACHE WRITE ERROR, RC=##, RSN=###
Explanation | The Coordinator daemon is running in an IBM sysplex environment and is using the coupling facility. An error occurred when trying to write data to the coupling facility cache memory. The coupling facility may be improperly set up or defined.
Action | Ensure that the cache structure is defined correctly in the Adabas System Coordinator group.

COR011I | MEMBER ######## JOINS ######## GROUP ######## ON SYSTEM ########
Explanation | The daemon has successfully joined the group.
Action | None. This message is for information only.

COR012S | MEMBER ######## FAILED TO JOIN SYSPLEX GROUP ########, RC=##, RSN=###
Explanation | The Coordinator daemon failed to connect to the sysplex group. The sysplex may not be properly defined. The return and reason codes are from the IXCJOIN macro.
Action | Consult the IBM Sysplex Services Reference to determine the cause of the problem.

COR013I | MEMBER ######## LEAVES ######## GROUP ######## ON SYSTEM ########
Explanation | The Coordinator daemon has left the group.
Action | None. This message is for information only.

COR014E | MEMBER ######## ERROR LEAVING SYSPLEX GROUP ########, RC=##, RSN=####
Explanation | The Coordinator daemon failed to correctly leave the group.
Action | Consult the IBM Sysplex Services Reference to determine the cause of the problem.

COR015S | IXCQUERY ERROR, RC=##, RSN=###
Explanation | A z/OS IXCQUERY service failed. The return and reason codes are from the IXCQERY macro.
Action | This is an internal error. Contact your technical support representative.

COR016S | ################ IXLCONN ERROR, RC=##, RSN=###
Explanation | The Coordinator daemon is running in an IBM sysplex environment and using the coupling facility. An error occurred when trying to connect to the coupling facility cache structure defined in the Adabas System Coordinator group record.
Action | Ensure that the required cache structure is defined in the CFRM policy for this sysplex.

COR017I | NO RUNTIME CONTROL FOUND FOR ######## - ADD-ON PRODUCTS ARE DEACTIVATED
Explanation | The configuration file does not contain a runtime control record for this job. The Adabas System Coordinator and installed products will be deactivated until a run-time control is defined and the job is restarted. It is likely that the Adabas System Coordinator link stub was added to the link module but no runtime control was defined for the job.
Action | Use one of the online administration applications (SYSAVI, SYSAFP, SYSATM) to define a runtime control; then restart the job.

COR018E | ################ ixlcache dirinfo error, rc=##, rsn=####
Explanation | An error occurred when retrieving directory information from the coupling facility cache structure.
Action | Consult the IBM Sysplex Services Reference to determine the cause of the error.

COR019E | ################ ICXMSGO SENDTO ############### ERROR, RC=##, RSN=###
Explanation | An error occurred when sending a message from one Coordinator daemon to another in an IBM sysplex.
Action | Consult the IBM Sysplex Services Reference to determine the cause of the error.

COR020I | SYSPLEX INTERFACE COMMAND QUEUE AT ########
Explanation | Issued at startup of a Coordinator daemon, this message displays the address of the command queue used for communication among the Coordinator daemons.
Action | None. This message is for information only.

COR021S | IOR FAILURE FUNC ## ERRCODE ##
Explanation | An error occurred during an ADAIOR service call.
Action | Contact your technical support representative for assistance.

COR022S | ################ IXLCACHE DELETE ERROR, RC=##, RSN=###
Explanation | The Coordinator daemon is running in an IBM sysplex environment and is using the coupling facility. An error occurred when trying to delete data from the coupling facility cache memory. The coupling facility may be improperly set up or defined.
Action | Ensure that the cache structure is defined correctly in the Adabas System Coordinator group.

COR023S | ################ IXLCACHE STATS ERROR, RC=##, RSN=###
Explanation | The Coordinator daemon is running in an IBM sysplex environment and is using the coupling facility. An error occurred when trying to read statistical information from the coupling facility cache memory.
Action | Ensure that the cache structure is defined correctly in the Adabas System Coordinator group. Note: This message will appear if you attempt to use the SYSCOR session monitoring “Display cache statistics” service, and the Coordinator daemon is not running with a coupling facility cache structure.

COR024E | CONFIGURATION FILE database / file READ ERROR (RSP ###), OPTIONAL PRODUCT CALLS BYPASSED
Explanation | System Coordinator suffered a problem using the configuration file. The job continues running unless one or more products are identified as being critical.
Action | Investigate the cause of the bad response code and take corrective action so that it no longer occurs.

COR025E | NO DAEMON ACTIVE FOR SYSCO GROUP ########, OPTIONAL PRODUCT CALLS BYPASSED
Explanation | System Coordinator has been unable to contact a daemon in the specified group. It it able to continue running but calls to non-critical products are bypassed.
Action | Activate the daemon for the group.

COR026E | CONFIGURATION FILE database / file READ ERROR (RSP ###) JOB ######## WAITING FOR ACTIVATION
Explanation | The database containing the configuration file is not active, and it has been requested (in the CORCFG configuration module) that client jobs should wait for the file to be activated. Adabas System Coordinator will attempt to read the configuration file every 15 seconds.
Action | Activate the database containing the configuration file as soon as possible.

COR027E | NO DAEMON ACTIVE FOR SYSCO GROUP ########, JOB ######## WAITING FOR ACTIVATION
Explanation | System Coordinator has been unable to contact a daemon in the specified group. The job is paused, pending daemon activation.
Action | Activate the daemon for the group.

COR028E | CONFIGURATION FILE database / file READ ERROR (RSP ###), INITIALIZATION DEFERRED FOR JOB ########
Explanation | The job parameter could not be read from the configuration file. Initialization of System Coordinator and add-on products is deferred. It is likely that the database containing the configuration file is inactive (response code 148, ADARSP148). The COR client will automatically attempt a periodic retry if it receives an error reading the configuration file. This avoids the need to recycle jobs when the file becomes available again.
Action | Activate the database containing the configuration file as soon as possible.

COR029E | DAEMON NOW RUNNING FOR GROUP ########, JOB ########
Explanation | System Coordinator has now detects the presence of a daemon.
Action | None.

COR030I | RESPONSE ###, RETRY ACTIVE FOR FILE database / file, JOB=########, COMMAND=##
Explanation | Command retry has been activated for the indicated response code, and it has been specified that a console message is to be issued whenever an retry is attempted.
Action | Take appropriate (installation-defined) action.

COR031I | RESPONSE ###, RETRY ABANDONED FOR FILE database / file, JOB=########, COMMAND=##
Explanation | The required number of command retries has been attempted, but the command has still not completed successfully. Retry is abandoned.
Action | Take appropriate (installation-defined) action.

COR034S | KERNEL(CORKRN) NOT FOUND, SERVICE CANNOT CONTINUE
Explanation | One or more add-on products has been defined with the "CRITICAL" specification in the configuration module (CORCFG). The Coordinator kernel module could not be located and the product will not function correctly. All Adabas requests will be rejected with response 101 subcode 58.
Action | Make the load library containing the COR kernel available, and restart the job or service.

COR035S | SERVICE CANNOT CONTINUE, CRITICAL PRODUCTS ARE NOT OPERATIONAL
Explanation | One or more add-on products has been defined with the "CRITICAL" specification in the configuration module (CORCFG). System Coordinator, or the product itself has detected that some product component is missing or not operational. In Adabas client jobs all Adabas requests will be rejected with response 101 subcode 59. This message can also be issued in Adabas nucleus jobs when System Coordinator fails to find or load a critical Adabas module (usually ADALNK). There will normally be another COR or product message identifying the component in error.
Action | Correct the error and restart the job or service.

COR036S | Runtime environment cannot initialize, initial allocation failed
Explanation | The Adabas System Coordinator client (CORSnn) was unable to acquire enough storage to initialize.
Action | Increase the amount of memory available to the job and restart it.

COR037I | SVC dump created
Explanation | The Adabas System Coordinator daemon has produced an SVC dump dataset as a result of an abend. This message is only issued when CORCFG specifies `ZOSDUMP=SVC` .
Action | None

COR038E | SVC dump failed, R15: hhhhhhhh
Explanation | The Adabas System Coordinator daemon was configured to produce an SVC dump in the event of an abend. The SVC dump failed with the indicated error code (hhhhhhhh) and a standard dump was produced instead.
Action | Review the IBM SDUMPX documentation to determine the reason for the failure.

COR039S | IBM STORAGE KEY OVERRIDE NOT ENABLED, COM-PLETE THREAD KEYS CANNOT BE USED
Explanation | Com-plete thread keys can only be supported when the IBM Storage Key Override is enabled.
Action | Enable IBM Storage Key Override or disable Com-plete thread keys.

COR040S | FAILED TO REGISTER JOB WITH COR DAEMON, ERROR=nnnnnnnn. CRITICAL SERVICE CANNOT CONTINUE
Explanation | The job is defined to run in daemon-mode, but an active local daemon could not be found. One or more add-on products have been defined with the "CRITICAL" specification in the configuration module (CORCFG). In this mode, the daemon is considered to be critical to the correct operation of the job. All Adabas requests will be rejected with response code 101 (ADARSP101), subcode 59.
Action | Make sure that the Coordinator daemon is active and restart the job or service.

COR041I | REVERTING TO DEFAULT CONSOLE USAGE AFTER ERROR : ########
Explanation | System Coordinator has received an error using the alternate console and has reverted to using the default console.
Action | None. This message is for information only.

COR042I | "XCF" is not supported. Terminating.
Explanation | XCF is not supported for this operating system.
Action | Correct the daemon group parameters.

COR043W | Jobname hhhhhhhh. Unexpected error response=####, subcode=####
Explanation | System Coordinator has detected an internal error for jobname thread-address hhhhhhhh, which has resulted in the specified response and subcode. This message occurs at most once per job.
Action | Contact your technical support representative.

COR045I | Co-ordinated stop set for User=userid, TID=aaaaaaaa
Explanation | This message is a response to a successful co-ordinated stop request where userid is the Adabas-assigned user ID and aaaaaaaa is the terminal ID (alphanumeric).
Action | None. This message is for information only.

COR046S | SPAWN FAILED RC=##
Explanation | An internal error has occurred during daemon processing.
Action | Contact your technical support representative.

COR047S | Installation error. COR is disabled.
Explanation | An installation error has been detected. This is usually accompanied by another error message explaining the installation error.
Action | Correct the installation error and re-try. If the problem persists, contact your Software AG technical support representative for further assistance.

COR048S | PRODUCT ## PACK FAILED RC=##
Explanation | An internal error has occurred during latency processing.
Action | Contact your technical support representative.

COR049S | PRODUCT ## UNPACK FAILED RC=##
Explanation | An internal error has occurred during latency processing.
Action | Contact your technical support representative.

COR050S | LATENCY FILE ###### FAILED RC=####
Explanation | An internal error has occurred during latency processing.
Action | Contact your technical support representative.

COR052I | SERVICE ######## STARTED USING ###### LATENCY (#############)
Explanation | System Coordinator has successfully started the named service. The type of latency used and whether the service is single or multi system is also displayed.
Action | None. This message is for information only.

COR053I | SERVICE ######## ENDED
Explanation | System Coordinator has successfully ended the named service.
Action | None. This message is for information only.

COR054S | COR054S JOB ######## REQUIRES DAEMON LATENCY ON DISK; LATENCY INITIALIZATION FAILED IN DAEMON ADDRESS SPACE
Explanation | A client job has been defined to use a daemon latency file. However the daemon does not have a latency file.
Action | Correct the configuration.

COR055I | Co-ordinated stop set for STOPI=nnn
Explanation | This message is a response to a successful co-ordinated stop request where nnn is the dormant session time applied.
Action | None. This message is for information only.

COR060I | Connected to daemon: #####
Explanation | A client job has been defined to use a daemon service and to issue daemon communication messages and has successfully connected to daemon node #####.
Action | None. This message is for information only.

COR061I | Disconnected from daemon: #####
Explanation | A client job has been defined to use a daemon service and to issue daemon communication messages and has successfully disconnected to daemon node #####.
Action | If the disconnection is unexpected, check that the daemon is active and accessible.

COR064I | UB extension enforcement activated – length ###
Explanation | A client job has been defined to use a product that requires a UB extension of the indicated length, however the Adabas link module has not been configured to provide a suitable UB extension. System Coordinator adjusts the UB dynamically as appropriate.
Action | Correct the Adabas LGBLSET LUINFO parameter and reinstall the Adabas link module/globals table. Note: this message is always issued for SPATs clients that execute participating triggers (if the SPATs job is defined to use a product that requires a UB extension).

COR065I | Input parameter: ##############################
Explanation | The input parameter ########### included in the daemon services DDCARD input has been processed.
Action | None. This message is for information only.

COR066E | Invalid parameter: ###########
Explanation | The parameter ########### included in the daemon services DDCARD input is invalid.
Action | Correct the DDCARD parameter. .

COR067E | Getmain for product parm block failed'
Explanation | The DDCARD input parameters could not all successfully be processed due a lack of memory.
Action | Increase the region size for the job.

COR069I | PMAF: eye=#### len=######## owner=### releaser=****
Explanation | This message indicates that some internal memory has been released by a different product to the one that allocated it. This is an informational message and in itself is not an indication of a problem.
Action | None. This message is for information only.

COR072I | UTM Memory Pool short on storage, Pool=################
Explanation | A client job has been unable to allocate enough memory for the thread from the UTM Pool ################. System Coordinator will try to allocate a smaller thread, but this may limit the activity of some users.
Action | Increase the UTM Pool size in the UTM Client Runtime Controls (see UTM pool settings).

COR073I | Configuration file database/file in use for job ########
Explanation | This message indicates that the client has successfully read the System Coordinator configuration file. It will only be issued if one of the following messages has previously indicated that there was a problem reading the configuration file: COR002S COR026E COR028E
Action | None. This message is for information only.

COR074I | Dataspace ######## created, token ################
Explanation | This message indicates that the named dataspace has been created by the Adabas System Coordinator daemon.
Action | None. This message is for information only.

COR075I | Enabling access to ########, token ################
Explanation | This message indicates that the address space within which this job is running is about to connect to the named dataspace.
Action | None. This message is for information only. To suppress this message, refer to the client runtime control Daemon connection messages in the Adabas System Coordinator Parameters documentation.

COR076I | Access to ######## enabled, token ################
Explanation | This message indicates that the address space within which this job is running has successfully connected to the named dataspace.
Action | None. This message is for information only. To suppress this message, refer to the client runtime control Daemon connection messages in the Adabas System Coordinator Parameters documentation.

COR077E | Access to ######## failed, token ################
Explanation | This message indicates that the address space within which this job is running failed to connect to the named dataspace.
Action | Contact your technical support representative.

COR078E | Error managing ######## Function=## RF=######## R0=########
Explanation | An internal error has occurred when managing the named dataspace.
Action | Contact your technical support representative.

COR079E | Job ######## unable to initialize; required daemon services are not licensed
Explanation | The Adabas System Coordinator client component within job ######## failed to register with the COR daemon to access required daemon services due to an invalid COR license.
Action | Check the COR daemon messages for a CORD98E message. This client message should only be issued after a COR daemon CORD98E message. Refer to the Action described in the CORD98E message and restart job ######## accordingly.