gtpm5m2lMessages (Online)

TTCP-TWRT

TTCP0001ILOCAL IP ADDRESS ipaddr DEFINED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP DEFINE command with the IP parameter specified.

System Action: The specified local IP address is defined.

User Response: None.

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0002IIP ROUTER SDA-sda IP-ipaddr DEFINED

Where:

sda
The symbolic device address (SDA).

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP DEFINE command with the SDA parameter specified.

System Action: The specified IP router is defined.

User Response: None.

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0003ILOCAL IP ADDRESS ipaddr CHANGED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP CHANGE command with the IP parameter specified.

System Action: The properties of the specified IP address are changed.

User Response: None.

See TPF Operations for more information about the ZTTCP CHANGE command.

TTCP0004IIP ROUTER SDA-sda NOW USING IP-ipnew

Where:

sda
The symbolic device address (SDA).

ipnew
The new local Internet Protocol (IP) address associated with the IP router.

Explanation: This is the normal response to the ZTTCP CHANGE command with the SDA parameter specified.

System Action: The local IP address associated with the specified IP router is changed to use the specified local IP address.

User Response: None.

See TPF Operations for more information about the ZTTCP CHANGE command.

TTCP0005ILOCAL IP ADDRESS ipaddr IS NOW THE DEFAULT

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP CHANGE command with the DEFIP parameter specified.

System Action: The default local IP address is changed.

User Response: None.

See TPF Operations for more information about the ZTTCP CHANGE command.

TTCP0006ILOCAL IP ADDRESS ipaddr DELETED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP DELETE command with the IP parameter specified.

System Action: The specified local IP address definition is deleted.

User Response: None.

See TPF Operations for more information about the ZTTCP DELETE command.

TTCP0007IIP ROUTER SDA-sda DELETED

Where:

sda
The symbolic device address (SDA).

Explanation: This is the normal response to the ZTTCP DELETE command with the SDA parameter specified.

System Action: The specified Internet Protocol (IP) router is deleted.

User Response: None.

See TPF Operations for more information about the ZTTCP DELETE command.

TTCP0010IIP ROUTER SDA-sda ACTIVATION STARTED

Where:

sda
The symbolic device address (SDA).

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the SDA parameter specified.

System Action: Processing to activate the specified Internet Protocol (IP) router continues.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0011IACTIVATION OF IP ADDRESS ipaddr STARTED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the IP parameter specified.

System Action: Processing to activate the IP routers associated with the specified IP address continues.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0013IIP ROUTER SDA-sda DEACTIVATION COMPLETED

Where:

sda
The symbolic device address (SDA).

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the SDA parameter specified.

System Action: The specified Internet Protocol (IP) router is deactivated.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0014IINACTIVATION OF IP ADDRESS ipaddr STARTED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the IP parameter specified.

System Action: Processing to deactivate the IP routers associated with the specified IP address continues.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0016IACTIVATION OF IP ADDRESS ipaddr COMPLETED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the IP parameter specified.

System Action: The IP routers associated with the specified IP address are activated.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0018IINACTIVATION OF IP ADDRESS ipaddr COMPLETED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the IP parameter specified.

System Action: The IP routers associated with the specified IP address are deactivated.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0021ILOCAL IP ADDRESS DISPLAY

Explanation: This is the normal response to the ZTTCP DISPLAY command with the LOCIPS parameter specified, or the IP parameter with an OSA Internet Protocol (IP) address specified.

System Action: Information about the local IP addresses that are defined to the TPF system is displayed.

User Response: None.

See TPF Operations for more information about the ZTTCP DISPLAY command.

TTCP0023IIP CONNECTIONS DISPLAY

Explanation: This is the normal response to the ZTTCP DISPLAY command with the SDA parameter specified, or with the IP parameter specified with a value that is a channel data link control (CDLC) address.

System Action: Information about Internet Protocol (IP) routers and OSA-Express connections is displayed.

User Response: None.

See TPF Operations for more information about the ZTTCP DISPLAY command.

TTCP0030IIP TRACE FOR LOCAL IP ADDRESS ipaddr STARTED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP TRACE command with the START and IP parameters specified.

System Action: Tracing for all IP routers associated with the specified channel data link control (CDLC) IP address begins or else tracing of the Open Systems Adapter (OSA) IP address begins.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0031IIP TRACE FOR IP ROUTER SDA-sda STARTED

Where:

sda
The symbolic device address (SDA).

Explanation: This is the normal response to the ZTTCP TRACE command with the START and SDA parameters specified.

System Action: Tracing for the specified Internet Protocol (IP) router begins.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0032IIP TRACE STARTED FOR ALL RESOURCES

Explanation: This is the normal response to the ZTTCP TRACE command with the START and ALL parameters specified.

System Action: Tracing for all Internet Protocol (IP) routers and OSA-Express connections in the TPF system begins.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0033IIP TRACE TO TAPE STARTED

