Administration Version 6.2.2
 —  Entire Net-Work Messages and Codes  —

NETnnnn - Entire Net-Work Control Module Messages

Messages relevant to overall Entire Net-Work operation are listed below. Messages are either issued to the print data set or displayed at the operator console and logged to the print data set, as appropriate.

Overview of Messages

NET0001I: | NET0002I: | NET0003I: | NET0004I: | NET0005I: | NET0006I: | NET0007I: | NET0008I: | NET0009I: | NET0010I: | NET0011I: | NET0012I: | NET0013I: | NET0014I: | NET0015I: | NET0016I: | NET0017I: | NET0018I: | NET0019I: | NET0020I: | NET0021I: | NET0022I: | NET0023I: | NET0024I: | NET0025I: | NET0026I: | NET0027I: | NET0028I: | NET0029I: | NET0031I: | NET0032I: | NET0033I: | NET0034I: | NET0035: | NET0036I: | NET0037I: | NET0039I: | NET0040I: | NET0041I: | NET0042I: | NET0043I: | NET0050I: | NET0051I: | NET0052I: | NET0053W: | NET0054I: | NET0055E: | NET0086I: | NET0087I: | NET0088I: | NET0089I: | NET0090I: | NET0091I: | NET0092I: | NET0093I: | NET0094I: | NET0095I: | NET0096I: | NET0097I: | NET0098I: | NET0099I: | NET0101I: | NET0103I: | NET0104I: | NET0105I: | NET0106I: | NET0107I: | NET0108I: | NET0109I: | NET0110I: | NET0111I: | NET0112I: | NET0113I: | NET0114I: | NET0115I: | NET0116I: | NET0117I: | NET0118I: | NET0119I: | NET0120I: | NET0121I: | NET0122I: | NET0123I: | NET0124I: | NET0125I: | NET0126I: | NET0127I: | NET0128I: | NET0129I: | NET0130I: | NET0131I: | NET0133: | NET0134I: | NET0135I: | NET0136I: | NET0137I: | NET0139I: | NET0141I: | NET0144I: | NET0145I: | NET0146I: | NET0147I: | NET0148I: | NET0149I: | NET0150I: | NET0151I: | NET0153I: | NET0154I: | NET0170E: | NET0171I: | NET0172I: | NET0174I: | NET0240E: | NET0241I: | NET0242I: | NET0243E: | NET0244E: | NET0245E: | NET0246E: | NET0247E: | NET0250I: | NET0251I: | NET0306I: | NET0308I: | NET0322I: | NET0328E: | NET0333I: | NET0334E: | NET0998I: | NET0999I: | NET1000I: | NET1001I: | NET1002I: | NET1003I:

NET0001I: STATEMENT TOO LONG
Explanation

Entire Net-Work parameter statements, even though they may extend over multiple lines, may not be infinitely long. The current maximum for any one statement is approximately 4000 characters (not counting embedded comments).

The statement in question is not interpreted; any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Try to abbreviate some keywords or eliminate some unnecessary blanks from the statement.


NET0002I: INVALID STATEMENT: aaaaaaaa
Explanation

The statement verb, aaaaaaaa, is not one of those recognized by Entire Net-Work (NODE, DRIVER, or LINK).

The statement in question is not interpreted; any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Ensure correct coding of recognized statements; you may have coded a comment or a continuation line incorrectly.


NET0003I: INVALID KEYWORD: aaaaaaaa
Explanation

A keyword parameter was coded (aaaaaaaa), that is not recognized in this statement.

The statement in question is not interpreted beyond this point; it and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Ensure correct coding of recognized keywords; note that the set of valid keywords is likely to be different between access methods, and between DRIVER and LINK statements of the same access method.


NET0004I: INVALID VALUE FOR KEYWORD: aaaaaaaa nnn
Explanation

There are certain constraints on valid values for some keyword parameters, such as:

  • numeric values

  • hexadecimal values

  • YES or NO only, etc.

In this case, parameter aaaaaaaa was not correctly specified. The nnn value in the message is specified for multiple value parameters only; if given, it specifies the position of the subparameter in error.

The statement in question and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Action

Refer to the section Entire Net-Work Parameter Statements for the allowed parameter values.


NET0005I: DUPLICATE NODE STATEMENT
Explanation

More than one NODE statement was coded in the parameter data set.

The statement in question is not interpreted. Any statements following it are scanned for errors. Session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Eliminate all but one of the NODE statements from the parameter data set.


NET0006I: INVALID DRIVER NAME: aaaaaaaa
Explanation

The value aaaaaaaa is not a valid line driver name.

The statement in question is not interpreted; any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

For the valid name, see the documentation for the Simple Connection Line Driver.


NET0007I: DUPLICATE aaaaaaaa DRIVER STATEMENT
Explanation

More than one DRIVER statement was coded for the access method aaaaaaaa.

The statement in question is not interpreted; any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Eliminate any extraneous DRIVER statements from the parameter data set.


NET0008I: aaaa DRIVER NOT AVAILABLE
Explanation

The NETaaaa line driver module could not be loaded from your libraries. This is either due to an error in specifying the line driver name, or the line driver is not installed in your libraries.

The statement in question is not interpreted; any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may result from this error.

Action

Ensure that the driver NETaaaa is available and installed correctly, verify correct spelling, or check your JCL for correct library specifications.


NET0009I: MORE THAN nn VALUES FOR KEYWORD: aaaaaaaa
Explanation

More values than expected were coded for the multiple-value keyword parameter aaaaaaaa. The value nn is the maximum number of values permitted by the definition of the parameter.

The statement in question and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may be caused by this error.

Action

Refer to the section Entire Net-Work Parameter Statements for the allowed parameter values.


NET0010I: REQUIRED PARAMETER NOT SPECIFIED: aaaaaaaa nnn
Explanation

The keyword or positional parameter aaaaaaaa was either incorrectly specified or was missing. The value nnn is specified for multiple value parameters only; if given, it specifies the position of the missing subparameter.

The statement in question and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may be caused by this error.

Action

Refer to the section Entire Net-Work Parameter Statements for the allowed parameter values.


NET0011I: EOF FOUND BEFORE END OF STATEMENT
Explanation

The last statement line found before the end of the data set indicated that a continuation line was to be expected.

The Entire Net-Work session is terminated abnormally.

Action

Correct the parameter statement.


NET0012I: Adabas LIBRARY IS NOT Y2K READY
Explanation

This message informs you that your Adabas library does not provide Year 2000 support.

