NETP* - TCP/IP and Simple Connection Line Driver Messages

The following are the categories used for operator messages for the TCP/IP and the Simple Connection Line Driver:

Message Range Description
NETP000- NETP099 Non-API-related messages mainly from NETTCPI
NETP200 - NETP299 IBM API-specific messages
NETP300 - NETP399 BS2000/OSD API-specific messages
NETP500 - NETP599 Connectivity Systems API-specific messages
NETP600 - NETP699 HPS API-specific messages
NETP700 - NETP799 OES API-specific messages
NETP800 - NETP899 Simple Connection Line Driver-specific messages

Overview of Messages

NETP001W: | NETP002W: | NETP003W: | NETP004W: | NETP005W: | NETP006I: | NETP007I: | NETP008I: | NETP009I: | NETP010E: | NETP011W: | NETP012W: | NETP013W: | NETP015W: | NETP016E: | NETP017I: | NETP018E: | NETP019I: | NETP020W: | NETP021W: | NETP022W: | NETP040I: | NETP041W: | NETP042W: | NETP043I: | NETP044I: | NETP046W: | NETP047I: | NETP048I: | NETP060I: | NETP061I: | NETP062I: | NETP063I: | NETP065I: | NETP066I: | NETP067I: | NETP200W: | NETP201I: | NETP202W: | NETP203W: | NETP204W: | NETP205W: | NETP206W: | NETP207E: | NETP208E: | NETP209E: | NETP300I: | NETP301I: | NETP305W: | NETP308I: | NETP322E: | NETP332E: | NETP333W: | NETP336I: | NETP338I: | NETP340I: | NETP341W: | NETP344W: | NETP345W: | NETP351I: | NETP354I: | NETP359I: | NETP369I: | NETP370I: | NETP373I: | NETP375I: | NETP502W: | NETP509E: | NETP511W: | NETP512W: | NETP521W: | NETP522W: | NETP531W: | NETP532W: | NETP541W: | NETP542W: | NETP551W: | NETP552W: | NETP561W: | NETP562W: | NETP571W: | NETP572W: | NETP581W: | NET0582W: | NETP600I: | NETP601I: | NETP602E: | NETP603E: | NETP604E: | NETP605W: | NETP606I: | NETP610E: | NETP611E: | NETP612E: | NETP613E: | NETP614E: | NETP615E: | NETP616E: | NETP617W: | NETP618W: | NETP620W: | NETP621E: | NETP622E: | NETP623W: | NETP624W: | NETP630E: | NETP631I: | NETP632I: | NETP633I: | NETP634I: | NETP635I: | NETP700I: | NETP701I: | NETP702E: | NETP703E: | NETP704E: | NETP705W: | NETP706I: | NETP707E: | NETP710E: | NETP711E: | NETP712E: | NETP713E: | NETP714E: | NETP715E: | NETP716E: | NETP717W: | NETP718W: | NETP719W: | NETP720W: | NETP721E: | NETP722E: | NETP723W: | NETP724W: | NETP730E: | NETP731I: | NETP732I: | NETP733I: | NETP734I: | NETP735I: | NETP800I: | NETP801E: | NETP802E: | NETP803I: | NETP804I: | NETP805E: | NETP806E: | NETP808E: | NETP809E: | NETP811I: | NETP813E: | NETP814E: | NETP816E: | NETP817E: | NETP818I: | NETP819I: | NETP820E: | NETP821E: | NETP822E: | NETP823E: | NETP899I:

NETP001W: ERROR DURING RECEIVE RC=(xx) LINK=llllllll
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs to receive data, but an error of some type occurred within the API, preventing it from completing the receive 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.

Action

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

Module

NETTCPI


NETP002W: ERROR DURING SEND RC=(xx) LINK=llllllll
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs 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.

Action

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.

Module

NETTCPI


NETP003W: LINK llllllll SEND TIME EXCEEDED, DISCONNECTING LINK
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs 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.

Action

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.

Module

NETTCPI


NETP004W: ERROR DURING CONNECT RC=(xx) LINK=llllllll
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs 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.

Action

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.

Module

NETTCPI


NETP005W: ERROR DURING ACCEPT RC=(xx) LINK=llllllll
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs 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.

Action

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.

Module

NETTCPI


NETP006I: DRIVBLK @ dddddddd NETTCPI @ mmmmmmmm
Explanation

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

Action

None.

Module

NETTCPI


NETP007I: INTERNAL TRACE TABLE ADDRESS = tttttttt
Explanation

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

Action

None

Module

NETTCPI


NETP008I: UNABLE TO LOAD LINK SPECIFIC EXIT
Explanation

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.

Action

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.

Module

NETTCPI


NETP009I: Entire Net-Work MODULE mmmmmmmm LOADED AT vvvvvvvv
Explanation

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

Action

None

Module

NETTCPI


NETP010E: UNABLE TO LOAD MODULE: mmmmmmmm
Explanation

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.

Action

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.

Module

NETTCPI


NETP011W: TCP/IP ACCESS METHOD ERROR; CONNECT IGNORED
Explanation

The Entire Net-Work TCP/IP 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.

Action

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.

Module

NETTCPI


NETP012W: CONNECTION TERMINATED BY API, LINK=llllllll
Explanation

An Entire Net-Work TCP/IP 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.

Action

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

Module

NETTCPI


NETP013W: CONNECTION REJECTED FOR xxx.xxx.xxx.xxx
Explanation

Remote Entire Net-Work host xxx.xxx.xxx.xxx attempted to establish a TCP/IP link with the Entire Net-Work host, but one of the following problems occurred, causing the connection to be rejected:

  • The host does not have a predefined LINK statement for the remote host and, because ACCEPTUI=N is specified in the DRIVER statement, Entire Net-Work cannot dynamically add a new link for the remote host; or

  • The host does have a predefined LINK statement for the remote host, but 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.