Explanation: This is the normal response to the ZTTCP TRACE command with the START and TAPE parameters specified.

System Action: The TPF system begins writing the Internet Protocol (IP) trace data to tape.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0034ITRACING OF ROUTING INFORMATION PROTOCOL MESSAGES HAS STARTED

Explanation: This is the normal response to the ZTTCP TRACE command with the RIP parameter specified.

System Action: Routing Information Protocol (RIP) messages will be included in the Internet Protocol (IP) trace.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0035ITRACING OF ROUTING INFORMATION PROTOCOL MESSAGES HAS STOPPED

Explanation: This is the normal response to the ZTTCP TRACE command with the NORIP parameter specified.

System Action: Routing Information Protocol (RIP) messages will not be included in the Internet Protocol (IP) trace.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0040IIP TRACE FOR LOCAL IP ADDRESS ipaddr STOPPED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: This is the normal response to the ZTTCP TRACE command with the STOP and IP parameters specified.

System Action: Tracing for all IP routers associated with the specified channel data link control (CDLC) IP address stops or else tracing of the Open Systems Adapter (OSA) IP address stops.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0041IIP TRACE FOR IP ROUTER SDA-sda STOPPED

Where:

sda
The symbolic device address (SDA).

Explanation: This is the normal response to the ZTTCP TRACE command with the STOP and SDA parameters specified.

System Action: Tracing for the specified Internet Protocol (IP) router stops.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0042IIP TRACE STOPPED FOR ALL RESOURCES

Explanation: This is the normal response to the ZTTCP TRACE command with the STOP and ALL parameters specified.

System Action: Tracing for all Internet Protocol (IP) routers and OSA-Express connections in the TPF system stops.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0043IIP TRACE TO TAPE STOPPED

Explanation: This is the normal response to the ZTTCP TRACE command with the STOP and TAPE parameters specified.

System Action: The TPF system stops writing the Internet Protocol (IP) trace data to tape.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0045INOW TRACING size BYTES OF EACH MESSAGE

Where:

size
The number of bytes of each message to trace.

Explanation: This is the normal response to the ZTTCP TRACE command with the SIZE parameter specified.

System Action: The specified number of bytes of each message is traced.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0047IINACTIVATION OF ALL SOCKETS COMPLETED

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the SOCKETS parameter specified.

System Action: All active sockets are deactivated.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0060IOSA-osaname ACTIVATED

Where:

osaname
The name of the OSA-Express connection.

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the OSA parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0061IOSA-osaname HAS BEEN DEACTIVATED

Where:

osaname
The name of the OSA-Express connection.

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the OSA parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0062IOSA-osaname ACTIVATION STARTED

Where:

osaname
The name of the OSA-Express connection.

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the OSA parameter specified.

System Action: Processing to activate the specified OSA-Express connection continues. Activating the connection takes 16 seconds or more to be completed.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0065IIP TRACE FOR OSA-osaname STARTED

Where:

osaname
The name of the OSA-Express connection.

Explanation: This is the normal response to the ZTTCP TRACE command with the START and OSA parameters specified.

System Action: Tracing for the specified OSA-Express connection begins.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0066IIP TRACE FOR OSA-osaname STOPPED

Where:

osaname
The name of the OSA-Express connection.

Explanation: This is the normal response to the ZTTCP TRACE command with the STOP and OSA parameters specified.

System Action: Tracing for the specified OSA-Express connection stops.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0090Wnum SOCKETS CLEANED UP BECAUSE OF EXTENDED NETWORK OUTAGES

Where:

num
The number of sockets cleaned up.

Explanation: The specified number of sockets were cleaned up by the socket sweeper because the network associated with those sockets was down for an extended period of time.

System Action: The sockets are cleaned up.

User Response: Examine the network to determine the cause of the extended outages.

See TPF Transmission Control Protocol/Internet Protocol for more information about the socket sweeper.

TTCP0091Wnum SOCKETS CLOSED BECAUSE OF NO APPLICATION ACTIVITY

Where:

num
The number of sockets that were closed.

Explanation: The specified number of sockets were closed by the socket sweeper because no application issued any socket calls for these sockets for an extended period of time.

System Action: The sockets are closed.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about the socket sweeper.

TTCP0100EFORMAT OF THE ZTTCP COMMAND IS NOT VALID

Explanation: A ZTTCP command was entered, but the combination of parameters specified was not valid.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format for the ZTTCP command.
  2. Enter the ZTTCP command again, specifying a valid combination of parameters.

See TPF Operations for more information about the ZTTCP commands.

TTCP0101EREJECTED, RESTRICT PARAMETER VALUE MUST BE YES OR NO

Explanation: The ZTTCP CHANGE or ZTTCP DEFINE command was entered with a value for the RESTRICT parameter that is not valid.

System Action: The command is rejected.

User Response: Enter the ZTTCP CHANGE or ZTTCP DEFINE command again and specify either YES or NO for the RESTRICT parameter.