None. This message is informational only.

Action

If you want Year 2000 compliance, upgrade the Adabas installed on your system to Version 6.2 SP1 or later or use the WAL library provided with Entire Net-Work.


NET0013I: BUFFER POOL INIT FAILED, RC=nn
Explanation

The Entire Net-Work Buffer Pool Manager failed to set up the buffer pools as specified in the BUFFERS keyword parameter on the NODE statement.

Return codes of 20 and 24 indicate that the required amounts of memory were not available; other values indicate possible internal errors, and should be reported to your Software AG technical support representative.

The Entire Net-Work session is terminated abnormally.

Action

Correct the condition that caused the buffer pool failure (provide enough storage in the partition or address space, provide enough real storage to permit page-fixing the page-fixed buffer pool, or consider reducing the buffer pool sizes). On BS2000 systems, check the address space limit by calling SHOW-USER-ATTRIBUTES and, if necessary, increase it using MODIFY-USER-ATTRIBUTES from a privileged user ID.


NET0014I: CONTROL BLOCK SPACE UNAVAILABLE
Explanation

A storage request for permanent control blocks failed. Permanent control blocks describing the network topology are not allocated from the buffer pools but obtained from the operating system instead.

The Entire Net-Work session is terminated abnormally.

Action

Provide more storage in the partition or address space.


NET0015I: aaaa DRIVER INIT FAILED (RC=nn)
Explanation

Line driver initialization failed; an explanatory message should have been issued by the line driver. The return code (nn) is access method dependent; it may relate to possible internal errors.

The statements following this DRIVER statement are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may be caused by this error.

Action

Refer to the access-method-specific messages for corrective action. If an internal error is indicated, have a system dump and any other documentation available and contact your Software AG technical support representative.


NET0016I: aaaa DRIVER NOT PREVIOUSLY INITIALIZED
Explanation

A LINK statement referred to the access method aaaa, but either a DRIVER statement for aaaa was not specified, the specified line driver could not be loaded, or the driver initialization failed. Note that the DRIVER statement must appear before the LINK statement.

The statement in question and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may be caused by this error.

Action

Ensure that a DRIVER statement is before the LINK statement and that the LINK statement specifies the correct DRIVER statement name.


NET0017I: DUPLICATE LINK NAME: aaaaaaaa
Explanation

The names of all links on a node must be unique.

The statement in question and any statements following it are scanned for errors; session initialization is aborted after all statements have been read.

Note:
Errors reported in subsequent statements may be caused by this error.

Action

Assign unique link names to all LINK statements on the node.


NET0018I: ADAMPM CALL nn FAILED
Explanation

An error occurred during interregion processing. Most likely, ADAMPM has also issued a NETMxx message to explain the problem; otherwise, an internal system error occurred. The call type is specified as nn.

The Entire Net-Work session is terminated abnormally.

Action

Refer to the section ADAMPM Messages for details. If a system error occurred, have a system dump and any other documentation available, and contact your Software AG technical support representative.


NET0019I: COMMAND QUEUE SPACE UNAVAILABLE
Explanation

The storage request for the command queue (request queue) failed. The amount of storage necessary is (NC+1)*192 bytes, where NC is the value of the NC parameter in the ADARUN statement.

The Entire Net-Work session is terminated abnormally.

Action

Provide more storage in the partition or address space or reset the NC parameter value. Note that the amount of storage required for the command queue is usually small compared to the overall storage requirements of Entire Net-Work.


NET0020I: UNRESOLVED VCONS IN DRIVER MODULE
Explanation

An internal error occurred; an incorrect line driver module was probably loaded.

The Entire Net-Work session is terminated abnormally.

Action

Have the storage dump and/or dumps of the Entire Net-Work modules available, then contact your Software AG technical support representative.


NET0021I: UNEXPECTED EVENT INDICATOR: xxxxxxxx
Explanation

An internal error occurred; an incorrect line driver module was probably loaded.

The Entire Net-Work session is terminated abnormally.

Action

Have the storage dump and/or dumps of the Entire Net-Work modules available, then contact your Software AG technical support representative.


NET0022I: ACM WORK BUFFER SHORTAGE
Explanation

The access method working storage requests could not be satisfied by the line driver. This typically indicates an insufficient asynchronous buffer pool size.

The Entire Net-Work session is terminated abnormally.

Action

Check the buffer pool statistics printed at the end of the session, provide more storage in the asynchronous buffer pool.

For BS2000 systems running TCP/IP with subtask NETTCP, the ADARUN CMSIZE parameter and possibly the address space size need to be increased.


NET0023I: NODE STATEMENT MISSING
Explanation

A NODE statement must be given as the first parameter statement.

The Entire Net-Work session is terminated abnormally.

Action

Code an appropriate NODE statement as the first parameter statement. For more information, see the section Entire Net-Work Parameter Statements.


NET0024I: NO DRIVER LOADED
Explanation

After initialization, the number of successfully initialized line drivers is zero. With no active line drivers, there is no point in continuing the Entire Net-Work session.

The Entire Net-Work session is terminated abnormally.

Action

Verify that all line drivers and their environments have been installed correctly, and that all DRIVER statements have been coded accordingly.


NET0025I: TRACE TABLE INIT FAILED, RC=nn
Explanation

The requested trace table could not be initialized. RC=4 indicates that not enough storage was available; any other value indicates an internal error.

The system continues to run, but with tracing disabled.

Action

If RC=4, either try to run with a smaller trace table or provide a larger partition or address space. If nn is other than 4, contact your Software AG technical support representative.


NET0026I: INITIALIZATION FAILED
Explanation

This is an informational message only, specific error conditions are described in preceding messages.

The Entire Net-Work session is terminated abnormally.

Action

Refer to the preceding messages for the reasons for the failure.


NET0027I: HANDSHAKE BUFFER SHORTAGE (RC=nn)
Explanation

There were not enough short-term buffers available to sustain the handshake process. It is highly unlikely that the present amount of buffer space is adequate to handle any message traffic.

Return code values other than 4 or 8 may indicate an internal problem and should be reported to your Software AG technical support representative.

The Entire Net-Work session is terminated abnormally.

Action

Provide more storage in the short term (or possibly the page-fixed) buffer pool, according to the buffer pool statistics provided.


NET0028I: MESSAGE BUFFER SHORTAGE
Explanation

There were not enough short-term buffers available to handle message traffic.

The Entire Net-Work session is terminated abnormally.

Action

