CASnnn Messages

A component task of a clustered application has started. The started task (job) is defined to use SYSCO to manage application users. User information is maintained in a common memory pool so that it can be shared with other components of the application.

This message is issued when the common memory pool is created.

None. This message is for information only.

A component task of a clustered application has started. The started task (job) is defined to use SYSCO to manage application users. User information is maintained in a common memory pool so that it can be shared with other components of the application.

This message is issued when the new task joins an existing memory pool.

None. This message is for information only.

All jobs using a common memory pool have terminated. The pool is deleted and its memory is released.

None. This message is for information only.

A request was received to shut down a SYSCO daemon, but client jobs are still active on this daemon.

Terminate the client job(s) and re-issue the shutdown request.

A common memory pool is full and has been dynamically extended.

None. This message is for information only.

The clustered application service (CAS) kernel module cannot be loaded.

Ensure that the load library containing the kernel module is available to the Adabas System Coordinator daemon task.

A System Coordinator operator command has failed.

This message is currently issued only in response to the DN (Display Active Nodes) command. The DN command is used to display Coordinator daemon nodes in a Sysplex configuration. Message CAS011E indicates that one or more nodes could not be contacted. Check the coordinator definitions and tasks to identify any setup problems that may have caused this error. Contact your Software AG technical representative for assistance if necessary.

In a standard (non-sysplex configuration) the command will fail and message CAS011E is the normal response. No further action is required.

An attempt to read the session status record failed. The daemon cannot determine if session or pool recovery is required.

Determine the reason for the read failure. It will not be possible to recover any previous failed session if the status record cannot be located.

The configuration file does not contain a session status record. This message will be issued the first time the pool recovery feature is used, or whenever a new configuration file is used.

None. It is assumed there is no previous failed session to recover.

An attempt to update the session status record failed. Session recovery will not be active for this daemon instance.

Determine the reason for the update failure. If session and pool recovery are required, restart the daemon when the problem is resolved.

This message can only occur during normal termination of the daemon. An attempt to update the session status record with termination information failed.

Determine the reason for the update failure. The next time the daemon is started it will probably attempt session recovery, but there will be no session to recover. Messages CAS013I or CAS017S may be issued, but can be ignored.

The session anchor is a common memory area that saves recovery information for the duration of the session. Session recovery will not be active if the anchor cannot be allocated.

Probable cause is insufficent common memory.

Review system initialization parameters and current use of common memory.

This message appears if the system is restarted after a daemon failure or if the anchor memory area is freed or overwritten by any other task.

The session anchor is a common memory area that saves recovery information for the duration of the session. The configuration file status record holds the address of this anchor. When a session fails that session anchor is preserved in common memory until a new daemon session starts and recovers the failed session.

None

The daemon detected that a previous daemon session failed. Session and pool recovery was invoked and has completed successfully.

None.

An error has been detected during session and pool recovery. There is probably a memory corruption problem in one of the pools. The session may have been partially recovered.

It is probably not safe to continue with the current daemon instance. It should be cancelled and restarted. If this message re-occurs, contact your Software AG technical support representative.

The daemon detected that a previous daemon session failed. The named pool was recovered.

None.