Entire Net-Work 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. nnn 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.1 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.

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.

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

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 VM and BS2000/OSD environments, 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.

In VM/CMS 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 VM/CMS 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

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 aaaa) 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 aaaa) 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:

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.

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. aaaaaaaa specifies the node name from the NODE parameter statement. bbbbbbbb is the node ID (target ID of the communicator). nnnnnn is the distance to the node (computed by adding all link weights along the path to the node; see the WEIGHT parameter in the section Entire Net-Work LINK Statement) and lll is the number of links between this Entire Net-Work node and node aaaaaaaa. cccccccc is the name of the first link on the path.

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. All targets that were ever active in the network are listed. nnnnn is the target ID, tt is the target type (see below), tr is T if the target uses Adabas Version 7 translation or N if it does not, and aaaaaaaa is the name of the node on which the target is or was active.

Inactive targets are shown on the node where they were last active. The LOCKED status indicator is shown only while a duplicate target conflict is being resolved. The following table contains the 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.

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 VSE/ESA 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

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.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It provides the name of the buffer pool (nnnn) and the storage location (llll).

No action is required. This message is informational only.

During buffer pool initialization, module xxxxxxxx could not be loaded and the buffer pool initialization was terminated.

Contact your Software AG technical support representative.

One of a group of messages generated in response to the DISPLAY STATS operator command or at the end of an Entire Net-Work session. It provides the number of successful (nnnnnnnn) and failed (xxxxxxxx) GET requests and the number of successful (yyyyyyyy) and failed (zzzzzzzz) FREE requests processed for a subpool within the buffer pool identified by the preceding NETB001I message.

No action is required. This message is informational only.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It provides the highest storage allocation (hhhhhhhh), the current storage allocation (cccccccc), and the current storage available (aaaaaaaa) for the buffer pool identified in the preceding NETB001I message.

No action is required. This message is informational only.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It describes an element for a specific subpool. It provides the base (bbbbbbbb), highest (hhhhhhhh), current available (cccccccc) and lowest (llllllll) number of elements as well as the element size (ssssssss) in bytes.

No action is required. This message is informational only.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It describes the storage environment of a specific subpool. It provides the base (bbbbbbbb), highest (hhhhhhhh), current available (cccccccc) and lowest (llllllll) storage allocations.

No action is required. This message is informational only.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It describes the expansion within a subpool. It provides the number of times this subpool has expanded (nnnnnnnn), the maximum number of times it is allowed to expand (xxxxxxxx), the current total number of expansions (yyyyyyyy), and the highest number of expansions at any time (zzzzzzzz).

When xxxxxxxx is equal to "1", unlimited expansions are allowed.

No action is required. This message is informational only.

One of a group of messages generated in response to the DISPLAY STATS operator command or the end of an Entire Net-Work session. It describes the total size of the buffer pool, i.e., nnnnnnnn is the combined size of all subpools in all buffer pools belonging to Entire Net-Work.

No action is required. This message is informational only.

The buffer pool manager detected an invalid request and the error trace table was initialized.

Beginning with this error, errors are traced in the error trace table until the error trace table is full (see message NETB015I).

No action is required. This message is informational only.

The error trace table is full.

Stops tracing errors in the error trace table.

Issue the operator command SNAP to output the trace table information. The SNAP command will then automatically clear the contents of the error trace table so that error tracing can continue. Save the DDPRINT and contact your Software AG technical support representative.

NETSMH called the Entire Net-Work SMH API to send data, but an error of some type occurred within the API, preventing it from completing the send function. A message that identifies the error is normally issued from the API preceding this message. Processing for the link is halted and the link is disconnected.

To determine why the API could not complete the send, locate a preceding error message from the API and perform the action related to that error, if any.

NETSMH

NETSMH called the Entire Net-Work SMH API to send data, but the send completion time limit expired before the send could complete normally. Processing for the link is halted and the link is disconnected.

The SENDTIME= parameter in the LINK statement is used to set the time limit for send completion. If the value specified for SENTIME= is too small for practical purposes, increase it to allow sends to complete without error. If the value specified for SENDTIME= is appropriate, follow normal TCP/IP network debugging procedures to determine why TCP messages are not arriving at their destinations within the time limit.

NETSMH

NETSMH called the Entire Net-Work SMH API to establish a connection, but an error of some type occurred within the API, preventing it from completing the connect function. A message that identifies the error is normally issued from the API preceding this message. Processing for the link is halted and the link is disconnected.

To determine why the API was not able to complete the connect, locate the preceding error message from the API and perform the action related to that error, if any.

NETSMH

NETSMH called the Entire Net-Work SMH API to accept a connection, but an error of some type occurred within the API, preventing it from completing the accept function. A message that identifies the error is normally issued from the API preceding this message. Processing for the link is halted and the link is disconnected.

To determine why the API was not able to complete the accept, locate the preceding error message from the API and perform the action related to that error, if any.

NETSMH

Initialization of the NETSMH driver has begun. The driver control block is located in storage at address dddddddd and the NETSMH module itself is located at address mmmmmmmm. This information is provided to aid in debugging.