See TPF Operations for more information about the ZTTCP commands.

TTCP0102EREJECTED, MPS PARAMETER VALUE IS NOT VALID

Explanation: The ZTTCP CHANGE or ZTTCP DEFINE command was entered with a value for the MPS parameter that is not valid.

System Action: The command is rejected.

User Response: Enter the ZTTCP CHANGE or ZTTCP DEFINE command again and specify a valid value for the MPS parameter.

See TPF Operations for more information about the ZTTCP commands.

TTCP0103EREJECTED, SYSTEM IS IN RESTART

Explanation: A ZTTCP command was entered, but the TPF system is in restart.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the TPF system to reach 1052 state.
  2. Enter the ZTTCP command again.

See TPF Operations for more information about the ZTTCP commands.

TTCP0104EREJECTED, TCP/IP NATIVE STACK SUPPORT NOT DEFINED

Explanation: A ZTTCP command was entered, but TCP/IP native stack support is not defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Code the TCP/IP native stack support parameters in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. Perform an initial program load (IPL) of the TPF system.
  5. Enter the ZTTCP command again.

See TPF Operations for more information about the ZTTCP commands. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for TCP/IP native stack support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

TTCP0105EREJECTED, IP ADDRESS SPECIFIED IS NOT VALID

Explanation: The ZTTCP DEFINE command was entered with the IP parameter specified, but the specified Internet Protocol (IP) address is one of the following reserved IP addresses:

System Action: The command is rejected.

User Response: Enter the ZTTCP DEFINE command again and specify a valid value for the IP parameter.

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0106EREJECTED, SDA PARAMETER VALUE IS NOT VALID

Explanation: The ZTTCP DEFINE command was entered with a value for the SDA parameter that is not valid.

System Action: The command is rejected.

User Response: Enter the ZTTCP DEFINE command again and specify a valid value for the SDA parameter.

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0110EREJECTED, LOCAL IP ADDRESS ipaddr ALREADY DEFINED

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: The ZTTCP DEFINE command was entered with the IP parameter specified, but the specified local IP address is already defined.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0111EREJECTED, MAXIMUM NUMBER OF LOCAL IP ADDRESSES ALREADY DEFINED

Explanation: The ZTTCP DEFINE command was entered with the IP parameter specified, but the maximum number of local Internet Protocol (IP) addresses that can be defined are already defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTTCP DISPLAY command and examine the local IP addresses that are defined.
  2. Enter the ZTTCP DELETE command to delete any local IP addresses that are not needed.
  3. Enter the ZTTCP DEFINE command again.

See TPF Operations for more information about the ZTTCP commands.

TTCP0112EREJECTED, IP ROUTER SDA-sda ALREADY DEFINED

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP DEFINE command was entered with the SDA parameter specified, but the specified Internet Protocol (IP) router is already defined.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0113EREJECTED, MAXIMUM NUMBER OF IP ROUTERS ALREADY DEFINED

Explanation: The ZTTCP DEFINE command was entered with the SDA parameter specified, but the maximum number of Internet Protocol (IP) routers that can be defined are already defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTTCP DISPLAY command and examine the IP routers that are defined.
  2. Enter the ZTTCP DELETE command to delete any IP routers that are not needed.
  3. Enter the ZTTCP DEFINE command again.

See TPF Operations for more information about the ZTTCP commands.

TTCP0114EREJECTED, LOCAL IP ADDRESS ipaddr DOES NOT EXIST

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: A ZTTCP command was entered with the IP parameter specified, but the specified local IP address is not defined.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP commands.

TTCP0115EREJECTED, IP ROUTER SDA-sda DOES NOT EXIST

Where:

sda
The symbolic device address (SDA).

Explanation: A ZTTCP command was entered with the SDA parameter specified, but the specified Internet Protocol (IP) router is not defined.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP commands.

TTCP0116EREJECTED, IP ROUTER SDA-sda IS ACTIVE

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP CHANGE or ZTTCP DELETE command was entered, but the specified Internet Protocol (IP) router is active.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTTCP INACTIVATE command to deactivate the IP router.
  2. Enter the ZTTCP CHANGE or ZTTCP DELETE command again.

See TPF Operations for more information about the ZTTCP commands.

TTCP0117EREJECTED, LOCAL IP ADDRESS ipaddr IS IN USE

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: The ZTTCP DELETE command was entered with the IP parameter specified, but the specified local IP address is in use.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTTCP INACTIVATE command with the IP parameter specified to deactivate all IP routers that are using the local IP address that you want to delete.
  2. Enter the ZTTCP DELETE or ZTTCP CHANGE command to ensure there are no IP routers assigned to the local IP address that you want to delete.
  3. Enter the ZTTCP DELETE command with the IP parameter specified again.

See TPF Operations for more information about the ZTTCP commands.

TTCP0118EREJECTED, THE DEFAULT LOCAL IP ADDRESS CANNOT BE DELETED

