AEO Messages

Every time an Adabas action is started, the message AXACT is written to standard output and is logged.

Example:
%ADANUC-I-AXACT, start action=ADANUC_STARTED, ROUTINE=ada_nsta.

None required

The messages CMDLOG1 and CMDLOG2 log Adabas commands whose return code is neither 0 nor 3. The severity is variable and depends on the Adabas return code. This message is logged but not written to standard output.
Refer to Response Codes that create a CMDLOG Message in Appendix A for more information.

Example:

%ADANUC-W-CMDLOG1,  FNR=999, RSP=17, CMD=L1, COP=  , AD2=...., AD2(HEX)=00000500

None required

The messages CMDLOG1 and CMDLOG2 log Adabas commands whose return code is neither 0 nor 3. The severity is variable and depends on the Adabas return code. This message is logged but not written to standard output.
Refer to the section Response Codes that create a CMDLOG Message in Appendix A for more information.

Example:

%ADANUC-W-CMDLOG2,  ISN=1, ISQ=0, UID=        , NID=PCWO02  , TID=miller/3, TH=3

Notes:

1. UID is the user ID specified in the corresponding OP command. If no Adabas session is active because no OP command was issued and option OPEN_REQUIRED is set, "********" is displayed. If a session is active, but no user ID was specified in Additions 1 of a corresponding OP command, blanks are displayed.
2. TID contains the login ID of the client program. In the case of multi-threaded applications, this is valid only for the first thread of the application doing Adabas calls; in other threads, the last bytes of the field are overwritten by a thread counter, for example TID="miller/3". This can result in overwriting parts of the login ID.
3. The values of NID and TID may have been set to different values if lnk_set_user_id was called in the client program.
4. TH is the number of the Adabas worker thread that processed the Adabas command.
5. Some Adabas commands are not transferred to the Adabas nucleus and the Adabas response code is generated directly in the ADALNK modules. For these Adabas commands, no messages CMDLOG1 and CMDLOG2 are generated.

None required

The message CPBFREE logs free entries in the checkpoint block (see: Offline Checkpoints). The severity is variable and depends on the definition of the item MESSAGE in the topic OFFLINE_CHECKPOINTS. This message is logged but not written to standard out.

Example:
If MESSAGE=(I=50,W=20,E=5,F=2) and the number of free entries=19: %ADAMUP-W-CPBFREE, free entries in checkpoint block = 19

None required

If a utility creates IPC (Interprocess communication) resources, the message CRIPC is logged. The severity is I (Information). This message is logged but not written to standard output.

Possible IPC types are:

• M = shared memory

• S = semaphore

• Q = message queue

Example:
%ADANUC-I-CRIPC, TYPE=M, NAME=0xada0004d, SIZE=913416

None required

Possible container types are ASSO and DATA. Every time a database file is extended, the remaining free space of ASSO and DATA is calculated. These values are compared with the MESSAGE definition of INCREASE_ASSO or INCREASE_DATA as appropriate. If the remaining free space ratio is less than or equal to one of these message values, the message DBFREE is logged with the associated severity. You can also use the function "adarep dbid=<dbid> free" to perform this calculation. This message is logged but not written to standard output. The extent count shows the number of allocated ASSO or DATA containers.

Example:
%ADANUC-I-DBFREE, TYPE=DATA, EXTENT-COUNT=3, SIZE=40000 KB, FREE=5320 KB, %FREE=13,30

None required

Every time a container or sequential file is opened, a DD message logs this information. The severity is always I (Information). This message is logged but not written to standard output.

Example (PC platforms):
%ADANUC-I-DD, ASSO1 = %ADADATADIR%\db<nnn>\ASSO1.<dbid>

Example (Linux):
%ADANUC-I-DD, ASSO1 = /dev/rdsk/c13d0s2

None required

If a database is extended, the message FEXT is logged. The severity is I (Information). This message is logged but not written to standard output. The extent count shows the number of allocated extents for this extent type (e.g. if the third DATA extent is allocated, COUNT=3). Possible extent types are AC, NI, UI and DATA.

Example:
%ADANUC-I-FEXT, EXTEND FNR=31, TYPE=DATA, COUNT=3, SIZE=6,63 MB (1697 * 4096 Bytes)

None required

Every time an database file is extended, the number of extents is compared with the definition of the item MESSAGE of the topic REORDER_FILE. If the extent count is greater than or equal to one of these message values, the message FIFREE is logged with the associated severity. You may use also the function "adarep dbid=<dbid> content" to perform this calculation. This message is logged but not written to standard output. The format of this message is:

Example:
%ADAMUP-I-FIFREE, FNR=12, TOPISN=110807, MAXISN=500000, NI=5, UI=2, AC=2, DS=3

None required

If a nucleus parameter is too small and an Adabas command aborts, the message INCNUCP is logged. The severity is variable and depends on the definition of the item MESSAGE in the topic INCREASE_<nucleus parameter>. Remark: A value of 101% in one of the parameters of the item MESSAGE indicates that INCNUCP will only be logged if the parameter overflows. This message is logged but not written to standard output. Refer to the section Response Codes resulting from insufficient parameter size in Appendix B for more information.

Example: for MESSAGE=(I=50,W=80,E=101):
%ADANUC-E-INCNUCP, nucleus parameter=NU, current size=500

None required

Every time a parameter is parsed by an Adabas utility, a INP message logs this information. The severity is always I (Information). This message is logged but not written to standard output.

Example: %ADAINV-I-INP, reinvert = *

None required

Every Adabas utility reads the ADABAS.INI initialization file when it is started. After the utility parameter DBID is parsed, the initialization file DBnnn.INI is also read, where nnn is the database number. If there is a configuration error in one of these files, the message INVCTRL is logged and the associated topic is disabled. This message is logged but not written to standard output.

Example:
%ADAOPR-W-INVCTRL, invalid definition: TOP1=DB_PARAMETER, TOP2=ADANUC_STARTED, ITEM=ACTION, VALUE=XYES

None required

If an error occurs while a utility creates IPC (Interprocess communication) resources, the message IPCERR is logged. The severity is F (Fatal). This message is logged but not written to standard output.
Possible IPC types are:

• M = shared memory

• S = semaphore

• Q = message queue

SYSFCT shows the C system function which is used to create the resource. ERRNO shows the system error number and ERRTXT shows the associated system error text.

Example:
%ADANUC-F-IPCERR, TYPE=M, NAME=0xada0004d, SIZE=913416, SYSFCT=shmget, ERRNO=12, ERRTXT=Not enough core

None required

An error happen during binding, typically occurs when specified port is already in use. %<utility>-I-ERROR will provide the information of the error.

Example:
%ADASTA-I-ERROR, Port XXXX is already in use
%ADASTA-E-SOCKERR, Error while performing Binding

None required