None.

NETSMH

The TCP/IP internal trace table is located in virtual storage at address tttttttt. This information is provided to aid in debugging.

None

NETSMH

The user exit that was specified by coding EXIT= on the link configuration statement could not be loaded into storage. The cause of the problem may be one of the following: an incorrect exit name was specified; the exit is not located in a data set that is in the STEPLIB, JOBLIB, or Linklist DD; or, there is insufficient virtual storage in the region to load the module. The operating system usually issues a message that provides more details about the cause of the load failure.

Make sure that the name of the exit is specified correctly and that the exit resides in an appropriate data set that is part of either the STEPLIB, JOBLIB or Linklist DD concatenations. If insufficient virtual storage exists in the region, increase the size of the region before continuing.

NETSMH

The Entire Net-Work SMH API module mmmmmmmm was loaded into virtual storage at address vvvvvvvv. The information in this message is provided to aid in debugging.

None

NETSMH

The Entire Net-Work module specified by mmmmmmmm could not be loaded into storage. The cause of the problem may be one of the following: the module is not located in a data set that is in the STEPLIB, JOBLIB, or Linklist DD; or, there is insufficient virtual storage in the region to load the module. The operating system usually issues a message that provides more details about the cause of the load failure.

Make sure that the module resides in an appropriate data set that is part of either the STEPLIB, JOBLIB or Linklist DD concatenations. If insufficient virtual storage exists in the region, increase the size of the region before continuing.

NETSMH

The Entire Net-Work SMH API routine could not complete the open process for the driver or the link. As a result, the link cannot establish a connection to another host. Other messages that explain why the driver or link could not be opened should precede this message.

Locate all previous error messages that deal with failures that occurred during driver open or link open processing and perform the action related to those error messages, if any.

NETSMH

The Entire Net-Work SMH API was asynchronously notified by its related access method that a connection was terminated. As a result, processing for the link was halted and the link was disconnected.

Locate all previous error messages from the Entire Net-Work SMH API that explain why the connection was severed or disconnected and perform the actions related to those messages, if any.

NETSMH

Remote Entire Net-Work host xxx.xxx.xxx.xxx attempted to establish an SMH link with the local Entire Net-Work host, but the connection was rejected for one of the following reasons:

• The remote host is intentionally prohibited from establishing a connection.

• The local host does not have a predefined LINK statement for the remote host.

• The Internet address for the remote host in the link related control blocks is incorrect. Either INETADDR= is incorrectly specified in the LINK statement, or ADJHOST= is specified in the LINK statement and the host name cannot be determined. Review the documentation for the LINK statement .

If the remote host is intentionally prohibited from establishing a connection, then no action is required. If the remote host should be able to establish a connection, then do one of the following:

• Create a link statement for the remote host.

• Issue the command SMH linkname SHOW to determine if the Internet address is correct in the link related control blocks. If the Internet address is incorrect, alter it manually with the commands SMH linkname CLOSE ALTER INETADDR=(x,x,x,x) and SMH linkname OPEN.

NETSMH

NETSMH called the Entire Net-Work SMH API to reject a connection, but an error of some type occurred within the API, preventing it from completing the reject function. A message that identifies the error is normally issued from the API preceding this message. The link returns to the disconnected state.

To determine why the API cannot complete the reject function, locate a preceding error message from the API and perform the action related to that error, if any.

NETSMH

An error occurred when attempting to obtain or release virtual storage. The cause of the error is usually one of the following: there is insufficient storage in the region to satisfy the obtain, or one of the buffer pools is not large enough to satisfy the storage request.

Check the buffer pool statistics by issuing the DISPLAY STATS operator command. If necessary, increase the size of the buffer pools. Otherwise, increase the private area size of the region to allow storage requests that are not allocated from buffer pools to properly complete.

NETSMH

Link llllllll was already in a connected state when a connect request was received from a partner link. Because MULTSESS=N is specified in the LINK statement for this link, the second connect request is treated as a reconnect. The existing connection is terminated and accept processing starts for the new connect request.

If the remote host is attempting to reconnect to this link, no action is required. If the remote host is attempting to connect to a second link, then change MULTSESS=N to MULTSESS=Y in the LINK statement; reconnect processing is skipped and the remote host is allowed to establish a second connection.

NETSMH

A message received on link llllllll contains a message type value in the message header that is not recognized by the program. The message is therefore discarded.

Issue the command SMH llllllll TRACE, where llllllll is the name of the link to be formatted; this causes the trace buffer for the link to be printed. One of the last RMSG entries will contain the message that caused the error.

NETSMH

Connection establishment negotiations took place on link llllllll, resulting in the reduction of the receive buffer size from 64k to nnnnn. This value is also the size of the largest message that can be sent to the remote node.

None.

NETSMH

The CONNECT operator command was issued but is not allowed for link SMHLINK in the SMH driver. CONNECT and DISCONNECT are handled internally when requests are sent by SMH.

No action is necessary.

NETSMH

