Version 7.4.4
 —  Messages and Codes  —

Adalink Messages (BS2000)

The following messages are presented when errors occur in the Adabas BS2000 TP monitor interface operation.

Overview of Messages

ADAK01 | ADAK02 | ADAK03 | ADAK04 | ADAK05 | ADAK06 | ADAK07 | ADAK08 | ADAK09 | ADAK10

ADAK01 dbid UNEXPECTED RETURN CODE ret-code IN function
Explanation:

The return code "ret-code" occurred in one of the following functions and for the specified reason:

Function Reason
TRGENAMP enable memory pool (ENAMP) to target failed
IDTENAMP enable memory pool (ENAMP) for IDT failed
DSOFEI DSOFEI macro failed
UENAEI ENAEI failed for user name
SOLSIG SOLSIG macro failed
LNKLEVEL the ADALNK and ADARER levels disagree (see the first and last bytes of "ret-code")
Action:

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


ADAK02 TYPES OF LOADLIB FOR ADALNK ( adalink) AND ADARER MISMATCH
Explanation:

One module was loaded from an XS library and the other from an NXS library. NXS and XS components cannot be mixed.

This message comes with the ADAK01 message. The "ret-code" 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). "yy" must be greater than or equal to "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.

Action:

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.


ADAK03 PARAMETER ERROR
Explanation:

The Adalink parameter service detected a syntax error.

Action:

Correct the syntax and rerun.


ADAK04 THE FOLLOWING ADALNK (adalink) ARE USED FOR THIS RUN
Explanation:

Header of the Adalink parameter listing.


ADAK05 DDLNKPAR OPEN ERROR: ret-code
Explanation:

Adalink failed to open the parameter file. The value "ret-code" is the DMS return code.

Action:

Use a SAM/V format for this file.


ADAK06 ADALINK STATEMENTS IGNORED, BECAUSE ADARUN STATEMENTS PRESENT
Explanation:

Adalink is running in a nucleus or utility context, or in a user context together with ADARUN. When either is the case, the Adalink statements are ignored. Processing continues.

Action:

For the Adalink statements to be effective, specify them in a non-nucleus or non-utility context, and without ADARUN statements.


ADAK07 LRVINFO>0 AND MODULE REVEXITB NOT FOUND, PROCESSING CONTINUES
Explanation:

A nonzero LRVINFO parameter value was specified in the Adalink parameter, but the Adabas Review user exit B (REVEXITB) module could not be found. Program processing continues without REVEXITB.

Action:

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


ADAK08 REVIEW EXIT B DEACTIVATED. PROCESSING CONTINUES
Explanation:

LRVINFO=0 was either specified or omitted in the Adalink parameter or the entire Adalink parameter service is inactive, and the Adabas Review user exit B (REVEXITB) is present in the user program.

Action:

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


ADAK09 INCOMPATIBLE VERSIONS OF ADALNK AND ADAL2P, PROCESSING ABORTED
Explanation:

The versions of ADALNk and ADAL2P do not match.

Action:

Check library assignments; check TSOSLNK/BINDER protocols.


ADAK10 ADAUSER type FOR ENTRY module RC error-code
Explanation:

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 "error-code" is the Siemens macro return code.

Action:

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


Top of page