No action is usually required for this mainly informational message. If followed by a NET017I Disconnect message, there is a buffer pool shortage. Provide more storage in the asynchronous buffer pool. In BS2000 systems running a TCP/IP subtask, increase the CMSIZE ADARUN parameter and possibly the address space size.


NET0029I: B1: TARGET xxxxx INIT ON UNKNOWN NODE yyyyy
Explanation

A B1 broadcast message was received from an unknown node. This indicates an error condition in the internal network tables.

None. This message is informational only. The Entire Net-Work session continues operation.

Action

If this message occurs repeatedly, attempt to locate inconsistent Entire Net-Work descriptions. Report the problem to your Software AG technical support representative.


NET0031I: INVALID LOG PARAMETER
Explanation

The value specified for the LOG keyword on the NODE statement or the SET operator command was invalid.

The erroneous parameter is ignored. Processing continues normally.

Action

Use the SET operator command to specify the correct LOG parameter value.


NET0032I: EXCESSIVE ECB COUNT IN DRIVER aaaa
Explanation

An internal error occurred; an incorrect module was probably loaded as line driver NETaaaa.

The Entire Net-Work session is terminated abnormally.

Action

Have the storage dump and/or dumps of the Entire Net-Work modules available, then contact your Software AG technical support representative.


NET0033I: aaaa DRIVER REQUIRES PAGE-FIXED BUFFERS
Explanation

The access method aaaa requires a page-fixed buffer pool in order to function in your operating system configuration.

The line driver initialization is aborted. The system may continue operating if other line drivers are active.

Action

Use the BUFFERS parameter on the NODE statement to specify a page-fixed buffer pool. For more information, see the section Entire Net-Work Parameter Statements.


NET0034I: UNSUPPORTED VERSION OF ADAIOR. NETWRK TERMINATING
Explanation

An unsupported version of Adabas or the WAL library is being used.

Action

Supply the appropriate Adabas or WAL libraries.


NET0035: ISOLATED TARGET targetid CANNOT BE ACCESSED FROM THIS NODE
Explanation

The targetid specified in the message cannot be handled because its value is greater than 255. This should only happen when Entire Net-Work is using an unsupported release of the WAL component. This target is unavailable to this node.

Action

Verify that the Entire Net-Work node that issued this message is using a supported version of WAL.


NET0036I: rrrrrrrr mmmmmmmmmm nnnnnnnnnn
Explanation

This message is issued in response to operator command DISPLAY STATS EXTENDED. It lists statistics for internal Entire Net-Work service routines.

Action

No action is required. This message is for Software AG use only.


NET0037I: module (yyyy-mm-dd SM=sss) ZAP LEVEL zzzz
Explanation

This message is issued in response to operator command DISPLAY ZAPS. For each Entire Net-Work module, its name, assembly date, system maintenance level, and zap level are displayed. If zaps were applied after initial shipment, their numbers are listed as 'Additional Zaps .

Action

No action is required. This message is informational only.


NET0039I: xxxxxxxx, NETSAF VERSION IS INVALID, SHUTDOWN
Explanation

The NETSAF module version is invalid or the NETSAF module is not available; xxxxxxxx is the name of the module issuing the message. Entire Net-Work will shut down following this message.

Action

Save the DDPRINT and contact your Software AG technical support representative.


NET0040I: GET NETSAF WORK AREA FAILED FOR LINK xxxxxxxx;
Explanation

An attempt to obtain buffer pool storage for the NETSAF work area failed for link xxxxxxxx. Security authorization cannot be performed without this work area, so the link is disconnected.

Action

The failure may be due to a buffer pool shortage. Check the buffer pool statistics. In z/VM and BS2000/OSD environments (running Sockets 2.1 or earlier), you may need to increase the value of the buffer pool parameters. In other environments, you may need to increase the region size.


NET0041I: NETRCV BUFFER SHORTAGE, NET-WORK TERMINATING.
Explanation

NETRCV was unable to get the necessary storage. Entire Net-Work will shut down following this message.

Action

Save the DDPRINT and the DUMP, if available, and contact your Software AG technical support representative.


NET0042I: LOCAL TARGET nnnnnn ACTIVE.
Explanation

This message is issued for each new target that becomes activated when Entire Net-Work is active.

Action

No action is required for this informational message.


NET0043I: LOCAL TARGET nnnnnn INACTIVE.
Explanation

This message is issued for each new target that becomes deactivated when Entire Net-Work is active.

Action

No action is required for this informational message.


NET0050I: PAGE FIXED BUFFERS MUST BE SET TO 0 IN CMS
Explanation

In z/VM environments, the Page-Fixed Buffer Pool size set by the BUFFERS parameter on the NODE statement must be zero (0). For more information, see the section Entire Net-Work Parameter Statements.

Entire Net-Work resets the Page-Fixed Buffer Pool size to 0 and continues the initialization process.

Action

Set the fourth value of the BUFFERS parameter on the NODE statement to 0.


NET0051I: NUCLEUS EXTENSION xxxxxxxx NOT FOUND
Explanation

The module xxxxxxxx has not previously been loaded as a nucleus extension. This message applies to z/VM environments only

Entire Net-Work terminates the initialization process.

Action

Ensure that Entire Net-Work is being started properly. The NUCXTNTS EXEC must be run before Entire Net-Work is started.


NET0052I: INVALID LOGSIZE VALUE; LOGSIZE SET TO 32000
Explanation

A value greater than 32000 has been specified for the LOGSIZE parameter. The valid range is 0 - 32000.

The value is set to 32000 and Entire Net-Work continues.

Action

Specify a valid LOGSIZE value.

Module

NETWRK


NET0053W: UNABLE TO VERIFY LICENSE MODULE NETLIC
Explanation

The customer license file is not available for Entire Net-Work to authenticate. This is a warning message, Entire Net-Work will initialize normally.

Issue warning message and continue initialization.

Action

Contact your Software AG sales representative to obtain a valid Entire Net-Work license file. The severity of this message may increase in future releases.

Module

NETWRK


NET0054I: STARTING LICENSE VERIFICATION FOR ENTIRE NET-WORK node
Explanation

Entire Net-Work is verifying your customer license.

Action

No action is required for this informational message.

Module

NETWRK


NET0055E: NETFLIC INTERNAL BUFFER ERROR. LICENSE VERIFICATION TERMINATED.
Explanation

License processing was unable to obtain the storage required to invoke LICMAIN, the Software AG license verification module. After this error, license verification will terminate, but Entire Net-Work will complete coming up and will run without license verification.

Action

