**** START OF SPECIFICATIONS ***************************************** * * **** MODULE NAME = APSGMAC1 * * * * COMP(APS) PROD(PSF) : RELEASE 3.1.0 * * * **** DESCRIPTIVE NAME = PSF FOR OS/390 MESSAGES AND CODES UPDATES * * * **** STATUS = VERSION 3, RELEASE 1, LEVEL 0 * * * **** FUNCTION = * * * * THIS MODULE CONTAINS ALL OF THE UPDATES TO THE PSF FOR * * OS/390 MESSAGES AND CODES SINCE THE LAST PUBLISHED VERSION OF * * THE MANUAL. * * * * THE UPDATES ARE PUT IN THE SAME FORMAT AS THEY WERE BEING * * PUT IN THE DOC ++HOLDS. * * * * EACH TIME A NEW APAR HAS UPDATES THE CHANGE ACTIVITY WILL * * BE UPDATED AND A NEW SECTION WILL BE ADDED TO THE END OF * * THIS MODULE PRECEDED BY A LINE THAT DENOTES THE APAR NUMBER. * * * * DO NOT GO PAST COLUMN 64 WITH YOUR DOC CHANGES. THE END OF * * THE DASHED LINES WITH YOUR APAR NUMBER IN THE TEXT INDICATE * * COLUMN 64. * * * **** RESTRICTIONS * * * * DO NOT EDIT OR UPDATE THIS FILE ON SAMPLIB AS THE * * NEXT APAR THAT CHANGES THIS MODULE WILL DO A TOTAL REPLACE * * OF IT THUS OVERLAYING YOUR CHANGES. IF YOU WISH TO MAKE * * CHANGES TO THIS MODULE THEN DO IT IN YOUR OWN COPY OF THIS * * MODULE. * * * * *** CHANGE ACTIVITY = * * $01=OW37851, HPRF310,990709,BDKUELJ: Printer Inventory * * $02=OW42106, HPRF310,991104,BLDCWJ: loop when small page * * length set at printer * * $03=OW42719, HPRF310,000111,BLDCWJ: APS502I issued * * $04=OW43161, HPRF310,000131,BDKURLD: Handle session closed * * $05=OW41991, HPRF310,000321,BDKULMM: Enable inline capture with * * WPM * * $06=OW43468, HPRF310,000321,BDKURLD: Add TCP/IP name to WTO * * messages * * $07=OW43880, HPRF310,000426,BDKUDDA: Allow >4GB num in APS988I * * $08=OW43717, HPRF310,000428,BDKUDDA: no change (done to sup OW43880* * $09=OW44475, HPRF310,000509,BDKURLD: Invalid TCP/IP prefix * * message length * 00610000 * $10=OW44862, HPRF310,000428,BDKUELJ: no change, supercede OW43468 * * * **** END OF SPECIFICATIONS ******************************************* All of the following changes are for the PSF for OS/390 Messages and Codes (G544-5627-01). -----------CHANGES FOR OW37851---------------------------------- 1. On page 171, change the text for APS619I to APS619I NOT ALL PARAMETERS REQUIRED TO INITIALIZE AN SNA DEVICE WERE SPECIFIED IN THE PRINTER INVENTORY FOR fsaname. 2. On page 286 under APS1004I in the System Programmer Response, change the second sentence to "For more information about the the Infoprint Server load errno, refer to OS/390 Infoprint Server Messages and Diagnosis." 34830000 -----------CHANGES FOR OW42106---------------------------------------- 06490000 APS151I THE PRINTABLE AREA LENGTH OF inches INCHES IS TOO SMALL TO PRINT MESSAGES. PSF HAS USED THE SMALLEST LENGTH FROM THE LOGICAL PAGE inches OR THE PHYSICAL PRINTABLE AREA inches OR THE USER PRINTABLE AREA inches. PRINTING OF MESSAGES IS TERMINATED. Explanation: A check was made to determine whether the message would fit in the printable area when printed on the paper size currently in the printer. It was determined that there was not enough space for even one message line. The page length specified is too small. System Action: The message dataset or interrupt message page is not printed. User Response: If the FORMLEN keyword has been specified in the user's OUTPUT JCL statement and this value is too small, increase the FORMLEN value and resubmit the job. The FORMLEN value is used for both the message dataset and the interrupt message page. See the PSF for OS/390 User's Guide for details on the FORMLEN keyword. If this does not fix the problem, inform your system programmer. System Programmer Response: If messages are to be printed, select a form, a logical page size, and a font size that allows messages to fit on the page. The form definition or page definition selected to process messages may be incorrect, or the font selected may be too large for the page size specified in the form definition or the page definition. In addition, the physical printable area length (form length) as returned in the XOH Obtain Printer Characteristics reply may be too small. PSF uses the smallest of the: 1) User Printable Area length plus its vertical offset, 2) the physical printable area length, or 3) the current logical page length plus its vertical offset to determine the printable area. The aforementioned printable area lengths are further reduced by any vertical offset from the medium origin (specified in the formdef), and by an additional .36 inches for all printers except the 3800 where .67 inches is used. 1. Use the smallest length as specified in the message and: o If the logical page length is too small, correct the length in the pagedef for the message dataset. See IBM Page Printer Formatting Aid: User's Guide for assistance. o If the physical page length(forms length) is too small and the forms length may be configured via the printer's operator panel, perform the action specified in the "Operator Response". o If the User Printable Area (UPA) is too small, see the PSF Security Guide for assistance. Note: All the values above are affected by the offset from the medium origin as specified in the formdef for the message dataset. Check this value to ensure the offset is not too large. See IBM Page Printer Formatting Aid: User's Guide for assistance. 2. See the "User Response" section if it can be determined that the submittor of the job has specified the FORMLEN keyword and the FORMLEN value is too small. 3. If the specified page length is not too small, it could be because PSF calculated an incorrect maximum page length. Operator Response: If the physical printable area length (forms length) may be configured by the operator and it's determined this is the problem, increase the printable area length (forms length) and resubmit the job. See the printer hardware manual for details on configuring forms length. Otherwise, inform your system programmer that this error has occurred. Problem Determination: Items 1, 17, 19. -----------CHANGES FOR OW42719---------------------------------- After last bullet in explanation for message APS502I, add following bullet: o Failed to include a FONTDD, PSEGDD or OVLYDD default on the PRINTDEV statement when using multiple resolution. -----------CHANGES FOR OW43161---------------------------------- 00860000 1. On page 272 for APS935I under the common ERRNOs in the explanation add errno 0 as follows. 0 See the previous message for a description of the problem. 2. Add message APS6500I. APS6500I UNEXPECTED SESSION ENDING RESPONSE RECEIVED FROM THE PRINTER. Explanation: An unexpected response was received from the printer that ended the TCP/IP session prematurely. System Action: If a data set was being printed at the time the session ended, the data set may be restarted from the most recent checkpoint before the session was ended or may be restarted from the beginning if no checkpoint had occurred. - If connecting to the printer and FAILURE=WCONNECT, PSF will issue message APS935I and the connect will be retried until the connect interval timer expires (CONNINTV). - If connecting to the printer and FAILURE=STOP, PSF will terminate the FSA and issue APS934I. - If attempting to send data and FAILURE=STOP, PSF will terminate the FSA and issue APS934I. - If attempting to send data and FAILURE=WCONNECT, PSF will issue messages APS932I and APS6501I and attempt to restablish the connection. User Response: Examine your output for duplicate pages. System Programmer Response: This indicates a possible logic error in the microcode of the printer or another problem with the printer. Consult your hardware service provider or the person responsible for the printer for assistance. Operator Response: No response is necessary. Problem Determination: Items 1, 18. 3. Add message APS6501I. APS6501I AN UNEXPECTED COMMUNICATION FAILURE OCCURRED. PRINTING WILL BE RESTARTED AT A PREVIOUS CHECKPOINT, AND PAGES MAY BE DUPLICATED. Explanation: PSF detected an unexpected failure in communication with the printer; for instance, the session was lost during page processing. Some pages may have printed, of which PSF was not informed. If the printer is attached via TCP/IP, this message could be caused by TCP/IP being recycled. This message will appear on the operator console. System Action: The data set being printed at the time of the error is restarted from the most recent checkpoint before the interrupt or possibly from the beginning if no previous checkpoint had been taken. User Response: Examine your output for duplicate pages. System Programmer Response: No response is necessary. Operator Response: To determine an appropriate response, see the specific error conditions described in any accompanying console message. Problem Determination: Items 1, 25, 26, 27. 4. Change the System Programmer Response for abend reason code 0E96 to read as follows. System Programmer Response: This PSF abend reason code results from a possible logic error in the microcode of the printer. Contact your hardware service provider for assistance regarding this error code. -----------CHANGES FOR OW41991---------------------------------- 00860000 1. pg 271 update the inserts for message APS933I for ATTACH to read "ATTACH=psf|dpf|psfdirect|wpm" Update the explanation for ATTACH to also list Workstation Print Manager (WPM). -----------CHANGES FOR OW43468---------------------------------- 1. On page 1 change the "attachment" for TCP/IP to read as follows. (tcpname)--For a TCP/IP attached printer where "tcpname" is the name of the TCP/IP startup procedure. -----------CHANGES FOR OW43880---------------------------------- 1. On page 283 change message text and the Expanation for message APS988I to: APS988I DOWNLOAD SENT number (base) BYTES TO nnn.nnn.nnn.nnn-- JOB=jobname STEP=jobstep ID=jobid. Explanation: A data set with the indicated number of bytes was transmitted to the remote system with the IP address (nnn.nnn.nnn.nnn) indicated in the message. In the message, 'number' has two possible forms. o For files less than 4 gigabytes (4GB), 'number' is the decimal number of bytes sent. In this case, 'base' is "DECIMAL". o For files greater than 4 gigabytes (4GB), 'number' is the hexadecimal number of bytes sent. In this case, 'base' is "HEX" and 'number' is always exactly 16 hexadecimal digits including leading zeros. The job submitter requested that this message be sent to the user IDs specified in the NOTIFY keyword in the JCL for the data set. When the job submitter specifies the NOTIFY keyword, this message is sent also to the SYSLOG data set. Refer to PSF for OS/390: Download for OS/390 for more information about this feature. -----------CHANGES FOR OW44475---------------------------------- 00860000 1. Change message APS946I to read as follows. APS946I THE IPADDR (ip_address) SPECIFIED IN THE PRINTDEV OR IN THE PRINTER INVENTORY COULD NOT BE RESOLVED. Explanation: If a dotted decimal address was provided, it was not in the correct format or was invalid. If a host name was provided, it could not be resolved by TCP/IP. System Action: The PSF FSA ends. User Response: Inform your system programmer that this error occurred. System Programmer Response: If a dotted decimal address was provided, correct the error. If a host name was provided, contact your TCP/IP administrator. PSF uses the same name resolver as the TSO LPR command. Operator Response: Notify your system programmer. Problem Determination: Item 1 2. Change message APS997I to read as follows. APS997I DOWNLOAD DID NOT TRANSMIT THE DATASET BECAUSE IPADDR (ip_address) COULD NOT BE RESOLVED. Explanation: The IPADDR specified in the routing-control data set could not be used so the file was not sent. If a dotted decimal address was provided, it was not in the correct format or was invalid. If a host name was provided, it could not be resolved by TCP/IP. System Action: Download for OS/390 attempts to retransmit the data set according to the retry interval and retry number specified in the matching routing record of the routing-control data set. If retry is not requested or is not successful, Download for OS/390 releases the data set back to JES and requests that it be held by the system. User Response: Inform your system programmer that this error occurred. System Programmer Response: If a dotted decimal address was provided, correct the IPADDR parameter in the routing-control data set. To use the modified routing control data set, stop the Download for OS/390 FSS and restart the FSAs. If a valid host name was provided, contact your TCP/IP administrator. Download for OS/390 uses the same name resolver as the TSO LPR command. Operator Response: Notify your system programmer. Problem Determination: Item 1 3. Add message APS6504I. APS6504I THE MESSAGE LENGTH IN THE TCP/IP PREFIX IS GREATER THAN THE MAXIMUM LENGTH ALLOWED. Explanation: The message length in the TCP/IP prefix is greater than the maximum message length allowed. System Action: If in the process of bringing up the session, PSF will attempt to restart the session. If already in session, PSF will bring down the session and attempt to restart the session. User Response: No response is necessary. System Programmer Response: This indicates a possible logic error in the microcode of the printer or another problem with the printer. Consult your hardware service provider or the person responsible for the printer for assistance. Operator Response: This indicates a possible logic error in the microcode of the printer or another problem with the printer. Consult your hardware service provider or the person responsible for the printer for assistance. Problem Determination: Items 1, 18.