Explanation: The ZTTCP DELETE command was entered with the IP parameter specified, but the specified local Internet Protocol (IP) address is defined as the default local IP address. The default local IP address cannot be deleted when more than one local IP address exists.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTTCP CHANGE command with the DEFIP parameter specified to change the default local IP address.
  2. Enter the ZTTCP DELETE command again and specify the IP parameter.

See TPF Operations for more information about the ZTTCP commands.

TTCP0120EREJECTED, IP ROUTER SDA-sda IS ALREADY ACTIVE

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP ACTIVATE command was entered, but the specified Internet Protocol (IP) router is already active.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0121EREJECTED, IP ROUTER SDA-sda CANNOT BE MOUNTED

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP ACTIVATE command was entered, but the device cannot be mounted.

System Action: The command is rejected.

User Response: Verify that the specified SDA is correct and that the Internet Protocol (IP) router is channel-attached to the TPF system.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0122EREJECTED, IP ROUTER SDA-sda IS NOT ACTIVE

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP INACTIVATE command was entered, but the specified Internet Protocol (IP) router is not active.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0125EREJECTED, IP TRACE ALREADY ACTIVE FOR LOCAL IP ADDRESS ipaddr

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: The ZTTCP TRACE command was entered with the START and IP parameters specified, but IP trace is already active for the specified local IP address.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0126EREJECTED, IP TRACE ALREADY ACTIVE IP ROUTER SDA-sda

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP TRACE command was entered with the START and SDA parameters specified, but IP trace is already active for the specified Internet Protocol (IP) router.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0127EREJECTED, IP TRACE TO TAPE ALREADY ACTIVE

Explanation: The ZTTCP TRACE command was entered with the START and TAPE parameters specified, but writing the Internet Protocol (IP) trace data to tape is already started.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0128EREJECTED, IP TRACE NOT ACTIVE FOR LOCAL IP ADDRESS ipaddr

Where:

ipaddr
The local Internet Protocol (IP) address.

Explanation: The ZTTCP TRACE command was entered with the STOP and IP parameters specified, but IP trace is not active for the specified local IP address.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0129EREJECTED, IP TRACE NOT ACTIVE FOR IP ROUTER SDA-sda

Where:

sda
The symbolic device address (SDA).

Explanation: The ZTTCP TRACE command was entered with the STOP and SDA parameters specified, but Internet Protocol (IP) trace is not active for the specified IP router.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0130EREJECTED, IP TRACE TO TAPE NOT ACTIVE

Explanation: The ZTTCP TRACE command was entered with the STOP and TAPE parameters specified, but writing the Internet Protocol (IP) trace data to tape is not active.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0131EREJECTED, VALUE OF THE SIZE PARAMETER IS NOT VALID

Explanation: The ZTTCP TRACE command was entered with the SIZE parameter specified, but the value specified is not valid.

System Action: The command is rejected.

User Response: Enter the ZTTCP TRACE command again and specify a valid value for the SIZE parameter.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0150EREJECTED, IP ROUTING TABLE ENTRIES EXIST FOR IP ADDRESS

Explanation: The ZTTCP DELETE command was entered with the IP parameter specified, but the local Internet Protocol (IP) address specified by the IP parameter cannot be deleted because it is used in one or more IP routing table entries.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZTRTE command specifying the DELETE parameter and the local IP address. This deletes all IP routing table entries using the local IP address.
  2. Enter the ZTTCP DELETE command again, specifying the IP parameter.

See TPF Operations for more information about the ZTRTE and ZTTCP DELETE commands.

TTCP0151EREJECTED, OSA-osaname DOES NOT EXIST

Where:

osaname
The name of the OSA-Express connection.

Explanation: A ZTTCP ACTIVATE, ZTTCP INACTIVATE, or ZTTCP TRACE command was entered with the OSA parameter specified; however, the specified OSA-Express connection is not defined.

System Action: The command is rejected.

User Response: Enter the appropriate command again, specifying an OSA-Express connection that is defined.

See TPF Operations for more information about the ZTTCP commands.

TTCP0152EREJECTED, OSA-osaname IS ALREADY ACTIVE

Where:

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP ACTIVATE command was entered with the OSA parameter specified; however, the OSA-Express connection is already active.

System Action: The command is rejected.

User Response: Enter the ZTTCP ACTIVATE command again with the correct OSA-Express connection specified.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0153EREJECTED, SDA-sda FOR OSA-osaname CANNOT BE MOUNTED

Where:

sda
The symbolic device address (SDA).

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP ACTIVATE command was entered with the OSA parameter specified; however, the specified SDA cannot be mounted.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that the specified SDA is attached to the TPF system.
  2. Enter the ZTTCP ACTIVATE command again.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0154EREJECTED, OSA-osaname IS NOT ACTIVE

Where:

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP INACTIVATE command was entered; however, the specified OSA-Express connection is not active.

System Action: The command is rejected.