ADJHOST=xxxxxxx, where xxxxxxx is the Internet host name, was specified in the LINK statement. However, the Entire Net-Work SMH API does not support the resolution of Internet host names to Internet numbers.

Change the LINK statement to use the INETADDR= parameter instead of the ADJHOST= parameter. Review the documentation for the LINK statement .

NETSMH

The command CONNECT llllllll was issued internally, where llllllll is the link name. The link was configured with an Internet host name instead of an Internet number, but an error occurred during the name resolution process. As a result, there is no Internet number to use and connect processing cannot continue.

One or more messages that describe the name resolution failure in more detail should precede this message. Locate these messages and perform the related actions, if any.

NETSMH

The CONNECT operator command is not allowed for link SMHLINK in the SMH driver. CONNECT and DISCONNECT are handled internally when requests are sent by SMH.

No action is necessary.

NETSMH

A link was found for the SMH driver that was not named "SMHLINK". Only one link can be defined for the SMH driver, and it must be named "SMHLINK". Message NET0103 follows, specifying the name of the invalid link.

Specify only one link for the SMH driver, named "SMHLINK".

NETSMH

The first form of the message is written whenever memory is dynamically acquired and the requested memory is available. The second form of the message is written whenever memory is dynamically acquired and less than the requested memory is available. In the messages, 'mmmmmmmm' is the amount of memory requested; 'aaaaaaaa' is the amount of memory available; and 'ssssss' (printed only under VSE), is the source of the memory (GETVIS, COMREG, ADABUF).

This is an informational message that occurs when the ADAIOR TRACE TABLE is made active and printed.

VSE/BS2000/OSD: This message indicates that Entire Net-Work requested cancellation. A dump is normally also provided. The value code corresponds to the user abend code. For more information, see the section Entire Net-Work Abend Codes. The value 'jobname' is the VSE job name or BS2000/OSD program name.

SYSLOG displays this message once operator communications has been requested by the operator with the VSE 'MSG' command. The value 'node-id' is the target ID of the node.

Enter a valid Entire Net-Work command.

VSE/MVS and BS2000/OSD: This message occurs in SYSLST as part of the session statistics during Adabas session termination. The value 'command' is the operator command last entered from SYSLOG.

An internal error has occurred in ADAIOR.

Make a note of all recent messages, and contact your Software AG technical support representative.

Entire Net-Work tried to process a user call, but the addressed data area was not addressable, or no longer contained recognizable data. This message occurred while Entire Net-Work was receiving the command (Router 08-CALL processing).

The program was apparently canceled after issuing an Entire Net-Work command (Router- 04-CALL), perhaps due to a communication delay or timeout. Ending, abending, or canceling of the program should be avoided, if possible.

Entire Net-Work tried to process a user call, but the addressed data area was not addressable, or no longer contained recognizable data. This message occurred while Entire Net-Work was posting the user after command completion (Router 12-CALL processing).

The program was apparently canceled after issuing an Entire Net-Work command (Router 04-CALL), perhaps due to a communication delay or timeout. Ending, abending, or canceling of the program should be avoided, if possible.

The user's program exceeded the ADARUN CT time allowed without receiving the results of an Adabas Call (performing Router 16-CALL processing). This could be caused by processing delays caused by an overloaded system or network, low priority, or teleprocessing delays. Adabas assumes that the user program has been canceled; Adabas frees the Command Queue Element (CQE) and alternate buffers.

Consider increasing the ADARUN CT time, or otherwise increase the resources for the user program. Avoid canceling or ending the user program, if this was done. If a user program eventually issues a Router 16-CALL, a response code 254 also occurs.

ASIDs are defined by Cross Memory Services. For more information regarding the use of ASCBs/ASIDs by Adabas, refer to the Adabas documentation.

None required. You may want to restart the terminating initiator.

ADAMPM was unable to establish interregion communication for the reason specified by cause, which is one of the following:

Either a system or Entire Net-Work abend activated the abnormal termination routine. In MVS systems, the rightmost three digits of operating system abend codes are zeros. The system abend code is then quoted as the value formed by the next three digits to the left (00ccc000). Abend codes contained in the rightmost three digits (00000ccc) are Entire Net-Work abend codes. Note that system abend codes are usually quoted in hexadecimal; user abend codes (Entire Net-Work), although displayed here in hexadecimal, are usually quoted in decimal (this is also true for the 'abend code' section of this manual).

The message also displays the active program status word (psw) and the work register contents at the time of the abend. 'psw' is the 16-character program status word and has the following format:

xxxxxxxx xxxxxxxx

where the rightmost six, or eight (XA systems) characters contain the instruction address at the time of the abend. The 16 register values (reg0 - regF) are the work register contents at the time of failure.

Link llllllll, which was previously suspended, has resumed processing as a result of the RESUME command.

None.

NWTCPOPC

Message processing has been suspended on link llllllll as a result of the SUSPEND command.

Issue the RESUME command to restart message processing when appropriate.

NWTCPOPC

An operator command was issued, however, the value specified for the link name was not "*", "#" or a valid link name. The command is ignored.

