NETnnnn - Entire Net-Work Control Module Messages

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.

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

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.

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

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.

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.

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.

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

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.

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

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.

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

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.

Eliminate any extraneous DRIVER statements from the parameter data set.

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.

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

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.

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

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.

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

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.

Correct the parameter statement.

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

None. This message is informational only.

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.

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.

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.

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.

Provide more storage in the partition or address space.

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.

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.

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.

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

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.

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

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.

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.

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.

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.

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

The Entire Net-Work session is terminated abnormally.

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

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

The Entire Net-Work session is terminated abnormally.

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

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.

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.

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

The Entire Net-Work session is terminated abnormally.

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

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.

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

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.

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.

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

The Entire Net-Work session is terminated abnormally.

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

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.

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

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

The Entire Net-Work session is terminated abnormally.

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.

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.

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

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.

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

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

The Entire Net-Work session is terminated abnormally.

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

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.

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.

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

Supply the appropriate Adabas or WAL libraries.

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.

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

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

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

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 .

No action is required. This message is informational only.

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.

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

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.

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.

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

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

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

No action is required for this informational message.

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

No action is required for this informational message.

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.

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

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.

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

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.

Specify a valid LOGSIZE value.

NETWRK

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.

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.

NETWRK

Entire Net-Work is verifying your customer license.

No action is required for this informational message.

NETWRK

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.

Contact your Software AG technical support representative about the error.

NETFLIC

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

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

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

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.

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.

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

Refer to the NET0091 message for more information.

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

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

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

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.

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.

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.

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.

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.

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.

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

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.

No action is required. This message is informational only.

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

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

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.

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.

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.

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.

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.

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.

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

The system continues to run normally without the links.

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.

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

The link is disconnected.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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

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

The command is ignored.

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

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

The command is ignored.

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

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:

The command is ignored.

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.

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.

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.

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.

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

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.

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.

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.

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:

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

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.

This message is displayed to acknowledge a SET operator command.

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.

One of the conflicting targets may be started again.

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.

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.

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.

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.

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

The command is ignored.

Re-specify the command with a valid target ID.

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.

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.

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.

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:

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.

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.

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

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

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.

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.

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

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

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:

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

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

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.

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.

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

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

Correct the VERIFY operator command input

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

No action is required for this informational message.

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

No action is required for this informational message.

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

No action is required for this informational message.

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

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

NETDUMP

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.

No action is required. This message is informational only.

NETDUMP

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.

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.

NETDUMP

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.

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

NETDUMP

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.

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

NETDUMP

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.

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.

NETDUMP

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").

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

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

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.

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.

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

NETMAIN

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.

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

NETMAIN

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.

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

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.

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

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.

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.

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

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

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.

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.

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

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

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

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.

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

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.

No action is required for this informational message.