Action

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

  • Predefine a link for this host. See the section TCP/IP LINK Statement.

  • Specify ACCEPTUI=Y to allow ALL unknown hosts to be dynamically defined; or

  • Issue the command TCPI linkname SHOW to determine if the Internet address is correct in the link related control blocks. If the Internet address is incorrect, do one of the following: alter it manually with the commands TCPI linkname CLOSE ALTER INETADDR=(x,x,x,x) and TCPI linkname OPEN; or, if ADJHOST= was specified and a name resolution error occurred, issue the command CONN linkname.

Module

NETTCPI


NETP015W: ERROR DURING REJECT RC=(xx) LINK=llllllll
Explanation

NETTCPI called one of the Entire Net-Work TCP APIs 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.

Action

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

Module

NETTCPI


NETP016E: ERROR OCCURRED OBTAINING OR FREEING STORAGE
Explanation

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.

Action

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.

Module

NETTCPI


NETP017I: RECONNECT IN PROGRESS FOR LINK llllllll
Explanation

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.

Action

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.

Module

NETTCPI


NETP018E: UNKNOWN RECORD TYPE RECEIVED ON LINK llllllll
Explanation

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. The cause of the problem may be one of the following: the remote node was upgraded and is taking advantage of features that were not available when NETTCPI was last developed, or an error occurred and invalid data was received.

Action

Issue the command TCPI 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.

Module

NETTCPI


NETP019I: READ BUFFER LENGTH SET TO = nnnnn ON llllllll
Explanation

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.

Action

None.

Module

NETTCPI


NETP020W: LINK xxxxxxxx INVALID STATE TO INITIATE A CONNECT
Explanation

The command CONN linkname was issued to initiate connect processing for a link. The link was already in connect processing, so the command was ignored.

Action

If the remote node is available and immediately accessible through TCP (that is, no networking problems exist), connect processing should complete in a very short time. This message indicates a failure in a previous connect attempt, which is still active and attempting to complete. Follow normal procedures for the debugging of TCP/IP related communications problems. Connect processing can be stopped for the link by issuing the command DISC linkname.

Module

NETTCPI


NETP021W: ADJHOST PARAMETER NOT SUPPORTED BY TCP API aaaaaaaa
Explanation

A value for the Internet host name was specified with the ADJHOST parameter in the LINK statement, and the Entire Net-Work TCP API specified by aaaaaaaa does not support the resolution of Internet host names to Internet numbers.

Action

Change the LINK statement to use the INETADDR= parameter instead of the ADJHOST= parameter. See the section TCP/IP LINK Statement .

Module

NETTCPI


NETP022W: CONNECT FAILED FOR llllllll, UNABLE TO RESOLVE HOST NAME
Explanation

