PLX* - ADACLU Messages

Having determined that no Adabas cluster control block (PLXCB) currently exists, the system is attempting to acquire a new one.

An attempt to acquire GETMAIN space for a new Adabas cluster control block (PLXCB) failed. Whichever is attempting to start, a cluster nucleus or an ADACOM task, terminates abnormally (abends).

Ensure that sufficient space is available to start PLXCB and resubmit the job.

Once the cluster is active; that is, once a nucleus or ADACOM starts, or a user issues commands to a cluster database, the NU parameter is set and cannot be changed without bringing down the entire cluster, changing the parameter value, and restarting.

If you need to change the NU parameter value, terminate all cluster nuclei, ADACOMs, and users and restart.

The NU parameter value is being changed. The old environment is being freed.

The system has processed the NU=0 parameter. The old environment has been freed.

These messages detect when PLXCBs have a different format than programs attempting to use them. Ensures compatibility between program levels and the permanently allocated PLXCBs that continue to exist when no nuclei or ADACOMs are active.

The Adabas cluster control block (PLXCB) has been located at the address shown in the message and contains entries sufficient for the number of users.

A previously-allocated PLXCB cannot be used because of a difference between the PSW and storage keys.

Run the nucleus in the PLXCB key, or delete the existing PLXCB and reallocate it in the desired key.

This message occurs during initialization or whenever a nucleus detects a change of status for an Entire Net-Work. Normally only one nucleus on a system will issue this and process the change of state event. If the new state is up, it will be followed by messages PLX044, PLX048 and PLX088. PLX087 will be issued on other member nuclei.

No action is required for this informational message.

During initialization or whenever an Entire Net-Work becomes active, the system target is defined to it. The system target is needed to support command routing to remote systems and to update PLXCB structures on systems with no nuclei. It is issued only by the nucleus that issued PLX043 when it detected that Entire Net-Work has started.

No action is required for this informational message.

A PLXMAP update was received from a remote system for which there was no existing PLXMAP. A free PLXMAP slot could not be located. The update is discarded.

This may occur if systems containing cluster nuclei were removed from the sysplex and other systems containing nuclei were added.

If ADACOM is running, issue the DUMP PLXMAP command to examine the assignment of each PLXMAP. Contact your Software AG technical support representative for additional assistance.

A nucleus was unsuccessful when attempting to acquire or release the Entire Net-Work target. This may be either the DBID target or the system image target.

This error may occur when an Entire Net-Work becomes unavailable or when the target is not in the correct state for the action.

Issue the Entire Net-Work command D T to examine the target. Contact your Software AG technical support representative if you are unable to resolve the conflict.

Entire Net-Work must be active and there must be at least one active nucleus if the system is to hold the DBID target. A poll of all systems with active nuclei found no such suitable system.

Start a nucleus or Entire Net-Work on a system to which the DBID target may be assigned.

After polling systems with active nuclei, the system named in the message (system-name) was selected as the most suitable to hold the DBID target. It is issued only by the nucleus that issued PLX043 when it detected that Entire Net-Work has started.

No action is required for this informational message.

A PLXMAP update containing information about active nuclei and load-balancing information was attempted for the system named in the message (system-name). The update failed with the response and subcode given in the message. The command may be V2, implying the update was sent using Adabas messaging (XCF for Cluster Services) or X3, implying the update was sent using Entire Net-Work. If a PLXMAP exists for the named system, the load balancing counters and nucleus information may be cleared.

If you are unable to identify a cause for the error, contact your Software AG technical support representative for assistance.

The cluster nucleus identified by its 'nucid' for cluster 'dbid' has been initialized.

The IDT table header has been corrupted. The Adabas cluster terminates abnormally (abends).

Reinstall the Adabas SVC to reconstruct the IDT.

The ID table header has been corrupted. The Adabas cluster terminates abnormally (abends).

Reinstall the Adabas SVC to reconstruct the IDT.

GETMAIN for CLUPLXB is acquired above the 16MB line in ECSA. You have insufficient space these for CLUPLXB.

Increase the space available to CLUPLXB in ECSA.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

Virtual storage was insufficient to allocate the CQXE structures.

Increase the virtual storage available and restart the nucleus.

The Adabas Parallel Services nucleus was unable to connect to a storage object. Further details are available in the associated ADACOM job's messages.

If the cause is not clear after examining the messages in the associated ADACOM, notify your Software AG technical support representative.

The Adabas Parallel Services nucleus was unable to delete a storage object. Further details are available in the associated ADACOM job's messages.

