ADAK* System Messages

This message is produced when the following ACIOPT statement is coded:

ACIOPT ENTRY=GLOBAL,IMSGDEST=TDQ/BOTH,IMQNAME=qname

It provides the name of the transient data queue (qname) where installation messages are written and the DD name (z/OS) or DLBL name (z/VSE) of the file (dname) associated with the transient data queue

No action is required for this informational message.

During BS2000 TP monitor interface operations, the return code (ret-code) given in the message occurred in one of the following functions and for the specified reason:

See the BS2000 Executive Macro documentation for an explanation of "ret-code".

During BS2000 TP monitor interface operations, one module was loaded from an XS library and the other from an NXS library. NXS and XS components cannot be mixed.

This message is accompanied by the ADAK01 message.

The adalnk field of this message has the format xx0000yy, where xx is the level of the ADALNK and yy is the level of the ADARER (router). The value of yy must be greater than or equal to the value of xx.

If yy is less than xx, the IDT common memory where the ADARER is loaded has been created by and loaded from an older Adabas version. For example, if xx=83 and yy=81, an Adabas 61x ADALNK is using an Adabas 53x ADARER.

Check the Adabas library versions of the databases that are using the IDTNAME (the default is ADABAS5F) of your ADALNK.

Either upgrade databases using older Adabas libraries to the new version, or use different IDTNAMEs for different Adabas versions.

A BS2000 attempt to access the ID table memory pool given in the parameter file or module returned the error shown in the message (err), probabl in ENAMP.

This error is accompanied by the user abend 680.

Check the parameter file for the IDTNAME or DBTIDT value; otherwise check the BSCONFIG(ENVNAME), IDTABEL, or MDBIDT macros in SSFB2C.

The DBID/ID table cannot be set up or accessed. This message is accompanied by user abend 678 or 679. This is usually an error in getting memory. The error code is from a BS2000 macro.

Contact your Software AG technical support representative with the error code produced.

During BS2000 TP monitor interface operations, the ADALNK parameter service detected a syntax error.

Correct the syntax and rerun.

This is the header of the ADALNK parameter listing used during BS2000 TP monitor interface operations.

No action is required.

Explanation: This message is produced at the beginning of ADACIC0 installation processing and identifies the number of TRUEs that ADACIC0 is attempting to install. The number (nnnn) is derived from the number of ENTRY=GROUP items that were coded in the ACIOPT module

No action is required for this informational message.

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

During CICS PLTPI processing, an initialization call is being made to the command-level link routine.

During CICS PLTPI processing, the Adabas SVC environment is being established.

During CICS PLTPI processing, the CICS environment needed for the command-level link components has been built.

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

This message occurs during CICS PLTPI processing and displays the default SVC number and DBID.

This message occurs during CICS PLTPI processing and displays the UB pool address and NUBS value.

This message occurs during CICS PLTPI processing and displays the address of the Adabas user exit 1 (user exit A in Adabas 7) or "not in use" if the user exit is not in use.

This message occurs during CICS PLTPI processing and displays the address of the Adabas user exit B or "not in use" if user exit B is not in use.

During BS2000 processing an attempt to access the file associated with the link name DDLNKPAR failed. The error is a DMS error code.

Perform a SHOW-FILE on the file associated with the linkname DDLNKPAR. If a DMS error occurs, perform HELP_MESSAGE DMSnnnn. This should help identify the problem.

This message occurs during CICS PLTPI processing and displays the address of the Adabas Review exit, or "not in use" if the Adabas Review exit is not in use.

During CICS PLTPI processing, the Adabas external security interface (ADASAF) is in use. This message is not displayed if ADASAF is not in use.

During CICS PLTPI processing, 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.

During CICS PLTPI processing, the Adabas Bridge for VSAM (AVB) is in use. This message is not displayed if AVB is not in use.

This message occurs during CICS PLTPI processing and displays the address allocated to the global work area.

This message occurs during CICS PLTPI processing and displays the entry point address (EPA) of the Adabas link routine.

This message occurs during CICS PLTPI processing and displays the entry point address (EPA) of the Adabas link routine direct call interface (DCI).

This message occurs during CICS PLTPI processing and displays the address of the Adabas SVC IDT header.

