Messages › LPD Session Messages › Messages Prefixes

Messages Prefixes

In the LPD Session Messages, the following generic message prefixes are used:

<prefix1> = Request from hhhh
<prefix2> = Request to dest dddd from hhhhh
<prefix3> = < ESF File 9999 | SAR Seqno 8888 | JES DD vvvv |
DUMMY File> nnnn(dddd|uuuu) from hhhhh

where:

• hhhh—is the remote host name or IP address
• dddd—is the printer queue name
• 9999—is the CA Spool file number
• 8888—is the CA View file sequence number
• vvvv—is the JES SYSOUT DD-name
• nnnn—is the filename
• uuuu—is the requestor's user ID

ESF7100

<prefix3> - 9999 < Text | AFP | PCL | PS | Bin > < pages | records | bytes > received

Reason:

A session task has successfully received the print file identified by the <prefix3> information. 9999 pages, records or bytes have been received. The session task completes.

Action:

None.

ESF7101

Signal Handler create failed. xxxxxxxxxxxxx

Reason:

A session task failed during creation of a Signal Handler. xxxxxxxxxxxxx is a run-time error message. The session task terminates.

Action:

Contact your systems programmer.

ESF7102

LPDTRACE open failed

Reason:

A session task was unable to open the LPDTRACE data set. Tracing will be disabled. Processing continues.

Action:

Contact your systems programmer.

ESF7103

Memory allocation error

Reason:

A session task could not allocate sufficient storage to initialize. The session task terminates.

Action:

Contact your systems programmer; it may be necessary to increase the region size.

ESF7104

<prefix1> - Invalid Daemon command received: 99

Reason:

An invalid daemon command 99 has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7105

<prefix2> - Unable to find LPDDEST parameters for: dddd

Reason:

A session task was unable to locate any LPDDEST parameters to be used for a request to printer queue dddd. The session task terminates.

Action:

Check for any LPDPARM errors during LPD startup.

ESF7106

<prefix2> - Start queue command received: dddd

Reason:

A start queue command for printer queue dddd has been received and ignored. The session task completes.

Action:

None.

ESF7107

<prefix2> - Send short queue state command ignored: dddd

Reason:

A send short queue state command for a non-CA Spool printer queue dddd has been ignored. The session task completes.

Action:

None.

ESF7108

<prefix2> - Remove job command ignored: dddd

Reason:

A remove job command for a non-CA Spool printer queue dddd has been ignored. The session task completes.

Action:

None.

ESF7109

<prefix2> - Invalid job subcommand received: 99 dddd

Reason:

An invalid job subcommand 99 for printer queue dddd has been received. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7110

<prefix3> - Abort job subcommand received: dddd

Reason:

An abort job subcommand for printer queue dddd has been received. The received data file identified by <prefix3> is deleted. The session task terminates.

Action:

None.

ESF7111

<prefix3> - Unable to receive control file

Reason:

A receive control file job subcommand has been received, but the session task was unable to receive the control file. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7112

<prefix3> - Unable to receive control file EOF

Reason:

A session task failed to receive an EOF after the control file. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7113

<prefix3> - Unable to receive data file

Reason:

A receive data file job subcommand has been received, but the session task was unable to receive the data file. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7114

<prefix3> - Unable to receive data file EOF

Reason:

A session task failed to receive an EOF after the data file. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7115

<prefix3> - Unable to re-read data file

Reason:

A session task failed to read a data file, which has been stored in virtual storage or on a temporary data set. The session task terminates.

Action:

Check LPDLOG for other related messages.

ESF7116

<prefix3> - Invalid control file line: xxxxxxxx

Reason:

An invalid control file line xxxxxxxx was found in the control file. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7117

<prefix3> - Disallowed file extension: xxx

Reason:

A print request was received for a file with an extension of xxx, which has been disallowed. The extension may have been omitted as a valid file extension or is explicitly defined as an invalid extension.

Action:

Check the LPDSERV/LPDDEST/LPDFILE xVALEXT= and xINVEXT= parameters. Verify if file extension 'xxx' must be allowed or not.

ESF7119

<prefix3> - Session cancelled by userexit RC=%

Reason:

The LPD user exit ESFU011 requested the session to be canceled by returning a non-zero return code 99. The session task terminates.

Action:

None.

ESF7120

Setenv failed. xxxxxxxxxxxxx

Reason:

A session task failed to set up an environment variable. xxxxxxxxxxxxx is a run-time error message. The session task terminates.

Action:

Contact your systems programmer.

ESF7121

Getnameinfo failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed to get the name of the peer because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7122

Getclientid failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed to get the client ID because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7123

Takesocket failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed to take the socket descriptor passed from the LPD manager task because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7124

Getpeername failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed to get the address of the peer because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7125

<prefix1> - Remote host not known to Name Server

Reason:

The LPD interface was configured with LPDSERV HOSTVAL=YES and a print request was received from a remote host which was not defined to the TCP/IP Name Server.

Action:

Define the remote host to the TCP/IP Name Server re: if it must be allowed to send print requests.

ESF7126

<prefix1> - Invalid source port: 9999

Reason:

The LPD interface was configured with LPDSERV PORTVAL=YES/SUPV and a print request were received from a remote host on source port 9999 which is not allowed with the current configuration.

Action:

Change the remote host to use a valid source port.

ESF7127

<prefix1> - Setsockopt SO_LINGER failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed to set socket options because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7128

<prefix1> – Unable to load CSNBSYD - ICSF AES Service

Reason:

The print data decryption support failed because it was unable to load module CSNBSYD which is installed as part of z/OS Integrated Cryptographic Service Facility (ICSF). The session task terminates.

Action:

Add the ICSF load library CSF.SCSFMOD0 to the LNKLST or to the CA Spool STEPLIB concatenation.

ESF7129

<prefix1> – AES decryption failed RC=88, Reason=77

Reason:

The data decryption module CSNBSYD failed with return code 88 and reason code 77. For documentation of ICSF return and reason codes, see Appendix A in z/OS ICSF Application Programmer Guide. Printer is drained.

Action:

Correct the reported ICSF configuration problem.

ESF7130

<prefix1-3> - Selectecb failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed during checking for socket ready for reading because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7131

<prefix1-3> - Selectecb exception errno=999. xxxxxxxxxxxxx

Reason:

A session task received a socket exception system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7132

<prefix1-3> - Session timed out

Reason:

A session task timed out, because no data was received in the specified TIMEOUT period. The session task terminates.

Action:

You might want to increase the used LPDDEST FTIMEOUT value.

ESF7133

<prefix1-3> - Recv failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed while receiving data because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7134

<prefix1-3> - Recv error, connection was closed

Reason:

A session task failed to receive data because the connection was closed. The session task terminates.

Action:

Check LPDLOG for other related messages.

ESF7135

<prefix1-3> - Send failed errno=999. xxxxxxxxxxxxx

Reason:

A session task failed during the sending of data because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The session task terminates.

Action:

Check the TCP/IP diagnostic message.

ESF7140

<prefix3> - ESFOPNC failed. Status code: ss <PID=ppp>

Reason:

An ESFOPNC—open CA Spool file—call failed with status code ss. If the status code is PE, the actual parameter in error ppp is also displayed. The session task terminates.

Action:

Check the CA Spool status code.

ESF7141

<prefix3> - ESFWRIT failed. Status code: ss

Reason:

An ESFWRIT—write CA Spool file call—failed with status code ss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7142

<prefix3> - ESFCLOS failed. Status code: ss

Reason:

An ESFCLOS—close CA Spool file call—failed with status code ss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7145

<prefix2> - ESFCOMI OPEN failed. Status code: ssss

Reason:

An ESFCOMI—open CA Spool Communication Channel—failed with status code ssss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7146