User Response: Enter the ZTTCP INACTIVATE command again with the correct OSA-Express connection specified.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0155EREJECTED, IP TRACE ALREADY ACTIVE FOR OSA-osaname

Where:

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP TRACE command was entered with the START and OSA parameters specified; however, the Internet Protocol (IP) trace is already active for the specified OSA-Express connection.

System Action: The command is rejected.

User Response: Enter the ZTTCP TRACE command again with the correct OSA-Express connection specified.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0156EREJECTED, IP TRACE NOT ACTIVE FOR OSA-osaname

Where:

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP TRACE command was entered with the STOP and OSA parameters specified; however, the Internet Protocol (IP) trace is not active for the specified OSA-Express connection.

System Action: The command is rejected.

User Response: Enter the ZTTCP TRACE command again with the correct OSA-Express connection specified.

See TPF Operations for more information about the ZTTCP TRACE command.

TTCP0157EREJECTED, IP-ipaddr IS ALREADY DEFINED TO OSA

Where:

ipaddr
The Internet Protocol (IP) address.

Explanation: The ZTTCP DEFINE command was entered with the IP parameter specified; however, the specified Internet Protocol (IP) address is already defined to an OSA-Express connection.

System Action: The command is rejected.

User Response: Enter the ZTTCP DEFINE command again, specifying an IP address that is not already defined.

See TPF Operations for more information about the ZTTCP DEFINE command.

TTCP0158EOSA-osaname ACTIVATION FAILED, ALL OSA CONTROL BLOCKS IN USE

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed to activate because all the OSA-Express control blocks are in use.

System Action: The OSA-Express connection is not activated.

User Response: Do the following:

  1. Increase the number of OSA-Express control blocks defined to the TPF system by using the MAXOSA parameter on the SNAKEY macro in keypoint 2 (CTK2).
  2. Enter the ZTTCP ACTIVATE command.

See TPF Operations for more information about the ZTTCP ACTIVATE command. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro and the MAXOSA parameter. See TPF Transmission Control Protocol/Internet Protocol for more information about the MAXOSA parameter.

TTCP0162EOSA-osaname DEFINITION NOT COMPLETE, CANNOT ACTIVATE

Where:

osaname
The name of the OSA-Express connection.

Explanation: The ZTTCP ACTIVATE command was entered; however, the definition for the specified OSA-Express connection is not completed.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZOSAE command again with the MODIFY parameter specified to define all the required parameters for an OSA-Express connection definition.
  2. Enter the ZTTCP ACTIVATE command again.

See TPF Operations for more information about the ZTTCP ACTIVATE and ZOSAE commands.

TTCP0163EREJECTED, OSA SUPPORT IS NOT DEFINED

Explanation: A ZTTCP ACTIVATE, ZTTCP INACTIVATE, or ZTTCP TRACE command was entered with the OSA parameter specified; however, OSA-Express support is not defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Code the OSA-Express support parameters in the SNAKEY macro.
  2. Reassemble keypoint 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system.
  5. Enter the appropriate command again.

See TPF Operations for more information about the ZTTCP commands. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for OSA-Express support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

TTCP0182IBEGIN ZTTCP STATS DISPLAY

Explanation: This is the normal response to the ZTTCP DISPLAY command with the STATS parameter specified.

System Action: Information about the resources used by TCP/IP native stack support is displayed.

User Response: None.

See TPF Operations for more information about the ZTTCP DISPLAY command.

TTCP0183ICOMPLETED, TCP/IP STATS CLEARED

Explanation: This is the normal response to the ZTTCP CLEAR command with the STATS parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTTCP CLEAR command.

TTCP0184IIP CONNECTIONS DISPLAY

Explanation: This is the normal response to the ZTTCP DISPLAY command with the ALL parameter specified.

System Action: Information about Internet Protocol (IP) routers and OSA-Express connections is displayed.

User Response: None.

See TPF Operations for more information about the ZTTCP DISPLAY command.

TTCP0185IACTIVATION OF ALL IP CONNECTIONS STARTED

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the ALL parameter specified.

System Action: Processing to activate all Internet Protocol (IP) connections in the TPF system continues.

User Response: None.

See TPF Operations for more information about the ZTTCP ACTIVATE command.

TTCP0186IINACTIVATION OF ALL IP CONNECTIONS STARTED

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the ALL parameter specified.

System Action: Processing to deactivate all Internet Protocol (IP) connections in the TPF system continues.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0187IACTIVATION OF ALL IP CONNECTIONS COMPLETED

Explanation: This is the normal response to the ZTTCP ACTIVATE command with the ALL parameter specified.

System Action: None.

User Response: Enter ZTTCP DISPLAY ALL to determine which IP connections or OSA-Express connections were actually activated.

See TPF Operations for more information about the ZTTCP commands.

TTCP0188IINACTIVATION OF ALL IP CONNECTIONS COMPLETED

Explanation: This is the normal response to the ZTTCP INACTIVATE command with the ALL parameter specified.

