Messages › LPD Interface Messages

LPD Interface Messages

This section contains messages issued by the LPD Interface main task, which takes care of initialization, operator communication and initiation of the LPD session tasks.

ESF7001

LPD interface started on port: 9999

Reason:

The LPD Interface has been successfully started, and it is ready to process incoming session requests on TCP/IP port number 9999. Processing continues.

Action:

None.

ESF7002

LPD interface terminated

Reason:

The LPD Interface has been successfully terminated. The LPD terminates processing.

Action:

None.

ESF7003

Initialization failed. Correct above problems and restart LPD

Reason:

Severe initialization problems were detected, which made it impossible to start the LPD Interface. The cause of the problem may be determined from previously issued error messages. The LPD Interface terminates processing.

Action:

Correct any problems, if possible, or contact the systems programmer.

ESF7004

Argument count error

Reason:

The LPD Interface has been started passing an incorrect number of parameters. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7005

Memory allocation error

Reason:

The LPD Interface could not allocate sufficient storage to initialize. The LPD Interface terminates processing.

Action:

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

ESF7006

Signal Handler create failed. xxxxxxxxxxxxx

Reason:

The LPD Interface failed during creation of a Signal Handler. xxxxxxxxxxxxx is a run-time error message. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7007

LPDLOG open failed

Reason:

The LPD Interface was unable to open the LPDLOG data set. Messages will be written to the SYSPRINT dates. Processing continues.

Action:

None.

ESF7008

<ESFLPDC|ESFCMSG|ESFOPEN|ESFWRIT|ESFCLOS|ESFCOMI|SARPAM> load failed

Reason:

The LPD Interface was unable to load the specified load module. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7010

LPD cancelled

Reason:

The LPD Interface main task was canceled. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7011

LPD abended with xxxx

Reason:

The LPD Interface abended with abend code xxxx. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7020

Setenv failed. xxxxxxxxxxxxx

Reason:

The LPD Interfaces failed to set up an environment variable. xxxxxxxxxxxxx is a runtime error message. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7021

Getaddrinfo failed RC=99, errno=888. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to translate a host name because of return code 99 and system error number 888. xxxxxxxxxxxxx is a TCP/IP diagnostic message. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7022

Service not found: printer/tcp. Port 515 used.

Reason:

The LPD listen port number was not specified using the LPDSERV statement and the printer service not specified in the TCP/IP service file, so the LPD Interface defaults to port 515. Processing continues.

Action:

None.

ESF7023

Unable to allocate socket errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to allocate a socket because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7024

Setsockopt SO_REUSEADDR failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD failed to set the SO_REUSEADDR socket option because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7025

Getclientid failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to get the listener clientid because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7026

Bind failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to bind to the specified port number because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7027

Getsockname failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to get the listener socket name because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7028

Listen failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to make the socket ready to accept incoming connection requests because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7029

Name Server disabled

Reason:

The use of the TCP/IP Name Server function was disabled, because it failed to respond in 1 minute. Processing continues.

Action:

None.

ESF7030

Selectecb failed errno=999. xxxxxxxxxxxxx

Reason:

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

Action:

Check the TCP/IP diagnostic message.

ESF7031

Selectecb exception errno=999. xxxxxxxxxxxxx

Reason:

A socket exception system error number 999 was received. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. Processing continues.

Action:

Check the TCP/IP diagnostic message.

ESF7032

LPDC Memory allocation error

Reason:

The LPD Interface could not allocate sufficient storage to initiate a new session. The LPD Interface terminates processing.

Action:

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

ESF7033

Accept failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed during accepting of a connection request because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7034

Setsockopt SO_REUSEADDR failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to set the SO_REUSEADDR socket option because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7035

Givesocket failed errno=999. xxxxxxxxxxxxx

Reason:

The LPD Interface failed to make a socket available because of system error number 999. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The LPD Interface terminates processing.

Action:

Check the TCP/IP diagnostic message.

ESF7036

Attach of ESFLPDC failed RC=99

Reason:

The LPD Interface failed to attach a LPD session subtask. 99 is the return code from the ATTACH call. The LPD Interface terminates processing.

Action:

Check the ATTACH RC.

ESF7040

LPDPARM open failed

Reason:

The LPD Interface was not able open the LPDPARM data set. Check to see if the LPDPARM DD statement was missing in the LPD JCL procedure. The LPD Interface terminates processing.

Action:

Contact your systems programmer.

ESF7041

LPDP Memory allocation error

Reason:

The LPD Interface could not allocate sufficient storage to process a LPDSERV or LPDDEST initialization statement. If problem occurs during startup, the LPD Interface terminates processing. If problem occurs during REINIT processing, the LPD Interface fails the REINIT request and continues processing.

Action:

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

ESF7042

Record: "Initialization parameter statement in error"

Reason:

The initialization parameter statement shown in this message was in error. This message is followed by error message ESF7043, ESF7044 or ESF7045. If problem occurs during startup, the LPD Interface ignores the invalid LPDSERV or LPDDEST statement and continues initialization. If problem occurs during REINIT processing, the LPD Interface fails the REINIT request and continues processing.

Action:

Correct the invalid initialization parameter statement.

ESF7043

Invalid parameter statement

Reason:

The parameter statement listed in the preceding error message ESF7042 is not a valid LPD parameter statement.

If a problem occurs during startup, the LPD Interface ignores the invalid LPDSERV or LPDDEST statement and continues initialization. If a problem occurs during REINIT processing, the LPD Interface fails the REINIT request and continues processing.

Action:

Correct the invalid LPD parameter statement.

ESF7044

