Version 8.1.3

PLX* - ADACLU Messages

ADACLU messages apply only to Adabas nucleus cluster environments.

All of the following messages are both printed on the console and written to the DD/PRINT data set.

Each message begins with a timestamp in the format "hh:mm:ss" and a jobname.

The 'dbid' and 'nucid' are shown as five numeric characters with leading zeros.

Overview of Messages

PLX001 | PLX002 | PLX003 | PLX004 | PLX005 | PLX006 | PLX007 | PLX014 | PLX043 | PLX044 | PLX045 | PLX046 | PLX047 | PLX048 | PLX049 | PLX050 | PLX051 | PLX052 | PLX053 | PLX054 | PLX055 | PLX056 | PLX057 | PLX058 | PLX059 | PLX060 | PLX061 | PLX062 | PLX064 | PLX066 | PLX067 | PLX068 | PLX069 | PLX071 | PLX073 | PLX074 | PLX075 | PLX076 | PLX078 | PLX080 | PLX081 | PLX082 | PLX083 | PLX084 | PLX085 | PLX086 | PLX087 | PLX088 | PLX089 | PLX090 | PLX091 | PLX092 | PLX097 | PLX099

PLX001 dbid Acquiring new PLXCB
Explanation

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


PLX002 dbid GETMAIN failed for PLXCB
Explanation

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

Action

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


PLX003 dbid Cannot change number of users now
dbid Cannot free PLXCB at this time
dbid There are active NUCs/ADACOMs
Explanation

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.

Action

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


PLX004 dbid Freeing old PLXCB
Explanation

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


PLX005 dbid Processed NU=O request
Explanation

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


PLX006 dbid PLXCB version is vrs
dbid program Program level is vrs
dbid FORCE=YES detected - initialization continues
dbid This SVC/DBID combination will terminate
Explanation

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.


PLX007 dbid Max users for image number-of-users
dbid PLXCB located at address
Explanation

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.


PLX014 PSW key pswkey not compatible with PLXCB key plxcbkey
Explanation

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

Action

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


PLX043 dbid Net-Work detected {up|down}
Explanation

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.

Action

No action is required for this informational message.


PLX044 dbid System image target target established
Explanation

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.

Action

No action is required for this informational message.


PLX045 dbid Unable to allocate PLXMAP for system-target on system-name
Explanation

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.

Action

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.


PLX046 dbid Feed{acquire|release} target target failed RSP rsp/node-subcode nucid
Explanation

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.

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.


PLX047 dbid No suitable system found for DBID target
Explanation

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.

Action

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


PLX048 dbid System system-name selected for DBID target
Explanation

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.

Action

No action is required for this informational message.


PLX049 dbidPLXMAP cmd RSP rsp/node-subcode from target on system-name
Explanation

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.

Action

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


PLX050 dbid ADACLU INIT DBID=dbid NUCID=nucid
Explanation

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


PLX051 dbid IDTH prefix is not valid
Explanation

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

Action

Reinstall the Adabas SVC to reconstruct the IDT.


PLX052 dbid Number of IDTE entries is zero
Explanation

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

Action

Reinstall the Adabas SVC to reconstruct the IDT.


PLX053 dbid GETMAIN for CLUPLXB failed
Explanation

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

Action

Increase the space available to CLUPLXB in ECSA.


PLX054 dbid MPM initialization failed
Explanation

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

Actions:

Contact your Software AG technical support representative.


PLX055 dbid GETMAIN for CQXE failed
Explanation

Virtual storage was insufficient to allocate the CQXE structures.

Action

Increase the virtual storage available and restart the nucleus.


PLX056 dbid Dataspace/S64 acquisition failed
Explanation

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

Action

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


PLX057 dbid Dataspace/S64 delete failed
Explanation

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

Action

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


PLX058 dbid ALSERV failed
Explanation

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

Action

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


PLX059 dbid pointer to IDTH is zero
Explanation

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

