**** START OF SPECIFICATIONS ***************************************** * * **** MODULE NAME = APSGDGN2 * * * **** COMP(APS) PROD(PSF) : RELEASE 3.2.0 * * * **** DESCRIPTIVE NAME = PSF FOR OS/390 DIAGNOSIS UPDATES * * * **** STATUS = VERSION 3, RELEASE 2, LEVEL 0 * * * **** FUNCTION = * * * * THIS MODULE CONTAINS ALL OF THE UPDATES TO THE PSF FOR * * OS/390 DIAGNOSIS 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 = * * $00=LAPS0008, HPRF320,000823,BDKURLD: Initial version * * $01=OW44362, HPRF320,001207,BDKULMM: Infoprint Color 130 Plus * * $02=OW44363, HPRF320,000920,BLDCWJ: Line mode migration * * $03=OW47659, HPRF320,010104,BDKUMLC: Reship only - no updates. * * $04=OW46911, HPRF320,000515,BLDCWJ : Media Fidelity support * * $05=OW50901, HPRF320,010821,BDKURLD: Retry some INITAPI failures * 03561990 * $06=OW50390, HPRF320,010927,BDKUSCM: 2D barcode support * 03561990 * $07=OW50960, HPRF320,011009,BDKULMM: Abend024 RC0C02 due to zero * 03561990 * msg id 029001..01 * * $08=OW47709, HPRF320,011125,BDKULMM: Support for punch NACK * 03561990 * $09=OW52112, HPRF320, 011108,BDKURLD: Side sensitivity support * 03561990 * $10=OW54627, HPRF330,020508,BDKURLD: Add ERRNO to APS6501I * 00400000 * $11=OW54412, HPRF320, 020430,BDKUBMM: CCM Roll down from 3.3.0 * 03561990 * $12=OW56201, HPRF320,020924,BDKULD : IM1 to IOCA, add * 03561990 * message APS2062I * * $13=OW57569, HPRF320, 021218,BDKUSCM: CCM Roll down from 3.3.0 * 03561990 * DAPARs * * * **** END OF SPECIFICATIONS ******************************************* All of the following changes are for the PSF for OS/390 Diagnosis (G544-5623-02). -----------CHANGES FOR OW44362---------------------------------- Chapter 3 Page 25 - FSA External Traces Add the following new sections after FSA Full Trace FSA Limit Trace: A limit trace is the second largest FSA external trace. It is a shortened version of the FSA full external trace. All PSF subcomponents and all input records and output printer commands are traced however the data on input records, output printer commands, and TCP/IP buffers for object container and IOCA image resources has been shortened to 32 bytes per record. This trace is best used when the job you are trying to print contains large object container and IOCA image resources. FSA IPDS Trace: An IPDS trace contains only the output printer commands (the IPDS structured fields). It is used when microcode support requires a trace. page 26, Understanding the Impacts of Tracing, add a new paragraph after the last one under DASD Requirements: If the print job contains large object container or IOCA image resources a full trace is most likely too large to store. In a full trace, each resource is entirely traced each time it is sent to the printer. For these types of print jobs, it is recommended that you use the FSA limit trace, which does not trace all of the data for object container and IOCA image resources. Chapter 4 Page 29 - Determining the Kind of Trace You Want Replace the following bullets in the list: 1st bullet - If the problem is related to page repositioning during the printing of a data set, request an FSA full trace or an FSA limit trace if the job you are running contains large object container or IOCA image resources. 2nd bullet - If the problem is related to incorrect handling of the JES spool, request an NST trace and an FSA full trace. If the job you are running contains large object container or IOCA image resources, then request an FSA limit trace instead of an FSA full trace. 4th bullet - If the the problem is related to a PSF abend, request an internal trace and, if possible, an FSA full trace. If the job you are running contains large object container or IOCA image resources, then request an FSA limit trace instead of an FSA full trace. 5th bullet - If the problem is related to printer errors or to incorrect processing of a data set, request an FSA full trace. If the job you are running contains large object container or IOCA image resources then request an FSA limit trace instead of an FSA full trace. 6th bullet - If the problem cannot be recreated with an FSA full trace or an FSA limit trace, try directing ... Page 30 - Table 7. Methods of Starting PSF Traces Add a row between FSA component and FSI: column 1 = FSA Limit column 2 through column 4 = x column 5 leave blank Add another row after the above new row: column 1 = FSA IPDS column 2 through column 4 = x column 5 leave blank Page 33 - Table8. Specifying Trace Parameters in the Printer Inventory (continued) Under the PIDU column at the second row (trace-mode), add at the end the following Values: limit ipds Under the ISPF Panel column at the second row (Trace mode), add at the end the following Values: 5= Limit 6= IPDS Under the Description column in the second row add the following at the end: LIMIT A shortened FSA external trace is started along with an internal trace. IPDS An FSA IPDS trace is started along with an internal trace. Change the Note to the following: Note: You must specify the FSA trace dsname parameter when the trace mode is SYNC, FULL, LIMIT, or IPDS. Otherwise, you might receive an error message and the trace is not started. Under the Description column in the third row change the second sentence to read: This allocation occurs only if the trace mode is INTERNAL, SYNC, FULL, LIMIT, or IPDS. Page 35 at the top of the page add two new type values after INTR LIMIT Specifies a shortened FSA external trace. IPDS Specifies an FSA IPDS external trace. Page 38 - Under Syntax of the PSF Operator Interface Command In the FORMAT= parameter change IGTF to GTF. Replace the MODE= statement with the following: Ý,MODE={NOTIFY | FULL | SYNC | INTR | LIMIT | IPDS}¨ ------ Page 39 In the middle of the page where is says "The four optional ..." replace the MODE= statement with the following: ÝMODE={NOTIFY | FULL | SYNC | INTR | LIMIT | IPDS}¨ ---- Page 40, add the following after Figure 21 LIMIT Specifies that a shortened FSA external trace is to be started. An internal FSA trace is also started, along with an internal PPCC trace for SNA-attached printers. MODIFY FSSname,TRACEON,,MODE=LIMIT Figure ##a. Specifying a Limit External Trace IPDS Specifies that an FSA external trace of only the output printer commands is to be started. An internal FSA trace is also started, along with an internal PPCC trace for SNA-attached printers. MODIFY FSSname,TRACEON,,MODE=IPDS Figure ##b. Specifying an IPDS external trace. pg 42 Under Examples of Starting Various Traces, add two new bullets to the end of the list: o FSA limit trace o FSA IPDS trace Page 49 Add the following before the Stopping a Trace section Starting an FSA Limit External Trace at PSF Initialization To start an FSA limit external trace at PSF initialization and direct its output to a data set called PSF.FSATRC, do one of these: * In the Printer Inventory: 1. Specify a trace mode of LIMIT 2. Specify an FSA trace data set name of PSF.FSATRC. Allocate at least 25 cylinders for the trace data set. See Table 8 on page 32 for a description of the trace mode and FSA trace data set name parameters. * In the PSF startup procedure: 1. Specify TRACE=YES on the PRINTDEV statement. TRACE=YES is the default. 2. Specify PARM=(,LIMIT) on the EXEC statement. 3. Include a DD statement for a new DSN containing the PSF limit trace (see Figure ##c). Allocate at least 25 cylinders for the trace data set. //PRT2 DD DSNAME=PSF.FSATRC,DISP=OLD . . . //PRT2 CNTL PRINTER 2 DEFINITION //PRT2 PRINTDEV // TRACE=YES . . . //PRT2 ENDCNTL Figure ##c. Starting an FSA Limit External Trace at PSF Initialization. FSA limit external tracing begins when the printer FSA is initialized. Starting an FSA Limit External Trace Dynamically. You can start an FSA limit external trace and direct its output to either a PSF-owned trace data set or to a GTF trace data set. Using a PSF-Owned Trace Data Set: To start an FSA limit external trace dynamically and direct its output to a data set called PSF.FSATRC, perform these steps: 1. Do one of these: * In the Printer Inventory: a. Specify a trace mode of INTERNAL. b. Specify an FSA trace data set name of PSF.FSATRC. See Table 8 on page 32 for a description of the trace mode and FSA trace data set name parameters. * In the PSF startup procedure: a. Specify either TRACE=NO or TRACE=YES on the PRINTDEV statement. IBM recommends specifying TRACE=YES so that an internal trace is started at PSF initialization. TRACE=YES is the default if you omit the TRACE parameter. b. Specify PARM=(,INTR) on the EXEC statement. INTR specifies that only an internal trace will start at PSF initialization. INTR is the default if you omit the PARM parameter. c. Include a DD statement in the PSF startup procedure to define the data set to receive the trace output. Figure ##d shows the statement for printer name PRT2. //PRT2 DD DSNAME=PSF.FSATRC,DISP=OLD . . . //PRT2 CNTL PRINTER 2 DEFINITION // TRACE=YES . . . //PRT2 ENDCNTL Figure ##d. Specifying the PSF-owned Data Set 2. Start the printer FSA with the START command. 3. Type a PSF operator interface command. Figure ##e on page ## shows the command for an FSSname of FSS5. MODIFY FSS5,TRACEON,PRT2,MODE=LIMIT Figure ##e. A PSF Operator Interface Command for an FSSname of FSS5. FSA limit external tracing begins when the FSA is idle, or at the next data set boundary. Using the GTF Trace Data Set: The directions for using a GTF trace data set for an FSA limit external trace are exactly the same as for a full external trace. Refer to Using the GTF Trace Data Set on page 46 for more information. Add two additional examples right after the one for FSA limit external traces: Starting an FSA IPDS External Trace at PSF Initialization Same as Starting an FSA Limit External Trace at PSF Initialization except that every instance of limit is replaced by IPDS. Starting an FSA IPDS External Trace Dynamically Same as Starting an FSA Limit External Trace Dynamically except that every instance of limit is replace by IPDS. Add the following new messages to the Message-to-Module Cross-Reference in Appendix A: APS1009I APSPPDVP APS2020I APRMSGEX APS2021I APRMSGEX APS2022I APRMSGEX APS2023I APRMSGEX APS2024I APRMSGEX APS2025I APRMSGEX APS2026I APRMSGEX APS2027I APRMSGEX APS2028I APRMSGEX APS2029I APRMSGEX APS2030I APRMSGEX APS2032I APRMSGEX APS2035I APRDOCEX APS2551I APSEATCD, APSEMSG APS2552I APSEMSG APS2553I APSEMSG APS2554I APSEMSG APS2555I APSEMSG APS2556I APSEMSG APS2557I APSEATCD APS2558I APSEATCD APS2559I APSEATCD APS2560I APSEMSG APS2564I APSEMSG APS3501I APSRIDOR, APSMDOR APS3502I APSRMDOR APS3503I APSRIDOR, APSRMDOR APS3504I APSRIDOR, APSRMDOR APS3505I APSRIDOR APS3506I APSRLDOR APS3507I APSRLDOR APS3508I APSRMDOR APS3509I APSRMDOR, APSRMOVL APS3510I APSRMDOR, APSRMOVL Add the following new reason codes to the table in Appendix C: X'01240400' A preload repositioning request. APSPPDVP X'04050400' A preload repositioning request. APSPDDS X'07804804' Include request is for unsupported APSRIDOR DOR. X'07804806' Attempted Exit 7 resource APSRIDOR substitution is not valid. X'07200400' Could not activate DOR. APSRLDOR X'07404404' Map request is for unsupported APSRMDOR data object resource. X'07404408' Substitution not valid for DOR. APSRMDOR X'0740440C' IOCA specified as OC. APSRMDOR X'08090106' Printer does not support Toner APRDOCEX Saver Triplet. X'08140149' OID length on BR, MDR, BIM, BOC APRMSGEX or IOB FQN triplet is greater than 129 bytes. X'08140150' X'BE' triplet on MDR repeating APRMSGEX group in OEG but no X'DE'. X'08140151' A secondary resouce on an IOB is APRMSGEX not mapped in the AEG. X'08140152' Bad FQN format on SF. APRMSGEX X'08140153' Found X'84' or X'CE' triplet on APRMSGEX MDR in OEG. X'08140154' More than 1 FQN per repeating APRMSGEX group on MDR. X'08140155' MDR specifies same resource group APRMSGEX more than once in an environment group. X'08140156' MDR cannot map same reference APRMSGEX than once in an environment group. X'08140157' Printer does not support download APRMSGEX of IOCA object. X'08140158' OID mismatch has occurred. APRMSGEX X'08140159' Secondary resource requested but APRMSGEX printer does not support DORE command. X'08140356' PSF or printer does not support APRMSGEX this resource as a hard resource. X'08170400' A preload repositioning request. APRESGEX Update the following existing reason code in the table in Appendix C: X'08140125' The CCM detected a mapping option APRMSGEX value that is not valid or unsupported in a Map Object structured field (MIO, MGO, MBO, MCD) or in an IOB Structured field with a bad mapping option triplet. -----------CHANGES FOR OW44363---------------------------------- 1. Change Table 9 on page 66 to add the following. APS7002I APSUEXIT 2. Change PSF Reason Code table on page 72 to add the following. X'04052110' Insufficient virtual storage was APSDDS available for buffering of a line mode migration pagedef. 3. On Figure 17 on page 38 change the COMP part to the following: Ý,COMP={ ALL | CCM | DEVM | DOCP | ERRM | EXIT | JCLM | LASI | LMC | LMM | MSGM | PPCC | PPQM | PPWTR | SRM | STRM | TCPIP }¨ LEGEND: Ý = LEFT BRACKET ¨ = RIGHT BRACKET 4. On Page 41 add the following between LMC and MSGM: LMM Line-mode migration 5. On page 41 add the following between SRM and TCP: STRM Storage Manager 6. On page 41 change TCP to TCPIP -----------CHANGES FOR OW46911---------------------------------- 1. Add the following new messages to the Message-to-Module Cross-Reference table: APS361I APRMSGEX APS865I APSESNTB 2. Add the following new reason code to the PSF Reason Codes table: X'08140230' Input bin not supported or not enabled. APRMSGEX -----------CHANGES FOR OW50901---------------------------------- 1. On page 66 add the following to Table 9. APS6505I APSNLINK -----------CHANGES FOR OW50390---------------------------------- 1. Add the following new messages to the Message-to-Module Cross-Reference table: APS2038I APRMSGEX APS2567I APSESNTB APS2568I APSESNTB APS2569I APSESNTB APS2570I APSESNTB APS2571I APSESNTB APS2572I APSESNTB APS2573I APSESNTB APS2574I APSESNTB APS2575I APSESNTB APS2576I APSESNTB APS2577I APSESNTB APS2578I APSESNTB APS2579I APSESNTB APS2580I APSESNTB 2. Add the following new reason code to the PSF Reason Codes table: X'08140357' Bar code too big for output buffer. APRMSGEX -----------CHANGES FOR OW50960---------------------------------- Add the following new message to the Message-to-Module cross-reference table on pg 65: APS2582I APSESNTB -----------CHANGES FOR OW47709---------------------------------- Add the following new message to the Message-to-Module cross-reference table on pg 65: APS2549I APSESNTB APS2550I APSESNTB APS2561I APSESNTB APS2562I APSERRM -----------CHANGES FOR OW52112---------------------------------- 1. Add the following new messages to the Message-to-Module cross-reference table: APS1500I APSDDOC APS1501I APSDDOC APS2058I APRMSGEX APS2059I APRMSGEX 2. Add the following new reason code to the PSF Reason Codes table: X'08140277' Printer or input bin number specified APRMSGEX for duplex cannot handle duplex X'08140278' Input bin number cannot be found or is APRMSGEX disabled -----------CHANGES FOR OW54627---------------------------------- 1. Add the following to the "Message-to-Module Cross-Reference" table. APS6510I APSCSNA -----------CHANGES FOR OW54412---------------------------------- 1. Remove the following from the Message-to-Module cross-reference table: APS356I APRMSGEX 2. Remove the following reason code from the PSF Reason Codes table X'08140339' In an LND ... were not specified for APRMSGEX the LND or RCD 3. Add the following new messages to the Message-to-Module cross-reference table: APS2041I APRMSGEX APS2060I APRMSGEX APS2046I APRMSGEX 4. Add the following new reason codes to the PSF Reason Codes table: X'08140358' Input data being used for a variable APRMSGEX resource name in an LND or RCD is double-byte data. X'08140279' This release of PSF does not support APRMSGEX the medium collection finishing function. X'08140365' XML data formatting was requested by APRMSGEX the page definition but this version of PSF doesn't support XML data. -----------CHANGES FOR OW56201----------------------------------- Add the following new message to the Message-to-Module Cross-Reference table: APS2062I APRIPSEX -----------CHANGES FOR OW57569---------------------------------- 1. Add the following new message to the Message-to-Module cross-reference table: APS2070I APRMSGEX 2. Add the following new reason code to the PSF Reason Codes table: X'08140280' This release of PSF does not support APRMSGEX the UP3i finishing function.