If the cause is not clear after examining the messages in the associated ADACOM, notify your Software AG technical support representative.

An error occurred attempting to define an ALET to access shared dataspaces.

If the cause is not clear after examining the messages in the associated ADACOM, notify your Software AG technical support representative.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

Adabas Cluster Services and Adabas Parallel Services nuclei must run with z/OS APF authorization.

APF-authorize all load libraries.

The range of valid NUCIDs is 1-65000. The Adabas cluster terminates abnormally (abends).

Provide a valid NUCID for the cluster nucleus and restart.

An active PLXNUC entry was found in the PLXCB structure for the same NUCID as the starting nucleus.

Nucleus IDs must be unique. If the PLXNUC entry is the result of an earlier nucleus that failed in such a way that it could not be deactivated, the ADARUN FORCE=YES parameter will allow the PLXNUC to be overwritten. Note that incorrect or inappropriate use of FORCE=YES, such as when the NUCID is still active, may cause all nuclei in the cluster to fail and expose the database to corruption.

The Adabas cluster initialized successfully.

No action is required for this informational message.

This message is informational only. It indicates whether shutdown processing for ADACLU has begun.

No action is required for this informational message.

This message is informational only. It indicates whether shutdown processing for ADACLU has been completed.

No action is required for this informational message.

These are internal errors. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

The NUCID cannot be the same as any DBID using the same IDT (ADASVC instance).

Specify a different NUCID and resubmit the job.

The CLUFREEUSER command syntax and operands have been validated.

No action is required for this informational message.

An error was detected in the syntax or operands of a CLUFREEUSER operator command.

Reissue the CLUFREEUSER operator command with correct syntax and operands.

Various message texts (message-text) are associated with this message number. Each is explained in the following table:

No action is required for these informational messages.

An Adabas Cluster Services or Adabas Parallel Services nucleus is attempting to start, but there is already an active single nucleus with the same DBID.

Stop the single nucleus and try again.

ADACLU did not find the expected user ID string when attempting to release a PLXUSER (UTE).

If the UTE value is all zeros, the UTE was already free. This can come about if an error recovery routine such as a z/OS ESTAE attempts to clean up by issuing CL commands. Natural has error recovery that may do this, particularly if a Natural program is canceled. If this is not the case, or the UTE is non-zero, this is an internal logic error. Contact your Software AG technical support representative.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

This is an internal error. The Adabas cluster terminates abnormally (abends).

Contact your Software AG technical support representative.

GETMAIN for the IDTH prefix (the 8-byte ID table header prefix element containing information about the database) is acquired above the 16MB line in ECSA, however there is insufficient space for the GETMAIN. Remote applications accessing the database may be affected.

Possibly increase the region size or decrease other parameters to resolve this problem. For additional assistance, contact your Software AG technical support representative.

During initialization, termination, or when an Entire Net-Work change of state is detected, the Entire Net-Work DBID target was found not to be assigned to any system.

No action is required for this informational message.

The Entire Net-Work DBID target could not be successfully assigned or acquired. This message is accompanied by others such as PLX046, PLX047, PLX048, and PLX089.

If you are unable to determine the cause of the error, contact your Software AG technical support representative for assistance.

This message is issued when a nucleus has detected the DBID target is either released or not assigned, a suitable system was selected to acquire the target, and a nucleus on the system identified in the message (system-name) has successfully acquired the Entire Net-Work DBID target.

No action is required for this informational message.

During initialization, termination or when an Entire Net-Work change of state is detected, the Entire Net-Work DBID target was found to be assigned to the system named in the message. This message is issued by all member nuclei whenever the DBID target assignment changes.

No action is required for this informational message.

This nucleus has successfully acquired the Entire Net-Work DBID target.

No action is required for this informational message.

The last nucleus, on the system to which the Entire Net-Work DBID target is assigned, is terminating. The DBID target is released and may be acquired by another system, should a suitable one become available.

No action is required for this informational message.

The nucleus has signaled ADACOM to attempt to allocate cluster data spaces and shared 64-bit addressable memory objects.

No action is required for this informational message.

This nucleus is terminating and is the last nucleus of this DBID. ADACOM has been signaled to delete cluster data spaces and shared 64-bit addressable memory objects.

No action is required for this informational message.

The cluster data spaces and shared 64-bit addressable memory objects have been successfully deleted.

No action is required for this informational message.

The cluster data spaces and shared 64-bit addressable memory objects have been successfully allocated.

ADACOM cannot be found.

Determine why ADACOM is not available and correct the problem. Then restart.