System Action: All Internet Protocol (IP) connections in the TPF system are deactivated.

User Response: None.

See TPF Operations for more information about the ZTTCP INACTIVATE command.

TTCP0201EIP ROUTER SDA-sda FAILED, SDA CANNOT BE MOUNTED

Where:

sda
The symbolic device address (SDA).

Explanation: An Internet Protocol (IP) router failed because the device cannot be mounted during TPF system restart.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0202EIP ROUTER SDA-sda FAILED, ALL IP CCW AREAS IN USE

Where:

sda
The symbolic device address (SDA).

Explanation: An Internet Protocol (IP) router failed because the TPF system is unable to allocate an IP channel command word (CCW) area entry. All IP CCW area entries are in use.

System Action: The IP router is cleaned up.

User Response: Do the following:

  1. Increase the value of the MAXIPCCW parameter in the SNAKEY macro to define more IP CCW area entries.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. Perform an initial program load (IPL) of the TPF system again.

See TPF Transmission Control Protocol/Internet Protocol for more information about IP CCW area entries. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

TTCP0203IIP ROUTER SDA-sda ACTIVATED

Where:

sda
The symbolic device address (SDA).

Explanation: An Internet Protocol (IP) router is activated.

System Action: None.

User Response: None.

TTCP0204EIP ROUTER SDA-sda ACTIVATION FAILED, CONTACT FAILURE

Where:

sda
The symbolic device address (SDA).

Explanation: Activation of an Internet Protocol (IP) router failed because the CONTACT channel command was rejected during exchange identification (XID) processing

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0205EIP ROUTER SDA-sda ACTIVATION FAILED, CV22 RECEIVED

Where:

sda
The symbolic device address (SDA).

Explanation: Activation of an Internet Protocol (IP) router failed. During the activation process, an exchange identification (XID) with control vector (CV) X'22' was received, indicating an error.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0206EIP ROUTER SDA-sda ACTIVATION FAILED ON PRE-NEG XID

Where:

sda
The symbolic device address (SDA).

Explanation: Activation of an Internet Protocol (IP) router failed during the prenegotiation exchange identification (XID) phase.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0207EIP ROUTER SDA-sda ACTIVATION FAILED ON NEG-PROC XID

Where:

sda
The symbolic device address (SDA).

Explanation: Activation of an Internet Protocol (IP) router failed during the negotiation proceeding exchange identification (XID) phase.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0208WLOST INTERRUPT ON IP ROUTER SDA-sda, OPERATION-op

Where:

sda
The symbolic device address (SDA).

op
The input/output (I/O) operation that was in progress.

Explanation: An I/O operation was started for an Internet Protocol (IP) router, but the operation was not completed successfully because an interrupt was not received.

System Action: The TPF system tries the operation again.

User Response: None.

TTCP0209EIP ROUTER SDA-sda FAILED, PERMANENT LOST INTERRUPT ON OPERATION-op

Where:

sda
The symbolic device address (SDA).

op
The input/output (I/O) operation that was in progress.

Explanation: An I/O operation was started twice in a row for an Internet Protocol (IP) router, but the operation was not completed successfully because an interrupt was not received.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0210EIP ROUTER SDA-sda DEACTIVATED DUE TO SLOWDOWN TIME OUT

Where:

sda
The symbolic device address (SDA).

Explanation: An Internet Protocol (IP) router was in slowdown mode for an extended period of time.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0211IIP ROUTER SDA-sda HAS BEEN DEACTIVATED

Where:

sda
The symbolic device address (SDA).

Explanation: An Internet Protocol (IP) router was deactivated normally.

System Action: None.

User Response: None.

TTCP0212EIP ROUTER SDA-sda, CHANNEL ERROR RETRY IN PROGRESS OPERATION-op CSW-status

Where:

sda
The symbolic device address (SDA).

op
The input/output (I/O) operation that was in progress.

status
The channel status word (CSW) associated with the I/O operation.

Explanation: A channel error was detected during an I/O operation for an Internet Protocol (IP) router.

System Action: The TPF system tries the I/O operation for the IP router again.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0213EIP ROUTER SDA-sda FAILED, ROUTER FOUND INOPERATIVE OPERATION-op CSW-status

Where:

sda
The symbolic device address (SDA).

op
The input/output (I/O) operation that was in progress.

status
The channel status word (CSW) associated with the I/O operation.

Explanation: The TPF system attempted to start an I/O operation for an Internet Protocol (IP) router, but the device was not operating.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0214EIP ROUTER SDA-sda FAILED, UNRECOVERABLE ERROR OPERATION-op CSW-status

Where:

sda
The symbolic device address (SDA).

op
The input/output (I/O) operation that was in progress.

status
The channel status word (CSW) associated with the I/O operation.

Explanation: An irrecoverable error was detected during an I/O operation for an Internet Protocol (IP) router.

System Action: The IP router is cleaned up.

User Response: See your network administrator to determine the error and correct the problem.

