|
|
This chapter describes messages issued by the socket API layer. These messages are T01SO000 through T01SO999.
Messages in this range detail information about the network protocol layers, Transmission Control Protocol (TCP), Internet Protocol (IP), Internet Control Message Protocol (ICMP), and User Datagram Protocol (UDP). These messages help someone familiar with the TCP/IP suite of protocols to troubleshoot problems arising in this area on the local system, remote system, or network.
These messages have the following general format:
code type: text (protocol) HOST=host_addr PORTS=lport:rport GATEWAY=gw_addr| Variable | Description |
| code | Code number, in the format ACC30xI, where x can be an integer 0 through 3. |
| type | General description of the message. This provides the networking software administrator with an idea about the severity and location of the problem.
Any of the following substrings can appear in the type field: MISC NOTE - Generally indicates some minor event or error that occurred with one of the protocols. This type of message has no severity. LCL EVENT - Indicates a protocol event that occurred on the local machine. The severity of this message is very low and normally requires no action. RMT ERROR - Indicates that the remote host or gateway did not respond properly at the specified protocol layer. Examples of this kind of error include the remote system/gateway sending a TCP packet with a bad checksum or responding incorrectly at the current TCP state LCL ERROR - Indicates a problem with the network protocols on the local machine. Problems with the Cisco IOS for S/390 implementation of TCP/IP may show themselves here or the error may be caused by an application layer module. |
| text | Brief description of the event or error.
Each message that uses a different text field is listed in the following sections with a description of each. |
| protocol | String of three characters indicating the protocol that displayed the message.
This field is optional. These are the possible values: TCP - Transmission Control Protocol ICM - Internet Control Message protocol ECO - ICMP Echo (ping) UDP - User Datagram Protocol IP - IP Protocol GWY - Gateway ptask and IP protocol |
| host_addr | Internet address in dot notation of the host to which the local system is communicating.
This field is optional. |
| lport | Protocol's pseudo-port on the local machine.
This parameter is optional. |
| rport | Protocol's pseudo-port on the remote machine.
This parameter is optional. |
| gw_addr | Internet address in dot notation of the first host gateway currently in use when communicating with the preceding host address.
This parameter is optional. |
| host_name | Remote host textual name. |
Most of the TCP messages have a four-character subfield in the text field. This subfield (state) contains one of these values:
| State | Description |
|---|---|
NULL | Null state. The local TCP is initializing. Once completed, the NULL state is exited to the listen state. |
| LSTN | Listen state. This state is entered after TCP receives a passive open request from a User Level Protocol (ULP), indicating TCP should wait for a connection request from a remote TCP. |
| SYNS | SYN sent state. The local TCP has sent an open request (SYN) and is waiting for a matching open request connection from the remote TCP. |
| SYNR | SYN received state. The local TCP has received and sent matching open requests from and to the remote TCP. It is now awaiting a confirming connection request acknowledgment (ACK) from the remote TCP. |
| ESTB | Connection established state. The local and remote TCPs have completed the open sequence and a path is now available for the two hosts to communicate with each other. |
| CLSW | Close wait state. The local TCP has received a connection close request (FIN) from the remote TCP and is waiting for the local ULP to issue a close request. |
| FINW | FIN wait state. The local TCP is waiting for either a close connection request (FIN) or an acknowledgment for a close connection request from the remote TCP. |
| CLSG | Closing state. In this state the local TCP is waiting for the acknowledgment of a close connection request from the remote TCP. |
| LACK | A wait ACK on local FIN state. This state represents having sent both the close connection request and close connection acknowledgment and now waiting for the last ACK from the remote TCP. |
| TIMW | Time wait state. Waiting for enough time to pass to ensure that the remote TCP has received the ACK of its close request. |
| RATW | Remote abort state. When attempting to open a connection to a remote TCP, a TCP reset is returned indicating that the remote TCP refuses the connection. |
Explanation Initialization of the Socket API environment completed successfully.
Explanation A required POOLDEF configuration statement was not coded in the configuration member IJTCFGxx.
Recommended Action Add a POOLDEF statement for pool "NAME(name)"
Initialization of the Socket API failed. Values for code are:
| 00 | Success |
| 04 | Error allocating SAVT |
| 08 | Error allocating SAVX |
| 0C | Error allocating ASVB |
| 10 | Error freeing SAVX after error allocating ASVB |
| 14 | Error allocating SPCB |
| 18 | Error freeing ASVB after error allocating SPCB |
Recommended Action If insufficient virtual storage exists in the region to allocate the necessary control blocks, stop Cisco IOS for S/390 and restart it with a larger REGION size.
Explanation An attempt to create a new socket following an inbound connection request failed. The reason code specified by value1 represents the return code from T01XCREA. The reason code specified by value2 is the diagnostic code returned by T01XCREA. Read the Cisco IOS for S/390 Prefixed Messages manual to locate the explanation for value2.
Recommended Action Normally a call to T01XCREA should not fail. Contact Customer Support.
Explanation An attempt to process an asynchronous socket API unit of work failed because the Socket API Work element (SAW) at address saw_addr was invalid. The SAW contained either an invalid function code func_code for the queue q_name it was placed upon or the Socket End Point Main (SEPM) control block address in the SAW did not match the SEPM on which the SAW was placed.
A queue name of SEPMSAWQ represents the SEPM work queue for a connection; a queue name of SPCBWORK is the provider work queue.
Recommended Action Dump the address space via the operator console and contact Customer Support.
Explanation The SAPI control block cntl_blck was found to be corrupted or invalid in module mod_name. Address cntl_addr is where the control should begin.
An attempt will be made to take an SVCDUMP of the base product address space.
Recommended Action Contact Customer Support.
|
|