NETP* - Simple Connection Line Driver Messages

#### Search Results

Search

# NETP* - Simple Connection Line Driver Messages

The following are the categories used for operator messages for the Simple Connection Line Driver:

Message Range | Description
--- | ---
NETP000- NETP099 | Non-API-related messages
NETP600 - NETP699 | HPS API-specific messages
NETP700 - NETP799 | OES API-specific messages
NETP800 - NETP899 | Simple Connection Line Driver-specific messages

### Overview of Messages

`NETP040I | NETP041W | NETP042W | NETP043I | NETP044I | NETP046W | NETP047I | NETP048I | NETP060I | NETP061I | NETP062I | NETP063I | NETP065I | NETP066I | NETP067I | 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 | NETP826E | NETP899I`

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

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.

NETP826E | API=OES is required if ZIIP=YES
Explanation | API=OES must be used if ZIIP=YES. This is because the calls used in the HPS routine require TCB mode, which would result in a very large number of mode switches.
Action | If ZIIP=YES, use API=OES

NETP899I | message text
Explanation | This message displays various informational messages during SSL initialization.
Action | No action is required for this informational message.