Invalid parameter keyword: xxxxxxx

Reason:

The keyword parameter xxxxxxxx is not a valid LPDSERV or LPDDEST parameter.

This message is preceded by error message ESF7042. If problem occurs during startup the LPD Interface ignores the invalid LPDSERV or LPDDEST statement and continues initialization. If a problem occurs during REINIT processing, the LPD Interface fails the REINIT request and continues processing.

Action:

Correct the invalid LPDSERV or LPDDEST parameter.

ESF7045

Invalid parameter value: xxxxxxx

Reason:

The parameter value xxxxxxxx is not a valid value for the specified LPDSERV or LPDDEST parameter.

This message is preceded by error message ESF7042. If problem occurs during startup the LPD Interface ignores the invalid LPDSERV or LPDDEST statement and continues initialization. If a problem occurs during REINIT processing, the LPD Interface fails the REINIT request and continues processing.

Action:

Correct the invalid LPDSERV or LPDDEST parameter.

ESF7050

===> xxxxxxx

Reason:

The LPD interface operator command xxxxxxxx have been entered. Processing continues.

Action:

None.

ESF7051

Invalid command: xxxxxxx

Reason:

The entered command xxxxxxxx was not recognized as a valid LPD interface operator command. Processing continues.

Action:

Enter the correct command.

ESF7052

REINIT successfully completed

Reason:

A REINIT command has been successfully completed. All changes to changes to the LPD parameter deck are in effect. Processing continues.

Action:

None.

ESF7053

REINIT failed

Reason:

A REINIT command failed because syntax errors found in the LPD parameter deck. Processing continues.

Action:

Correct the invalid LPDSERV or LPDDEST parameter and then re-issue the REINIT command.

ESF7060

No active sessions

Reason:

This message is displayed in response to a DA (display-active) command if no sessions were active. Processing continues.

Action:

None.

ESF7061

Request from hhhh - <<Receive LPD Daemon command |
Request to dest dddd from hhhhh - Start printer queue |
Request to dest dddd from hhhhh - Send short queue state |
Request to dest dddd from hhhhh - Send long queue state |
Request to dest dddd from hhhhh - Remove jobs |
Request to dest dddd from hhhhh - Receive job |

< ESF File 9999 | SAR Seqno 8888 | JES DD vvvv| DUMMY File> nnnn(dddd|uuuu) from hhhhh -66 Mbytes of 77 Mbytes(55%) |
< ESF File 9999 | SAR Seqno 8888 | JES DD vvvv| DUMMY File> nnnn(dddd|uuuu) from hhhhh -66 Kbytes of 77 Kbytes (55%) |
< ESF File 9999 | SAR Seqno 8888 | JES DD vvvv| DUMMY File> nnnn(dddd|uuuu) from hhhhh -66 bytes of 77 bytes (55%)

Reason:

This message is displayed in response to a DA (display-active) command for each active session showing their actual status where:

hhhh

Specifies the remote host name or IP address.

dddd

Specifies the printer queue name.

9999

Specifies the CA Spool file number.

8888

Specifies the CA View file sequence number.

vvvv

Specifies the JES SYSOUT DD-name.

nnnn

Specifies the filename.

uuuu

Specifies the requestor's user ID.

66

Specifies the number of bytes, KB or MB received.

77

Specifies the total file size in bytes, KB or MB.

55

Specifies the percentage of data received so far.

Processing continues.

Action:

None.

ESF7065

Session cancelled: hhhh

Reason:

This message is displayed in response to a Cancel session command to session hhhh. Processing continues.

Action:

None.

ESF7070

CA Spool LPD Version.Level *xxxxxxx*

Reason:

This message is displayed in response to a DS (display-status) command. xxxxxxx specifies the current CA Spool LPD version number and release number. Processing continues.

Action:

None.

ESF7071

Total sessions: 999 Active sessions: 888 Max sessions: 777

Reason:

This message is displayed in response to a DS (display-status) command where:

• 999—is the total number of sessions thus far
• 888—is the current number of active sessions
• 777—is the max number of concurrent sessions

Processing continues.

Action:

None.

ESF7072

LPR requests: 999 LPQ requests: 888 LPRM requests: 777

Reason:

This message displays in response to a DS (display-status) command where:

• 999—is the total number of LPR requests
• 888—is the total number of LPQ requests
• 777—is the total number of LPRM requests

Processing continues.

Action:

None.

ESF7073

ESF files: 999, SAR files: 888, JES files: 777

Reason:

This message displays in response to a DS (display-status) command where:

• 999—is the total number of CA Spool files received
• 888—is the total number of CA View files received
• 777—is the total number of JES files received

Processing continues.

Action:

None.

ESF7074

Text files: 999 AFP files: 888 PCL files: 777

Reason:

This message is displayed in response to a DS (display-status) command where:

• 999—is the total number of Text files received
• 888—is the total number of AFP files received
• 777—is the total number of PCL files received

Processing continues.

Action:

None.

ESF7075

Bin files: 999 PS files: 888

Reason:

This message is displayed in response to a DS (display-status) command where:

• 999—is the total number of Binary files received
• 888—is the total number of PostScript files received

Processing continues.

Action:

None.

ESF7076

Total bytes: 999 Total records: 888 Total pages: 777

Reason:

This message is displayed in response to a DS (display-status) command where:

• 999—is the total number of bytes/KB/MB received
• 888—is the total number of records/Krecords/Mrecords received
• 777—is the total number of pages/Kpages/Mpages received

Processing continues.

Action:

None.

ESF7079

Reason:

This empty message is displayed last in response to a DS (display-status) command. Processing continues.

Action:

None.