|
|
This chapter lists the messages that can be generated by the FINGER, WHOIS, ACSHELLO, and TTCP sample API application programs. It includes these sections:
This section lists messages generated by the socket version of the WHOIS sample program.
Most of these messages use the perror function call of the socket library to issue the message, and therefore these messages have an error-specific string appended to them. Read perror Messages in this document for descriptions of the perror error messages of the socket library.
If the WHOIS program executes successfully, it returns a value of 0. When the socket WHOIS program encounters an error, it immediately terminates execution with a return code of 16.
Explanation Usage help message display if the WHOIS command is issued with invalid command line parameters. WHOIS must be called with a required parameter of NAME() and with the optional parameter of HOST() (name of host to request WHOIS service).
Explanation The WHOIS program cannot bind a name to the socket used to communicate with the WHOIS server. Read perror Messages in this document for more information about the error message.
Explanation The WHOIS program cannot establish a TCP connection with the WHOIS server. Read perror Messages in this document for more information about the error message.
Explanation The WHOIS program encountered an error when reading from the socket used to communicate with the WHOIS server. Read perror Messages in this document for more information about the error message.
Explanation The WHOIS program cannot open a socket to use to connect to the WHOIS server. Read perror Messages in this document for more information about the error message.
Explanation The WHOIS client cannot determine the port number of the WHOIS server to connect to, due to a failure of the directory services to return a correct value. Check that the database contains an entry for the WHOIS service using TCP.
Explanation The WHOIS program encountered an error when writing to the socket used to communicate with the WHOIS server. Read perror Messages in this document for more information about the error message.
Explanation The WHOIS program cannot find the name of the host specified by the command line parameter HOST() using the directory services feature of Cisco IOS for S/390.
This section lists messages generated by the C library version of the WHOIS client program. If the C WHOIS program completes successfully, it returns an error code of 0. If any errors are encountered, it returns a 16.
Explanation This message is issued when a command parameter is formatted incorrectly. It is to provide the user the syntax of the command. WHOIS must be called with a required parameter of NAME() and with optional parameters of HOST() (name of host to request WHOIS service) and SYSID (subsystem ID of Cisco IOS for S/390).
Explanation When terminating the user session with the API, the WHOIS program detected an error at the completion of the ACLOSE. ret_code is the general return code of the ACLOSE macro; err_code is the error code field of the APCB that was used to call ACLOSE.
Explanation These two lines of output indicate that the WHOIS program cannot open an application session with the API. ret_code is the general return code of the AOPEN macro; err_code is the error code field of the APCB used to call AOPEN.
Explanation The WHOIS program attempted to assign a name to its local endpoint using TBIND, but an error was encountered by the API. The TBIND macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation This error message may be followed by a message generated by the API. Read the API messages in Cisco IOS for S/390 Prefixed Messages for information about the message.
Explanation After completing the conversation with the WHOIS server, the client encountered an error when attempting to close the endpoint used for this session. The TCLOSE macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation While attempting to confirm the connection sequence, the API returned an error to the WHOIS program. The TCONFIRM macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When trying to initiate a connection with the WHOIS server, an error was encountered. The TCONNECT macro returned an error indicated by the general error code, displayed at the err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation These three lines of messages are printed if the WHOIS program cannot locate the WHOIS service port for TCP using the directory services. num is the number of the general return code returned by the DIRSRV macro expansion. value is the value of the return code field of the Directory Services Parameter List (DPL) used when DIRSRV is called.
Explanation The WHOIS program attempted to open a transport endpoint through which to communicate to the WHOIS server. The TOPEN macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When receiving data from the WHOIS server, an error was detected. The TRECEIVE macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When attempting to acknowledge a release indication received from the WHOIS server, the client detected an error. The TRELACK macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When completing the orderly release between the client and the server, an error was detected by the WHOIS program. The TRELEASE macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation While transmitting data to the WHOIS server, an error was detected. The TSEND macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation These three lines of messages are printed if the WHOIS program cannot locate the Network Information Center's name using the directory services. The hostname is replaced by the default host name of the NIC or by the name of the host specified by the user in the HOST command parameter. num is the number of the general return code returned by the DIRSRV macro expansion. value is the value of the return code field of the Directory Services Parameter List (DPL) used when DIRSRV is called.
This section lists those messages issued by the C library version of the ACSHELLO program. If the ACSHELLO program encounters any unrecoverable problem during its operation, it returns a code of 16. Because the program executes a loop servicing the clients requesting information, the program does not terminate successfully. You must either cancel the job or attention out the TSO command.
Explanation This message is issued when a command parameter is formatted incorrectly. It is to provide the user the syntax of the command. ACSHELLO may be called with no parameters or optionally with a well-known port number and/or a subsystem ID.
Explanation These two lines of output indicate that the ACSHELLO program cannot open an application session with the API. ret_code is the general return code of the AOPEN macro, and err_code is the error code field of the APCB that was used to call AOPEN.
Explanation The ACSHELLO server cannot look up its local host name and/or its internet address from NDS. ret_code is the number of the general return code returned by the DIRSRV macro expansion. value is the value of the return code field of the Directory Services Parameter List (DPL) used when DIRSRV was called.
Explanation On receiving a connection request from a client, the server attempted to accept the connection to a new endpoint. The TACCEPT macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation The ACSHELLO program attempted to assign a name to its local endpoint using TBIND but an error was encountered by the API. The TBIND macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code. This error message may be followed by a message generated by the API. Read the API messages in Cisco IOS for S/390 Prefixed Messages for information about the message.
Explanation After providing service to a client, the ACSHELLO program detected an error on the TCLOSE used to destroy the local endpoint. The TCLOSE macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation The ACSHELLO program attempted to wait on the local endpoint receiving an incoming connection request from a client. The TLISTEN macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation The ACSHELLO program attempted to open a transport endpoint through which to wait for incoming connection requests from clients. The TOPEN macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When acknowledging the completion of the orderly release from the client, the ACSHELLO server received an error on the release acknowledgment. The TRELACK macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation After issuing a TRELEASE request to the API to begin an orderly release of the TCP connection to the client, an error was returned by the API to the ACSHELLO program. The TRELEASE macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation When trying to send data to a connected client, the ACSHELLO server was returned an error from the API. The TSEND macro returned an error indicated by the general error code, err_code, and the Transport Parameter List (TPL) return code field, ret_code.
Explanation This message is transmitted to a connected client to indicate the CPU serial number and model number of the host on which ACSHELLO is running.
Explanation This message is transmitted to a connected client to indicate the internet address used by this host to communicate.
Explanation This message is transmitted to a connected client to indicate the SMF ID of the host on which ACSHELLO is running.
Explanation This message is transmitted to a connected client to indicate the version level of MVS on which the ACSHELLO program is running.
Explanation This message is transmitted to a connected client to indicate the name of the host on which ACSHELLO is executing. hostname is the name of the host or the string No host name, if ACSHELLO encountered a problem getting its name from NDS.
Explanation This message is transmitted to a connected client to indicate that the ACSHELLO server has accepted its request for service and proceeds to do so. date_time is the current date and time as reflected by the system on which ACSHELLO is running.
Recommended Action This message is transmitted to a connected client to indicate that the ACSHELLO has completed its service to the connected client and now terminates. date_time is the current date and time as reflected by the system on which ACSHELLO is running.
This section lists the messages generated by the socket version of the ACSHELLO sample program. The ACSHELLO program runs in a loop, servicing clients as they request information of the server. Therefore it does not terminate with a successful return code. The user should cancel it or attention interrupt the TSO command. However if the ACSHELLO server detects an unrecoverable error, it terminates with a return code of 16.
Most of these messages use the perror function call of the socket library to issue the message and have an error-specific string appended to them. Read perror Messages in this document for more information.
Explanation This message is issued when a command parameter is formatted incorrectly. It is to provide the user the syntax of the command. ACSHELLO may be called with no parameters or optionally with a well-known port number.
Explanation The ACSHELLO program encountered an error when trying to accept an incoming connection from a client. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program cannot bind a well-known name to the socket used to listen for requests from clients. Read perror Messages in this document for a more detailed explanation of the error message.
Explanation The ACSHELLO program encountered an error when closing the connection to a client that just received servicing. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program encountered an error after issuing a request to NDS to retrieve its internet address.
Explanation The ACSHELLO program detected an error after issuing a request to NDS to retrieve the local host's name. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program encountered an error when attempting to enable the socket for accepting connection requests. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program detected an error when using the select socket call to perform synchronous I/O multiplexing. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program cannot open a socket to use to serve clients requesting service. Read perror Messages in this document for more information about the error message.
Explanation The ACSHELLO program encountered an error when writing data to a connected client. Read perror Messages in this document for more information about the error message.
Explanation This message is transmitted to a connected client to indicate the CPU serial number and model number of the host on which ACSHELLO is running.
Explanation This message is transmitted to a connected client to indicate the internet address used by this host to communicate.
Explanation This message is transmitted to a connected client to indicate the SMF ID of the host on which ACSHELLO is running.
Explanation This message is transmitted to a connected client to indicate the version level of MVS on which the ACSHELLO program is running.
Explanation This message is transmitted to a connected client to indicate the name of the host on which ACSHELLO is executing. hostname is the name of the host or the string no host name, if ACSHELLO encountered a problem getting its name from NDS.
Explanation This message is transmitted to a connected client to indicate that the ACSHELLO server has accepted its request for service and proceeds to do so. date_time is the current date and time as reflected by the system on which ACSHELLO is running.
Explanation This message is transmitted to a connected client to indicate that the ACSHELLO has completed its service to the connected client and now terminates. The date_time is replaced with the current date and time as reflected by the system on which ACSHELLO is running.
This section lists messages generated by the FINGER program. Most of these messages use the perror function call of the socket library to issue the message. Therefore these messages have an error-specific string appended to them. Read perror Messages in this document more information.
If the FINGER program executes successfully, it returns a value of 0. When the FINGER program encounters an error, it immediately terminates execution with a return code of 16.
Explanation Usage help message display if FINGER command is issued with invalid command line parameters. FINGER must be called with a required parameter of NAME() and with the optional parameter of LONG.
Explanation The FINGER program could not establish a TCP connection with the FINGER server. Read the section on perror generated messages for a more detailed explanation of the error message.
Explanation The FINGER program could not open a socket to use to connect to the FINGER server. Read the section on perror generated messages for a more detailed explanation of the error message.
Explanation The FINGER client could not determine the port number to connect to of the FINGER server, due to a failure of the directory services to return a correct value. The user should ensure that the database contains an entry for the FINGER service using TCP.
Explanation The FINGER program could not find the name of the host specified by the command line parameter NAME() using the directory services feature of Cisco IOS for S/390.
Explanation The name of the host specified as part of the NAME() parameter has been located by the directory services.
This section lists messages generated by the TTCP sample program.
If the TTCP program executes successfully, it returns a value of 0. A return code of 100 (decimal) indicates that the MVS IKJPARS facility encountered a severe error in trying to parse the TTCP parameters. A return code of 52 (decimal) indicates a general TTCP program error and is accompanied by a message. A return code of 48 (decimal) indicates the failure of a TPL-based API operation and is also accompanied by a message.
Explanation An AOPEN macro issued by TTCP failed. This generally means that the SSN parameter was incorrectly specified or that the specified Cisco IOS for S/390 subsystem is not executing.
Explanation After a DIRSRV macro issued by TTCP failed, the DPL function code (DPLFNCCD) was found to be invalid.
Explanation After a TPL-based operation issued by TTCP failed, the TPL function code (TPLFNCCD) was found to be invalid.
Explanation When running TTCP under the TSO TMP in a batch job, the address of the CIB was found to be zero after an MVS STOP (P) command.
Explanation When running TTCP under the TSO TMP in a batch job, the CIBVERB field in the CIB control block was found not to contain the expected CIBSTOP value after an MVS STOP (P) command.
Explanation When running TTCP under the TSO TMP in a batch job, the EXTRACT COMM macro resulted in the returned COMLIST address being zero.
Explanation The BUFLEN parameter entered by the user is invalid. BUFLEN must be less than or equal to the Transport Information Block (TIB) maximum size of TRECV/TRECVFR data (TIBLTRCV) that is set via the MAXLTRECV parameter of the TCP or UDP statement.
Explanation The BUFLEN parameter entered by the user is invalid. BUFLEN must be less than or equal to the Transport Information Block (TIB) maximum size of TSEND/TSENDTO data (TIBLTSND) that is set via the MAXLTSEND parameter of the TCP or UDP statement.
Explanation The BUFLEN parameter entered by the user is invalid. When TTCP is in receive mode, BUFLEN must be greater than zero.
Explanation The BUFNUM parameter entered by the user is invalid. BUFNUM must be less than or equal to the Transport Information Block (TIB) maximum size of the receive queue (TIBQRECV) that is set via the MAXQRECV parameter of the TCP or UDP statement.
Explanation The BUFNUM parameter entered by the user is invalid. BUFNUM must be less than or equal to the Transport Information Block (TIB) maximum size of the send queue (TIBQSEND) that is set via the MAXQSEND parameter of the TCP or UDP statement.
Explanation The BUFNUM parameter entered by the user is invalid. BUFNUM must be greater than zero.
Explanation While the individual BUFLEN and BUFNUM parameters entered by the user are valid, the combination of the two is invalid. The product of BUFLEN multiplied by BUFNUM must be less than or equal to the Transport Information Block (TIB) maximum size of the receive buffer (TIBLRECV) that is set via the MAXRECVBUF parameter of the TCP or UDP statement.
Explanation While the individual BUFLEN and BUFNUM parameters entered by the user are valid, the combination of the two is invalid. The product of BUFLEN multiplied by BUFNUM must be less than or equal to the Transport Information Block (TIB) maximum size of the send buffer (TIBLSEND) that is set via the MAXSENDBUF parameter of the TCP or UDP statement.
Explanation The count parameter entered by the user is invalid. When TTCP is in transmit mode, COUNT must be greater than zero.
Explanation The TTCP subroutine that issues the TSO PUTLINE macro was passed an invalid message identifier.
Explanation In TTCP receive mode, a free receiver subtask control block was not found to allow passing of the endpoint to a receiver subtask.
Explanation In TTCP receive mode, the receiver subtask was passed an invalid (null) endpoint ID.
Explanation When running TTCP under the TSO TMP in a batch job, the QEDIT CIBPTR=0 macro failed; the macro is issued to disallow the MVS MODIFY (F) command from being issued to the batch job.
Explanation When running TTCP under the TSO TMP in a batch job, the QEDIT FREE of the CIB failed; this CIB represents the MVS STOP (P) command.
Explanation When running TTCP under TSO (nonbatch) the STAX ATTNEXIT macro failed.
Statistic message issued Transport Information Block (TIB) completion of a receive (sink) transfer.
| Parameter | Description |
|---|---|
| secs | The number of seconds the transfer took. |
| trecvs | The number of TRECV/TRECVFR operations completed. |
| trecvsps | The number of TRECV/TRECVFR operations completed per second. |
| bytes | The number of data bytes received. |
| bytesps | The number of data bytes received per second. |
Statistic message issued Transport Information Block (TIB) completion of a transmit (source) transfer.
| Parameter | Description |
|---|---|
| secs | The number of seconds the transfer took. |
| tsends | The number of TSEND/TSENDTO operations completed. |
| tsendsps | The number of TSEND/TSENDTO operations completed per second. |
| bytes | The number of data bytes received. |
| bytesps | The number of data bytes received per second. |
Explanation In TTCP receive mode, the receiver subtask found the passed endpoint to be in the wrong state.
|
|