NETH* - SMH Line Driver Messages

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