During CICS PLTPI processing, the CICS RMI for Adabas is in use and resynchronization will now take place for any incomplete transactions involving Adabas databases.

During CICS PLTPI processing, 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.

A BS2000 session is running an ADALNK with both ADARUN and link name DDCARD, together with a file on the link name DDLNKPAR. The parameters in DDLNKPAR will not be used.

No action required for this informational message.

The task related user exit could not be enabled due to the EIB response codes xxxxxxxx1 and xxxxxxxx2.

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 codes given as xxxxxxxx1 and xxxxxxxx2.

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

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

Various message texts may be provided using this message number. Review the table below to determine the cause of the error and the course of action to take.

The action that should be taken depends on the message text issued with this message number. Review the table above for the appropriate action.

Various message texts may be provided using this message number. Review the table below to determine the cause of the error and the course of action to take.

The action that should be taken depends on the message text issued with this message number. Review the table above for the appropriate action.

During BS2000 TP monitor interface operations, a nonzero LRVINFO parameter value was specified in the ADALNK parameter, but the Adabas Review user exit B (REVEXITB) module could not be found. Program processing continues without REVEXITB.

Either specify LRVINFO=0, remove the LRVINFO parameter statement, or include the REVEXITB module in the program.

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 ADACIC0 installation program. These messages are written to the JES job log for z/OS and to SYSLOG for z/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 ADACIC0 installation program. These messages are written to the JES job log for z/OS and to SYSLOG for z/VSE. For more information please consult your Adabas installation documentation.

The CICS GETMAIN for shared storage for the Adabas user buffer pool failed. The returned value of EIBRESP from the CICS request is printed in hexadecimal at the end of the message.

Consult the appropriate IBM CICS documentation for the meaning of the returned EIBRESP value.

The storage for the Adabas user buffer pool was not released. The returned value of EIBRESP from the CICS FREEMAIN request is returned at the end of the message.

Consult the appropriate IBM CICS documentation for the meaning of the returned EIBRESP value.

The LGBLSET parameters DYNDBSVC=YES and DBSVCTN=dbid-svc-tbl-name parameters are coded in the CICS link globals table and the named DBID/SVC routing table is found and loaded. The name of the DBID/SVC routing table is given in the message (table-name).

No action is required for this informational message.

This message provides the status of the Adabas Review client exit, REVEXIT2. If a hexadecimal address is listed in the message, the Adabas Review client exit is installed and active. If "Not Installed" is listed in the message, then the Adabas Review client exit is not linked with the globals table used by the TRUE being activated in this phase of the installation. If "Not Active" is listed in the message, the Adabas Review client exit is linked with the globals table, but REVCLNT=NO was coded before the globals table was assembled and the exit is considered inactive.

No action is required for this informational message.

If the Review client exit is installed (see ADAK075), this message is produced during the installation of the Adabas CICS components to indicate the default Adabas Review hub ID that will be used by this client exit. If the numeric hub ID is listed in the message, then this is the target where client records will be sent by default, as specified in the globals table with the REVHID keyword. If "dynamic" is listed in the message instead of a specific hub ID, then no value was given in the globals table and the caller, usually SYSREVDB, must provide the hub ID to be used by the Adabas Review client exit.

No action is required for this informational message.

During BS2000 TP monitor interface operations, LRVINFO=0 was either specified or omitted in the ADALNK parameter or the entire ADALNK parameter service is inactive, and the Adabas Review user exit B (REVEXITB) is present in the user program.

To activate REVEXITB, specify LRVINFO=256; otherwise, no change is necessary.

This message is issued at the end of ADACIC0 installation processing. It provides the actual number of TRUEs that were successfully installed (nnnn) and identifies the number of TRUE installations that were attempted (tttt).

No action is required for this informational message.

During BS2000 TP monitor interface operations, it was determined that the versions of ADALNK and ADAL2P do not match.

Check library assignments; check TSOSLNK/BINDER protocols.

During BS2000 TP monitor interface operations, an error occurred while attempting to access the Adabas link module where type is either REQM for requesting memory or BIND for attempting to load; module is the name of the module to be accessed; and rc is the Fujitsu Technology Solutions macro return code.

If the type is

• BIND, check the file link statements for the presence of the Adabas library

• REQM, there is a memory shortage in the application program address space