Version 8.1.3

Messages and Codes

Several different kinds of error messages can result when running Adabas Cluster Services: cluster nucleus, ADACOM, ADACLU, and Entire Net-Work messages.

Messages and codes issued from Adabas Cluster Services are described under the following headings:

../graphics/gr_b_sm.gif ADAX* Messages Adabas cluster nucleus messages
../graphics/gr_b_sm.gif PLI* Messages ADACOM initialization messages
../graphics/gr_b_sm.gif PLX* Messages ADACLU messages.

Messages and codes issued from Entire Net-Work are described under the following headings:

../graphics/gr_b_sm.gif NETnnnn Messages Entire Net-Work control module messages.
../graphics/gr_b_sm.gif NETB* Messages Entire Net-Work expandable buffer pool messages
../graphics/gr_b_sm.gif NETI* Messages ADAIOR system messages (from Entire Net-Work)
../graphics/gr_b_sm.gif NETM* Messages ADAMPM system messages (from Entire Net-Work)
../graphics/gr_b_sm.gif NETS* Messages NETSIP/NETSIR messages from the Entire Net-Work SVC installation /initialization programs.
../graphics/gr_b_sm.gif NETU* Messages Batch utility program messages
../graphics/gr_b_sm.gif NETX* Messages Entire Net-Work XCF Option messages
../graphics/gr_b_sm.gif Abend Codes Adabas and Entire Net-Work abend codes

The abend (abnormal end) codes may be issued by Adabas modules operating with Entire Net-Work. Entire Net-Work itself issues only the abend code 253 to indicate an abnormal termination occurred. The specific termination information is given in the messages written to the print data set.

../graphics/gr_b_sm.gif Response Codes Adabas nucleus response codes

In Entire Net-Work environments, the cause for these response codes is not always as apparent as in single systems. This is due to the fact that all calls are passed through interregion communications in two places: first they are passed from the user's task to Entire Net-Work; then, on the server's node, they are passed from Entire Net-Work to the server. In both instances, the same types of errors may occur. Therefore it is sometimes difficult if not impossible to determine the node on which the problem was encountered.

To aid in diagnosing such situations, Entire Net-Work provides the node ID (target ID) of the Entire Net-Work node where the problem was encountered for all problems related to these response codes. The information is returned in the Additions 2 field of the Adabas control block. Note that this field is not modified by Entire Net-Work under any other circumstances. In some cases, where the problem prevents the call from reaching Entire Net-Work on the user's node, the information obviously cannot be provided by Entire Net-Work.

In addition, a group of Adabas codes ranging from 220 through 229 is reserved for use by Entire Net-Work.

Top of page