Reason:
An aaaaaaa call in the TCP/IP interface for file number 999999 on printer pppppppp has returned status code bb. If an ESFOPEN or an ESFREAD call has failed, the print job terminates and the file is held.
If an ESFCCKPT call has failed, the file printout will continue and be checkpointed as part of the next normal checkpoint. Status code: 05 means-Temporarily no free space for check pointing. Processing continues normally.
Action:
Interpret the return code bb from the aaaaaaa routine.
Reason:
The TCP/IP interface could not allocate sufficient storage to process the print file number 999999 on printer pppppppp. The print job terminates and the printer is drained.
Action:
Contact your systems programmer; it may be necessary to increase the region size for CA Spool.
Reason:
A send socket call for file number 999999 on printer pppppppp has failed. xxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface has failed to receive the expected response from the print server for file number 999999 on printer pppppppp. xxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface has received an unexpected response from the print server for file number 999999 on printer pppppppp. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
Allocate Code Conversion Descriptor for the specified DBCS translate table cccccccc failed. The print job terminates and the printer is drained.
Action:
Correct the translate table definition in the module ESFTRAN.
Reason:
The Code Conversion for file number 999999 on printer pppppppp failed. xxxxxxxx is a diagnostic message from Unicode Conversion Services.
The print job terminates and the printer is drained.
Action:
Correct the translate table definition in the module ESFTRAN.
Reason:
The TCPHOST parameter on the NODE statement specified a TCP/IP host name that could not be resolved by TCP/IP for file number 999999 on printer pppppppp. The print job terminates and the printer is drained.
Action:
Check the TCPHOST parameter to be sure it is correct.
Reason:
The TCP/IP interface failed to allocate a socket for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface failed to set socket implementation or to set socket option SO_REUSADDR or SO_LINGER for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface failed to connect the socket to the TCPHOST for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface failed to determine the address of the local host for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface failed to connect to the TCPHOST for file number 999999 on printer pppppppp in 2½ minutes. This message is preceded by message ESF911. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
The TCP/IP interface failed to select pending sockets for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface did not receive a reply from the receiving printer for file number 999999 on printer pppppppp within the time specified on the TIMEOUT NODE parameter. The exception to this is the LPR receive a printer job command where the timeout value is 2 minutes. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
The printer pppppppp defined with ACQUIRE=TIME was unable to successfully print a file within the specified FSSNPRO retry timeout value, so the printer is automatically changed to use ACQUIRE=WORK.
Once a file has successfully been printed the printer will automatically be changed back to use ACQUIRE=TIME.
Action:
Check the TCP/IP connection to the printer.
Reason:
The TCP/IP interface has not received a proper acknowledgment from the receiving printer for file number 999999 on printer pppppppp. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
A send PCL resource request for file number 999999 on printer pppppppp has failed. This message is preceded by message ESF903. The print job terminates and the printer is drained.
Action:
See the action for the message ESF903.
Reason:
The TCP/IP interface failed during creation of an ESTAE environment for print file number 999999 on printer pppppppp. 88 is the return code from the ESTAE call. The print job terminates and the printer is drained.
Action:
Contact your systems programmer.
Reason:
The printer node pppppppp has started printing file number 999999 using TCP/IP socket descriptor number 666. If the file page count is greater than 1, the number of pages are shown; otherwise the number of lines are shown.
The word "partially" means partial printing was requested for the file. The word "initially" means that this is the first time the file is on the printer. The word "restarted" means that the printing of the file was interrupted earlier, and is now restarted. The word "reprinted" means that the file has been requeued for reprinting.
Action:
None.
Reason:
The TCP/IP interface failed to print file number 999999 on printer pppppppp. This message is preceded by another message explaining why the print request failed; values are as follows:
Action:
See the action for the preceding message.
Reason:
The processing state of file number 999999 on printer node pppppppp has been changed. The specified action is performed; processing continues.
Action:
None.
Reason:
The printing of file number 999999 on printer node pppppppp has been terminated by a cancel or interrupt printer command during TCP/IP session establishment. The print job terminates and the printer is drained.
Action:
None.
Reason:
The printing of file number 999999 on printer node pppppppp has been terminated and file 999999 will be held.
Action:
Check the printer status in the menu system or the messages written to ESFLOG to determine why the file was held.
Reason:
The processing status of the printer node pppppppp has been changed to edrained.
Action:
Check the printer status in the menu system or the messages written to the ESFLOG to determine why the printer was edrained.
Reason:
An unsolicited device warning message has been received for printer node pppppppp. 99999 is the PJL status code number. If present, tttttttt is the display panel message normally displayed on the printer control panel display. The display panel message will be displayed in the default national language configured on the printer.
See the HP manual 5021-0328 Printer Job Language Technical Reference for more information about PJL status codes and display panel messages.
Action:
None.
Reason:
An intervention-required device status message has been received for printer node pppppppp. 99999 is the PJL status code number. If present, tttttttt is the display panel message, normally displayed on the printer control panel display. The display panel message will be in the default national language configured on the printer.
See the HP manual 5021-0328 Printer Job Language Technical Reference for more information about PJL status codes and display panel messages.
Action:
Prepare the printer for printing.
Reason:
The TCP/IP interface abended with abend code xxxxxx during the printing of print file number 999999 on printer pppppppp. The print job terminates and the printer is drained.
Action:
Contact your systems programmer.
Reason:
File 999999 on printer pppppppp failed during PCL command flushing. Processing continues.
Action:
None.
Reason:
File 999999 has been printed on printer pppppppp. The print job terminates and the printer is drained. If the page count is greater than 1, the number of pages printed are shown; otherwise the number of lines are shown. The Active number 666 contains the current number of active TCP/IP printers. The Elapse time 555 contains the elapse time from the file was initially created and until it was initially successfully sent to the printer. Processing continues.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp transferred 8888 bytes in 7.777 seconds resulting in transfer rate 666.66 Kbytes/sec. Processing continues.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp failed because the FTP program EZAFTPKS was not found. For more help see the FTP Client Application Programming Interface (API) chapter in the z/OS Communications Server IP Programmer's Guide and Reference. Printer is drained.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp failed because the FTP command cccccccc call failed with return code 88. For documentation of FTP return codes, see the FTP Client Application Programming Interface (API) chapter in the z/OS Communications Server IP Programmer's Guide and Reference.
Printer is drained.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp failed because FTP failed with return code 88. For documentation of FTP return codes, see the FTP Client Application Programming Interface (API) chapter in the z/OS Communications Server IP Programmer's Guide and Reference.
Printer is drained.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp failed because the FTP subcommand cccccccc failed with return code 88. For documentation of FTP return codes, see the FTP Client Application Programming Interface (API) chapter in the z/OS Communications Server IP Programmer's Guide and Reference.
Printer is drained.
Action:
None.
Reason:
File 999999 on FTP printer pppppppp failed because the FTP subcommand cccccccc failed with return code 88. For documentation of FTP return codes, see the FTP Client Application Programming Interface (API) chapter in z/OS Communications Server IP Programmer's Guide and Reference.
Printer is drained.
Action:
None.
Reason:
File 999999 on Connect:Direct printer pppppppp failed because the Connect:Direct DD-name cccccccc was not allocated. For more help see the Application Program Interface chapter in the Connect:Direct OS/390 User's Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on Connect:Direct printer pppppppp failed because the Connect:Direct program DMCHLAPI was not found. For more help see the Application Program Interface chapter in the Connect:Direct OS/390 User's Guide. Printer is drained.
Action:
None.
Reason:
A send PJL command request for file number 999999 on printer pppppppp has failed. This message is preceded by message ESF903. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
The TCP/IP interface failed to select pending sockets for file number 999999 on printer pppppppp. xxxxxxxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface has failed to receive PJL data from the print server for file number 999999 on printer pppppppp. xxxxxxxx is a diagnostic message from TCP/IP. The print job terminates and the printer is drained.
Action:
Check the TCP/IP diagnostic message and the connection to the printer.
Reason:
The TCP/IP interface did not receive a PJL status reply from the receiving printer for file number 999999 on printer pppppppp in 10 minutes. The print job terminates and the printer is drained.
Action:
Check the TCP/IP connection to the printer.
Reason:
File 999999 on XCOM printer pppppppp failed because the CA XCOM program XCOMJOB was not found. For more help see the Programming Interface chapter in the CA XCOM User Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on XCOM printer pppppppp failed because the CA XCOM DD-name cccccccc was not allocated. For more help see the Programming Interface chapter in the CA XCOM User Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on XCOM printer pppppppp failed because the CA XCOM DD-name cccccccc could not be opened. For more help see the Programming Interface chapter in the CA XCOM User Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on XCOM printer pppppppp failed because write to file SYSIN01 failed. For more help see the Programming Interface chapter in the CA XCOM User Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on XCOM printer pppppppp failed because write to file SYSIN01 failed. For documentation of CA XCOM return codes see the Programming Interface chapter in the CA XCOM User Guide. Printer is drained.
Action:
None.
Reason:
File 999999 on Connect:Direct printer pppppppp failed with return code 88 and UIRTNCD
99
. For documentation of Connect:Direct return codes codes and UIRTNCD values, see the Application Program Interface chapter in the Connect:Direct OS/390 User's Guide. Printer is drained.Action:
None.
Reason:
File 999999 on FTP/XCOM/C:D printer pppppppp failed to open the allocated DD-name NETRC. Printer is drained.
Action:
None.
Reason:
File 999999 on DISK/ESF/SAR/JES/FTP/XCOM/C:D printer pppppppp has been copied successfully. Processing continues.
Action:
None.
Reason:
File 999999 on Data Set printer pppppppp failed because an invalid Data Set keyword parameter kkkkkkkk was specified. File is held and printer is drained.
Action:
Correct the invalid keyword parameter specified in the printer's TCPHOST parameter or the file's OUTPUT ADDRESS parameter.
Reason:
File 999999 on Data Set printer pppppppp failed because an invalid value vvvvvvvv was specified for the Data Set keyword parameter kkkkkkkk. File is held and printer is drained.
Action:
Correct the invalid keyword parameter value specified in the printer's TCPHOST parameter or the file's OUTPUT ADDRESS parameter.
Reason:
File 999999 on Data Set printer pppppppp failed during dynamic data set allocation or free with return code 88, error code 7777, info code 6666 and SMS reason code 5555. Printer is drained.
Action:
Correct the reason for the dynamic dataset allocation or free problem.
Reason:
The warning message wwwwwwww was returned during dynamic data set allocation or free.
Action:
Correct the reason for the dynamic dataset allocation or free warning.
Reason:
File 999999 on Data Set printer pppppppp failed during data set open, write or close. File is held.
Action:
Correct the reason for the data set open, write or close problem.
Reason:
File 999999 on Data Set printer pppppppp failed because the allocated existing data set do not match the specified dataset parameters. File is held.
Action:
Correct the reason for the dynamic dataset allocation problem.
Reason:
File 999999 on Data Set printer pppppppp failed because the allocated existing data set lrecl was to small for the new dataset. File is held.
Action:
Correct the reason for the dynamic dataset allocation problem.
Reason:
Text to PDF/HTML/RTF wrapping of file 999999 failed because the corresponding DEFNODE T2PD | T2HT | T2RT was not defined. Processing continues.
Action:
None.
Reason:
File number 999999 on printer pppppppp did not accept data within the time specified on the NODE TIMEOUT parameter. If DSO printer with TCPDRIV option N and TIMEOUT>0 the printer enters INTREQ status (Intervention Required).
Action:
Resolve the reason for the INTREQ status (Intervention Required).
Reason:
File 999999 on Email printer pppppppp was successfully sent to email address mmmmmmmm. Processing continues.
Action:
None.
Reason:
File 999999 on Email printer pppppppp failed because an invalid Email keyword parameter kkkkkkkk was specified. File is held and printer is drained.
Action:
Correct the invalid keyword parameter specified in the file's OUTPUT ADDRESS or USERDATA parameters.
Reason:
File 999999 on Email printer pppppppp failed because an invalid value vvvvvvvv was specified for the Email keyword parameter kkkkkkkk. File is held and printer is drained.
Action:
Correct the invalid keyword parameter value specified in the file's OUTPUT ADDRESS or USERDATA parameters.
Reason:
File 999999 on Email printer pppppppp failed because it was rejected by the receiving Email server with message number 999 with message text **SMTP error message text**. Depending on the actual error message received the file is held, or the printer is drained or both.
Action:
Correct the reason for the received SMTP error message.
Reason:
File 999999 on printer pppppppp failed because the Text to PDF wrapper found a page larger than 32 KB. File is held.
Action:
Try to reduce the number of lines per page by using a smaller FCB or LINECOUNT.
Reason:
File 999999 on printer pppppppp failed because the Text to PDF wrapper generated more than 65535 PDF objects. File is held.
Action:
Split file into multiple files of less than 32760 pages.
Reason:
This informational message always appears when a file is processed by the Connect Direct print driver. If this message appears after an ESF949, it contains additional information about the error.
The Extended Codes are interpreted as follows:
Action:
None. However, see the Connect:Direct for z/OS User's Guide for corrective action if this message follows an ESF949 error message, indicating a fatal error.
Reason:
This informational message always appears when a file is processed by the Connect Direct print driver. It contains the Connect Direct Submitted process number.
Action:
None.
Reason:
File 999999 on LCDS printer pppppppp failed during sending of the FCB to the printer. Printer is drained.
Action:
Check printer is ready.
Reason:
File 999999 on LCDS printer pppppppp failed because it could not allocate sufficient storage to process the print file.
Action:
Contact your systems programmer; it might be necessary to increase the CA Spool region size.
Reason:
The encryption key kkkkkkkk specified on printer pppppppp is not valid. The encryption KEY must be specified as 32, 48 or 64 hexadecimal characters. Printer is drained.
Action:
Correct the specified printer node encryption KEY parameter.
Reason:
The print data encryption support failed because it was unable to load module CSNBSYE which is installed as part of z/OS Integrated Cryptographic Service Facility (ICSF). Printer is drained.
Action:
Add the ICSF load library CSF.SCSFMOD0 to the LNKLST or to the CA Spool STEPLIB concatenation.
Reason:
The data encryption module CSNBSYE 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.
Reason:
The print data encryption support failed because it was unable to load the Lexmark CRYPTLIB module which is installed from the Lexmark Decryption Card CD.
Action:
Upload the CRYPTLIB load module from the Lexmark Decryption Card CD and place in a library in the CA Spool STEPLIB concatenation.
Reason:
The Lexmark CRYPTLIB load module failed with return code 88. Printer is drained.
Action:
Correct the configuration problem if possible.
Reason:
The ESF print driver failed in the displayed ESFOPEN, ESFWRIT or ESFCLOS call with status code ss. If ESFOPEN with status code PE, the actual parameter in error ppp is also displayed. File is held.
Action:
Check the CA Spool status code.
Reason:
The SAR print driver failed because no SAR= CA View database-index was specified through the printer node TCPHOST parameter or the input file's OUTPUT ADDRESS parameters. File is held.
Action:
Specify SAR= CA View-database-index in the printer node TCPHOST parameter.
Reason:
The SAR print driver was unable to load the SARPAM—CA View Interface module. The printer is drained and the file is held.
Action:
Add a current CA View load library to the CA Spool STEPLIB concatenation.
Reason:
The SAR print driver failed because the displayed SARPAM interface returned return code 99.The file is held.
Action:
Check the CA Spool joblog for CA View error messages.
Reason:
Add or delete of Dynamic Output Descriptor failed with return code 99 and reason code 88. The internal number of the invalid Text Unit is 7777. The file is held.
Action:
Check the returned OUTADD/OUTDEL return code and reason code.
Reason:
Allocation or free of a JES SYSOUT data set failed with return code 99 and reason code 88. xxx is an error message returned by dynamic allocation. The session task terminates.
Action:
Check the returned dynamic allocation return code and reason code.
Reason:
The JES print driver failed because the displayed interface failed. The file is held.
Action:
Check the CA Spool joblog for error messages
|
Copyright © 2011 CA.
All rights reserved.
|
|