PLI* - ADACOM Initialization Messages

This message identifies the ADACOM that is initializing by its database ID and SVC settings. It is followed by one or more relevant initialization message(s) (check the following possible PLI002 messages):

Confirms the operator command just issued and the SVC/DBID combination for which it is issued.

This message is issued in response to an ADACOM DN or DIM operator command. It displays the status of the cluster nuclei located on the named image, which may be local or remote images. There is one header line for each image which may be followed by detail lines for each active nucleus. The following table describes the components of this message:

There may be conditions that prevent displaying active nuclei. These lines may appear instead of active nucleus detail lines.

This message follows PLI004 for either a DIM or DN command when there are no active cluster nuclei to display on the local image.

The command entered is not a valid ADACOM command. This message follows PLI060, which displays the invalid command entered.

Check the command used; reenter a valid ADACOM command.

This message follows PLI060 for the SN command and indicates that the SN command with the parameters specified in PLI060 has been successfully executed.

The module listed in the message (module) could not be loaded. The affected task abends.

Ensure the named module is available in the load library concatenation. If you are unable to resolve the error, contact your Software AG technical support representative.

An internal error occurred while executing STIMERM. The affected ADACOT module abends.

Contact your Software AG technical support representative.

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

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

The attempt to allocate space for an ADACOT work area failed. The affected SVC/DBID combination abends.

Increase the region size.

An internal error occurred: IDTHPRFX is invalid. The affected ADACOT module abends.

Contact your Software AG technical support representative.

An internal error occurred: the IDTH is invalid. The affected ADACOT module abends.

Contact your Software AG technical support representative.

The PLXINIT module failed during initialization. The affected ADACOT module abends.

Contact your Software AG technical support representative.

ADACOT was unable to obtain the address of the IDTH. The affected ADACOT module abends.

Contact your Software AG technical support representative.

This message occurs whenever an SVC/DBID combination terminates for any reason.

ADACOM detected that the local Entire Net-Work is not active.

ADACOM detected that the local Entire Net-Work is active and processing commands.

A parameter was supplied when issuing the ADACOM command DN. No parameters are allowed for the DN command. This message follows PLI060 which indicates the command and parameters issued.

Remove the parameter(s) and issue DN again.

The DIM command allows you to optionally supply an image name as a parameter. The DIM command was issued with a parameter value, but the value supplied is not a valid image name. This message follows PLI060 which indicates the command and parameters issued.

Supply a valid image name and issue DIM again.

CMDMGR=NO was specified in the ADACOM; ADACOM quiesces after setting the environment.

ADACOM detected an active Entire Net-Work address space and issued a periodic internal command to verify that Entire Net-Work is accepting and processing commands. The internal command received an unexpected response code and subcode, which are given in the message (rc/sc). This usually indicates a problem with Entire Net-Work.

Review the response code and subcode to determine the cause of the problem. If the problem persists, contact your Software AG technical support representative for assistance.

This message follows PLI060 for the SN command and indicates that the specified nucleus ID is not valid.

Specify a valid nucleus ID and issue the command again.

This message follows PLI060 for the SN command and indicates that the required parameters OP/CL were not specified.

Specify the required parameters and issue the command again.

This message follows PLI060 for the SN command and indicates that too many parameters have been specified when opening or closing one or more remote nuclei. Remote nuclei are always opened to local users only.

Remove the erroneous parameter(s) and issue the command again.

This message follows PLI060 for the SN command and indicates that the local nucleus specified was not found on the local image. If LCLALL was used in the command, no cluster nuclei were found on the local image.

This message follows PLI060 for the SN command. "ALL" is not a valid parameter. You must indicate whether you want to open or close all local nuclei (LCLALL) or all remote nuclei (RMTALL). You cannot open or close all cluster nuclei on all images at once. You can, of course, open a specified nucleus or all nuclei on a specified remote image, if you choose.

Specify the required parameters and issue the command again.

This message follows PLI060 for the SN command. When opening or closing nuclei on local images, you must indicate whether you are opening them to local users only (LCL) or to all cluster users (GBL).

Specify the required information and issue the command again.

This message follows PLI060 for the SN command. When opening or closing nuclei on the local image, your only choices are to open the nuclei to local users only (LCL) or to all cluster users (GBL). No other options are allowed.

Specify LCL or GBL and issue the command again.

This message follows PLI060 for the SN command and indicates that the remote nucleus specified was not found on any remote image. If a remote image was specified, no cluster nuclei were found on that image. If RMTALL was used in the command, no cluster nuclei were found on any remote image.

There are active Adabas Parallel Services nuclei that have active dataspaces, or a PLXCB dataspace is being used and one or more Adabas Parallel Services or Adabas Cluster Services nuclei are active.

Terminate any Adabas Parallel Services or Adabas Cluster Services nuclei and try again.

A DUMP operator command was entered with an operand other than one of the valid ones listed in the message.

Reissue the command with a correct operand.