TTCP0215EIP ROUTER SDA-sda XID3 FAILED, SENSE sense

Where:

sda
The symbolic device address (SDA).

sense
The sense data associated with the input/output (I/O) operation that was in progress.

Explanation: An irrecoverable error was detected during an I/O operation that was part of exchange identification (XID) processing between the TPF system and an Internet Protocol (IP) router.

System Action: The XID fails and the IP router is cleaned up.

User Response: Do the following:

  1. Review the sense data information to determine the cause of the XID failure.
  2. Correct the problem.

TTCP0216EIP ROUTER SDA-sda INVALID XID FORMAT RECEIVED

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) information field (I-field) was received by the TPF system that was not format 3.

System Action: The XID fails and the Internet Protocol (IP) router is cleaned up.

User Response: Do the following:

  1. Determine why the IP router is not using format 3 XID I-fields.
  2. Correct the problem.

TTCP0217EIP ROUTER SDA-sda NOT DEFINED

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) was started by an Internet Protocol (IP) router with an SDA that is not in the IP configuration record for the TPF system.

System Action: The XID fails and the IP router is cleaned up.

User Response: Enter ZTTCP DISPLAY ALL to show all valid SDAs defined for the TPF system and do one of the following:

See TPF Operations for more information about the ZTTCP commands.

TTCP0218EIP ROUTER SDA-sda NOT AVAILABLE

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) was started by an Internet Protocol (IP) router with an SDA that was deactivated with the ZTTCP INACTIVATE command while link activation was in progress.

System Action: The XID fails and the IP router is cleaned up.

User Response: Do one of the following:

See TPF Operations for more information about the ZTTCP commands.

TTCP0219EIP ROUTER SDA-sda XID3 FAILED, NO CV57 RECEIVED

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) information field (I-field) was received that did not include control vector (CV) X'57', which is the data link control (DLC) connection data CV.

System Action: The XID fails and the Internet Protocol (IP) router is cleaned up.

User Response: Do the following:

  1. Determine why the IP router did not provide CV57 in the XID I-field.
  2. Correct the problem.

TTCP0220EIP ROUTER SDA-sda XID3 FAILED, INVALID STATE

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) information field (I-field) was received that included an incorrect XID state setting.

System Action: The XID fails and the Internet Protocol (IP) router is cleaned up.

User Response: Do the following:

  1. Deactivate the link from the IP router.
  2. Activate the link again.

TTCP0221EIP ROUTER SDA-sda XID3 FAILED, READ BUFFER MISMATCH

Where:

sda
The symbolic device address (SDA).

Explanation: An exchange identification (XID) information field (I-field) was received that included a read buffer count that did not match the IPRBUFFS parameter setting in the SNAKEY macro. The IPRBUFFS parameter defines the number of read buffers per channel program.

System Action: The XID fails and the Internet Protocol (IP) router is cleaned up.

User Response: Do the following:

  1. Examine the IP router definitions to determine why this value was incorrect.
  2. Correct the problem.

TTCP0222EIP ROUTER SDA-sda XID3 FAILED, ALL READ BUFFERS IN USE

Where:

sda
The symbolic device address (SDA).

Explanation: During exchange identification (XID) processing, the TPF system attempted to allocate channel data link control (CDLC) read buffers for an Internet Protocol (IP) channel command word (CCW) area, but there were no read buffers available.

System Action: The XID fails and the IP router is cleaned up.

User Response: Do the following:

  1. Determine why all read buffers are in use.
  2. Correct the problem.

See TPF Transmission Control Protocol/Internet Protocol for more information about the read, recv, and activate_on_receipt functions.

TTCP0301EOSA-osaname FAILED, CHANNEL STATUS xxyy ON SDA-sda RECEIVED

Where:

osaname
The name of the OSA-Express connection.

xx
The device status.

yy
The subchannel status.

sda
The symbolic device address (SDA).

Explanation: An OSA-Express connection failed because error status was received on the channel.

System Action: A 007859 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0302EOSA-osaname FAILED, INCORRECT CONTROL DATA RECEIVED

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because incorrect control data was received from the OSA-Express card.

System Action: A 007858 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0303EOSA-osaname FAILED, OSA REJECTED CONTROL COMMAND

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the OSA-Express card rejected a control command sent by the TPF system.

System Action: A 007857 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0304EOSA-osaname FAILED, LOST INTERRUPT ON SDA-sda

Where:

osaname
The name of the OSA-Express connection.

sda
The symbolic device address (SDA).

Explanation: An OSA-Express connection failed because no response was received to a control command sent to the OSA-Express card, resulting in a lost interrupt condition.

System Action: A 007856 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0305EOSA-osaname FAILED, CC condcode ON SIOSC FOR SDA-sda

Where:

osaname
The name of the OSA-Express connection.

condcode
The condition code from the SIOSC macro.

sda
The symbolic device address (SDA).