Reissue the command with a correct link name or a wild card value.

NWTCPOPC

An operator command was issued. The command passed initial parsing, that is, each subcommand was processed. The success or failure of a subcommand is independent of this message being issued.

None.

NWTCPOPC

Statistics for link lllllll or the TCPI driver have been either printed or reset, as indicated by xxxxxxxx.

None.

NWTCPOPC

An attempt to alter the active configuration for link llllllll or the TCPI driver has failed due to invalid parameter specifications in the command TCPI lllllll ALTER xxxx, where llllllll is a link name or a wildcard value and xxxx is one or more configuration keywords and parameters. The cause of the problem may be one of the following:

• A parameter specification contains a typographical or format error that makes the specification invalid.

• A value specified as the operand for a specific keyword is out of range, of incorrect format, or otherwise invalid.

• A keyword that is valid only when the link or driver is closed was specified when the link or driver was open.

If a keyword that is valid only when the link or driver is closed was specified, close the link or driver and reissue the command. Be aware that if the value specified for the RESTART parameter is too low, the link or driver may be automatically reopened after the CLOSE command is issued and before the ALTER command can be rekeyed. To prevent this, specify CLOSE (CL) in the command string immediately before the subcommand ALTER. For example:

TCPI linkname CL ALTER INETADDR=(127,0,0,1)

If the specified keywords are valid for the current state of the link or driver, verify that the keywords are spelled correctly, that all punctuation is correct, and that the operands are valid.

NWTCPOPC

A TCPI command was issued to one or more links or to the TCPI driver, and the action identified by xxxxxx was taken as a result.

None.

This message is issued in response to an operator command that was sent to link or driver llllllll. The link or driver name is followed by informational message text, which is one of the following:

Invalid State For Cmnd - The driver or link was in an invalid state (open) for the command to be executed.

Configuration Altered - The driver or link configuration was successfully updated.

Manual Open Failed - Open processing failed.

Connect In Progress - Connect processing for the link has been initiated.

Disconnect In Progress - Disconnect processing for the link has been initiated.

No action is required unless the message is 'Invalid State For Cmnd'. If so, wait for the link or driver to go into the proper state; then reissue the command, if appropriate.

NWTCPOPC

This multi-line display shows the current configuration for link llllllll. The parameters displayed may be different from those specified at Entire Net-Work initialization if they have been modified manually, or if they have been modified internally as a result of being out of range. For example, the last line appears only if IP Version 6 is in use.

None.

NWTCPOPC

The current state of link or driver llllllll is displayed with a count of messages sent and received. The message counts are for the period of time since the driver was opened, the link connected, or the statistics reset for either the driver or the link.

This message is automatically produced as a result of a command being issued to a link or driver while the link or driver was in an incorrect state for the command or as a result of a TCPI llllllll STATUS command being issued.

None.

NWTCPOPC

This multi-line display shows the current configuration for driver dddd. The parameters displayed may be different from those specified at Entire Net-Work initialization if they have been manually modified or if they have been modified internally as a result of being out of range.

Note:
The client table size is initially determined by the NUMUSERS parameter setting.

None.

NWTCPOPC

    +----------------------------------------------------------------------+
(a) + Statistics For Link XXXXXXXX  Period xxxxx:xx:xx (xxxxxxx.xxx Secs)  +
    + -------------  ---Bytes----  --Messages--  -Api Calls--  ----------- +
(b) + Writes         xxxxxxx.xxxz xxxxx,xxx,xxx Xxxxx,xxx,xxx  Total       +
(c) + xxxxxxx.xxxz xxxxx,xxx,xxx Xxxxx,xxx,xxx  Per Second  +
(d) + Reads          xxxxxxx.xxxz xxxxx,xxx,xxx Xxxxx,xxx,xxx  Total       +
(e) + xxxxxxx.xxxz xxxxx,xxx,xxx Xxxxx,xxx,xxx  Per Second  +
    + -------------  ---Total----  ----Task----  ---Other----  ----------- +
(f) + WRITE Cmds  xxxxx,xxx,xxx  xxxxx,xxx,xxx xxxxx,xxx,xxx   Total       +
(g) +              xxxxx.xxx.xxx  xxxxx,xxx,xxx Xxxxx,xxx,xxx  Per Second  +
(h) + REAC Cmds   xxxxx,xxx,xxx  xxxxx,xxx,xxx xxxxx,xxx,xxx   Total       +
(i) +              xxxxx,xxx,xxx  xxxxx,xxx,xxx Xxxxx,xxx,xxx  Per Second  +
    +----------------------------------------------------------------------+

This multi-line display is produced when the command TCPI xxxx STATS is issued, or when the automatic statistics interval has expired and PSTATS=Y is specified in the LINK statement. Values are displayed and updated asynchronously; therefore, the totals displayed may not always be accurate.

The display contains the following information:

None.

NWTCPOPC

This multi-line display is produced when you issue the USERS operator command for the Simple Connection Line Driver. The type in the message indicates whether the statistics listed in the output are for a driver or a link. The name in the message indicates the name of the driver or link to which the statistics apply.