Contact your Software AG technical support representative about the error.

Module

NETFLIC


NET0086I: INVALID SNAP PARAMETER: xxxxxxxx
Explanation

A SNAP operator command was issued with an invalid additional parameter. Valid parameters are MAIN, MYBLK, TRACE, CURRMSG, UBQ, CQ, and BPH.

Action

Re-issue the SNAP command with valid parameters. For more information, see the section Entire Net-Work Operator Commands.


NET0087I: nnnnnnnnnn REQUESTS FROM LOCAL RQ
Explanation

This is an informational message displaying the number of requests Entire Net-Work received from its local Request Queue for transmission to other nodes.


NET0088I: nnnnnnnnnn REQUESTS FOR TARGET nnnnn ON NODE aaaaaaaa
Explanation

This is an informational message displaying the number of requests Entire Net-Work handled for target nnnnn.

If aaaaaaaa is the local node, the number specifies incoming requests, otherwise outgoing requests.

This message is not displayed for targets with a message count of zero.


NET0089I: nnnnnnnnnn REQUESTS TOTAL ......... FOR NODE aaaaaaaa
Explanation

This is an informational message displaying the number of requests that Entire Net-Work handled for all targets on node aaaaaaaa.

If aaaaaaaa is the local node, the number specifies incoming requests, otherwise outgoing requests. This message is not displayed for nodes with a request count of zero.


NET0090I: BUFFER USAGE STATISTICS
Explanation

This is an informational message that immediately precedes the NET0091 message.

Action

Refer to the NET0091 message for more information.


NET0091I: resourcename: sizea (= nn.n %) OF sizeb K USED
Explanation

At the end of each Entire Net-Work session, usage statistics (sizea) for major buffer pool resources are displayed; values are in Kbytes (1024-byte units, or sizeb), and fractional values are rounded to the next lower value; the percentages given provide a better measurement of buffer pool usage (Request Queue statistics are specified in the number of Queue elements).

Action

Monitor buffer usage, and take corrective action if any of the usage figures are near 100%.


NET0092I: nnnnnnnnnn NODE STACK EXPANSIONS PERFORMED
Explanation

The value provided by the MAXPATH keyword parameter on the NODE statement determines the size of the node stack in the message header, which in turn records the message's path through the network. Whenever a message path exceeds the capacity of the originally created node stack, the relay node detecting the condition has to expand the node stack by copying the message into another buffer. To avoid this overhead, specify a larger MAXPATH value on the originating node (not on the node that presents this message to alert you to the condition at session termination).

Action

If the number of node stack expansions becomes significant, try to identify the originating node and increase the MAXPATH value. A good look at the network topology is likely to provide all the necessary clues. For more information, see the section Entire Net-Work Parameter Statements.


NET0093I: nnnnnnnnnn REPLIES COULD NOT BE ROUTED
Explanation

This is an informational message giving the number of cases where a reply could not be routed to the user s node, probably because the node ended operation or became unreachable after the subject messages were sent. No provision is made to deliver the reply elsewhere. The reply is abandoned; the count in this message is the only remaining indication of the abandoned replies.


NET0094I: nnnnnnnnnn MESSAGES WERE STRANDED
Explanation

This is an informational message. 'Stranded' messages are user requests that could not be routed to the target node, but also could not be returned to the user to provide a response code because the user s node (or the only link to it) terminated or became unusable after the message was sent. Since there is nowhere else the messages could be delivered, they were abandoned. The count in this message is the only remaining indication of the abandoned messages.


NET0095I: nnnnnnnnnn REQUESTS TIMED OUT (RSP224)
Explanation

This is an informational message displaying the number of times this Entire Net-Work node had to issue the Response Code 224 for message timeouts.

Action

If the number becomes significant, it indicates certain bottlenecks somewhere in the network. You should identify and eliminate these. Alternatively, increase the REPLYTIM parameter on the NODE Statement. For more information, see the section Entire Net-Work Parameter Statements.


NET0096I: nnnnnnnnnn REQUESTS FAILED DUE TO BUFFER SHORTAGE
Explanation

This is an informational message displaying the number of times this Entire Net-Work node had to issue the Response Code 220 for short term buffer shortage conditions.

Action

If the number becomes significant, increase the size of the short term buffer pool.


NET0097I: NETWORK TERMINATING DUE TO PARM ERRORS
Explanation

This informational message is issued after all parameter statements have been read, indicating that due to previously listed parameter errors the session of Entire Net-Work is about to be terminated.

Action

No action is required. This message is informational only.


NET0098I: ABNORMAL TERMINATION COMPLETED
Explanation

This is an informational message indicating that the abnormal termination procedures were completed successfully.


NET0099I: NORMAL END OF RUN
Explanation

This is an informational message indicating that the normal termination procedures were completed successfully.


NET0101I: aaaaaaaa DRIVER OPEN FAILED (RC=nn)
Explanation

The line driver aaaaaaaa could not be opened. More specific messages should have been issued by the line driver. The return code (nn) is access method dependent.

If this condition is detected during session initialization, Entire Net-Work will terminate abnormally; if it occurred during an attempt to re-open a line driver after access method failure (either manually by the START operator command or automatically based on the RESTART parameter values specified in the DRIVER statement), normal system operation continues - without the line driver in question.

Action

Refer to the related access-method-specific line driver error message for information on what condition caused this error. Correct the access method problem and issue a START operator command for the driver, or wait for the next RESTART to occur. Under certain circumstances, you may have to stop and restart the Entire Net-Work session to make the line driver available.


NET0103I: LINK aaaaaaaa (bbbb) OPEN FAILED (RC=nn)
Explanation

The link aaaaaaaa (of driver bbbb) could not be opened. More specific messages describing the link problem were probably issued by the line driver. The return code (nn) is access method dependent.

The system continues to run normally without the link.

Action

Refer to the related line driver error message for information on the cause of this error. Rectify the access-method problem and issue a CONNECT operator command for the link, or wait for the next RESTART to occur. Under certain conditions you may have to stop and restart the Entire Net-Work session in order to make the link available.


NET0104I: LINK aaaaaaaa (bbbb) CONNECT FAILED
Explanation

The link aaaaaaaa (for driver bbbb) could not be connected. More specific messages describing the link problem were probably issued by the line driver.

Note that this is an actual error condition. The normal operating case where one node tries to connect before the partner is available cannot cause this error.

The system continues to run normally without the link.

Action