Various message texts are associated with this message number. Each is described in the following table:

An internal error occurred: ADACOT was unable to release serialization for the named resource. The affected ADACOT module abends.

Contact your Software AG technical support representative.

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.

This is the first message produced when ADACOM is starting.

A MODIFY command was issued to change the SVC/DBID combination that is to receive all following MODIFY commands.

Characters were found at the end of a SVC=svc,DBID=dbid when no comma follows the SVC/DBID combination. Note that the SVC=svc and DBID=dbid can be in any order.

A MODIFY command to change the SVC/DBID combination for commands was issued with more than one SVC= or DBID=.

Reissue the command with only one SVC/DBID parameter set.

A MODIFY command to change the SVC/DBID combination for commands was issued with a nonnumeric, invalid, or out of range SVC or DBID number.

Reissue the command with a valid SVC/DBID parameter set.

A MODIFY command to change the SVC/DBID combination for commands was issued and no comma between SVC=svc and DBID=dbid.

Correct the format and reissue the command.

A MODIFY command to change the SVC/DBID combination for commands was issued and either SVC= or DBID= missing.

Add the required parameter and reissue the command.

A MODIFY command to change the SVC/DBID combination for commands was issued and the SVC/DBID pair was not specified in the input stream.

Specify the required parameters and reissue the command.

A MODIFY command to change the SVC/DBID combination for commands was issued and the SVC/DBID pair processing has ended either from NU=0 or an abend.

If you are unable to determine and correct the problem, contact your Software AG technical support representative.

This message indicates that the specified command has been issued from the ADACOM identified by the SVC and DBID listed.

A command is queued for execution. The results of the command will appear in the output data set for the SVC/DBID combination to which the command was issued.

Issued during initialization for each input line from DDKARTE or for an ADACOM operator command establishing or modifying support for a DBID/SVC pair. The text of the line appears to the right of the colon.

If you are unable to determine and correct the problem with the SVC/DBID parameter set, contact your Software AG technical support representative.

This is the last message produced when the ADACOM job is terminating as a result of an ADAEND command or an error situation.

ADACOM has initialized all specified DBID/SVC pairs. See the preceding PLI063 messages for the status of each pair's initialization.

No action is necessary for this informational message.

A request to create a PLXCB dataspace failed because ADASVC is not at the proper minimum level.

Upgrade ADASVC or request the PLXCB be allocated in common memory.

During initialization when processing input from DDKARTE, an unrecognized parameter was encountered on the card. ADACOM abends.

Check the DDKARTE parameters. If you are unable to determine and correct the problem, contact your Software AG technical support representative.

Issued on initialization when processing input from DDKARTE and a duplicate parameter entry is seen. ADACOM abends.

Correct the parameter entries and rerun the job.

Issued on initialization when an SVC or DBID number is recognized as invalid. ADACOM abends.

Correct the parameter entries and rerun the job.

Issued on initialization when an SVC or DBID number is recognized as invalid. ADACOM abends.

Correct the parameter entries and rerun the job.

Issued during initialization when the required IDTH control block cannot be found. ADACOM abends.

If you are unable to determine and correct the problem, contact your Software AG technical support representative.

Issued during initialization when the number of IDTEs specified in the IDTH is zero. ADACOM abends.

If you are unable to determine and correct the problem, contact your Software AG technical support representative.

Issued during initialization if two input cards from DDKARTE specify the same SVC/DBID combination. ADACOM abends.

Correct the parameter entries and rerun the job.

Issued during initialization when an input card from DDKARTE does not begin with "ADACOM" followed by at least one space. ADACOM abends.

Correct the format of the parameter entries and rerun the job.

Issued as the result of an ADAEND command or internal error causing an orderly shutdown. The part of the message enclosed in brackets is issued when an SVC/DBID combination has ended processing.

If you are unable to determine and correct the problem, contact your Software AG technical support representative.

Duplicate SVC/DBID combination in startup JCL. ADACOM abends.

Correct the JCL and rerun.

This message indicates a GETMAIN failure at startup (ADACOM abends) or while dynamically adding an SVC/DBID combination (the system continues running).

At startup, increase the region size and rerun. When dynamically adding an SVC/DBID combination, either terminate ADACOM, increase the region size, and rerun; or start a second ADACOM.

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

ADACOM must run with z/OS APF authorization.

Ensure that all load libraries are APF-authorized and rerun.

An Adabas ADACOM job servicing Adabas Cluster Services or Adabas Parallel Services nuclei issued an internal X2 command to release a PLXUSER representing a user either originating from or routed to another system. Such users have PLXUSERs on both systems. The command failed with the displayed response code and subcode.

The code listed in the message identifies the reason for the X2 command:

If the PLXUSER cannot be released at this time, attempts will be made at intervals to release it. Contact your Software AG technical support representative for assistance if the reason for the response code cannot be identified.

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 l get response code 148 (ADARSP148).

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, the user should contact Software AG Customer Support.

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.

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

No action is required for this informational message.