This is a sample of the output that will appear when issued to the driver:

NETP065I: Active Users For Driver TCPX                                 
NETP065I: --------- Client ID     1 -----------------                  
NETP065I: Active on Link TCX00001 TCP/IP address 10.132.33.48          
NETP065I: Adabas Userid:                                               
NETP065I: Char(        NET-WORKS   NORGAY    )                           
NETP065I:  Hex(01210000 00000000 D5C5E360 E6D6D9D2 E22B0001 D2C5D5E3 40404040)
NETP065I: Context ID(E22B0001) Context Verifier(01000000)              
NETP065I: Number of requests processed           1                     
NETP065I:     1 Active Users printed              

This is a sample of the output that will appear when issued to a link:

NETP065I: Active Users For Link TCX00001 TCP/IP address 10.132.33.48  
NETP065I: --------- Client ID     1 -----------------                 
NETP065I: Adabas Userid:                                              
NETP065I: Char(        NET-WORKS   NORGAY    )                          
NETP065I:  Hex(01210000 00000000 D5C5E360 E6D6D9D2 E22B0001 D2C5D5E3 40404040)
NETP065I: Context ID(E22B0001) Context Verifier(01000000)             
NETP065I: Number of requests processed           1                    
NETP065I:     1 Active Users printed                                                       
                                 

None.

NWXTSOPC

This multi-line display shows the current configuration for the Simple Connection Line Driver link llllllll. The parameters displayed may be different from those specified at Entire Net-Work initialization if they have been modified manually, or if they have been modified internally as a result of being out of range.

None.

NWXTSOPC

This multi-line display shows the current configuration for the Simple Connection Line Driver. The parameters displayed may be different from those specified at Entire Net-Work initialization if they have been manually modified or if they have been modified internally as a result of being out of range.

Note:
The client table size is initially determined by the NUMUSERS parameter setting.

None.

NWXTSOPC

All connect queue entries are in use.

The number of connect queue entries is specified by the CONNQUE parameter on the DRIVER statement. Increase the value of this parameter to accommodate the maximum number of simultaneous connection requests from remote nodes.

An error occurred when attempting to obtain or release virtual storage. This error usually occurs because there is insufficient storage in the region to satisfy the obtain or one of the buffer pools is not large enough to satisfy the storage request.

Check the buffer pool statistics by issuing the DISPLAY STATS operator command. If necessary, increase the size of the buffer pools. Otherwise, increase the private area size of the region to allow storage requests that are not allocated from buffer pools to properly complete.

NWTCPCNS

There was an error in acquiring storage to perform a passive OPEN call to the TCP/IP partition. RC = 4 indicates a problem acquiring partition GETVIS storage. RC = 16 indicates a problem acquiring SVA GETVIS storage.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWVSESTK

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a passive OPEN(Listen) call.

Report the error to your Software AG technical support representative.

NWVSESTK

There was an error in acquiring storage to perform an OPEN call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on an OPEN call.

Report the error to your Software AG technical support representative.

NWTCPCNS

There was an error in acquiring storage to perform a SEND call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a SEND call.

Report the error to your Software AG technical support representative.

NWTCPCNS

There was an error in acquiring storage to perform a RECEIVE call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a RECEIVE call.

Report the error to your Software AG technical support representative.

NWTCPCNS

There was an error in acquiring storage to perform an CLOSE call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a CLOSE call.

Report the error to your Software AG technical support representative.

NWTCPCNS

There was an error in acquiring storage to perform an OPEN CONTROL call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. For RC=8, corrrect the value of the USERID parameter on the DRIVER statement to match the ID= subparameter of the PARM field for an active TCP/IP stack. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on an OPEN CONTROL call.

Report the error to your Software AG technical support representative.

NWTCPCNS

There was an error in acquiring storage to perform a CLOSE,CONTROL call to the TCP/IP partition. RC is the return code from a VSE GETVIS call. For more information, refer to the appropriate VSE documentation.

For RC=4, increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible. With RC=16, additional allocation is required in the system GETVIS area in the SVA. For other values, contact your Software AG technical support representative.

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a CLOSE CONTROL call.

Report the error to your Software AG technical support representative.

NWTCPCNS

An error was received while executing a call to resolve the host name or address. RC is the contents of Register 15 on return from the call. For more information, see the appropriate VSE documentation.

The action to take depends on the return code (RC=), as shown in the following table:

NWTCPCNS

RC is the return code passed back to Entire Net-Work by the TCP/IP partition on a call to resolve the host name or address.

Report the error to your Software AG technical support representative.

NWTCPCNS

A call to the IBM TCP/IP HPS API failed for function xxxxxxxx. The error number nnnnn provides the reason the failure and sssss is the socket where the failure occurred. This message provides diagnostic information about a previous error message. It may also be followed by a NETP601I message that explains the error number.

Locate message NETP601I for a description of the error number.

NWTCPHPS

This message describes the error number provided in message NETP600I.