Refer to the access-method-specific error messages for information on the cause of this error. Correct the access method problem and issue a CONNECT operator command for the link, or wait for the next RESTART to occur. Under certain circumstances, you may have to stop and restart the Entire Net-Work session in order to make the link available.


NET0105I: ALL aaaa LINKS CLOSED BY ACCESS METHOD TERMINATION
Explanation

The access method aaaa was terminated. Links using that access method can no longer function.

The system continues to run normally without the links.

Action

When the access method becomes available again, use the operator commands START and CONNECT to restart the line driver and links involved. You may want to specify the RESTART parameters on the DRIVER or LINK statements to automate this process. For more information, see the section Entire Net-Work Operator Commands.


NET0106I: LINK aaaaaaaa CAN'T CONNECT TO NODE bbbbbbbb REASON reason
Explanation

Handshaking could not be completed to node bbbbbbbb via link aaaaaaaa for the reason given, which can be one of the following reasons:

Reason Description
INV(ALID) LINK STATUS The link received a handshake request from the other side that conflicted with the current link status. A handshake error message is sent to the other node, rejecting the request.
REJECTED BY NODE A handshake request was rejected by the other node; this may be due to network conflicts (see below), in which case messages NET0108 and NET0109 are issued to describe the conflict; if no such messages appear, the problem is probably caused by an invalid link status on the other side (see above).
NETWORK CONFLICT Handshaking determined that conflicts exist between the network topologies as seen by this node and node bbbbbbbb; therefore, a connection via link aaaaaaaa was not established. Messages NET0108 and NET0109 are also issued before this message, defining the conflicts. Note that the connection is physically functional, but cannot be used due to the conflicts.

The link is disconnected.

Action

Remove the conflict from the network. This may require terminating and renaming a node, or terminating one or more targets with duplicate target IDs. Then use the CONNECT operator command to resume handshaking.


NET0107I: LINK aaaaaaaa DISCONN. FROM NODE bbbbbbbb
Explanation

The link aaaaaaaa was disconnected from node bbbbbbbb by one of the following events: node termination, a DISCONNECT operator command, certain types of link failures (described by related line driver messages), or a disconnect request from the other node due to one of these causes.

The system continues processing without the link.

Action

If appropriate, try to reconnect the link with the CONNECT operator command. If the cause of the disconnect has not been corrected, the reconnect attempt will fail.


NET0108I: CONFLICT: TARGET nnnnn ON NODE aaaaaaaa AND bbbbbbbb
Explanation

Target IDs have to be unique throughout the network. If multiple targets with the same ID are detected during link connection, the link cannot be connected until the conflict is resolved. Message NET0106 or NET0306 is issued after all detected conflicts have been listed.

The link is disconnected.

Action

Remove the conflict from the network by terminating targets with duplicate target IDs. Then use the CONNECT operator command to resume handshaking.


NET0109I: CONFLICT: NODE aaaaaaaa
Explanation

Node names must be unique throughout the network. If multiple nodes with the same name are detected during link connection, the duplicate link cannot be connected. Message NET0106 or NET0306 is issued after all detected conflicts have been listed.

The link is disconnected.

Action

Remove the conflict from the network by terminating and renaming the conflicting node(s). As an alternative, first try the PROBE operator command to verify if node aaaaaaaa is actually active, then issue the CONNECT operator command to resume handshaking.


NET0110I: LINK aaaaaaaa CONNECTED TO NODE bbbbbbbb
Explanation

Link aaaaaaaa was successfully connected to node bbbbbbbb. The function may have been initiated from either side.

Normal processing continues, the newly connected link will be considered for message traffic.


NET0111I: LINK aaaaaaaa CLOSED
Explanation

During Entire Net-Work termination, link aaaaaaaa was closed. Usage statistics for the link follow this message.

After displaying the usage statistics, termination processing continues normally.


NET0112I: nn,nnn,nnn,nnn MSGS; BLK FACTOR = nnn.nn
Explanation

This message details the number of messages and transmission blocks sent via the link and the blocking factor achieved. This last item is only displayed if BLOCKMSG=Y and STATBLK=Y are in effect for this link.

This message is displayed as a result of the DISPLAY LINK operator command. With the Simple Connection Line Driver, this count is reset to zero (0) after link connect processing.


NET0113I: nn,nnn,nnn,nnn {INPUT | OUTPUT} THROWBACKS;
Explanation

This message is printed in conjunction with message NET0111 if throwbacks occurred. It is an indication that not enough message buffers (short term or page-fixed buffer pool) were available at some point during the session. The worst case figure specifies how often one individual message was thrown back.

Action

Check the buffer pool usage statistics; increase the appropriate buffer pool size to prevent future occurrences of this message.


NET0114I: SNAP DUMP WRITTEN TO NETPRNT / DDPRINT
Explanation

The SNAP output is written to NETPRNT if it is available; otherwise, the output is written to DDPRINT.


NET0115I: OPERATOR COMMAND NOT RECOGNIZED
Explanation

The last operator command entered was not recognized by Entire Net-Work.

The command is ignored.

Action

For the correct syntax, see the section Entire Net-Work Operator Commands; then reissue the operator command.


NET0116I: LINK aaaaaaaa NOT FOUND
Explanation

An operator command was issued to act on link aaaaaaaa, but no link with that name is defined.

The command is ignored.

Action

To determine which links are defined, use the DISPLAY LINKS operator command, then reissue the corrected command.


NET0117I: LINK aaaaaaaa CANNOT BE CONNECTED, STAT=ssssss
Explanation

An operator command was issued to connect link aaaaaaaa, but the link is in a state that does not allow connection (the link is probably already connected). STAT=ssssss may be one of the following status codes:

NOTOPEN The link is not open yet.
OPEN The link is open.
CONSTA The connection process started.
COPEND The connection process is in waiting status.
COFAIL The connection attempt failed.
CONN The link requested is already connected.
HSERR A handshaking conflict occurred.
HS1 First handshake message was sent.
HS2 Second handshake message was sent.
HSING An interim status during handshake.
ACTIVE Active for payload message traffic.
SUSPND Connection process was suspended.
DISCRQ Other party requested to be disconnected.
DISC Successful disconnection completed.

The command is ignored.


NET0118I: INVALID RQE ADDRESS IN REPLY; DETAILED SNAP DUMP
Explanation

A reply was received for a user request originating at this node. The message header's pointer to this request s Request Queue Element (RQE) is invalid. This is probably an internal error. A possible valid cause for this condition could be that the node was terminated and restarted while the message was under way in the network.