Explanation: An OSA-Express connection failed because an error return code was received from the SIOSC macro.

System Action: A 00785A system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0306EOSA-osaname FAILED, ERROR WRITING IP PACKETS TO OSA

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because an error occurred while writing Internet Protocol (IP) packets to the OSA-Express card.

System Action: A 007854 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0307EOSA-osaname FAILED, ERROR READING IP PACKETS FROM OSA

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because an error occurred while reading Internet Protocol (IP) packets from the OSA-Express card.

System Action: A 007855 system error dump is issued and the OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Examine the system error dump to determine the cause of the error.
  2. Correct the error.

TTCP0308EOSA-osaname ACTIVATION FAILED, OSA NAME ALREADY IN USE

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the OSA-Express connection name is already in use by another host connnected to the OSA-Express card.

System Action: The OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Enter the ZOSAE command with the DEFINE and OSA parameters specified to define a different OSA-Express connection.
  2. Enter the ZTTCP ACTIVATE command to activate the OSA-Express connection.

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0309EOSA-osaname ACTIVATION FAILED, INCORRECT PORT NAME

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the port name is not correct.

System Action: The OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Enter the ZOSAE command with the MODIFY and PORT parameters specified to define a different port name.
  2. Enter the ZTTCP ACTIVATE command to activate the OSA-Express connection.

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0310EOSA-osaname ACTIVATION FAILED, DATA SDA-sda IS NOT VALID

Where:

osaname
The name of the OSA-Express connection.

sda
The symbolic device address (SDA).

Explanation: An OSA-Express connection failed because the data SDA is not valid.

System Action: The OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Enter the ZOSAE command with the MODIFY and DATA parameters specified to define a valid data SDA to this OSA-Express card.
  2. Enter the ZTTCP ACTIVATE command to activate the OSA-Express connection.

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0312EOSA-osaname ACTIVATION FAILED, OSA CANNOT CONNECT TO THE NETWORK

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the OSA-Express card was unable to connect to the network.

System Action: The OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Correct the connection between the OSA-Express card and the network.
  2. Enter the ZTTCP ACTIVATE command to activate the OSA-Express connection.

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0313EOSA-osaname FAILED, OSA DETECTED NETWORK OUTAGE

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the connection between the OSA-Express card and the network failed.

System Action: The OSA-Express connection is cleaned up.

User Response: Do the following:

  1. Correct the connection between the OSA-Express card and the network.
  2. Enter the ZTTCP ACTIVATE command to activate the OSA-Express connection.

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0314EOSA-osaname FAILED, IP-ipaddr IS IN USE BY ANOTHER HOST

Where:

osaname
The name of the OSA-Express connection.

ipaddr
The Internet Protocol (IP) address.

Explanation: An OSA-Express connection failed because one of the IP addresses defined to this connection is already in use by another host connected to the OSA-Express card.

System Action: The OSA-Express connection is cleaned up.

User Response: Do one of the following:

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0315EOSA-osaname FAILED, IP-ipaddr EXISTS ELSEWHERE IN THE NETWORK

Where:

osaname
The name of the OSA-Express connection.

ipaddr
The Internet Protocol (IP) address.

Explanation: An OSA-Express connection failed because the real IP address of this connection is already in use elsewhere in the network.

System Action: The OSA-Express connection is cleaned up.

User Response: Do one of the following:

See TPF Operations for more information about the ZOSAE and ZTTCP ACTIVATE commands.

TTCP0316EOSA-osaname FAILED, IP TABLE IS FULL IN THE OSA CARD

Where:

osaname
The name of the OSA-Express connection.

Explanation: An OSA-Express connection failed because the IP address table in the OSA-Express card is full.

System Action: The OSA-Express connection is cleaned up.

User Response: Do one of the following to decrease the number of IP addresses in the Internet Protocol (IP) address table (IPT):

See TPF Operations for more information about the ZOSAE and ZTTCP commands.

TWRT0001Ename tapename devaddr CCcode CCW-command CSW-word SNS-data

Where:

name
The subsystem user (SSU) name or the basic subsystem (BSS) name.

tapename
The symbolic tape name (for example, RTL).

devaddr
The device address.
Note:
Where two paths are defined for the drive, the address given is that used for the failing operation.

code
The SIO condition code. When a deferred SIOF condition code occurs the deferred condition code is given.

command
The failing channel command.
Note:
When a data chained channel program specified through the TDCTC macro fails, the operation code given is that of the first CCW in the chain.

word
The channel status word. This is the CSW associated with the error.
Note:
For the SIO condition code 3 (not operational), the CSW is not meaningful and is not included in the message.

data
The sense data. The sense data is only included in the message for unit-check conditions. The number of sense bytes displayed is dependent on the device type. There are 24 bytes displayed for the IBM 3400 series tape drives. If an input/output (I/O) error prevents the successful sensing of the device, the UNABLE word is displayed in place of the sense data.

Explanation: None.

System Action: None.

User Response: None.