Try to eliminate the condition that caused the message.

NWTCPHPS

An invalid request was made to the API.

Contact your Software AG technical support representative.

NWTCPHPS

An attempt to load a required module for TCP/IP failed. The driver and all links using this API will be unusable. This is most likely caused by TCP/IP not being correctly installed. It could also be caused by a short-on-storage condition or an I/O error.

Check the joblog and syslog for any additional messages, such as operating system messages, that may provide a reason for the problem.

NWTCPHPS

An attempt to allocate storage for a required control block failed. The control block is needed for the driver and all active links using the API. Only the new link being connected to or the new driver being opened is affected. All active links and drivers continue to run as long as the storage shortage does not cause other problems with Entire Net-Work.

Look for other messages indicating storage problems and perform any recommended action.

NWTCPHPS

An error occurred while trying to close a socket used for a connection. The Entire Net-Work connection is closed, but the socket is not usable for future connections.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A TCP/IP driver using API=HPS has been closed.

None required. This message is informational only.

NWTCPHPS

API=HPS was specified for a driver on a system that does not support it. MVS is currently the only operating system that supports this API.

Specify a valid API for the system and the TCP/IP stack that you are running.

NWTCPHPS

An INITAPI function call was made to TCP/IP and failed. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A call made to TCP/IP to get a new socket failed. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information. You may need to adjust some TCP/IP parameters to allow for more sockets.

NWTCPHPS

A BIND function call to TCP/IP failed. The BIND function tells TCP/IP which port to listen on, as well as any restrictions on who can connect to this port. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A GETSOCKOPT function call to TCP/IP failed. The GETSOCKOPT function is used to determine the maximum message size that can be sent. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A LISTEN function call to TCP/IP failed. The LISTEN function is used to set the number of connection requests that can be queued. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

An ACCEPT function call to TCP/IP failed. The ACCEPT function waits for a connection request and returns a socket to be used for the new conversation. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

The connection request was rejected because there was no connect queue entry available to process the request.

Increase the value of the CONNQUE parameter on the DRIVER statement.

NWTCPHPS

A SETSOCKOPT function call to TCP/IP failed. The SETSOCKOPT function is used to set the KEEPALIV parameter on the TCP/IP DRIVER and LINK statements. If KEEPALIV=YES, a message is sent periodically to verify that a connection is still active. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information. To disable this function, specify KEEPALIV=NO on the DRIVER and LINK statements.

NWTCPHPS

A CONNECT function call to TCP/IP failed. The CONNECT function is used to connect to a remote Entire Net-Work node. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information. Make sure that the remote Entire Net-Work node is running and is accepting connections from this node.

NWTCPHPS

A SENDMSG function call to TCP/IP failed. The SENDMSG function is used to send a data packet to a remote Entire Net-Work node. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A RECV function call to TCP/IP failed. The RECV function is used to receive a data packet from a remote Entire Net-Work node. This call waits for incoming data before returning to Entire Net-Work. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information.

NWTCPHPS

A GETHOSTBYNAME function call to TCP/IP failed. This type of function is used to determine the TCP/IP address of an Entire Net-Work node that used the ADJHOST parameter to specify the name. NETP600I will provide an error number that indicates why it failed.

Locate messages NETP600I and NETP601I for additional information. Make sure the name specified on ADJHOST parameter is correct and that this name is in the hosts file or domain name server. Read about the ADJHOST parameter

NWTCPHPS

A GetHostByAddr function call to TCP/IP failed, probably because the host name address was not defined in the DNS (Domain Name Service). The GetHostByAddr call is used to determine the name of a connecting IP address when ADJHOST has been specified on a LINK statement.

Add the host name and IP address to your domain name server.

NWTCPHPS

This message indicates an internal logic error in the HPS API.

Issue the TRACE and SNAP operator commands for the line driver.

For more information, see the section Entire Net-Work Operator Commands. Then contact your Software AG technical support representative.

NWTCPHPS

TCP/IP is being terminated on the local system. All connections using this driver will be disconnected. This is an informational message and does not indicate an error in Entire Net-Work.

Determine why the TCP/IP address space is being terminated.

NWTCPHPS

TCP/IP has terminated the connection for this link. Therefore, the link is no longer active.

Look for other messages on both the local and remote systems that will help you determine why the link was terminated.

NWTCPHPS

The asynchronous exit abended processing a previous TCP/IP function. This message indicates an internal logic error in the HPS API.

Issue the TRACE and SNAP operator commands for this driver.

For more information, see the section Entire Net-Work Operator Commands. Then contact your Software AG technical support representative.

NWTCPHPS

This message indicates an internal logic error in the HPS API.

Issue the TRACE and SNAP operator commands for this driver. For more information, see the section Entire Net-Work Operator Commands. Then contact your Software AG technical support representative.

NWTCPHPS

The asynchronous exit was entered without a required token. This message indicates an internal logic error in the HPS API.

Issue the TRACE and SNAP operator commands for this driver. For more information, see the section Entire Net-Work Operator Commands. Then contact your Software AG technical support representative.