The message in error is dumped to the printer data set for diagnostic pureness and then discarded. A user waiting for this reply is timed out with response code 224.

Action

If a node restart did not cause the message, have the printout (as well as any other related information) available, and contact your Software AG technical support representative.


NET0119I: REPLY CANNOT BE MATCHED TO RQE; USER=userid
Explanation

A reply to user userid s message has arrived, but the user no longer owns the Request Queue Element (RQE) associated with the dialogue. This might be caused by the user program terminating abnormally or by a timeout condition due to the REPLYTIM parameter on the NODE statement. In either case, the user program that requested the reply is no longer waiting for it.

This condition is very similar to the 'USER GONE' error detailed in messages NETM91, NETM92, and NETM93.

The message in error is discarded.

Action

To reduce the chance of this error, increase the REPLYTIM parameter value on the NODE statement to accommodate the longest transmission time that typically occurs in the network. For more information, see the section Entire Net-Work Parameter Statements.


NET0120I: aaaa LINK bbbbbbbb TO NODE cccccccc STAT=ssssss
Explanation

This message is issued in response to the DISPLAY LINKS operator command. aaaa specifies the access method for the link, bbbbbbbb is the link name from the LINK parameter statement, cccccccc is the name of the node on the other side of the link, and ssssss is the link status. Refer to the status code descriptions for NET0117 explaining the meaning of the link status codes.

If the link is a TCPX link, the partner's TCP/IP address is displayed rather than the node name (cccccccc setting).


NET0121I: OUTPUT QUEUE: nnnn MSGS, mmmm TR.BLKS
Explanation

This message is issued in response to the DISPLAY LINKS operator command unless both nnnn and mmmm are zero. It indicates a transmission backlog for the link.

A small backlog is normally not an error condition, but a backlog that increases over time may indicate a problem with the link.

Note that there are usually no messages in the input queue when operator commands are handled.


NET0122I: NODE aaaaaaaa (bbbbbbbb) DIST nnnnnn (lll) VIA LINK cccccccc
Explanation

This message is issued in response to the DISPLAY NODES, DISPLAY PATHS, or PROBE operator command. The node name (aaaaaaaa) from the NODE parameter statement, the node ID (bbbbbbbb) or target ID of the communicator, the distance (nnnnnn) to the node (computed by adding all link weights along the path to the node), the number (lll) of links between this Entire Net-Work node and node aaaaaaaa, and the name of the first link (cccccccc) on the path are given in the message.

See the WEIGHT parameter in the section Entire Net-Work LINK Statement) for more information about link weights.

In the case of a DISPLAY NODES command, only the shortest path is shown; in this case, the local node is shown with the term LOCAL in place of the distance information.

Either a DISPLAY NODES command specifying a node name or a PROBE command can cause 'INACTIVE' or 'NOT FOUND' to be displayed in place of the link information. For a DISPLAY PATHS command, all paths to all nodes are displayed; that is; each node is listed once for each link which has a path to it.

The distance shown is the shortest path length via the link.


NET0123I: TARGETS: nnnnn,mmmmm, ... j NONE
Explanation

This message is issued in response to the DISPLAY NODES operator command. It lists the IDs of all targets currently active on the node named in the preceding message NET0122; the communicator's ID is not listed again in this message. The term NONE indicates that no targets except the communicator are active on that node.


NET0124I: TARGET nnnnn (tt - tr) LOCKED | ACTIVE | INACTIVE ON NODE aaaaaaaa
Explanation

This message is issued in response to the DISPLAY TARGETS operator command or at Entire Net-Work startup. All targets that were ever active in the network are listed. The target ID (nnnnn), the target type (tt), and the name of the node (aaaaaaaa) on which the target is or was active are given in the message. The value of tr is T if the target uses Adabas Version 7 translation or N if it does not.

At Entire Net-Work startup, this message is issued only for the local target; remote targets will not be displayed.

Inactive targets are shown on the node where they were last active. The following table contains the possible target types:

Target Type Code Description
A Anchor (e.g., Natural Global Buffer Pool)
c Client-only Element
C Communicator (Entire Net-Work)
I Global isolated database
L Local isolated database
N Non-database target (ACCESS)
T Translation / UES-enabled database
V Adabas Cluster Services database

NET0125I: NO ACTIVE PATHS
Explanation

This message is displayed in response to a DISPLAY PATHS operator command when no paths are currently active.


NET0126I: NO LINKS FOUND
Explanation

This message is displayed in response to a DISPLAY LINKS operator command when no links have been defined or no links match the qualifier specified.

Note:
Although it may seem pointless to have a communicator active with no links defined, a DRIVER statement specifying ACCEPTUI=YES could be used to generate links dynamically when other nodes attempt to connect.


NET0127I: SET COMMAND ACCEPTED
Explanation

This message is displayed to acknowledge a SET operator command.


NET0128I: Entire Net-Work TERMINATING TARGET nnnnn DUE TO
Explanation

Entire Net-Work usually prevents concurrent sessions by more than one target with the same ID. If targets with the same ID are started simultaneously on different nodes, the condition is recognized as soon as the broadcast messages meet.

All targets with the same ID are terminated by their respective communicators, and this message is displayed on the operator consoles.

Action

One of the conflicting targets may be started again.


NET0129I: aaaa DRIVER OPENED
Explanation

This message acknowledges the successful execution of a OPEN driver (or START driver) operator command. aaaa defines the access method of the driver that was restarted.


NET0130I: aaaa DRIVER NOT OPENED
Explanation

The CONNECT link operator command could not be executed because the associated line driver was not open. aaaa is the access method of the line driver.

The command is ignored.


NET0131I: aaaa DRIVER ALREADY OPEN
Explanation

The START driver operator command could not be executed because the line driver is already open. aaaa is the access method of the line driver.

The command is ignored.


NET0133: INVALID TRACE ARGUMENT: aaaaaaaa
Explanation

An invalid argument aaaaaaaa was given for either the TRACE, TRON or TROFF parameter on the NODE statement or on a SET operator command. Valid trace arguments are 'MAIN' for the control module, 'BPM for the buffer pool manager, "TQM" for the Transmission Queue Manager, and "RQM" for the Receive Queue Manager as well as the access method names of all loaded line drivers. For more information, see the section Entire Net-Work Parameter Statements.


NET0134I: NO SUCH TARGET
Explanation

The target ID specified as an argument of a DISPLAY TARGETS operator command was either invalid, or does not exist.

The command is ignored.

Action

Re-specify the command with a valid target ID.


