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

An attempt was made to update PLXCB structures on another operating system image participating in Adabas Cluster Services (ALS). The response code (rsp) and subcode (subcode) given in the message indicate an unexpected condition. The Entire Net-Work node ID may also be given in the message (node) if Entire Net-Work does not have connectivity to the remote system or if there are problems in the PLXCB structures on the remote system.

If the reason for the response code is not clear and you cannot resolve the error by analyzing it, contact your Software AG technical support representative.

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.

The remote image, identified in the message by its system name, holds the DBID as a network target.

No action is required for this informational message.

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

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.

No image in the network holds the DBID as a network target and this nucleus failed in its attempt to establish it. This is an error condition. Commands from users in an image with no active nucleus and no active ADACOM 1 get response 148.

Either start up a different node in the network or shut down and restart an existing node to see if the problem resolves itself. If the problem persists, contact your Software AG technical support representative.

After a nucleus terminated, no remaining nucleus acquired the Net-Work DBID target.

If there are one or more nuclei that could become the Net-Work DBID target, either start up a different node in the network or shut down and restart an existing node to see if the problem resolves itself. If the problem persists, contact your Software AG technical support representative.

After a nucleus terminated, the Net-Work DBID target was acquired on the system named in the message by another nucleus.

No action is required for this informational message.

The image in which this nucleus is active holds the DBID as a network target.

No action is required for this informational message.

This nucleus is terminating and is the last nucleus on this system. The Net-Work DBID target is held on this system and is not released. If there are nuclei available on other systems, one of them should acquire the DBID target.

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.