LNKENAB Messages During CICS PLTPI Processing

The Adabas task-related user exit has been enabled.

CICS is determining the location of the global work area (GWA) for the command-level link components.

An initialization call is being made to the command-level link routine.

The Adabas SVC environment is being established.

The CICS environment needed for the command-level link components has been built.

This message displays the task-related user exit name and the Adabas link routine with which it is associated.

This message displays the default SVC number and DBID.

This message displays the UB pool address and NUBS value.

This message displays the address of the Adabas user exit A or "not in use" if user exit A is not in use.

This message displays the address of the Adabas user exit B or "not in use" if user exit B is not in use.

This message displays the address of the Adabas Review exit, or "not in use" if the Adabas Review exit is not in use.

The Adabas external security interface (ADASAF) is in use. This message is not displayed if ADASAF is not in use.

Adabas transactions are being coordinated through the CICS Resource Manager Interface (RMI) using the Adabas Transaction Manager (ATM). This message is not displayed if the RMI is not in use.

The Adabas Bridge for VSAM (AVB) is in use. This message is not displayed if AVB is not in use.

This message displays the address allocated to the global work area.

This message displays the entry point address (EPA) of the Adabas link routine.

This message displays the entry point address (EPA) of the Adabas link routine direct call interface (DCI).

This message displays the address of the Adabas SVC IDT header.

The CICS RMI for Adabas is in use and resynchronization will now take place for any incomplete transactions involving Adabas databases.

The CICS RMI for Adabas is in use and resynchronization may be required for incomplete transactions involving Adabas databases. However, the Adabas Transaction Manager (ATM) is not currently active. Resynchronization will occur when ATM is restarted.

The task related user exit could not be enabled due to the EIB response code "xxxxxxxx" and EIB response code 2 "xxxxxx".

Consult the appropriate CICS documentation to determine the cause of the error in the exec interface block (EIB).

The requested task-related user exit global storage could not be EXTRACTed due to the EIB response and response 2 codes given as "xxxxxxxx".

Consult the appropriate CICS documentation to determine the cause of the error in extracting the global work area.

The Initialize Link command (IL) could not be executed because of EIB response code "xxxxxxxx", or Adabas response code "nnnn".

If the EIBRCODE field returns a non-zero value, consult the appropriate CICS documentation to determine the cause of the error. If the ADARSP returns a non-zero value, consult the response codes in chapter 2.

The close command (CL) to Adabas failed due a response code other than response 148.

Most often, this is caused by an incorrect Adabas SVC number in the ADAGSET macro; otherwise, check to see that the Adabas SVC is installed, and at the correct version.

The IDTH address was not set by the command-level link routine during the CL command.

Verify that the correct version of the Adabas command-level link routine is installed, and that the entry point name "ENTPT=" in ADAGSET is correct.

The ADAENAB version does not match the version of the ADATRUE or "ADABAS" link routine being installed. All three modules must be at the same version for the install to succeed.

Verify that the correct version of all three modules is installed.

The RMI initialization routine could not complete its processing due to the indicated error. The message may provide a failing CICS command ("cmd") and response code ("resp"), or an ATM error code ("rc") and, if relevant, Adabas response code ("resp").

Investigate the meaning of the displayed response code and/or error code. If possible, correct the error; otherwise, report the details to your Software AG technical support representative.

The load of the Adabas command-level link routine module failed. The hexadecimal representation of the CICS EIBRCODE (eibrcode) returned by the failing EXEC CICS LOAD command is given in the message.

Determine the cause of the failure. The reason for the failure may be determined by examining previous messages produced by the ADAENAB installation program. These messages are written to the JES joblog for z/OS and to SYSLOG for VSE. For more information please consult your Adabas installation documentation.

A failure occurred during the execution of the enhanced installation program. The Adabas TRUE (Task Related User Exit) is disabled. The name of the Adabas TRUE module being installed is given in the message (module-name).

Determine the cause of the failure. The reason for the failure may be determined by examining previous messages produced by the ADAENAB installation program. These messages are written to the JES joblog for z/OS and to SYSLOG for VSE. For more information please consult your Adabas installation documentation.

A failure occurred during the execution of the enhanced installation program. The CICS command-level link routine has been released. The name of the Adabas CICS command-level link routine being installed is given in the message (module-name).

Determine the cause of the failure. The reason for the failure may be determined by examining previous messages produced by the ADAENAB installation program. These messages are written to the JES joblog for z/OS and to SYSLOG for VSE. For more information please consult your Adabas installation documentation.