The command CONN llllllll was issued (possibly 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.

Action

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.

Module

NETTCPI


NETP040I: LINK llllllll HAS RESUMED PROCESSING
Explanation

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

Action

None.

Module

NWTCPOPC


NETP041W: PROCESSING ON LINK llllllll HAS BEEN SUSPENDED
Explanation

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

Action

Issue the RESUME command to restart message processing when appropriate.

Module

NWTCPOPC


NETP042W: INCORRECT LINK SPECIFIED IN COMMAND
Explanation

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

Action

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

Module

NWTCPOPC


NETP043I: TCP/IP COMMAND(S) ACCEPTED
Explanation

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.

Action

None.

Module

NWTCPOPC


NETP044I: LINK llllllll STATISTICS xxxxxxx
Explanation

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

Action

None.

Module

NWTCPOPC


NETP046W: LINK llllllll NOT ALTERED, BAD CONFIGURATION PARAMETERS
Explanation

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.

Action

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

Module

NWTCPOPC


NETP047I: LINK llllllll HAS BEEN MANUALLY xxxxxx
Explanation

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.

Action

None.


NETP048I: LINK llllllll xxxxxxxxxxxxxxxxxxxxxxxx
Explanation

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.

Action

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.

Module

NWTCPOPC


NETP060I: ------------CONFIGURATION FOR LINK llllllll------------
ADJHOST(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
INETADDR(xxx.xxx.xxx.xxx) LILNODE(xxxxxxxx)
MULTSESS(x) PSTATS(x)
RSTATS(x) SAF(x) SENDTIME(xxxxxxx)
STATINT(xxxxxxx) TRACESIZ(xxxxxxx)
IP Version 6 address=xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Explanation

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.

Action

None.

Module

NWTCPOPC


NETP061I: LINK llllllll STATE(xxxxxxxxxxxx) MSGS SENT(xxxxxxx)
Explanation

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.

Action

None.

Module

NWTCPOPC


NETP062I: CONFIGURATION FOR DRIVER dddd
ACCEPTUI(x) API(xxx) APITRACE(x,x,x,x,x,x,x,x,x,x)
CONNQUE(xxxxx) DRVNAME(xxxx)
PSTATS(x) RESTART(xxxxx,xxxxx) RSTATS(x)
SERVERID(xxxxx) STATINT(xxxxxxx) SUBSYS(xxxx)
TRACE(xxx) TRACELEV(x,x,x,x,x,x,x,x,x,x) TRACESIZ(xxxxxxx)
MULTSESS (x) USERID(xxxxxxxx)
OPTIONS1(xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx)
OPTIONS2(xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx)
IP VERSION 6 ALLOWED=x, SUPPORTED=x
CURRENT SIZE OF CLIENT TABLE xxx
Explanation

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.

Action

None.

Module

NWTCPOPC


NETP063I: STATISTICS FOR LINK llllllll OR DRIVER dddddddd
Explanation
    +----------------------------------------------------------------------+
(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:

Line (a) The name of the link or driver and the time period in hours:minutes:seconds and seconds:milliseconds since the last time statistics were reset or a link was connected (if applicable).
Line (b) Shows the cumulative number of bytes and messages written and the cumulative number of write API calls.
Line (c) Shows the average number of bytes and messages written and the average number of write API calls per second.
Line (d) Shows the cumulative number of bytes and messages read and the cumulative number of read API calls.
Line (e) Shows the average number of bytes and messages read and the average number of read API calls per second.
Line (f) Shows the cumulative number of WRITE commands that occurred. The total number of WRITEs is equal to the number of WRITEs from the Entire Net-Work task plus the number of WRITEs from asynchronous routines.
Line (g) Shows the average number of WRITE commands that occurred per second. The total average WRITEs is equal to the average of WRITEs from the Entire Net-Work task plus the average of WRITEs from asynchronous routines.
Line (h) Shows the cumulative number of READ commands that occurred. The total number of READs is equal to the number of READs from the Entire Net-Work task plus the number of READs from asynchronous routines.
Line (i) Shows the average number of READ commands that occurred per second. The total average READs is equal to the average of READs from the Entire Net-Work task plus the average of READs from asynchronous routines.
Action

None.

Module

NWTCPOPC


NETP065I: ACTIVE USERS FOR type name
Explanation

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                                                       
                                 
Action

None.

Module

NWXTSOPC


NETP066I: ------------CONFIGURATION FOR LINK llllllll------------
ADJHOST(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
ADJNODE(xxxxxxxx) INETADDR(xxx.xxx.xxx.xxx)
KEEPALIV(x) MULTSESS(x) PSTATS(x)
RSTATS(x) SAF(x) SENDTIME(xxxxxxx)
STATINT(xxxxxxx) TRACESIZ(xxxxxxx)
Explanation

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.

Action

None.

Module

NWXTSOPC


NETP067I: CONFIGURATION FOR DRIVER TCPX
ACCEPTUI(x) API(api) APITRACE(x,x,x,x,x,x,x,x,x,x)
CONNQUE(n) DRVCHAR(x) DRVNAME(name) KEEPALIV(x)
MULTSESS(x) PSTATS(x) RESTART(xxxxx,xxxxx) RSTATS(x)
SERVERID(serverid) STATINT(seconds) SUBSYS(subsys)
TRACE(x) TRACELEV(x,x,x,x,x,x,x,x,x,x) TRACESIZ(bytes)
USERID(userid)
OPTIONS1(xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx)
OPTIONS2(xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx)
IP VERSION 6 ALLOWED=x, SUPPORTED=x
CURRENT SIZE OF CLIENT TABLE (NUMUSERS)n
Explanation

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.

Action

None.

Module

NWXTSOPC


NETP200W: xxxx SUBSYSTEM ENTRY NOT FOUND
Explanation

The IBM TCP/IP implementation under MVS is a 'port' of the TCP/IP implementation under z/VM. Under z/VM, applications issue Socket calls to the TCP/IP virtual machine via IUCV. Under MVS, applications issue Socket calls to the TCP/IP address space via simulated IUCV calls. Simulated IUCV calls are performed by issuing 'Program Call' (PC) instructions to routines that can move data from the application program address space to the TCP/IP address space. These routines are loaded when the VMCF address space is started during system (MVS) initialization.

IBM has implemented this by requiring changes to member IEASSN00 of SYS1.PARMLIB to define both a VMCF address space and VMCF subsystem control blocks. Entire Net-Work must locate the PC numbers that reside in the VMCF subsystem control blocks before it can issue any IUCV socket call. The subsystem control block chain is searched to locate the subsystem whose name matches the SUBSYS=parameter specified on the DRIVER statement. This message is issued if no such subsystem control block can be found.

Action

Make sure that the value coded on the SUBSYS= parameter of the driver configuration statement matches the value specified in member IEASSN00 which resides in SYS1.PARMLIB. The subsystem name used by most installations and which is also the default as shipped by IBM is 'VMCF'.

Module

NWTCPIBM


NETP201I: xxxxxxxx IS NOT ACTIVE (LOGGED ON)
Explanation

The IBM TCP/IP address space whose job or started task name is specified by xxxxxxxx is not actively waiting for IUCV Socket calls. The Entire Net-Work TCP/IP driver obtains this name from the USER= parameter of the driver configuration statement. The default name is 'TCPIP', but this may vary from site to site.

Action

Determine the name of the TCP/IP started task that is running the IBM TCP/IP protocol stack and specify that name on the USER= parameter of the driver configuration statement. If the name is correct, make sure that the TCP/IP started task/job is active and ready for processing.

Module

NWTCPIBM


NETP202W: UNABLE TO ALLOCATE CONNECT QUEUE ENTRY
Explanation

When a connect request from a remote Entire Net-Work node is received, information such as host number and remote/local ports is stored in a connect queue entry. The main Entire Net-Work TCP program uses this information to decide whether to accept or reject the connection. The number of connect queue entries is determined at Entire Net-Work startup time by the CONNQUE= parameter in the DRIVER statement.

When this message was issued, all connect queue entries were in use. As a result, the connection was rejected.

Action

The IBM API relies on the IBM TCP/IP stack to provide queuing of connect requests internally by specifying a queue depth when it BINDs its well known port. Entire Net-Work then issues a LISTEN call followed by asynchronous ACCEPT calls to receive incoming connect requests. Before Entire Net-Work issues any subsequent ACCEPT, it performs all necessary processing to accept or reject the connection. As a result, no more than one connect queue entry should ever be in use at a time. If this message is issued, there is a problem freeing connect queue entries within Entire Net-Work. Contact your Software AG technical support representative.

Module

NWIBMEXT


NETP203W: SOCKET ERROR OCCURRED ON xxxxxxxxxx FOR PARTNER xxx.xxx.xxx.xxx
Explanation

An IUCV Socket call identified by xxxxxxxxxxxx failed for the link whose partner has the Internet host number xxx.xxx.xxx.xxx. Host number 000.000.000.000 indicates that the error occurred on the main driver socket. This message is followed by message NETP204W, which provides the ERRNO value and an explanation of the error.

Action

Locate message NETP204W following this message and perform the related action, if any.

Module

NWTCPIBM, NWIBMEXT


NETP204W: ERRNO=xxxxxxxxxxxxxxxxxx(..................................)
Explanation

A socket error occurred on a socket request issued by the Entire Net-Work IBM TCP API. This message consists of two parts, the error number mnemonic (ERRNO=) and the explanation of the error. See the IBM TCP/IP documentation.

Action

Message NETP203W should have been issued prior to this message. NETP203W contains the socket call that failed. Refer to the IBM TCP/IP documentation, and locate the section dealing with the issuance of the socket call that failed. Also locate the list of ERRNO values that can occur, and an explanation of how the ERRNO value applies to the failing socket call. Perform the action specified for the specific ERRNO value/socket call combination, if any.

Module

NWTCPIBM, NWIBMEXT


NETP205W: SEVER CODE: xxxxxxxxxxxxxxxx FROM PARTNER AT xxx.xxx.xxx.xxx
Explanation

The IBM TCP/IP protocol stack has severed the IUCV connection between itself and the Entire Net-Work IBM TCP API for the link whose partner has the Internet host number xxx.xxx.xxx.xxx. If the Internet host number is 000.000.000.000, the sever occurred on the main IUCV path for the driver. The IBM TCP/IP stack provides a sever reason code when it terminates the IUCV path. Sever reason codes are located in the IBM TCP/IP documentation.

Action

Locate the sever reason code and follow the action for that specific reason code, if any.

Module

NWIBMEXT


NETP206W: iiiiiiiiiiiiiiii CALL FAILED, R15 = xxxx, FUNCTION= ffffffffff
Explanation

An attempt to issue a socket call via an IUCV function iiiiiiiiiiiii such as IUCVMCOM SEND failed. The related socket function, if applicable, is listed as ffffffffff. The value returned in register 15 (xxxx) is displayed in decimal to aid in debugging.

Action

A return value generated by an IUCV call and displayed as xxxx in this message can be the IUCV return code or the IUCV IPR return code. If the return value is between 2 and 999, it is an IUCV return code. If the return value is greater than 1000, it is the sum of the IPR return code and 1000. Subtract 1000 from the return value to get the true IPR return code.

Return codes are described in the IBM TCP/IP documentation. Perform the related actions for the IUCV Return Code or the IUCV IPR code, if any.

Module

NWTCPIBM, NWIBMEXT


NETP207E: IPAUDIT=X'xxxxxx ON xxxxxxxxxx FOR PARTNER xxx.xxx.xxx.xxx
Explanation

When an IUCV request completed, one or more of the three audit fields (IPAUDIT) located in the IUCV parameter list (IPARML) was set. The IPAUDIT fields are comprised of bit settings that indicate what type of exceptional error occurred when IUCV tried to process the request. When any of the IPAUDIT bits are set, this message is issued on behalf of the link whose partner has the Internet host number xxx.xxx.xxx.xxx. If the Internet host number is 000.000.000.000, the exceptional error occurred on the main socket for the driver.

Action

This error is generally indicative of a logic error in the Entire Net-Work IBM TCP API. Issue the SNAP operator command and contact your Software AG technical support representative.

Module

NWTCPIBM, NWIBMEXT


NETP208E: AN IUCV CONNECT COMPLETED BUT UNABLE TO LOCATE A CONNECTING SCT
Explanation

An IUCV connect was issued to create a path between Entire Net-Work and the IBM TCP/IP protocol stack. The IUCV interface does not provide a mechanism to pass user context to the IUCV connect completion routine. The IUCV connect completion routine must therefore scan through a chain of Session Control Tables (SCTs) searching for an SCT waiting for an IUCV connect to complete. However, at the time the IUCV connect completed, there were no SCTs on the chain. IUCV connect processing terminates.

Action

This condition should not normally occur. Issue an Entire Net-Work SNAP command and contact your Software AG technical support representative.

Module

NWIBMEXT


NETP209E: ERROR OCCURRED OBTAINING OR FREEING STORAGE
Explanation

An error occurred when attempting to obtain or release virtual storage. When this occurs, it is usually caused by one of the following: there is insufficient storage in the region to satisfy the obtain; or, one of the buffer pools was not large enough to satisfy the storage request.

Action

Check the buffer pool statistics by issuing the operator command DISPLAY STATISTICS. 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.

Module

NWTCPIBM, NWIBMEXT


NETP300I: NET-WORK TCP/IP BS2000/OSD API STARTED, VERSION xxx / xxxxxx / CHANGE STATUS xxx
Explanation

This message provides the version, creation date, and change status for BS2000 systems running Sockets version 2.1 or earlier.

Action

No action is required for this informational message.

Module

NWTCPBS2


NETP301I: NET-WORK BS2000 EVENT COUPLED SOCKETS API STARTED, VERSION version BUILD build
Explanation

This message provides the version and build number for the BS2000 Sockets TCP/IP interface running Sockets version 2.2 or later.

Action

No action is required for this informational message.

Module

NWTCPBS2


NETP305W: UNEXPECTED RETURN CODE xxxxxxxx FROM xxxxxxxxxx
Explanation

A system call returns an unexpected error.

Action

Refer to the SNI documentation for BS2000, and contact your Software AG technical support representative.

Module

NWTCPBS2


NETP308I: MEMORY POOL xxxxxxxxxxxxxxxx AT xxxxxxxx
Explanation

This message provides information for support.

Action

None

Module

NWTCPBS2


NETP322E: LINK TABLE IS FULL, INCREASE YOUR CLIENT LIMIT
Explanation

The client limit has been reached in the common memory pool.

Action

Increase the number of clients specified for the OPTIONS1 parameter on the DRIVER statement for the next Entire Net-Work startup and/or disconnect any unused links. For more information, see the section TCP/IP DRIVER Statement.


NETP332E: REMOTE HOST xxxxxxxxxxxxX NOT FOUND, GETHOSTBYNAME() = xxx
Explanation

The host name corresponding to this IP address could not be found. The host name may be incorrect, too long, undefined, or otherwise invalid.

Action

Specify the correct entry with the /BCIN command or try using the IP address, i.e., specify the INETADDR= parameter instead of the ADJHOST= parameter, but do not specify both. See the section TCP/IP LINK Statement.

Module

NWBS2SUB


NETP333W: UNEXPECTED RC rc FROM process
Explanation

These are errors in the initialization of the BS2000 TCP/IP Sockets Interface. The response codes (rc) are described in the NETP344W error message. The process in which the error occurred is given in the message (process) and may be one of the following:

Process Description
IOR GETMAIN P1 Cannot get memory for the interface.
IOR GETMAIN P2 Cannot get memory for the interface.
IOR GET EVENT ID Internal information concerning the event name cannot be carried out.
SOCKET FOR LISTEN Cannot get the listen socket.
BIND Cannot bind the listen socket.
POST The post back to the driver has failed.
GETEVENT Getting the P1 event
Action

Review the response code to determine what the problem is. If you need additional assistance, contact your Software AG technical support representative.

Module

NWTCPBS2


NETP336I: UNEXPECTED RC rc FROM SOCKET CALL type FOR SOCKET sname
Explanation

An error has been received from an action on the socket named in the message (sname). The response code from the attempt (rc) and the type of socket call (type) are given in the message. The types of calls may be one of the following:

Call Type Description
RECEIVE Receive error on the socket
CLOSE Close socket call
CLOSE DRIVER Close line call
Action

Review the response code to determine what the problem is. If you need additional assistance, contact your Software AG technical support representative.

Module

NWTCPBS2


NETP338I: MAIN TASK LOST
Explanation

The Entire Net-Work main task terminated abnormally. The subtask forces its own termination processing.

Action

Refer to the SYSOUT protocol for further details.

Module

NWBS2SUB


NETP340I: process ** FAILED ** RSP rc
Explanation

An error occurred in the event acceptor callback routine defined by the response code given in the message (rc). These response code numbers are described in error message NET0344W. The process in which the error occurred is given in the message (process) and may be one of the following:

Call Type Description
ACCEPT CONN SOCKET Accept socket connection.
ACCEPT NO SOCKET Socket cannot be accessed because it is not in the internal table.
ACCEPT ADD SOCKET Socket connection cannot be accepted because there is no space for the new connection.
ACCEPT OUT Outgoing connect request refused.
GO SIGNAL Connection signaling error occurred.
Action

Review the response code to determine what the problem is. If you need additional assistance, contact your Software AG technical support representative.

Module

NWTCPBS2


NETP341W: UNEXPECTED RC rc FROM SOCKET CALL type
Explanation

An error occurred during a Sockets call. The response code from the call (rc) and the type of socket call (type) are listed in the message. The type of socket call may be one of the following:

Call Type Description
SOCKET CONN Connect to the socket
CONNECT Build of connection
Action

Review the response code to determine what the problem is. If you need additional assistance, contact your Software AG technical support representative.

Module

It should contain the file BS2.ERRNO.H. Check the meaning of the RC in this file and if necessary, contact your Software AG technical support representative.

Module

NWTCPBS2 / NWBS2SUB

Module

NWTCPBS2


NETP344W: UNEXPECTED RC rc FROM process-type, LEN=length
Explanation

An error occurred in the BS2000 Sockets TCP/IP interface and the response code (rc), type of process (for example, SEND/RECEIVE) and the length of the data involved (length) are given in the message. Here are some possible sockets response codes:

Response Code Description
60 The device is not a stream.
61 No data (for no delay I/O).
62 The timer expired.
63 An out of streams resource was detected.
64 The machine is not on the network.
65 A package is not installed.
66 The object is remote.
67 The link has been severed.
68 An advertise error occurred.
69 An srmount error occurred.
70 A communication error occurred during a send operation.
71 A protocol error occurred.
74 A multihop was attempted.
95 A socket operation was attempted on a non-socket.
96 A destination address is required.
97 The message is too long.
98 The specified protocol is the wrong type for the socket.
99 The protocol is not available.
120 The specified protocol is not supported.
121 The socket type is not supported.
122 The specified operation is not supported on the socket.
123 The protocol family is not supported.
124 The address family is not supported by the protocol family.
125 The address is already in use.
126 An attempt to assign the requested address failed.
127 The network is down.
128 The network is unreachable.
129 The network dropped the connection.
130 The software caused a connection abort.
131 The connection was reset by a peer.
132 No buffer space is available.
133 The socket is already connected.
134 The socket is not connected.
143 An attempt to perform a send operation occurred after the socket was shut down.
144 Too many references -- attempts to splice fail.
145 The connection timed out.
146 The connection was refused.
147 The host is down.
148 There is no route to the host.
149 The operation is already in progress.
150 The operation is now in progress.
206 No such device or address can be found.
207 The argument list is too long.
208 An Exec format error occurred.
210 No children exist.
211 No more processes exist.
212 Not enough core.
213 Permission is denied.
215 A block device is required.
243 No CSI structure is available.
244 Level 2 halted.
250 A block has not been fully transferred.
Action

Check the response code to determine the cause of the problem.

Module

NWTCPBS2


NETP345W: SC SEND INCOMPLETE, bytes FROM start-value
Explanation

Entire Net-Work has attempted to send data via the BS2000 TCP/IP Sockets interface. Only some of the data has been sent. The number of bytes sent (bytes) and the starting value (start-value) are given in the message.

Action

Check accompanying error messages and act accordingly.

Module

NWTCPBS2


NETP351I: LD ACCEPTED NO ADD SOCKET name
Explanation

This is a Sockets management error. There are only a maximum of 2048 sockets. The socket named in the message (name) cannot be added to the list.

Action

Consider reconfiguring your system to reduce the number of sockets being used. For additional assistance, contact your Software AG technical support representative.

Module

NWTCPBS2


NETP354I: MAIN TASKS TCP/IP INITIALIZATION FAILED
Explanation

A problem occurred during the command socket initialization; i.e., this is a TCP/IP problem.

Action

Try again when TCP/IP is functioning properly or contact your Software AG technical support representative.

Module

NWBS2SUB


NETP359I: SUBTASK NORMALLY TERMINATED
Explanation

Entire Net-Work terminated normally as the result of an operator command.

Action

None

Module

NWBS2SUB


NETP369I: SUBTASK INITIALIZED
Explanation

The subtask is successfully initialized and is ready to accept any incoming connections.

Action

None

Module

NWBS2SUB


NETP370I: NETWORK ABEND OCCURRED, PSW: xxxxxxxx, IC: xx
Explanation

An Entire Net-Work program interrupt has occurred. The message displays the program counter and the interrupt code, and Entire Net-Work terminates abnormally.

Action

Produce an Entire Net-Work dump and then contact your Software AG technical support representative.

Module

NWTCPBS2 / NWBS2SUB


NETP373I: UNKNOWN COMMAND RECEIVED
Explanation

The operator command for the subtask has a syntax error.

Action

Correct and retry.

Module

NWBS2SUB


NETP375I: xxxxxxxx ACCEPTED
Explanation

The operator command is accepted and activated.

Action

None.

Module

NWBS2SUB


NETP502W: UNABLE TO ALLOCATE CONNECT QUEUE ENTRY
Explanation

All connect queue entries are in use.

Action

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.


NETP509E: ERROR OCCURRED OBTAINING OR FREEING STORAGE
Explanation

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.

Action

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.

Module

NWTCPCNS


NETP511W: TCP API ERROR ON LISTEN - RC = xxxx
Explanation

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.

Action

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.

Module

NWVSESTK


NETP512W: TCP RETURNED LISTEN ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWVSESTK


NETP521W: TCP API ERROR ON CONNECT - RC = xxxx
Explanation

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

Action

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.

Module

NWTCPCNS


NETP522W: TCP RETURNED CONNECT ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP531W: TCP API ERROR ON SEND - RC = xxxx
Explanation

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

Action

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.

Module

NWTCPCNS


NETP532W: TCP RETURNED SEND ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP541W: TCP API ERROR ON RECEIVE - RC = xxxx
Explanation

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

Action

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.

Module

NWTCPCNS


NETP542W: TCP RETURNED RECEIVE ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP551W: TCP API ERROR ON DISCONNECT - RC = xxxx
Explanation

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

Action

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.

Module

NWTCPCNS


NETP552W: TCP RETURNED DISCONN ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP561W: TCP API ERROR ON OPEN - RC = xxxx
Explanation

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 z/VSE GETVIS call. For more information, refer to the appropriate z/VSE documentation.

Action

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, correct 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.

Module

NWTCPCNS


NETP562W: TCP RETURNED OPEN ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP571W: TCP API ERROR ON CLOSE - RC = xxxx
Explanation

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 z/VSE GETVIS call. For more information, refer to the appropriate z/VSE documentation.

Action

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.

Module

NWTCPCNS


NETP572W: TCP RETURNED CLOSE ERROR - RC = xxxx
Explanation

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

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP581W: TCP API ERROR ON RESOLVE - RC = xxxx
Explanation

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 z/VSE documentation.

Action

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

RC=4 Increase the size of the Entire Net-Work partition or decrease the SIZE= parameter on the EXEC card if possible.
RC=8 Correct 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.
RC=16 Provide additional allocation in the system GETVIS area in the SVA.
Any other value Contact your Software AG technical support representative.
Module

NWTCPCNS


NET0582W: TCP RETURNED RESOLVE ERROR - RC=xxxx
Explanation

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.

Action

Report the error to your Software AG technical support representative.

Module

NWTCPCNS


NETP600I: xxxxxxxx ERROR NUMBER nnnnn SOCKET sssss
Explanation

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.

Action

Locate message NETP601I for a description of the error number.

Module

NWTCPHPS


NETP601I: variable text message
Explanation

This message describes the error number provided in message NETP600I.

Action

Try to eliminate the condition that caused the message.

Module

NWTCPHPS


NETP602E: INVALID FUNCTION REQUESTED
Explanation

An invalid request was made to the API.

Action

Contact your Software AG technical support representative.

Module

NWTCPHPS


NETP603E: TCP/IP FAILED TO LOAD
Explanation

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.

Action

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

Module

NWTCPHPS


NETP604E: UNABLE TO ALLOCATE STORAGE FOR SCT
Explanation

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.

Action

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

Module

NWTCPHPS


NETP605W: UNABLE TO CLOSE SOCKET
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP606I: HPS DRIVER CLOSED
Explanation

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

Action

None required. This message is informational only.

Module

NWTCPHPS


NETP610E: INVALID OPERATING SYSTEM FOR API=HPS
Explanation

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.

Action

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

Module

NWTCPHPS


NETP611E: UNABLE TO INITIALIZE TCP/IP INTERFACE
Explanation

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

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP612E: UNABLE TO GET A SOCKET
Explanation

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

Action

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

Module

NWTCPHPS


NETP613E: UNABLE TO BIND SOCKET TO LOCAL SYSTEM
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP614E: UNABLE TO DETERMINE MAXIMUM SENDMSG SIZE
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP615E: UNABLE TO SET LISTEN OPTIONS
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP616E: UNABLE TO LISTEN FOR NEW CONNECTIONS
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP617W: UNABLE TO ALLOCATE CONNECT QUEUE ENTRY
Explanation

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

Action

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

Module

NWTCPHPS


NETP618W: UNABLE TO SETSOCKOPT KEEPALIVE OPTION
Explanation

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.

Action

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

Module

NWTCPHPS


NETP620W: UNABLE TO CONNECT TO REMOTE SYSTEM
Explanation

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.

Action

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.

Module

NWTCPHPS


NETP621E: UNABLE TO SENDMSG TO REMOTE SYSTEM
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP622E: UNABLE TO RECV DATA FROM REMOTE SYSTEM
Explanation

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.

Action

Locate messages NETP600I and NETP601I for additional information.

Module

NWTCPHPS


NETP623W: UNABLE TO DETERMINE TCP/IP ADDRESS
Explanation

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.

Action

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

Module

NWTCPHPS


NETP624W: UNABLE TO DETERMINE HOST NAME FROM ADDRESS
Explanation

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.

Action

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

Module

NWTCPHPS


NETP630E: ASYNC EXIT ENTERED FOR UNKNOWN ROUTINE
Explanation

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

Action

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.

Module

NWTCPHPS


NETP631I: ASYNC EXIT ENTERED FOR TCP/IP TERMINATION
Explanation

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.

Action

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

Module

NWTCPHPS


NETP632I: ASYNC EXIT ENTERED FOR LINK TERMINATION
Explanation

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

Action

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

Module

NWTCPHPS


NETP633I: ASYNC EXIT ENTERED FOR PREVIOUS ABEND
Explanation

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

Action

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.

Module

NWTCPHPS


NETP634I: ASYNC EXIT ENTERED FOR UNKNOWN REASON
Explanation

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

Action

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.

Module

NWTCPHPS


NETP635I: ASYNC EXIT ENTERED WITH INVALID SCT TOKEN
Explanation

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

Action

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.

Module

NWTCPHPS


NETP700I: xxxxxxxx ERROR NUMBER nnnnn REASON rrrrrrrr SOCKET sssss
xxxxxxxx AIOCB ERRNUM nnnnn REASON rrrrrrrr SOCKET sssss
Explanation

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.

Action

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.

Module

NWTCPOES


NETP701I: variable text message
Explanation

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

Action

Eliminate if possible the condition that caused this message.

Module

NWTCPOES


NETP702E: INVALID FUNCTION REQUESTED
Explanation

An invalid request was made to this API.

Action

Contact your Software AG technical support representative

Module

NWTCPOES


NETP703E: TCP/IP FAILED TO LOAD
Explanation

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.

Action

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

Module

NWTCPOES


NETP704E: UNABLE TO ALLOCATE STORAGE FOR SCT
Explanation

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

Action

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

Module

NWTCPOES


NETP705W: UNABLE TO CLOSE SOCKET
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP706I: OES DRIVER CLOSED
Explanation

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

Action

None

Module

NWTCPOES


NETP707E: OES Driver requires APF authorization
Explanation

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

Action

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

Module

NWTCPOES


NETP710E: INVALID OPERATING SYSTEM FOR API=OES
Explanation

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.

Action

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

Module

NWTCPOES


NETP711E: UNABLE TO INITIALIZE TCP/IP INTERFACE
Explanation

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

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP712E: UNABLE TO GET A SOCKET
Explanation

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

Action

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.

Module

NWTCPOES


NETP713E: UNABLE TO BIND SOCKET TO LOCAL SYSTEM
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP714E: UNABLE TO DETERMINE MAXIMUM SENDMSG SIZE
Explanation

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

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP715E: UNABLE TO SET LISTEN OPTIONS
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP716E: UNABLE TO LISTEN FOR NEW CONNECTIONS
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP717W: UNABLE TO ALLOCATE CONNECT QUEUE ENTRY
Explanation

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

Action

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

Module

NWTCPOES


NETP718W: UNABLE TO SETSOCKOPT KEEPALIVE OPTION
Explanation

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.

Action

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

Module

NWTCPOES


NETP719W: UNABLE TO SETSOCKOPT REUSEADDR OPTION
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information. .

Module

NWTCPOES


NETP720W: UNABLE TO CONNECT TO REMOTE SYSTEM
Explanation

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.

Action

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.

Module

NWTCPOES


NETP721E: UNABLE TO SENDMSG TO REMOTE SYSTEM
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP722E: UNABLE TO RECV DATA FROM REMOTE SYSTEM
Explanation

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.

Action

Locate messages NETP700I and NETP701I for additional information.

Module

NWTCPOES


NETP723W: UNABLE TO DETERMINE TCP/IP ADDRESS
Explanation

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.

Action

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

Module

NWTCPOES


NETP724W: UNABLE TO DETERMINE HOST NAME FROM ADDRESS
Explanation

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.

Action

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

Module

NWTCPOES


NETP730E: ASYNC EXIT ENTERED FOR UNKNOWN ROUTINE
Explanation

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

Action

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

Module

NWTCPOES


NETP731I: ASYNC EXIT ENTERED FOR TCP/IP TERMINATION
Explanation

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.

Action

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

Module

NWTCPOES


NETP732I: ASYNC EXIT ENTERED FOR LINK TERMINATION
Explanation

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

Action

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

Module

NWTCPOES


NETP733I: ASYNC EXIT ENTERED FOR PREVIOUS ABEND
Explanation

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

Action

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

Module

NWTCPOES


NETP734I: ASYNC EXIT ENTERED FOR UNKNOWN REASON
Explanation

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

Action

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

Module

NWTCPOES


NETP735I: ASYNC EXIT ENTERED WITH INVALID SCT TOKEN
Explanation

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

Action

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

Module

NWTCPOES


NETP800I: ACT ARRAY ALLOCATED AT xxxxxxxx
Explanation

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.

Action

None required. This message is informational only.

Module

NETTCPX, NXTSRV


NETP801E: ACT ALLOCATION ERROR; NO FREE ENTRIES
Explanation

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

  • shortage of storage

  • exceeding the total number of clients allowed (32767)

  • internal error

Action

Increase storage or limit the number of clients.

Module

NXTSRV


NETP802E: ERROR FREEING ACT; ARRAY AND ELEMENT MISMATCH
Explanation

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

Action

Contact your Software AG technical support representative.

Module

NETTCPX


NETP803I: MAXIMUM NUMBER OF CLIENTS INCREASED TO xxxxx
Explanation

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.

Action

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

Module

NXTSRV


NETP804I: MSG RECEIVED FROM UNKNOWN CLIENT; CONTEXTID xxxxxxxx, CONTEXTV xxxxxxxx
Explanation

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.

Action

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

Module

NETTCPX


NETP805E: INTERNAL ERROR, UNABLE TO CONVERT MESSAGE
Explanation

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

Action

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

Module

NETTCPX


NETP806E: INVALID NUMUSERS VALUE, SETTING TO DEFAULT OF 100
Explanation

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

Action

Correct the NUMUSERS value.

Module

NETTCPX


NETP808E: CLIENT xxxxx IS NO LONGER ACTIVE; UNABLE TO SEND REPLY
Explanation

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.

Action

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

Module

NETTCPX


NETP809E: UNABLE TO LOAD MODULE: modname, FOR SSL SUPPORT.
Explanation

The attempt failed to load the module named in the message (modname). This module is required for SSL support. The driver fails to open.

Action

Make sure this module is available to the Entire Net-Work job.


NETP811I: COMPLETED SSL INITIALIZATION, DRIVER (drvname).
Explanation

SSL support for the driver named in the message (drvname) has been successfully initialized.

Action

No action is required for this informational message.


NETP813E: DRIVER (drvname) SSL SUPPORT FAILED, RC(code)
Explanation

Initialization of SSL support failed for the driver named in the message (drvname) with the internal return code shown in the message (code). The driver is not opened.

Action

Contact your Software AG customer support representative for assistance.


NETP814E: sslfunction FAILED WITH RC code FOR LINK lnkname
Explanation

The SSL function named in the message (sslfunction) failed with the displayed return code (code) for the link named in the message (lnkname).

Action

Contact your Software AG customer support representative for assistance.


NETP816E: INVALID VALUE FOR SSLVRS
Explanation

An invalid value was specified for the SSLVRS parameter.

Action

Specify a valid value for the parameter and try again.


NETP817E: INVALID VALUE FOR SSLVRF
Explanation

An invalid value was specified for the SSLVRF parameter.

Action

Specify a valid value for the parameter and try again.


NETP818I: LINK link CONNECTED TO ADDRESS nnn.nnn.nnn.nnn
Explanation

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

This message is issued for Entire Net-Work Client links in place of NET0110 (NET0110 is issued when Entire Net-Work 7 connects). It is written only to DDPRINT/NETPRNT, not the console.

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

Action

No action is required for this informational message.


NETP819I: LINK link DISCONN. FROM ADDRESS nnn.nnn.nnn.nnn
Explanation

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 client 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 Entire Net-Work Client links in place of NET0107 (NET0107 is issued when Entire Net-Work 7 disconnects). 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.

Action

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


NETP820E: ERROR POSTING SSL HANDSHAKE SUBTASK RC=(rc) LINK=link
Explanation

An error occurred attempting to notify the SSL subtask to process a new connection. The connection fails for the specified link.

Action

This is an internal error. Contact your Software AG customer support representative.


NETP821E: SSLSETSESSION FAILED WITH RETURN CODE code
Explanation

The SslSetSession function failed with the return code displayed in the message (code).

Action

Check your SSL configuration and try again.


NETP822E: API= OES IS REQUIRED WITH SSL
Explanation

On z/OS systems, only API=OES can be used with the SSL driver.

Action

Specify API=OES and restart.


NETP823E: Connecting two mainframe nodes with TCPX is not allowed
Explanation

The Simple Connection Line Driver (TCPX line driver) is used for connections between mainframe Entire Net-Work nodes and open systems Entire Net-Work Kernels and clients. TCPX mainframe-to-mainframe connections are not allowed.

The link is disconnected.

Action

Use the TCP/IP line driver (TCPI line driver) to make mainframe-to-mainframe connections.


NETP899I: msg-text
Explanation

This message displays various informational messages during SSL initialization.

Action

No action is required for this informational message.