NWTCPHPS

A call to the IBM TCP/IP stack failed for function xxxxxxxx. The error number nnnnn and the reason code rrrrrrrr indicate the reason the call failed, while sssss is the socket that the function failed on. This message provides diagnostic information about a previous error message. This message may also be followed by a NETP701I message that explains the error number and reason codes.

Locate message NETP701I for a description of the error number. Refer to the IBM documentation for an explanation of the error number and the reason code.

NWTCPOES

The text of this message describes the error number from message NETP700I.

Eliminate if possible the condition that caused this message.

NWTCPOES

An invalid request was made to this API.

Contact your Software AG technical support representative

NWTCPOES

An attempt to load a required module for TCP/IP failed. The driver and all links using this API will be unusable. This is most likely caused by TCP/IP not being correctly installed. It could also be caused by a short on storage condition or an I/O error.

Check the joblog and syslog for any additional messages that may indicate a reason for the problem. These messages may be operating system messages.

NWTCPOES

An attempt to allocate storage for a required control block failed. This control block is needed for the driver and all active links using this API. Only the new link being connected or the new driver being opened are affected. All active links and drivers will continue to run as long as the storage shortage does not cause other problems with Entire Net-Work

Look for other messages indicating storage problems and perform any action recommended.

NWTCPOES

An error occurred trying to close a socket used for a connection. The Entire Net-Work connection is closed, but this socket will be unusable for a future connection.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A TCP/IP driver using API=OES has been closed. This is an informational message and does not indicate an error.

None

NWTCPOES

This message indicates that Entire Net-Work is not APF authorized. APF authorization is required in order to use the API=OES.

Provide APF authorization for all load libraries in the Entire Net-Work STEPLIB.

NWTCPOES

API=OES was specified for a driver on a system that does not support it. Currently OS390 is the only operating system that supports this API.

Specify a valid API for the system and TCP/IP stack you are running.

NWTCPOES

An Open Edition call to DUB the TCB failed. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A call made to TCP/IP to get a new socket failed. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information. Some adjusting of parameters for TCP/IP may need to be done to allow for more sockets.

NWTCPOES

A BIND function call to TCP/IP failed. The BIND function is used to tell TCP/IP what port to listen on and what restrictions apply, i.e., who can connect to this port. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A GETSOCKOPT function call to TCP/IP failed. The GETSOCKOPTfunction is used to determine the maximum message size that can be sent. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A LISTEN function call to TCP/IP failed. The LISTEN function is used to set the number of connection requests that can be queued. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

An ACCEPT function call to TCP/IP failed. The ACCEPT function waits for a connection request and returns a socket to be used for the new conversation. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A connect queue entry is needed to process a connection request and none is currently available. The connection request is rejected.

Increase the value of the CONNQUE parameter on the DRIVER statement.

NWTCPOES

A SETSOCKOPT function call to TCP/IP failed. The SETSOCKOPT function is used to set the KEEPALIVE option in TCP/IP. KEEPALIVE is a TCP/IP option that regularly sends a message to verify that a connection is still active. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information. Set KEEPALIVE=NO parameter on driver and link statements to disable this function.

NWTCPOES

A SETSOCKOPT function call to TCP/IP failed. The SETSOCKOPT function is used to set the REUSEADDR option in TCP/IP so that a socket can be reused immediately after being closed.

Locate messages NETP700I and NETP701I for additional information. .

NWTCPOES

A CONNECT function call to TCP/IP failed. The CONNECT function is used to connect to a remote Entire Net-Work node. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information. Make sure that the remote Entire Net-Work node is running and is accepting connections from this node.

NWTCPOES

A SENDMSG function call to TCP/IP failed. The SENDMSG function is used to send a data packet to a remote Entire Net-Work node. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A RECV function call to TCP/IP failed. The RECV function is used to receive a data packet from a remote Entire Net-Work node. This call waits for incoming data before returning to Entire Net-Work. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information.

NWTCPOES

A GETHOSTBYNAME function call to TCP/IP failed. The GETHOSTBYNAME function is used to determine the TCP/IP address of an Entire Net-Work node that used the ADJHOST parameter to specify the name. NETP700I will provide an error number that indicates why it failed.

Locate messages NETP700I and NETP701I for additional information. Make sure that the name specified on ADJHOST parameter is correct and that this name is in the hosts file or domain name server. Read about the ADJHOST parameter

NWTCPOES

A GetHostByAddr function call to TCP/IP failed, probably because the host name address was not defined in the DNS (Domain Name Service). The GetHostByAddr call is used to determine the name of a connecting IP address when ADJHOST has been specified on a LINK statement.

Add the host name and IP address to your domain name server.

NWTCPOES

This message indicates an internal logic error in the OES API.

Issue the TRACE and SNAP Entire Net-Work commands for this driver. Then contact your Software AG technical support representative.

NWTCPOES

TCP/IP is being terminated on the local system. All connections using this driver will be disconnected. This is an informational message and does not indicate an error in Entire Net-Work.

Determine why the TCP/IP address space is being terminated.

