CORnnn Messages

The Adabas System Coordinator client (CORSnn) failed to locate or load the runtime kernel module CORKRN.

Ensure that the load library containing the kernel module is available to the TP monitor or batch job that issued the message.

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.

Refer to the Adabas Messages and Codes documentation to determine the reason for the error.

The job is defined to expect a Adabas System Coordinator group but an active local member could not be located.

A response code 148 is returned if the required daemon server is not running. For other errors, refer to the Adabas Messages and Codes documentation to determine the reason for the error.

An error occurred when attempting to read the defined group parameters.

If the Adabas System Coordinator group parameters have not been defined, use the SYSCOR online application to define them and resubmit the job.

The configuration module CORCFG cannot be loaded. This module contains the SVC, DBID, and file number for reading the configuration file. The job continues to run but the Adabas System Coordinator operates in a default mode for the job. This may be acceptable, depending on the optional products installed.

Refer to the section Installation for information about assembling a configuration module.

A job is defined to expect an Adabas System Coordinator group. The group has been defined but no SYSCO members have been defined within the group.

Use the SYSCOR online application to define required SYSCO members in the group.

A job is defined to expect an Adabas System Coordinator group, but none of the SYSCO daemons defined in the group are active on this system.

After ensuring that the local SYSCO daemon is started, restart the job.

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.

Use the SYSCOR online application to enter the correct SVC number in the group record.

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

Ensure that the cache structure is defined correctly in the Adabas System Coordinator group.

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

Ensure that the cache structure is defined correctly in the Adabas System Coordinator group.

The SYSCO 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.

Consult the IBM Sysplex Services Reference to determine the cause of the problem.

A sysplex IXCQUERY service failed. The return and reason codes are from the IXCQERY macro.

This is an internal error. Contact your Software AG technical support representative.

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

Ensure that the required cache structure is defined in the CFRM policy for this sysplex.

The configuration file does not contain a job parameter record for this job. The Adabas System Coordinator and installed products operate in default mode.

It is likely that the Adabas System Coordinator link stub was added to the link module but no job parameter was defined for the job.

If default mode is acceptable, no action is required. Otherwise, use one of the online administration applications (SYSAVI, SYSAFP, SYSATM) to define a job parameter; then restart the job.

An error occurred when sending a message from one SYSCO daemon to another in an IBM sysplex.

Consult the IBM Sysplex Services Reference to determine the cause of the error.

Issued at startup of a SYSCO daemon, this message displays the address of the command queue used for communication among the SYSCO daemons.

None. This message is for information only.

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.

Activate the database containing the configuration file as soon as possible.

The job parameter could not be read from the configuration file. The Adabas System Coordinator and installed products operate in default mode.

It is likely that the database containing the configuration file is inactive (response code 148).

If default mode is acceptable, no action is required. Otherwise, start the database or determine the cause of the read error; then restart the job.

The job was defined as a clustered application, but no Adabas System Coordinator daemon is active for the specified group. Dynamic transaction routing does not operate correctly without an active daemon.

If it is acceptable for the job to continue in non-clustered mode, no action is required. Otherwise, start the daemon and restart the job.

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.

Take appropriate (installation-defined) action.

The required number of command retries has been attempted, but the command has still not completed successfully. Retry is abandoned.

Take appropriate (installation-defined) action.

BS2000 only. A request to enable a memory pool has failed.

Contact your Software AG technical support representative.

BS2000 only. There has been an error during allocation of a System Coordinator memory pool. The failure is probably due to a shortage of memory in the global memory pool defined in the Coordinator group parameter for the service.

Increase the size of the global memory pool in the group definition.