<prefix2> - ESFCOMI SEND failed. Status code: ssss

Reason:

An ESFCOMI—send CA Spool command—failed with status code ssss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7147

<prefix2> - ESFCOMI RECEIVE failed. Status code: ssss

Reason:

An ESFCOMI—receive CA Spool command response—failed with status code ssss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7148

<prefix2> - ESFCOMI CLOSE failed. Status code: ssss

Reason:

An ESFCOMI—close CA Spool Communication Channel—failed with status code ssss. The session task terminates.

Action:

Check the CA Spool status code.

ESF7150

<prefix3> - No CA View database specified

Reason:

Missing CA View database name on selected LPDSERV/LPDDEST parameter statement. The session task terminates.

Action:

Add DSAR or FSAR parameter to LPDPARM and perform a REINIT.

ESF7151

<prefix3> - SARPAM load failed

Reason:

A session task was unable to load the SARPAM CA View interface module. The session task terminates.

Action:

Locate the SARPAM load module.

ESF7152

<prefix3> - SARPAM - Init failed RC=99

Reason:

A CA View SARPAM Init call failed with return code 99. The session task terminates.

Action:

Check the LPD joblog for CA View error messages.

ESF7153

<prefix3> - SARPAM – Open failed RC=99

Reason:

A CA View SARPAM open call failed with return code 99. The session task terminates.

Action:

Check the LPD joblog for CA View error messages.

ESF7154

<prefix3> - SARPAM – Write failed RC=99

Reason:

A CA View SARPAM write call failed with return code 99. The session task terminates.

Action:

Check the LPD joblog for CA View error messages.

ESF7155

<prefix3> - SARPAM – Close failed RC=99

Reason:

A CA View SARPAM close call failed with return code 99. The session task terminates.

Action:

Check the LPD joblog for CA View error messages.

ESF7156

<prefix3> - SARPAM – Term failed RC=99

Reason:

A CA View SARPAM term call failed with return code 99. The session task terminates.

Action:

Check the LPD joblog for CA View error messages.

ESF7160

<prefix3> - JES Allocate SYSOUT failed RC=99, Error=8888, Info=7777

Reason:

Allocation of a JES SYSOUT data set failed with return code 99, error code 8888 and info code 7777. The session task terminates.

Action:

Check the returned dynamic allocation return code, error code and info code.

ESF7160

<prefix3> - <OUTADD / OUTDEL> failed RC=99, Reason=88, TU=7777

Reason:

Add or delete of Dynamic Output Descriptor failed with return code 99 and reason code 88. 7777 is the internal number of the invalid Text Unit.The session task terminates.

Action:

Check the returned OUTADD/OUTDEL return code and reason code.

ESF7161

<prefix3> - JES Open SYSOUT failed

Reason:

Open of a JES SYSOUT data set failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7162

<prefix3> - JES Write SYSOUT failed

Reason:

Write to a JES SYSOUT data set failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7163

<prefix3> - JES Close SYSOUT failed

Reason:

Close of a JES SYSOUT data set failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7164

<prefix3> - JES Free SYSOUT failed RC=99, Error=8888, Info=7777

Reason:

Free of a JES SYSOUT data set failed with return code 99, error code 8888 and info code 7777. The session task terminates.

Action:

Check the returned dynamic allocation return code, error code and info code.

ESF7170

<prefix3> - Temp DS—Allocate failed RC=99, Error=8888, Info=7777

Reason:

Allocation of a temporary data set failed with return code 99, error code 8888 and info code 7777.  The session task terminates.

Action:

Check the returned dynamic allocation return code, error code and info code.

ESF7171

<prefix3> - Temp DS—Open output failed

Reason:

Open of a temporary data set for output failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7172

<prefix3> - Temp DS—Write failed

Reason:

Write to a temporary data set failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7173

<prefix3> - Temp DS—Close output failed

Reason:

Close of a temporary data set for output failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7174

