|
|
This chapter describes messages issued by the User SMTP. These messages are T01US000 through T01US999.
Explanation A print request was received by Cisco IOS for S/390 from a host not on the local network. The print request from the remote host (rem_host) was ignored and the connection is terminated.
Recommended Action Verify the APPCFGxx PARM member for LPR restricted access and modify if appropriate.
Explanation The Line Printer Server (LPS) received a command or verb that is unknown from a remote host (rem_host). Valid commands include lpc, lpr, lpq, and lprm. Cisco IOS for S/390 discards the command and release the connection.
Recommended Action Notify remote client that this command is unknown or not supported.
Explanation The LPS received a command or subcommand that was not terminated with a line-feed from remote host rem_host.
Recommended Action Notify remote client that this command format is incorrect.
Explanation The LPS received an lpr subcommand that was either unknown or unsupported from remote host rem_host. Valid lpr subcommands include abort, control, and data. Cisco IOS for S/390 discards the subcommand, closes the open file and releases the connection.
Recommended Action Notify remote client that this lpr subcommand is bad.
Explanation An alternate printer was requested from lpr's print job command, but either no name was found or the name was greater than eight characters.
Recommended Action If the SELECT option was specified on the APPCFGxx LPR statement, the default DESTID is tried. If the FLUSH option was specified, then the file is purged.
Explanation On reception of an lpr command from another host, Cisco IOS for S/390 attempts to allocate resources to perform the print request. One such resource is the SYSOUT data set. Verify options selected in APPCFGxx's LPR statement. If the installation specified NOSELECT, then the default DESTED failed. If SELECT or FLUSH was specified, then the remote "print queue name" was invalid.
Recommended Action If the SELECT option was specified on APPCFGxx's LPR statement, then the default DESTID is tried. If the FLUSH option was specified, then the file is purged. If the default DESTID is invalid verify name is defined to JES.
Explanation After the SYSOUT data set is allocated, USPOOL attempts to open it for use. Any failure with opening the SYSOUT data set causes the print request to be ignored and the TCP connection to be closed.
Recommended Action See the description of message T01US006I for additional information.
Explanation When the remote host (rem_host) closes the TCP connection after sending the contents of the file it wanted printed, Cisco IOS for S/390 releases the SYSOUT data set. No matter how the free request completes, the TCP connection is closed.
Recommended Action See the description of message T01US006I for additional information.
Explanation The number of lines printed by USPOOL for this LPR request exceed the site maximum as specified on the OUTLIM parameter of the APPCFGxx's LPR statement. The rest of the output is flushed.
Recommended Action If the site specified limit for OUTLIM is too small, increase the OUTLIM value of the LPR statement in APPCFGxx to a higher value. JES2 users may specify OUTLIM=0 on the LPR statement to disable SYSOUT outline checking.
Explanation An lpr data file was received that contained a record longer than the LRECL of the SYSOUT data set (254 characters). Cisco IOS for S/390 closes the SYSOUT file and releases the connection. The remaining output is flushed.
Recommended Action Examine the file being printed to ensure that it contains eor (end-of-record) markers. Data files must contain eor markers (LF, FF, CR) to indicate end of record. Cisco IOS for S/390 does not support lpr records in excess of 254 characters.
Explanation The LPS received an lpr abort subcommand from a remote host (rem_host). Cisco IOS for S/390 closes the SYSOUT file and releases the connection.
Explanation The LPS received a "print any waiting jobs" (lpc) command from a remote host (rem_host). This command is not supported by the LPS. Cisco IOS for S/390 discards the request and releases the connection.
Recommended Action Notify remote client that this command is not supported.
Explanation The LPS received a "queue state" (lpq) command from a remote host (rem_host). This command is not supported by the LPS. Cisco IOS for S/390 discards the request and releases the connection.
Recommended Action Notify remote client that this command is not supported.
Explanation The LPS received a "remove from queue" (lprm) command from a remote host (rem_host). This command is not supported by the LPS. Cisco IOS for S/390 discards the request and releases the connection.
Recommended Action Notify remote client that this command is not supported.
Explanation The remote host did not respond within the allotted time.
Recommended Action Retry later.
Explanation There is no port defined under the LPR statement in member APPCFGxx.
Recommended Action Define a port in member APPCFGxx
Explanation The remote client transmitted a data file header that contains an invalid "data bytes to be received count". The field either has bad characters that are not numbers or the number is greater than 99,999,999. rem_addr is the Internet address in dot notation of the remote host.
Recommended Action A TCPEEP trace will verify the data being received. The client should be corrected to contain the correct value in the "data bytes to be received count".
Local Subsystem ID: ssid Lookup error is: ac.ec text, Diag=x'code' Explanation A GET HOST BY NAME call to DNR for the specified subsystem ID failed. Read
"DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information on action, error, and diagnostic codes.
| ssid | The subsystem ID. |
| ac | The action code. |
| ec | The error code. |
| text | The message text. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action. One possible reason is that the local subsystem ID is not defined in the DNR alias member.
This message can be due to a temporary resource initialization coordination problem or it can be due to a bad DNR configuration. Multiple occurrences of this message may be an indicator of configuration or network problems.
The TCP base product must be able to resolve the subsystem name into a host name. One can use the TSO command DNRGET to verify whether the TCP base product can correctly map the subsystem name into a host name.
An MVS host IBMHOST.COLUMBIA.COM using the subsystem name ACSS with an IP address of 138.42.32.24 can be verified with the following TSO command:
DNRGET H BYN ACSS SYSID(ACSS)
If the response from the DNRGET command does not indicate a correct host name and IP address combination then one should check the installation's DNR definitions in configuration files DNRALCxx and DNRHSTxx.
These are the DNRALCxx file entries for the local host IBMHOST.COLUMBIA.COM:
ACSS IBMHOST.COLUMBIA.COM.These are the DNRHSTxx file entries for the local host IBMHOST.COLUMBIA.COM:
IBMHOST.COLUMBIA.COM. 138.42.32.24Local Subsystem ID: ssid Lookup error return code: rc Explanation A GET HOST BY NAME call to DNR for the specified subsystem ID failed. Module GETHBDNR could not accommodate the request and returned the specified error code.
| ssid | The subsystem ID. |
| rc | The error code:
-2 - Bad arguments were passed to GETHBDNR -4 - No core was available for the request -5 - A software error occurred when processing the DIRSRV call in GETHBDNR. |
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problem persists, check for related SVC dumps that may have been issued. The T01LOG and JES log of the job should be saved. Contact Customer Support. This message can be due to a temporary resource initialization coordination problem or it can be due to a bad DNR configuration. Multiple occurrences of this message may be an indicator of configuration or network problems.
The TCP base product must be able to resolve the subsystem name into a host name. One can use the TSO command DNRGET to verify whether the TCP base product can correctly map the subsystem name into a host name.
An MVS host IBMHOST.COLUMBIA.COM using the subsystem name ACSS with an IP address of 138.42.32.24 can be verified with this TSO command:
DNRGET H BYN ACSS SUBSYS(ACSS)If the response from the DNRGET command does not indicate a correct host name and IP address combination then one should check the installation's DNR definitions in configuration files DNRALCxx and DNRHSTxx.
These are the DNRALCxx file entries for the local host IBMHOST.COLUMBIA.COM:
ACSS IBMHOST.COLUMBIA.COM.These are the DNRHSTxx file entries for the local host IBMHOST.COLUMBIA.COM:
IBMHOST.COLUMBIA.COM. 138.42.32.24Null x-header found Explanation The X-from or X-to header in the mail file contained neither a user or host address. The outbound mail request is rejected. Check the log for related messages for the data set name.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with a null X-header and correct it.
Bad character c in x-headerExplanation An X-from or X-to header in the mail file contains incorrect syntax. Character c is the start of the incorrect syntax on the X-header. header is the X-header data. The outbound mail request is rejected. Check the log for related messages for the data set name.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with bad syntax and correct it.
Bad Literal string in x-header: xxxxxxx Explanation An X-from or X-to header in the mail file contains incorrect syntax. A literal string does not terminate in the X-header. The X-header terminates before the ending double quote is found. xxxxxxx is the X-header data. The outbound mail request is rejected. Check the log for related messages for the data set name.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with bad syntax and correct it.
Bad Domain Literal in x-header: xxxxxxx Explanation An X-from or X-to header in the mail file contains incorrect syntax. A domain literal contains incorrect syntax. xxxxxxx is the X-header data.
The outbound mail request is rejected. Check the log for related messages for the data set name.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with bad syntax and correct it.
X-header enclosed incorrectly: xxxxxxx Explanation An X-from or X-to header in the mail file contains incorrect syntax. Special characters < and > are found in the X-header text. These special characters are allowed to envelope X-header message text but they must be balanced (i.e., the beginning of the message text contains < while the end of the message text should be >.) xxxxxxx is the X-header text.
The outbound mail request is rejected. Check the log for related messages for the data set name.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with bad syntax and correct it.
No local user found in x-header: xxxxxxx Explanation An X-from or X-to header in the mail file contains incorrect syntax. Only hosts and routes were found in the X-header. xxxxxxx is the X-header text.
The outbound mail request is rejected. Check the log for related messages for the data set.
Recommended Action Delete the ail file data set. Try to find what software generated this mail message with bad syntax and correct it.
No host found in x-header: xxxxxxx Explanation An X-from or X-to header in the mail file contains incorrect syntax. No host or route was found in the X-header. xxxxxxx is the X-header text. The outbound mail request is rejected. Check the log for related messages for the data set.
Recommended Action Delete the mail file data set. Try to find what software generated this mail message with bad syntax and correct it.
|
|