NET0135I: PROBE FOR NODE aaaaaaaa (nnnn.nnn SEC)
Explanation

A PROBE operator command was issued for node aaaaaaaa, and the resulting message was returned. PROBE messages are time-stamped to measure the time needed to communicate between the local node and node aaaaaaaa. The required time is displayed in nnnn.nnn seconds.


NET0136I: PROBE MSG SENT. USER DATA LENGTH: nnnnn
Explanation

This message acknowledges a PROBE operator command and displays the length of the random user data sent (maximum length is 64512 bytes). Message NET0135 is displayed when the PROBE reply is returned.


NET0137I: LINK aaaaaaaa CONNECT INITIATED
Explanation

This is an informational message indicating that a connect request was issued for link aaaaaaaa. Further message will be displayed as the connection process progresses. If the partner node is not active some access methods may display appropriate messages, others may not.

The link is placed in 'Connect Pending' status; when all required actions by both nodes are completed, the link will be placed in 'Active' status and message NET0110 will be displayed.


NET0139I: nn,nnn a BYTES SENT; COMPRESSION RATE nnn.nn
Explanation

This is an informational message displaying the number of (uncompressed) bytes sent via this link and the compression rate that was accomplished. The multiplier character 'a' may take on one of the following values:

blank = bytes
K = kilobytes
M = megabytes
G = gigabytes
T = terabytes

NET0141I: VIA NODE(S): nodename
Explanation

This message appears in response to a PROBE command if the node being probed is not directly connected; that is, it is reached via some other node. The message shows the relay node(s) used to complete the end-to-end connections.


NET0144I: CSCI FUNCTION NOT AVAILABLE
Explanation

A DISPLAY CSCI operator command was issued, but the NETCSI module is not linked to Entire Net-Work and is not available for dynamic load.


NET0145I: LINK xxxxxxxx DISABLED
Explanation

This message is a confirmation message in response to a DISABLE operator command. For more information, see the section Entire Net-Work Operator Commands.


NET0146I: LINK xxxxxxxx SUSPENDED
Explanation

This message is a confirmation message in response to a SUSPEND operator command. For more information, see the section Entire Net-Work Operator Commands.


NET0147I: LINK xxxxxxxx IS NOT ACTIVE
Explanation

A SUSPEND operator command was issued for a link whose status is not active. Only active links can be suspended. For more information, see the section Entire Net-Work Operator Commands.


NET0148I: LINK xxxxxxxx IS NOT SUSPENDED
Explanation

A RESUME operator command was issued for a link that was not previously SUSPENDed. For more information, see the section Entire Net-Work Operator Commands.


NET0149I: LINK xxxxxxxx RESUMED
Explanation

This message is a confirmation message in response to a RESUME operator command. For more information, see the section Entire Net-Work Operator Commands.


NET0150I: 'NODE DOWN' MESSAGE SENT
Explanation

This is the response to the Entire Net-Work operator command FORCE node. For more information, see the section Entire Net-Work Operator Commands.


NET0151I: INVALID NET-WORK MESSAGE ON LINK xxxxxxxx (REASON=nn)
Explanation

A message was received on link xxxxxxxx that violates the internal Entire Net-Work message protocol. The reason code indicates the type of error detected, as follows:

Reason Code Description
1 Invalid message header
2 Invalid control message
3 Invalid probe message
4 Invalid probe reply
5 Message length exceeds 16 megabytes
6 Invalid distribution list pointer
7 Invalid node name reported in message
8 Target number zero reported in message
9 Target list exceeds message length
10 Node list exceeds message length
11 Invalid extra buffers in control message
12 Buffer space exhausted
13 Message header invalid or not specified

A hexadecimal dump of the message is written to DDPRINT, and link xxxxxxxx is disconnected.

Action

Retain all related information and contact your Software AG technical support representative.


NET0153I: PARMS: link parameters
Explanation

This message is issued in response to operator command DEFINE LINK. It lists the parameters initially in effect for the new link. For more information, see the section Entire Net-Work Operator Commands.


NET0154I: LINK xxxxxxxx USER EXIT DETECTED ON PARTNER SYSTEM
Explanation

A message was received on link xxxxxxx that was manipulated by a user exit on the sending Entire Net-Work node. A corresponding user exit was not defined on this Entire Net-Work node.

The link is disconnected.

Action

Ensure that the adjacent Entire Net-Work nodes both have a user exit defined, or delete the user exit on the other side.


NET0170E: Verify argument not valid
Explanation

A non-numeric or out of range(1-65535) target ID was specified for the VERIFY operator command.

Action

Correct the VERIFY operator command input


NET0171I: Verify target target-id already active
Explanation

The target to be verified and listed in the message (target-id) is in the network and is active.

Action

No action is required for this informational message.


NET0172I: Verify target target-id not in this Net-Work
Explanation

The target to be verified and listed in the message (target-id) is not in this network.

Action

No action is required for this informational message.


NET0174I: Verify target target-id is relocatable or virtual
Explanation

The target to be verified and listed in the message (target-id) is relocatable or virtual.

Action

No action is required for this informational message.


NET0240E: UNKNOWN NETPRNT REQUEST
Explanation

An invalid NETPRNT request was detected. The only requests currently supported are OPEN, CLOSE, and WRITE.

Action

This message indicates a logic problem in Entire Net-Work and should be reported to your Software AG technical support representative.

Module

NETDUMP


NET0241I: NETPRNT FILE CLOSED
Explanation

The NETPRNT file has been closed. All print output is sent to DDPRINT until this file is re-opened. While the file is closed it remains allocated, but it can be copied and re-opened.

Action

No action is required. This message is informational only.

Module

NETDUMP


NET0242I: NETPRNT FILE OPENED
Explanation

The NETPRNT file has been opened. All print output is sent to the file allocated to the NETPRNT DD statement. If the file was allocated SHR or OLD, it contains no existing print records. If the file was allocated MOD, the new records are placed after the existing records.

Action

No action is normally required. However, if you are running in z/VSE and the file has an expiration date that has not been met, you will need to issue a DELETE or CANCEL operator command. If DELETE is issued, the file is overwritten and Entire Net-Work continues processing. If CANCEL is issued, Entire Net-Work terminates. And if the initial space allocation becomes exhausted, you will need to specify a secondary extent allocation.

Module

NETDUMP


NET0243E: NETPRNT FILE OPEN FAILED - USING DD PRINT
Explanation

The NETPRNT file failed to open. This may be caused by a missing NETPRNT DD statement or some other allocation error. All output is sent to the DDPRINT file until the NETPRNT file can be successfully opened.