NWTCPOES

TCP/IP has terminated the connection for this link. This link is no longer active.

Look for other messages on both the local and remote systems to determine why the link was terminated.

NWTCPOES

The asynchronous exit abended while processing a previous TCP/IP function. This message indicates an internal logic error in the OES API.

Issue the TRACE and SNAP Entire Net-Work commands for this driver. Then contact your Software AG technical support representative.

NWTCPOES

This message indicates an internal logic error in the OES API.

Issue the TRACE and SNAP Entire Net-Work commands for this driver. Then contact your Software AG technical support representative.

NWTCPOES

The asynchronous exit was entered without a required token. This message indicates an internal logic error in the OES API.

Issue the TRACE and SNAP Entire Net-Work commands for this driver. Then contact your Software AG technical support representative.

NWTCPOES

The Simple Connection Line Driver's Active Client Table (ACT) array was allocated at the indicated address. This message is issued at initialization, and also if the ACT array is expanded.

None required. This message is informational only.

NETTCPX, NXTSRV

Allocation of a client control block failed. Possible causes are:

• shortage of storage

• exceeding the total number of clients allowed (32767)

• internal error

Increase storage or limit the number of clients.

NXTSRV

An internal error occurred when attempting to free a client control block.

Contact your Software AG technical support representative.

NETTCPX

The Active Client Table (ACT) array has been increased because it was full and a new client attempted to initialize. The table is increased by 50% of its current size.

If this message occurs frequently, increase NUMUSERS to minimize expansions.

NXTSRV

Each incoming request is validated against that client's current information. This message is issued if there was a mismatch or the client was not found.

Collect traces on the client and server side and contact your Software AG technical support representative.

NETTCPX

An error occurred when converting the message to Entire Net-Work's MHDR format. The probable cause is a shortage of storage.

If increasing storage does not resolve the error, contact your Software AG technical support representative.

NETTCPX

An invalid value was specified for NUMUSERS. Entire Net-Work sets NUMUSERS to 100 and continues to initialize.

Correct the NUMUSERS value.

NETTCPX

The CONNECT command is not allowed with the Simple Connection Line Driver. Connect processing is handled automatically when a client initiates.

None required. This message is informational only.

NETTCPX

Client xxxxx was terminated before the current reply could be sent back, where xxxxx is the ACT index and the rightmost two bytes of the Context ID in the A1 message header. This can happen if the client times out or otherwise terminates while Entire Net-Work is processing a reply for that client.

If the client did not legitimately time out or terminate, obtain traces and contact your Software AG technical support representative.

NETTCPX

The link named in the message was successfully connected to the partner TCP/IP address named in the message.

This message is issued for TCPX links in place of NET0110. It is written only to DDPRINT/NETPRNT, not the console.

Normal processing continues and the newly connected link can be used for message traffic.

None required. This message is informational only.

The link named in the message was disconnected from the partner TCP/IP address named in the message by one of the following events:

• The node terminated.

• A DISCONNECT operator command was issued.

• One of several types of link failures occurred (these link failures are described by related line driver messages)

• The partner TCP/IP address terminated the socket connection.

This message is issued for TCPX links in place of NET0107. It is written only to DDPRINT/NETPRNT, not the console.

The system continues processing without the link. If the disconnection was due to an error, other messages should indicate the cause of the disconnection.

Correct the error, if required,and retry the application.

An error occurred while trying to open file xxxxxxx (DDCARD, NETFILE, or DDPRINT) and the file could not be opened. This error causes the utility program to terminate with a return code of 8.

Look at the job log or system log for additional system messages that indicate why the file could not be opened.

NETPFIL1, NETPFIL2

An error occurred while trying to read from file xxxxxxx (DDCARD or NETFILE). This error causes the utility program to terminate with a return code of 8.

Look at the job log or system log for additional system messages that indicate the cause of the I/O error.

NETPFIL1, NETPFIL2

An error occurred while trying to write to the DDPRINT file. This error causes the utility program to terminate with a return code of 8.

Look at the job log or system log for additional system messages that indicate the cause of the I/O error.

NETPFIL1, NETPFIL2

An error occurred while trying to close file xxxxxxx (DDCARD, NETFILE or DDPRINT). This error causes the utility program to terminate with a return code of 8. The files are not closed until the end of the program, so the output file may or may not contain the desired data.

Look at the job log or system log for additional system messages that indicate the cause of the I/O error.

NETPFIL1, NETPFIL2

A FIND parameter was specified with an invalid syntax. This probably means that the OFFSET or VALUE keywords were not specified or were specified out of order.

Correct the FIND parameter using the following syntax:

FIND=logging title,OFFSET=nnn,VALUE=characters
FIND=logging title,OFFSET=nnn,VALUE=X'hex values'

NETPFIL2

The OFFSET specified on a FIND parameter did not contain a valid hexadecimal displacement. The displacement value must be a valid hexadecimal number containing only 0-F.

Correct the FIND parameter OFFSET=xxx to a valid hexadecimal displacement.

NETPFIL2