<prefix3> - Temp DS—Open input failed

Reason:

Open of a temporary data set for input failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7175

<prefix3> - Temp DS—Close input failed

Reason:

Close of a temporary data set for input failed. The session task terminates.

Action:

Check the LPD joblog for error messages.

ESF7176

<prefix3> - Temp DS—Free failed RC=99, Error=8888, Info=7777

Reason:

Free of a temporary data set failed with return code 99, error code 8888 and info code 7777.  The session task terminates.

Action:

Check the returned dynamic allocation return code, error code and info code.

ESF7177

<prefix3> - Load of DBCS translate table cccccccc failed

Reason:

Load of the specified DBCS translate table cccccccc failed. The session task terminates.

Action:

Correct the DBCS translate table definition in the module ESFTRAN.

ESF7178

<prefix3> - DBCS translation failed with RC=99

Reason:

The DBCS translation failed with return code 99. The session task terminates.

Action:

Correct the DBCS translate table definition in the module ESFTRAN.

ESF7180

<prefix1> - Invalid Daemon command received: 99

Reason:

An invalid daemon command 99 has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7181

<prefix1> - Invalid or missing printer queue name

Reason:

A daemon command with an invalid or missing printer queue name has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7182

<prefix1> - Invalid user name and job number list

Reason:

A daemon command with an invalid user name and job number list has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7183

<prefix1> - Invalid or missing file number

Reason:

A LPRM daemon command with an invalid or missing file number has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7185

<prefix2> - Invalid or missing count in receive job command

Reason:

A job subcommand, with an invalid or missing byte count, has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7186

<prefix2> - Invalid or missing name in receive job command

Reason:

A job subcommand, with an invalid or missing file name, has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7187

<prefix2> - Invalid file name in receive job command

Reason:

A job subcommand, with a file name which is neither a control file or a data file, has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7188

<prefix2> - Invalid job subcommand received: 99 nnnn

Reason:

An invalid job subcommand 99 with file name nnnn has been received from the remote host identified by the <prefix1> information. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7189

<prefix2-3> - Output Limit exceeded - 99999 bytes

Reason:

A print request was received which exceeds the allowed output limit of 99999 bytes. The print request is canceled.

Action:

Check the LPDSERV/LPDDEST xOUTLIM= parameters. Increase the output limit if you need to larger print files to be received.

ESF7190

<prefix3> - Unable to receive binary data file

Reason:

A session task failed to receive a binary data file. The session task terminates.

Action:

Check the LPDLOG for preceding messages.

ESF7191

<prefix3> - Unable to receive AFP data file

Reason:

A session task failed to receive an AFP data file. The session task terminates.

Action:

Check the LPDLOG for preceding messages.

ESF7192

<prefix3> - Invalid AFP record received

Reason:

A session task received an invalid AFP record. The session task terminates.

Action:

An LPD trace may help identify the problem.

ESF7193

<prefix3> - Unable to receive text data file

Reason:

A session task failed to receive a text data file. The session task terminates.

Action:

Check the LPDLOG for preceding messages.

ESF7194

<prefix3> - Unable to receive PCL data file

Reason:

A session task failed to receive a PCL data file. The session task terminates.

Action:

Check the LPDLOG for preceding messages.

ESF7198

<prefix1-3> - cancelled

Reason:

A session task was canceled. The session task terminates.

Action:

None.

ESF7199

<prefix1-3> - abended with xxxx

Reason:

A session task abended with abend code xxxx. The session task terminates.

Action:

Check the description of the abend code.

ICSF Messages

SARICF01

ICSF key(s) generated - be sure to backup ICSF CKDS data

Reason:

New keys have been placed in the ICSF CKDS data set. This data set should be backed up as soon as possible.

Action:

CA Spool has updated encryption keys in the ICSF CKDS dataset. These keys will be required when encrypting and decrypting report data. To insure that these keys are available, this data set should be backed up and sent to your disaster recovery site.