Action

Check the JOBLOG and SYSLOG for operating system messages that indicate the cause of the allocation failure.

Module

NETDUMP


NET0244E: WRITE FAILED TO NETPRNT FILE
Explanation

A WRITE to the NETPRNT file failed. The cause may be an out-of-space condition such as ABENDSD37 or other I/O error or short-on-storage condition (e.g., IOR failed to get the storage it needed). The NETPRNT file is closed and all output is sent to the DDPRINT file. It may be possible to re-open the NETPRNT file if it was allocated SHR. The data set should be copied before reopening because all records will be deleted.

Action

Check the JOBLOG and SYSLOG for operating system messages that indicate the cause of the I/O error.

Module

NETDUMP


NET0245E: WRITE FAILED TO NETPRNT FILE
Explanation

A CLOSE of the NETPRNT file failed. This is an internal logic error or I/O error. The NETPRNT file will be unusable until Entire Net-Work is brought down.

Action

Check the JOBLOG and SYSLOG for operating system messages that indicate the cause of an I/O error. If no I/O error can be found, report this to your Software AG technical support representative.

Module

NETDUMP


NET0246E: LOGBUFSZ=0; LOG BUFFER NOT ALLOCATED
Explanation

The LOGBUF parameter is set "ON" and logging is active, but there is no log buffer available because the LOGBUFSZ parameter is set to "0". As a result, LOGBUF is turned off (set to "OFF").

Action

Specify a size for the LOGBUFSZ parameter and set the LOGBUF parameter to "ON" again.


NET0247E: FAILED TO GET LOG BUFFER STORAGE
Explanation

An attempt to get the storage specified by the LOGBUFSZ parameter failed. As a result, LOGBUF is turned off (set to "OFF").

Action

Increase the amount of storage available to Entire Net-Work or specify a smaller value for the LOGBUFSZ parameter. In either case, set the LOGBUF parameter to "ON" again.


NET0250I: DUMP OPTIONS aaaaaaaa
Explanation

This message lists the values specified for the DUMP parameter on the NODE statement. This message will also be seen as a reply to the SET DUMP operator command. For more information, see the section Entire Net-Work Parameter Statements.

Action

This is an informational message only and no action is required.

Module

NETMAIN


NET0251I: INVALID DUMP OPTIONS aaaaaaaa
Explanation

An invalid value was specified for the DUMP parameter on the NODE statement. The default value 'ALL' is used to dump all areas. This message may also be seen as a reply to an invalid SET DUMP operator command specification.

Action

Correct the DUMP parameter specification on the NODE statement before restarting Entire Net-Work. A SET DUMP operator command can be used to specify the dump options for the currently running Entire Net-Work (see SET DUMP in the section Entire Net-Work Operator Commands). .

Module

NETMAIN


NET0306I: DISCONNECTING LINK xxxxxxxx DUE TO NETWORK CONFLICT
Explanation

An Entire Net-Work conflict was detected in a control message received on link xxxxxxxx. The nature of the conflict is reported in preceding messages NET0108, NET0109, or NET0308.

The link is disconnected.

Action

Follow the user action recommended in the description of the preceding message, i.e., NET0108, NET0109, or NET0308.


NET0308I: NODEID ON xxxxxxxx IN CONFLICT WITH TARGET ttttt
Explanation

An Entire Net-Work control message reported a node xxxxxxxx whose target ID is already active elsewhere in the network. This presents a network conflict, as target IDs must be unique throughout the network. Message NET0106 or NET0306 is issued after all detected conflicts have been listed.

The link is disconnected.

Action

Remove the conflict from the network by either terminating target ttttt, or assigning a new unique target ID to node xxxxxxxx.


NET0322I: NODE dddddd.aaaaaaaa (bbbbb) DIST nnnnnn (lll) VIA cccccccc
Explanation

This message replaces the corresponding form of NET0122, when a node is listed that has a non-blank domain name. Also see the DOMAIN parameter in the section NODE Statement Parameters.


NET0328E: MESSAGE BUFFER SHORTAGE. SENDING DEFERRED
Explanation

A message is to be sent on a link that has a user exit defined. There is not enough buffer space to provide a work area to the user exit.

The message is not sent at this time. An attempt is made to free enough working storage. Sending the message is then tried again.

Action

Increase the size of the Short Term Buffer Pool to prevent future occurrences of this problem.


NET0333I: operator command - short description
Explanation

Multiple messages NET0333 are issued in response to the HELP command. The available operator commands are listed with a short explanation of their function.


NET0334E: ADAIOR FUNCTION CALL nnn FAILED WITH RC=xxx; TERMINATING
Explanation

The ADAIOR function call named in the message failed with the return code given in the message. The values are displayed in decimal.

This is a critical error; Entire Net-Work terminates. Probable causes are a storage shortage or incompatible version of the WAL data set.

Action

Determine if the problem is caused by a storage shortage or if there is an incompatibility with the WAL data set version and fix the problem. If neither of these conditions are causing the problem, contact your Software AG Customer Support representative.


NET0998I: Entire Net-Work NODE aaaaaaaa ABNORMAL END
Explanation

This is an informational console message indicating that abnormal termination procedures have been started.


NET0999I: Entire Net-Work NODE aaaaaaaa TERMINATING
Explanation

This is an informational console message indicating that normal termination procedures have been started.


NET1000I: Entire Net-Work NODE aaaaaaaa ACTIVE
Explanation

This is an informational console message indicating that the Entire Net-Work session has successfully completed initialization and is now ready for processing.


NET1001I: CURRENT DATE IS yyyy-mm-dd
Explanation

This message is displayed on the operator console and on the Entire Net-Work log data set at the beginning and end of a session as well as just after midnight. It helps to identify the exact time and date of any events recorded in the log.


NET1002I: NET-WORK NODE xxxxxxxx ACTIVE SINCE yyyy-mm-dd hh:mm:ss
Explanation

This message is issued in response to the operator command DISPLAY STATS. It shows the startup date and time of the local node xxxxxxxx.


NET1003I: DBID dbid RELOCATED FROM LOCAL NODE TO node
Explanation

The database target identified in the message (dbid) was previously active on this Entire Net-Work node. The target has been relocated to the node identified in the message (node). This message is associated with Adabas Cluster Services and Adabas Parallel Services database ID targets. Relocation was done on behalf of a command issued by an Adabas nucleus.

Action

No action is required for this informational message.


Top of page