Action

Contact your Software AG technical support representative.


PLX060 dbid Invalid function code for ADACLU
Explanation

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

Action

Contact your Software AG technical support representative.


PLX061 dbid No useable PLXNUC found
Explanation

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

Action

Contact your Software AG technical support representative.


PLX062 dbid Job is not authorized
Explanation

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

Action

APF-authorize all load libraries.


PLX064 dbid Maximum NUCID is 65000
Explanation

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

Action

Provide a valid NUCID for the cluster nucleus and restart.


PLX066 dbid Duplicate NUCID in active PLXNUC
Explanation

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

Action

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.


PLX067 dbid Initialization of ADACLU complete
Explanation

The Adabas cluster initialized successfully.

Action

No action is required for this informational message.


PLX068 dbid Termination of ADACLU beginning
Explanation

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

Action

No action is required for this informational message.


PLX069 dbid Termination of ADACLU complete
Explanation

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

Action

No action is required for this informational message.


PLX071 dbid ADACLU - Invalid CLUINTER eyecatcher
dbid ADACLU - Invalid thread number
dbid ADACLU - CLUINTER in use
Explanation

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

Action

Contact your Software AG technical support representative.


PLX073 dbid NUCID in use as a cluster DBID
Explanation

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

Action

Specify a different NUCID and resubmit the job.


PLX074 dbid CLUFREEUSER command accepted
Explanation

The CLUFREEUSER command syntax and operands have been validated.

Action

No action is required for this informational message.


PLX075 dbid CLUFREEUSER invalid syntax starting text
Explanation

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

Action

Reissue the CLUFREEUSER operator command with correct syntax and operands.


PLX076 dbid message-text
Explanation

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

Message Text Explanation
No users were deleted The CLUFREEUSER operator command was issued, but no eligible users were found to delete.
Not deleted pending RSP 9/20 is number-of users The CLUFREEUSER operator command was issued but the FORCE parameter was not specified and the number of users specified were pending a response code 9, subcode 20.
Number of users deleted is number The CLUFREEUSER operator command was issued and the number of users listed in the message were deleted.
Action

No action is required for these informational messages.


PLX078 dbid A local single nucleus is already up (an IDTE is active for this DBID)
Explanation

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.

Action

Stop the single nucleus and try again.


PLX080 UID mismatch freeing PLXUSER/UTE address UID uid1 UTE uid2
Explanation

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

Action

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.


PLX081 dbid IDTHPRFX not found
Explanation

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

Action

Contact your Software AG technical support representative.


PLX082 dbid DBID is zero
Explanation

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

Action

Contact your Software AG technical support representative.


PLX083 dbid Obtain of IDTHPRFX failed
Explanation

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.

Action

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


PLX084 dbid Net-Work DBID target not held
Explanation

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.

Action

No action is required for this informational message.


PLX085 dbid Net-Work DBID target not acquired
Explanation

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.

Action

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


PLX086 dbid Net-Work DBID target acquired by system-name
Explanation

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.

Action

No action is required for this informational message.


PLX087 dbid Net-Work DBID target held bysystem-name
Explanation

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.

Action

No action is required for this informational message.


PLX088 dbid Net-Work DBID target acquired by this image
Explanation

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

Action

No action is required for this informational message.


PLX089 dbid Net-Work DBID target released by this image
Explanation

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.

Action

No action is required for this informational message.


PLX090 dbid Attempting to create dataspaces/S64
Explanation

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

Action

No action is required for this informational message.


PLX091 dbid Attempting to delete dataspaces/S64
Explanation

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.

Action

No action is required for this informational message.


PLX092 dbid Dataspaces/S64 deleted
Explanation

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

Action

No action is required for this informational message.


PLX097 dbid Dataspaces acquired
Explanation

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


PLX099 dbid ADACOM not available
Explanation

ADACOM cannot be found.

Action

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


Top of page