**** START OF SPECIFICATIONS ***************************************** 00010000 * * 00020000 **** MODULE NAME = APSGAPGU * 00030000 * * 00040000 **** COMP(APS) PROD(PSF) : RELEASE 2.2.0 * 00050000 * * 00060000 **** DESCRIPTIVE NAME = PSF/MVS APPLICATION PROGRAMMING GUIDE UPDATES* 00070000 * * 00080000 **** STATUS = VERSION 2, RELEASE 2, LEVEL 0 * 00090000 * * 00100000 **** FUNCTION = * 00110000 * * 00120000 * THIS MODULE CONTAINS ALL OF THE UPDATES TO THE PSF/MVS * 00130000 * APPLICATION PROGRAMMING GUIDE SINCE THE LAST PUBLISHED * 00140000 * VERSION OF THE MANUAL. * 00150000 * * 00160000 * THE UPDATES ARE PUT IN THE SAME FORMAT AS THEY WERE BEING * 00170000 * PUT IN THE DOC ++HOLDS. * 00180000 * * 00190000 * EACH TIME A NEW APAR HAS UPDATES THE CHANGE ACTIVITY WILL * 00200000 * BE UPDATED AND A NEW SECTION WILL BE ADDED TO THE END OF THIS * 00210000 * MODULE PRECEDED BY A LINE THAT DENOTES THE APAR NUMBER. * 00220000 * * 00230000 * DO NOT GO PAST COLUMN 64 WITH YOUR DOC CHANGES. THE END OF * 00240000 * THE DASHED LINES WITH YOUR APAR NUMBER IN THE TEXT INDICATE * 00250000 * COLUMN 64. * 00260000 * * 00270000 **** RESTRICTIONS * 00280000 * * 00290000 * DO NOT EDIT OR UPDATE THIS FILE ON SAMPLIB AS THE * 00300000 * NEXT APAR THAT CHANGES THIS MODULE WILL DO A TOTAL REPLACE * 00310000 * OF IT THUS OVERLAYING YOUR CHANGES. IF YOU WISH TO MAKE * 00320000 * CHANGES TO THIS MODULE THEN DO IT IN YOUR OWN COPY OF THIS * 00330000 * MODULE. * 00340000 * * 00350000 * *** CHANGE ACTIVITY = * 00360000 * $00=LAPS0006, HPRF220, 970130, BDKURLD: INITIAL VERSION * 00370000 * $01=OW24771 , HPRF220, 970131, BDKURLD: Set Media Size support * 00380000 * $02=OW24868 , HPRF220, 970207, BDKUELJ: PRTERROR support * 00390000 * $03=OW19864 , HPRF220, 970207, BDKUSCM: CCM New Function * 00400000 * $04=OW24057 , HPRF220, 970213, BDKUSCM: MODCA IOB support * 00410000 * $05=OW26871 , HPRF220, 970609, BDKUSCM: SOSI3 support * 00420000 * $06=OW28050 , HPRF220, 970703, BDKUSCM: AE, recompile only * 00430000 * $07=OW22894 , HPRF220, 970327, BDKULD : Color Mapping Tables * 00440000 * $08=OW27622 , HPRF220, 970903, BDKULMM: Multiple Resolution * 00450000 * $09=OW29241 , HPRF220, 970917, BDKUSCM: Relative Print Line * 00460000 * $10=OW27623 , HPRF220, 971014, BDKUELJ: New OUTPUT keywords * 00470000 * $11=OW29993 , HPRF220, 971209, BDKULMM: Don't capture inline or * 00480000 * userlib resources * 00490000 * $12=OW31424 , HPRF220, 980128, BDKURLD: Support measurement units * 00500000 * from 1 to 32767 per 10 in. * 00510000 * $13=OW31717 , HPRF220, 980310, BDKUELJ: Inhibit repositioning * 00520000 * $14=OW33942 , HPRF220, 980630, BDKURLD: RPM & DPF support * 00530000 * $15=OW24360 , HPRF220, 980828, BDKULMM: Finisher Support * 00540000 * $16=0W36168, HPRF220, 990312, BDKURLD: Specify PRMODE via * 00550000 * exit 07 * 00560000 * $17=0W39987, HPRF220,990804,BDKULD: APSRCF30 - DBCS warning * 00550000 * $18=OW41705, HPRF220,991104,BLDCWJ: loop when small page @18A* * length set at printer @18A* * * 00570000 **** END OF SPECIFICATIONS ******************************************* 00580000 00590000 All of the following changes are for Print Services 00600000 Facility/MVS Application Programming Guide Version 2, 00610000 Release 2.0 (S544-3673-03). 00620000 00630000 -----------CHANGES FOR OW24771---------------------------------- 00640000 00650000 1. On page 41 in Figure 22 "AFP Parameters in JCL", add: 00660000 00670000 FORMLEN=xx.yyyIN|xx.yyyCM 00680000 00690000 2. On page 53, preceeding the description of FORMS=, add: 00700000 00710000 FORMLEN=xx.yyyIN|xx.yyyCM 00720000 Specifies the paper length in inches or in centimeters. The 00730000 numeric value may contain up to two digits and up to three 00740000 digits following the decimal point. The units must be 00750000 specified as either IN for inches or CM for centimeters. 00760000 00770000 If this keyword is not specified, the printer's default 00780000 paper length will be used. If the printer does not 00790000 support the Set Media Size command, the FORMLEN keyword 00800000 is ignored. 00810000 00820000 This keyword should be used when you wish to change the 00830000 paper length at the printer (changing the physical paper) 00840000 without reconfiguring the printer. 00850000 00860000 -----------CHANGES FOR OW24868---------------------------------- 00870000 00880000 1. On page 41, 00890000 in Figure 22, AFP Parameters in JCL, add the PRTERROR 00900000 parameter: 00910000 00920000 PRTERROR = HOLD|QUIT|DEFAULT 00930000 00940000 2. On page 58 following the description of PRMODE, add 00950000 00960000 PRTERROR = HOLD|QUIT|DEFAULT 00970000 Specifies the disposition of the print data set to be used 00980000 if an error occurs during printing for which PSF terminates 00990000 the data set. 01000000 Note: Your system programmer must enable the use of PRTERROR 01010000 in the initialization statement (PRINTDEV) for PSF. 01020000 01030000 Note: The disposition specified on PRTERROR will NOT be used 01040000 for the following conditions: 01050000 - PRTERROR has not been allowed on the initialization 01060000 statement (PRINTDEV) for this printer. 01070000 - Data sets put on hold by PSF Installation exits. 01080000 - Errors which result in a PSF abend. 01090000 - Errors in Direct Printing Mode. 01100000 - When Mandatory Print Labeling is active. 01110000 01120000 HOLD 01130000 specifies that if a terminating error occurs during 01140000 printing, the data set will be held on the JES spool 01150000 until it is released by the system operator. 01160000 QUIT 01170000 specifies that PSF will release the data set complete 01180000 even if a terminating error occurs during printing. 01190000 JES will then dispose of the data set as if printing 01200000 had completed successfully. 01210000 For JES2, the data set will be handled according to 01220000 the OUTDISP value associated with the data set. 01230000 For JES3, the data set will be deleted from the spool. 01240000 DEFAULT 01250000 specifies that the standard PSF action will be taken if 01260000 a terminating error occurs during printing. 01270000 This is the default. 01280000 01290000 -----------CHANGES FOR OW19864---------------------------------- 01300000 01310000 1. On page 9, remove the note about converting double dot images 01320000 at the bottom of the section on IM images. 01330000 01340000 2. On page 33, right before the section on "Object Container 01350000 "Resource, add a new section called Testing Overlays & 01360000 make it the same heading level as Using Overlays on page 32. 01370000 01380000 Testing Overlays 01390000 01400000 To make the testing of overlays easier, PSF/MVS allows an 01410000 overlay to be submitted as print data. To do this, in the job 01420000 submission JCL, the overlay name is specified as the data set 01430000 name. The overlay will be treated as a page. Only a single 01440000 overlay at a time can be printed in this manner. 01450000 01460000 -----------CHANGES FOR OW24057---------------------------------- 01470000 01480000 1. On page 17, "PSF Resources": 01490000 First bulleted list, add after last bullet: 01500000 01510000 MODCA IOCA, GOCA, and BCOCA resources 01520000 01530000 2. On page 17, "PSF Resources": 01540000 Second bulleted list, "Print data sets:" after "-page segments" 01550000 01560000 MODCA IOCA, GOCA, and BCOCA resources 01570000 01580000 3. On page 27, add a new paragraph after the third paragraph 01590000 under the Page Segments section: 01600000 01610000 Page segments included via an Include Object (IOB) structured 01620000 field must be MODCA page segments. MODCA page segments 01630000 consist of image (IOCA), graphic (GOCA), or bar code (BCOCA) 01640000 data. 01650000 01660000 4. On page 28, add a new paragraph after the third paragraph 01670000 under the Using Page Segments section: 01680000 01690000 Page segments included via an Include Object (IOB) structured 01700000 field are always soft. This is because the information in 01710000 the object environment group must be changed for the override 01720000 values specified in the IOB. 01730000 01740000 5. On page 29, before "Overlays" add: 01750000 01760000 MODCA Resources 01770000 The MODCA resources are IOCA, BCOCA and GOCA and are 01780000 included in the page segment library. The BCOCA is used 01790000 to describe and generate bar code symbols, the GOCA is 01800000 used to represent pictures generated by a computer, 01810000 commonly referred to as computer graphics, and the IOCA 01820000 is used to represent image information such as scanned 01830000 pictures. With the addition of these resources to the 01840000 page segment library, the page segment library will 01850000 now contain multiple resource types. 01860000 Since PSF does not enforce a prefix for the 8-character 01870000 resource name, you should define a naming convention 01880000 that identifies each type of resource in the page 01890000 segment library. 01900000 IBM recommends a two character prefix: 01910000 B1 for BCOCA resources. 01920000 G1 for GOCA resources. 01930000 I1 for IOCA resources. 01940000 S1 for Page Segment resources 01950000 01960000 6. On page 33, change the section called Testing Overlays to 01970000 the following: 01980000 01990000 Testing Overlays and Page Segments 02000000 02010000 To make the testing of overlays and page segments easier, 02020000 PSF/MVS allows an overlay or page segment to be submitted as 02030000 print data. To do this, in the job submission JCL, the overlay 02040000 or page segment name is specified as the data set name. The 02050000 overlay or page segment will be treated as a page. Only a 02060000 single overlay or page segment at a time can be printed in this 02070000 manner. 02080000 02090000 Caution: printing of page segments that have text (PTOCA) 02100000 included will have unpredictable results. The page segment 02110000 does not contain enough information about the font. Therefore, 02120000 you may get message APS818I posted or you may get your text 02130000 printed with an incorrect font causing incorrect output. 02140000 02150000 7. On page 106, change the first paragraph under Printing Page 02160000 Segments to the following: 02170000 02180000 Page Segments can be printed as part of an overlay or can be 02190000 printed as part of the data by using the Include Page Segment 02200000 (IPS) or Include Object (IOB) structured field. The IPS and 02210000 IOB structured fields that name and position the page segment 02220000 are included as a record in the print data set. 02230000 02240000 8. On page 113, "Printing with Inline Resources" 02250000 First Paragraph, in last sentence, add after "page segments," 02260000 02270000 MODCA resources (IOCA, BCOCA, or GOCA), 02280000 02290000 02300000 -----------CHANGES FOR OW26871---------------------------------- 02310000 02320000 1. On page 57, PRMODE= section. 02330000 Change the "PRMOD=" line to: 02340000 02350000 PRMODE=SOSI1 | SOSI2 | SOSI3 | aaaaaaaa 02360000 02370000 2. On page 58, PRMODE= section. 02380000 Add the following description of the SOSI3 value after the 02390000 description of the SOSI2 value: 02400000 02410000 SOSI3 02420000 02430000 Specifies that the shift-in code is to be converted to 02440000 a Set Coded Font Local text control and 2 blanks. A 02450000 shift-out code is to be converted to a Set Coded Font 02460000 Local text control. 02470000 02480000 The data conversion that PSF makes for SOSI3 is described 02490000 in "Using Shift-Out, Shift-In (SOSI) Codes" on page 126. 02500000 02510000 3. On page 126, 'Using Shift-Out, Shift-In (SOSI) Codes' 02520000 section, second sentence of the first paragraph: 02530000 02540000 change the phrase "PRMODE=SOSI1 or PRMODE=SOSI2" to 02550000 "PRMODE=SOSI1, PRMODE=SOSI2 or PRMODE=SOSI3" 02560000 02570000 4. On page 126, add the following after the description of the 02580000 conversion for PRMODE=SOSI2: 02590000 02600000 The conversion for PRMODE=SOSI3 is as follows: 02610000 02620000 1. Each X'0E' is replaced with a MO:DCA structure that 02630000 contains a Set Coded Font Local text control for the 02640000 second font. 02650000 02660000 2. Each X'0F' is replaced with a MO:DCA structure that 02670000 contains a Set Coded Font Local text control for the 02680000 first font, followed by two blanks (X'4040'). 02690000 02700000 5. On page 126, delete the 1 sentence paragraph (second from the 02710000 bottom of the page) that starts off "The difference between 02720000 these conversions...". 02730000 02740000 6. On page 127, Note 3, first sentence, change to: 02750000 02760000 If your print job consists of multiple steps that alternate 02770000 between PRMODE=SOSI1, PRMODE=SOSI2 and PRMODE=SOSI3, JES2 02780000 and JES3 will reorder the steps to group all those with the 02790000 same PRMODE value together. 02800000 02810000 -----------CHANGES FOR OW22894----------------------------------@07A 02820000 02830000 1. On page 34, just before heading "Using Resources with the 02840000 Distributed Print Function (DPF) of PSF", add: 02850000 02860000 Color Mapping Table Resource (COLORMAP) 02870000 To exploit the capabilities of a color printer, you may choose 02880000 to specify a color mapping table resource. The color mapping 02890000 table resource allows colors specified in a source document 02900000 to be mapped to colors more suitable to the selected printer 02910000 without requiring changes to the application that generates 02920000 the document. 02930000 02940000 For information about color mapping table resources see 02950000 "InfoPrint Hi-Lite Color Application Design Reference", available 02960000 from your IBM marketing representative. For information about 02970000 creating color mapping table resources see PSF/MVS APAR OW25538 02980000 for the Color Mapping Table Utility. 02990000 03000000 IBM recommends a prefix of M1 for color mapping table resources. 03010000 03020000 2. On page 37, add this bullet to the bulleted list: 03030000 03040000 o Specify the color mapping table object container resource to be 03050000 used when you send AFP output to a color printer. 03060000 03070000 3. On page 39, add item 13 to "PAGE-PRINTER DEFAULTS FORM": 03080000 03090000 13. COLORMAP = ___M1RESET_______ (color printer only) 03100000 03110000 4. On page 41, Figure 22, add: 03120000 03130000 COLORMAP=membername 03140000 03150000 5. On page 45, just prior to COMSETUP=membername, add: 03160000 03170000 COLORMAP=membername 03180000 Specifies the member name (from 1 to 8 alphanumeric or national 03190000 characters) of the object container for the color mapping table 03200000 resource. The full member name must be specified; PSF will not 03210000 add a prefix. The first character cannot be numeric. IBM 03220000 recommends a prefix of M1 for color mapping table resources. 03230000 PSF uses the COLORMAP parameter only when sending output to a 03240000 printer that supports color mapping table resources. 03250000 03260000 EXAMPLE 03270000 03280000 Following is an example of JCL in which the COLORMAP parameter 03290000 is specified in the OUTPUT statement for data to be printed on 03300000 a printer that supports color mapping tables. 03310000 03320000 //OUTPUT1 OUTPUT DEST=name,FORMDEF=fdefname,PAGEDEF=pdefname, 03330000 // COLORMAP=membername 03340000 //DD1 DD SYSOUT=q,OUTPUT=(*.OUTPUT1) 03350000 03360000 Check with your system programmer about which DEST is available 03370000 for printing to a printer that supports color mapping tables. 03380000 03390000 Using Color Mapping Table Resources from a User Library: 03400000 03410000 You can instruct PSF to select a color mapping table resource 03420000 from a user library rather than a system library assigned to 03430000 PSF. To use a color mapping table resource from a user library, 03440000 do the following: 03450000 03460000 o Reference the user library containing the color mapping table 03470000 resource in the JCL OUTPUT statement. For details, see the 03480000 description of the USERLIB parameter on page 60. 03490000 03500000 o Specify the name of the color mapping table resource in the 03510000 COLORMAP parameter. 03520000 03530000 Using Inline Color Mapping Table Resources: 03540000 03550000 To use a color mapping table resource inline, do the following: 03560000 03570000 o Include an inline color mapping table resource in the print 03580000 data set. 03590000 03600000 o If you specify the COLORMAP parameter in your JCL, the name 03610000 of the inline color mapping table resource must match the 03620000 COLORMAP name specified in the JCL, or else you must specify 03630000 COLORMAP=DUMMY in the JCL. 03640000 03650000 o If you do not specify the COLORMAP parameter in your JCL, PSF 03660000 selects the first inline COLORMAP from the print data set. 03670000 03680000 o If a color mapping table resource is included inline with the 03690000 data, the data set must be identified as containing carriage 03700000 control characters. If the length of the records in the color 03710000 mapping table resource is less than or equal to the 03720000 logical-record length defined for the data set, you can specify 03730000 fixed-length records for the record format. If the length of 03740000 the records in the color mapping table resource is greater than 03750000 the logical-record length defined for the data set, you must 03760000 specify variable-length records. For variable-blocked records 03770000 with ANSI carriage control characters, use VBA for the record 03780000 format. For variable-blocked records with machine carriage 03790000 control characters, use VBM for the record format. 03800000 03810000 You can include more than 1 inline color mapping table resource 03820000 in a print data set and you can change the name in the 03830000 COLORMAP parameter in the JCL on different printing jobs to 03840000 test different color mapping table resources. If, however, the 03850000 name specified in the COLORMAP parameter in the JCL does not 03860000 match any names of inline color mapping tables resources, PSF 03870000 will look for the color mapping table resource in the user 03880000 library or the object container library. 03890000 03900000 6. Page 46, change second bullet under "Using Inline Microfilm Setup 03910000 Resources:" to: 03920000 03930000 o If you specify the COMSETUP parameter in your JCL, the name 03940000 of the inline microfilm setup resource must match the COMSETUP 03950000 name specified in the JCL, or else you must specify 03960000 COMSETUP=DUMMY in the JCL. 03970000 03980000 03990000 7. Page 60, replace NOTE under "USERLIB=('libname1',...)" with: 04000000 04010000 Note: Some AFP resources have naming conventions with reserved 04020000 prefixes. For example, the following AFP resource name prefixes 04030000 are reserved: 04040000 04050000 o C0 for 240/300 pel character sets (except 3800) 04060000 o C1-C9 and CA-CG for 3800 character sets 04070000 o F1 for form definitions 04080000 o O1 for overlays 04090000 o P1 for page definitions 04100000 o T1 for code pages 04110000 o X0 for 240/300 pel coded fonts (except 3800) 04120000 o X1-X9 and XA-XG for 3800 coded fonts 04130000 04140000 Furthermore, IBM recommends the following prefixes to the names 04150000 of the indicated resource types: 04160000 04170000 o CZ for outline character sets 04180000 o H1 for microfilm setup object containers 04190000 o M1 for color mapping table object containers 04200000 o S1 for page segments 04210000 o XZ for outline coded fonts 04220000 04230000 8. Page 61, section "Using Inline Resource", second paragraph, 04240000 lines 5, change: 04250000 04260000 from - "form definition, a page definition, or a microfilm setup 04270000 resource" 04280000 to - "form definition, a page definition, a color mapping table 04290000 resource, or a microfilm setup resource" 04300000 04310000 9. Page 61-62, section "Using Inline Resource", second paragraph, 04320000 lines 6, 8, 10 12, and 14, change all occurrences: 04330000 04340000 from - "FORMDEF, PAGEDEF, or COMSETUP" 04350000 to - "FORMDEF, PAGEDEF, COLORMAP, or COMSETUP" 04360000 04370000 10. Page 66, Table 1, after "CLASS", add: 04380000 ________________________________________________________________ 04390000 | COLORMAP (none) | 04400000 |________________________________________________________________| 04410000 04420000 11. Page 89, add a bullet to end of bulleted list: 04430000 04440000 o "Specifying JCL parameters for Jobs using Color Mapping Table 04450000 Resources" on page 118 04460000 04470000 12. Page 118, add new section to end of Chapter 4: 04480000 04490000 Specifying JCL parameters for Jobs using Color Mapping Table 04500000 Resources 04510000 04520000 When you send output to a printer that supports the color mapping 04530000 table resource, you may specify a color mapping table resource to 04540000 indicate color translations to the printer. The full name of the 04550000 color mapping table resource is coded in the COLORMAP parameter 04560000 of the OUTPUT JCL statement. You can code the COLORMAP parameter 04570000 on the OUTPUT JCL statement and/or it can be coded by the system 04580000 programmer on the PRINTDEV JCL statement. 04590000 04600000 If you do not code a COLORMAP parameter on your OUTPUT JCL 04610000 statement, PSF will use the default COLORMAP parameter that 04620000 your system programmer specified in the PRINTDEV JCL statement. 04630000 If the COLORMAP parameter is not coded on the OUTPUT JCL 04640000 statement, and the COLORMAP parameter is not coded on the 04650000 PRINTDEV JCL statement, and a color mapping table resource is not 04660000 coded inline in the print data set, PSF will use a hard-coded 04670000 reset color mapping table resource (M1RESET). Basically, the 04680000 reset color mapping table resource is the absence of a color 04690000 mapping table resource in the printer. For information about 04700000 the reset color mapping table resource, see "InfoPrint Hi-Lite 04710000 Color Application Design Reference" (available from your IBM 04720000 marketing representative), or "Mixed Object Document Content 04730000 Architecture Reference" (SC31-6802-03). 04740000 04750000 The color mapping table resource specified on the COLORMAP 04760000 parameter must be in a PSF system object container library, 04770000 in a user library specified by the USERLIB parameter, or coded 04780000 inline as part of the print data set. You can create your own 04790000 color mapping table resource using the sample program provided 04800000 by IBM in PSF/MVS service for APAR OW25538 or you can use an 04810000 existing resource created by your system programmer (no color 04820000 mapping table resources are shipped with PSF/MVS). 04830000 04840000 This is an example of JCL in which the COLORMAP parameter is 04850000 specified in the OUTPUT JCL statement for application data sent 04860000 to a printer that supports color mapping table resources. IBM 04870000 recommends the prefix of M1 for the names of all color mapping 04880000 table resources. 04890000 04900000 //OUTPUT1 OUTPUT DEST=name,FORMDEF=fdefname,PAGEDEF=pdefname, 04910000 // COLORMAP=membername 04920000 //DD1 DD SYSOUT=q,OUTPUT(*.OUTPUT1) 04930000 04940000 Ask your system programmer which DEST has been set up for 04950000 sending AFP print data sets to a printer that supports color 04960000 mapping table resources. 04970000 04980000 13. Page 160, Insert an Appendix between Appendix D and Appendix E: 04990000 05000000 Appendix D-1. Color Device Considerations 05010000 05020000 With PSF/MVS APAR OW22894 you can exploit color mapping tables 05030000 for printers that support them. Besides this publication, there 05040000 are several other references that will be helpful. 05050000 05060000 o "PSF/MVS: System Programming Guide" 05070000 05080000 o "Mixed Object Document Content Architecture Reference", 05090000 SC31-6802-3 05100000 05110000 o "InfoPrint Hi-Lite Color Application Design Reference", 05120000 available from your marketing representative 05130000 05140000 o "InfoPrint 4000 HC Introduction and Planning Guide", G544-5420 05150000 05160000 14. Page 167, Glossary, after "code point", add: 05170000 05180000 color mapping table. An architected MODCA object that is used to 05190000 map color values specified in a source color space to color values 05200000 specified in a target color space. This object is loaded into 05210000 printers that support the color mapping table. 05220000 05230000 05240000 -----------CHANGES FOR OW27622---------------------------------- 05250000 05260000 Chapter 1. Introducing Print Services Facility/MVS 05270000 05280000 pg 19 add the following new bullet to the list of form 05290000 definition controls: 05300000 o Font fidelity. If the font fidelity is set to STOP, PSF 05310000 will ensure the font used to format the data and the 05320000 font used to print the data have the same 05330000 resolution. If the font fidelity is set 05340000 to Do Not Stop, PSF will allow resolution and metric 05350000 substitutions. See the MO:DCA reference for more 05360000 information. 05370000 05380000 05390000 pg 26 add the following just prior to the last paragraph: 05400000 05410000 Obviously the host font that you use to print must be 05420000 supported by the printer. Some printers support only a 05430000 single resolution and metric technology raster font (e.g. 05440000 240 pel fixed-metric), some support outline fonts and a 05450000 single raster font resolution and metric technology 05460000 and some are manually configured 05470000 to support a single raster resolution at a time but can be 05480000 switched between two different raster resolutions. Now there 05490000 is printer support to accept multiple raster resolutions 05500000 and metric technology fonts at the same time. This function 05510000 is sometimes called Automatic or Auto resolution mode. 05520000 05530000 A PSF printer may have had only a single system library of fonts. 05540000 This may have contained outline fonts and a single resolution 05550000 of raster fonts. 05560000 Now PSF printer definitions for switchable and 05570000 Auto mode printers, can be set up with access to 05580000 multiple system font libraries (e.g. 240 pel, 300 pel and 05590000 default). If the printer only accepts resources at a single 05600000 resolution then the printer's resolution is used by PSF 05610000 to determine which system library to use. If the printer 05620000 accepts multiple resolutions you can tell PSF which raster 05630000 resolution to use in the following ways: 05640000 05650000 1) Your System Programmer can use the Resource Exit 05660000 (APSUX07) to specify a format resolution. 05670000 05680000 2) Format the MO:DCA data using an application that includes 05690000 the Font Resolution and Metric Technology triplet on 05700000 the MCF2 structured field. Two applications that 05710000 currently support this triplet are DCF/370 with 05720000 APAR PQ07945 and OGL/370 with APAR PQ07878. 05730000 See your application user's 05740000 guide or the MO:DCA Reference for more information. 05750000 05760000 3) Specify the RESFMT keyword on the OUTPUT statement. 05770000 RESFMT tells PSF what resolution raster fonts were used 05780000 to format the data. See "Specifying AFP Parameters in 05790000 the JCL" for more information. 05800000 05810000 4) You can just let PSF use the default system font library. 05820000 05830000 If the format resolution is specified in multiple places, 05840000 PSF uses the first non-zero value it finds in the list above. 05850000 05860000 MO:DCA has defined a Font Fidelity triplet (X'78') 05870000 to the Presentation Fidelity Control (PFC) structured 05880000 field in the form definition. 05890000 05900000 The Font Fidelity triplet is used to tell PSF what 05910000 to do if the font with the requested resolution is not 05920000 found. 05930000 05940000 The triplet has two settings: 05950000 05960000 o Stop presentation at the point of the first font- 05970000 resolution exception and report exception. 05980000 05990000 o Do not stop presentation due to font-resolution 06000000 exceptions. 06010000 06020000 PSF/MVS uses font fidelity to control two things: 06030000 06040000 o Whether the specified format resolution must match the 06050000 actual font resolution. 06060000 06070000 o Whether it is acceptable to activate a resident outline 06080000 font for a raster font. 06090000 06100000 06110000 If the font fidelity setting is set to Stop and a 06120000 format resolution was specified, PSF will check to 06130000 make sure the format resolution and the actual 06140000 resolution of the font match. If they do not 06150000 PSF will terminate the page and report the exception. 06160000 06170000 If the font fidelity setting is set to Do Not Stop, PSF 06180000 will not require the specified format resolution and the 06190000 actual font resolution to match. PSF will also allow a 06200000 resident outline font to be activated for a raster font. 06210000 06220000 Therefore if it is critical that your document prints 06230000 using the same resolution resources as were used when 06240000 it was formatted then specify font fidelity equals Stop 06250000 in your form definition. 06260000 06270000 If your document prints just fine at any resolution then 06280000 either specify font fidelity equals Do Not Stop in the 06290000 form definition or do not specify anything at all. The 06300000 default font fidelity setting for PSF is Do Not Stop. 06310000 06320000 06330000 pg 28 add a new paragraph to the end of the "Using Page Segments" 06340000 section: 06350000 06360000 PSF can now be set up with multiple system page segment 06370000 libraries. The three possible system libraries are 240 pel, 06380000 300 pel or a default library. The respective libraries 06390000 would contain page segments designed to print at 240 pel 06400000 resolution, 300 pel resolution or any resolution. If you 06410000 know that your page segment prints best at a certain 06420000 resolution then you should have the page segment stored 06430000 in that resolution system library and specify this 06440000 resolution to PSF. 06450000 There are several ways to specify the format resolution: 06460000 06470000 1) Your System Programmer can use the Resource Exit 06480000 (APSUX07) to specify a format resolution. 06490000 06500000 2) Specify the RESFMT keyword on the OUTPUT statement. 06510000 RESFMT tells PSF at what resolution the page segments 06520000 were formatted. See "Specifying AFP Parameters 06530000 in the JCL" for more information. 06540000 06550000 3) You can just let PSF use the default system page segment 06560000 library. 06570000 06580000 pg 32 add a new paragraph after the first paragraph under "Using 06590000 Overlays:" 06600000 06610000 PSF can now be set up with multiple system overlay 06620000 libraries. The three possible system libraries are 240 pel, 06630000 300 pel or a default library. The respective libraries 06640000 would contain overlays designed to print at 240 pel 06650000 resolution, 300 pel resolution or any resolution. If you 06660000 know that your overlay prints best at a certain 06670000 resolution then you should have this overlay stored in 06680000 that resolution system library and specify this 06690000 resolution to PSF. 06700000 There are several ways to specify the format resolution: 06710000 06720000 1) Your System Programmer can use the Resource Exit 06730000 (APSUX07) to specify a format resolution. 06740000 06750000 2) Specify the RESFMT keyword on the OUTPUT statement. 06760000 RESFMT tells PSF at what resolution the overlays were 06770000 formatted. See "Specifying AFP Parameters 06780000 in the JCL" for more information. 06790000 06800000 3) You can just let PSF use the default system overlay 06810000 library. 06820000 06830000 pg 37 add a new bullet to the list of JCL parameters: 06840000 06850000 o Specify the resolution at which the output was formatted. 06860000 06870000 pg 41 add a new AFP parameter for Figure 22: 06880000 06890000 RESFMT=P240|P300 06900000 06910000 pg 58 add a new keyword entry above the SEGMENT keyword entry: 06920000 06930000 RESFMT=P240|P300 06940000 06950000 Specifies the resolution at which the output was formatted. 06960000 PSF uses this information to choose the correct resolution 06970000 system library. 06980000 06990000 The format resolution can be specified in several ways. 07000000 PSF will use the first specified value that is not zero. 07010000 07020000 1) Your System Programmer can use the Resource Exit 07030000 (APSUX07) to specify a format resolution. 07040000 07050000 2) For fonts mapped in MO:DCA data the application may 07060000 specify the Font Resolution and Metric Technology 07070000 triplet on the MCF2 structured field. 07080000 See your application user's 07090000 guide or the MO:DCA Reference for more information. 07100000 07110000 3) The RESFMT keyword on the OUTPUT statement. 07120000 07130000 4) You can just let PSF use the default system library. 07140000 07150000 EXAMPLE 07160000 07170000 Specify the RESFMT keyword in the OUTPUT statement. 07180000 07190000 //OUT2 OUTPUT RESFMT=P240 07200000 //DD2 DD SYSOUT=class,OUTPUT=(*OUT2) 07210000 07220000 pg 66 add a new entry for RESFMT to Table 1 07230000 07240000 _____________________________________________________________ 07250000 | Output Parameter Equivalent Parameter on DD statement| 07260000 |____________________________________________________________| 07270000 | RESFMT (none) | 07280000 |____________________________________________________________| 07290000 07300000 pg 85, 2nd paragraph. Correct the first sentence to read: 07310000 "You can use the PPFA FONT command to select either raster 07320000 fonts or outline fonts." 07330000 07340000 pg 134 Insert a new chapter after Chapter 6 07350000 07360000 07370000 Chapter xx. Handling Job Streams that are Formatted at 07380000 Different Resolutions 07390000 07400000 07410000 Typically, production of printed data is a multiple 07420000 step process. An application first formats and spools 07430000 data for printing. Later, the data 07440000 is passed to a printer for presentation on paper. 07450000 07460000 In the past, printers printed at a single resolution 07470000 (pel density) and all the printers in the enterprise 07480000 printed at the same resolution. Jobs formatted with 07490000 resource libraries containing resources at that same 07500000 resolution as the printer. 07510000 07520000 Today, an enterprise may have printers with varied 07530000 resolution. Some printers print with a resolution of 07540000 240 pels per inch, some printers print with a resolution 07550000 of 300 pels per inch, some printers can switch between 07560000 resolutions, and to complicate matters new resolutions 07570000 for printers are being developed. 07580000 07590000 Furthermore, some jobs are dependent upon the resolution 07600000 of the resource libraries in use at the time the job was 07610000 formatted. If a job is formatted with resources of one 07620000 resolution and printed with resources with another 07630000 resolution, fidelity imperfections can occur. 07640000 07650000 In many cases, fidelity imperfections are not important. In 07660000 these cases, formatting with resources of one resolution and 07670000 printing with resources of a different resolution could be 07680000 acceptable. In other cases, perfect fidelity may be 07690000 required. 07700000 07710000 Some of the types of fidelity imperfections that can occur 07720000 from failing to format and print with the same resolution 07730000 resources are: 07740000 o data no longer exactly fits in a box on a form. 07750000 o columns for tabular data overlap or are spaced wider 07760000 then intended. 07770000 o right justified data may show a ragged right margin. 07780000 o minor typeface difference may be observed. 07790000 07800000 In the past, to deal with these complications in an 07810000 enterprise, printers were grouped by print resolution. 07820000 Using routing options and print queues specified in the 07830000 application, the application output got routed to a 07840000 compatible printer. 07850000 07860000 A better solution is provided with PSF/MVS APAR OW27622 07870000 and MVS APAR OW27295 where a single FSA can: 07880000 o have access to multiple resource libraries of the same 07890000 resource type but with different resolutions. 07900000 o accept information from the application indicating the 07910000 resolution used to format the application output. 07920000 o select the resource libraries with the correct 07930000 resolution to print the data. 07940000 o be given resource libraries to be used as default 07950000 resource libraries when the application does not 07960000 indicate what resolution was used to format the 07970000 application data. 07980000 o accept information from the data stream indicating how 07990000 to handle any mismatches between the resolution 08000000 specified when formatting and the resolution of the 08010000 resource found when printing. 08020000 o exploit printers that accept print data formatted at 08030000 multiple resolutions. 08040000 o exploit printers that allow manual switching of 08050000 print resolution, for example the InfoPrint 4000. 08060000 08070000 The following sections introduce the key concepts related 08080000 to printing at multiple resolutions and point to specific 08090000 sections with more details. The topics discussed are: 08100000 1) Multiple resolution printers. 08110000 2) Segmenting resource libraries for multiple resolution. 08120000 3) Specifying format resolution from the application. 08130000 4) Multiple resolution and installation exits 08140000 08150000 Multiple Resolution Printers 08160000 08170000 08180000 Two printer multiple resolution modes are now supported 08190000 by PSF/MVS. This support is for printers that: 08200000 1) can be manually switched from one resolution to 08210000 another (switchable resolution mode). 08220000 2) accept print data even though it was not formatted for 08230000 the particular resolution of the printer (automatic 08240000 or auto resolution mode). 08250000 08260000 Printers with Switchable Resolution Mode 08270000 08280000 With APAR OW27622 PSF/MVS has support for printers that can be 08290000 manually switched from one resolution to another. 08300000 08310000 Before this support, when PSF/MVS was attached to a printer 08320000 that could be switched from one resolution to another, the 08330000 following procedure was used: 08340000 o Purge the FSA for the printer 08350000 o Switch the printer to the new resolution 08360000 o Start a new FSA that points to resource libraries 08370000 compatible with the printers new resolution. 08380000 This required coordination for the stopping/starting of 08390000 PSF/MVS and for the switching of the printer resolution. 08400000 08410000 Now, with this support, a single FSA can be defined with 08420000 multiple specifications for resource libraries for fonts, 08430000 page segments and overlays. There can be a 240 pel JCL DD 08440000 statement, and/or a 300 pel JCL DD statement, and/or a 08450000 default JCL DD statement for each of these resource types. 08460000 08470000 When a printer is manually switched from one resolution to 08480000 another PSF will automatically start using the resource 08490000 libraries specified for the new printer resolution. 08500000 08510000 Printers operating in Switchable Resolution mode report to 08520000 PSF the resolution that they are currently switched to. If 08530000 a printer is switched to 300 pel resolution, it reports an 08540000 IPDS resolution of 300 pels to PSF. PSF will use this 08550000 resolution when selecting resource libraries for this 08560000 printer. 08570000 08580000 For more information on how to define these JCL DD 08590000 statements and an example start-up procedure refer 08600000 to Print Services Facility/MVS: System 08610000 Programming Guide. 08620000 08630000 Printers with Automatic or Auto Resolution Mode 08640000 08650000 PSF/MVS now supports printers operating in automatic or 08660000 auto resolution mode. 08670000 08680000 Printers with automatic mode print at a particular pel 08690000 density (for example 600 pels per inch) but will accept 08700000 resources at different resolutions, such as, 240 and 300 08710000 pels per inch. The printer then scales the resources 08720000 appropriately based on their resolution and metric 08730000 technology. 08740000 08750000 Printers operating in the Auto Resolution Mode report to 08760000 PSF the resolution of its print head (for example, 600 pel). 08770000 However, they also tell PSF that they accept other 08780000 resolutions. 08790000 08800000 In order to exploit this feature the PSF printer 08810000 definition must be set up 08820000 with access to all the different resolution resource 08830000 libraries for fonts, overlays and page segments. 08840000 Additionally, PSF must receive an indication of the 08850000 intended resolution when the print data was formatted. 08860000 If no intended resolution is given, PSF will use the 08870000 default JCL DD statement for that resource type. 08880000 08890000 For more information on how to define these JCL DD 08900000 statements and an example start-up procedure refer 08910000 to Print Services Facility/MVS: System 08920000 Programming Guide. 08930000 08940000 Segmenting Resource Libraries for Multiple Resolution. 08950000 08960000 08970000 Resource libraries are used during formatting of print 08980000 data and during the printing of the data. It may be 08990000 important that the resource libraries 09000000 specified to the print data formatting application match 09010000 the resource libraries specified to PSF when the data is 09020000 being printed. Failure to do this may result in 09030000 skewing of column alignment and of line endings when the 09040000 data is printed. 09050000 09060000 The following AFP resource types are affected by print 09070000 resolution: 09080000 09090000 o Fonts: raster fonts MUST match the printer resolution, 09100000 unless your printer has automatic resolution mode. Even 09110000 with automatic mode, it is generally preferable to use 09120000 a font that matches the resolution at which the document 09130000 was formatted. Outline fonts can print at any resolution, 09140000 but it may be preferable to use a raster font if the 09150000 document was formatted with raster fonts. 09160000 09170000 o Overlays: overlays contain text formatted with fonts, 09180000 and images created at specific resolutions. For this 09190000 reason, an overlay may print better at a specific printer 09200000 resolution. 09210000 09220000 o Page segments: most printers can scale page segments 09230000 to print at the resolution of the printer. However, the 09240000 image in a page segment prints best at the resolution 09250000 in which it was created. 09260000 09270000 09280000 Some enterprises may already have printers with different 09290000 print resolutions attached to PSF/MVS. Multiple JCL DD 09300000 statements may be present in the start-up procedure 09310000 defining particular sets of resources based on resolution. 09320000 For example: 09330000 09340000 //FONT01 DD DSN=SYS1.FONT3800 /* 3800 font library */ 09350000 //* 09360000 //FONT02 DD DSN=SYS1.FONTLIBB /* 240 pel raster fonts */ 09370000 // DD DSN=SYS1.FONTOLN /* Outline fonts */ 09380000 //* 09390000 //FONT03 DD DSN=SYS1.FONT300 /* 300 pel raster fonts */ 09400000 // DD DSN=SYS1.FONTOLN /* Outline fonts */ 09410000 09420000 In this case the FONT02 font library should be used when 09430000 formatting data for and printing data on a 240 pel 09440000 resolution printer. Likewise, the FONT03 font library 09450000 should be used for a 300 pel resolution printer. 09460000 09470000 Notice that a JCL DD statement for the same outline font 09480000 data set appears in the font library for 240 pel resolution 09490000 fonts and for 300 pel resolution fonts. This is because 09500000 the outline fonts are resolution independent and can be used 09510000 by a printer (that supports outline fonts) without regard 09520000 for the resolution of that printer. 09530000 09540000 To use multiple resolution capabilities of PSF/MVS it is 09550000 necessary to separate font libraries into separate font 09560000 libraries (JCL DD statements) one for the 240 pel raster 09570000 fonts and another for the 300 pel raster fonts. Outline 09580000 fonts can be specified in both libraries. 09590000 09600000 The same is true for overlay and page segment libraries. If 09610000 there are overlays and page segments that print better on 09620000 240 pel printers then separate them into a 240 pel overlay 09630000 or page segment library. Similarly, if some overlays and 09640000 page segments print better on 300 pel printers then separate 09650000 them into a 300 pel overlay or page segment libraries. 09660000 09670000 Separating the resource libraries by resolution allows you 09680000 to then define them to PSF/MVS through the PRINTDEV JCL 09690000 statement indicating the resolution of the resources in each 09700000 particular library. 09710000 09720000 For more information on how to define these JCL DD 09730000 statements and an example start-up procedure refer 09740000 to Print Services Facility/MVS: System 09750000 Programming Guide. 09760000 09770000 Specifying Format Resolution from the Application 09780000 09790000 In earlier discussions in this chapter it was pointed out 09800000 that multiple resolution printers can scale print data 09810000 formatted for particular resolution printer to another 09820000 resolution if the printer understands the intended 09830000 resolution for the print data. To do this, the print data 09840000 must be tagged with the format resolution. The format 09850000 resolution can be specified either in the JCL for the print 09860000 data or directly in the print data stream. 09870000 09880000 Note also, there is a companion parameter (Font Fidelity) 09890000 that PSF uses if there is a mismatch between the resolution 09900000 specified in the application and the resolution of the 09910000 resources. 09920000 09930000 Specifying Format Resolution in JCL 09940000 09950000 The RESFMT JCL keyword on the OUTPUT statement 09960000 indicates which resolution was used to format the job. For 09970000 more information on the RESFMT keyword see page 58. 09980000 09990000 Specifying Format Resolution in the Print Data Stream 10000000 10010000 Applications that generate Map Coded Font Format 2 (MCF2) 10020000 structured fields (such as DCF/370 with APAR PQ07945 or 10030000 OGL/370 with APAR PQ07878) can now add a font 10040000 resolution and metric technology triplet (X'84') in the 10050000 MCF2. This triplet tells PSF what resolution was used to 10060000 format this print data. For more information on the 10070000 triplet refer to the MO:DCA Reference, SC31-6802-4. For 10080000 more information on the support of the triplet for your 10090000 application refer to that application's documentation. 10100000 10110000 Specifying Font Fidelity in the Print Data Stream 10120000 10130000 MO:DCA has defined a Font Fidelity triplet (X'78') 10140000 to the Presentation Fidelity Control (PFC) structured 10150000 field in the form definition. The scope 10160000 of the PFC structured field is the 10170000 document controlled by the form definition that contains 10180000 the structured field. 10190000 10200000 The Font Fidelity triplet is used to specify the 10210000 exception continuation rules for the font exceptions 10220000 that are generated when the font referenced in the data 10230000 stream was found but is not available to PSF at the 10240000 specified resolution. 10250000 10260000 The triplet has two settings: 10270000 10280000 o Stop presentation at the point of the first font 10290000 resolution exception and report exception. 10300000 10310000 o Do not stop presentation due to font resolution 10320000 exceptions. 10330000 10340000 PSF/MVS uses font fidelity to control two things: 10350000 10360000 o Whether the specified format resolution must match the 10370000 actual font resolution. 10380000 10390000 o Whether it is acceptable to activate a resident outline 10400000 font for a raster font. 10410000 10420000 If the font fidelity setting is set to Stop and a 10430000 format resolution was specified, PSF will check to 10440000 make sure the format resolution and the actual 10450000 resolution of the font match. If they do not 10460000 PSF will terminate the page and report the exception. 10470000 10480000 If the font fidelity setting is set to Do Not Stop, PSF 10490000 will not require the specified format resolution and the 10500000 actual font resolution to match. PSF will also allow a 10510000 resident outline font to be activated for a raster font. 10520000 10530000 Therefore, if it is critical that your document prints 10540000 using the same resolution resources as were used when 10550000 it was formatted, specify font fidelity equals Stop in 10560000 the form definition. 10570000 10580000 If is acceptable to print the document at any resolution, 10590000 either specify font fidelity equals Do Not Stop in the 10600000 form definition or do not specify font fidelity in the 10610000 form definition. The default font fidelity setting for 10620000 PSF is Do Not Stop. 10630000 10640000 Multiple Resolution and Installation Exits 10650000 10660000 The PSF/MVS installation exit for Resource Management 10670000 (APSUX07) can be used to specify the format resolution 10680000 in a couple of ways. 10690000 1) The installation exit can establish a PSF/MVS default 10700000 format resolution with the initialization call (INIT). 10710000 2) The installation exit can set the format resolution 10720000 value for any or all print data sets with the begin data 10730000 set call (BDSC). 10740000 10750000 For more information about setting the format resolution 10760000 using the installation exit, refer to Print Services 10770000 Facility/MVS System Programming Guide.. 10780000 10790000 10800000 Sorting Out Format Resolution Specification 10810000 10820000 10830000 As can be seen from the discussions on multiple resolution 10840000 earlier in this chapter, the format resolution can be 10850000 specified in numerous places, (eg., data stream, JCL, 10860000 etc...). In this section you will see the order in which 10870000 PSF/MVS looks for format resolution and how potential errors 10880000 in specifying format resolution and resource libraries are 10890000 handled. 10900000 10910000 1. If the printer is NOT in automatic mode and therefore 10920000 is accepting resources only at a single resolution, PSF 10930000 will use the resolution reported to PSF by the printer to 10940000 select the resolution for the resource libraries. 10950000 10960000 2. If the printer is in automatic mode and is therefore 10970000 capable of accepting resources at multiple resolutions, 10980000 PSF looks for the first specification of the format 10990000 resolution in the following order: 11000000 11010000 A. The PSF installation exit for Resource Management 11020000 (APSUX07) begin data set call. 11030000 11040000 B. The PSF installation exit for Resource Management 11050000 (APSUX07) initialization call. 11060000 11070000 C. In the data stream in the Map Coded Font format 2 11080000 (MCF2) structured fields in the Font Resolution and 11090000 Metric Technology triplet (X'84'). 11100000 11110000 D. In the JCL OUTPUT statement RESFMT keyword. 11120000 11130000 The determined format resolution is used by PSF to choose 11140000 the SYSTEM Libraries to use when looking for resources. If 11150000 inline resources and/or User Libraries are specified, PSF 11160000 will search them first. 11170000 11180000 Font Fidelity will control the disposition of any errors 11190000 where the font found by PSF does not match the specified 11200000 format resolution. 11210000 11220000 11230000 -----------CHANGES FOR OW29241---------------------------------- 11240000 11250000 1. On page 83, Page Format Options for Formatted Print Records 11260000 section, add the following to the bottom of the list: 11270000 11280000 Specify an absolute or relative position for records, fields, 11290000 or objects. 11300000 11310000 2. On page 84, replace the third bullet at the top of the page 11320000 with: 11330000 11340000 Place each field on the page with absolute or relative 11350000 positioning. 11360000 11370000 -----------CHANGES FOR OW27623---------------------------------- 11380000 11390000 1. On page 27 in the next to last paragraph, 11400000 replace 11410000 (The logical page origin is defined in the form definition.) 11420000 with 11430000 (The logical page origin is defined in the form definition or 11440000 with the OFFSETXF and OFFSETYF or the OFFSETXB and OFFSETYB 11450000 keywords on the OUTPUT statement.) 11460000 11470000 2. On page 30 under Page Overlays, replace the last sentence of 11480000 the first paragraph with: 11490000 11500000 The logical page origin is defined in the form definition or 11510000 with the OFFSETXF and OFFSETYF or the OFFSETXB and OFFSETYB 11520000 keywords on the JCL OUTPUT statement. 11530000 11540000 3. On page 32 replace the paragraph with the title "Medium Overlays" 11550000 with the following: 11560000 11570000 Medium Overlays: A medium overlay can be included on all sheets 11580000 of a data set by specifying the overlay name on the OVERLAYF 11590000 or OVERLAYB keywords of the JCL OUTPUT statement. The form 11600000 definition can be used to include a medium overlay on some or 11610000 all of the sheets of a print data set. You need not modify the 11620000 print data set in order to print a medium overlay on every sheet. 11630000 11640000 4. On page 37 add two new items to the list of things you can 11650000 specify with JCL parameters 11660000 11670000 - Override form definition values for logical page offsets, 11680000 duplexing and paper source (input tray). 11690000 11700000 - Specify medium overlays to be included on each sheet. 11710000 11720000 5. On page 41 add the following to Figure 22, AFP Parameters in JCL 11730000 11740000 DUPLEX=NO|NORMAL|TUMBLE 11750000 INTRAY=nnn (nnn=1-255) 11760000 OFFSETXB=nnnn<.mmm>unit (unit=IN|CM|MM|PELS|POINTS) 11770000 OFFSETXF=nnnn<.mmm>unit (unit=IN|CM|MM|PELS|POINTS) 11780000 OFFSETYB=nnnn<.mmm>unit (unit=IN|CM|MM|PELS|POINTS) 11790000 OFFSETYF=nnnn<.mmm>unit (unit=IN|CM|MM|PELS|POINTS) 11800000 OVERLAYB=ovlyname 11810000 OVERLAYF=ovlyname 11820000 11830000 6. On page 51 add the following description before FCB= 11840000 11850000 DUPLEX=NO|NORMAL|TUMBLE 11860000 Specifies whether printing is to be done on both sides of 11870000 each sheet. If DUPLEX is not specified, the value specified 11880000 in the form definition is used. 11890000 11900000 NO 11910000 Specifies that printing is to be done on only the front 11920000 side of each sheet. 11930000 11940000 NORMAL 11950000 Specifies printing on both sides of the sheet such that 11960000 the sheets can be bound on the long edge of the paper. 11970000 11980000 TUMBLE 11990000 Specifies printing on both sides of the sheet such that 12000000 the sheets can be bound on the short edge of the paper. 12010000 12020000 EXAMPLE 12030000 12040000 The following JCL requests normal duplexing (such that the 12050000 output is rotated about the long edge of the paper). 12060000 12070000 //OUT1 OUTPUT DUPLEX=NORMAL 12080000 //DDN DD SYSOUT=P,OUTPUT=(*.OUT1) 12090000 12100000 7. On page 54 add the following description before NOTIFY= 12110000 12120000 INTRAY=nnn 12130000 Specifies the one to three decimal digit number from 1 to 255 12140000 which identifies the tray from which paper is to be selected. 12150000 To determine the input tray identifiers for your printer, see 12160000 Advanced Function Presentation: Printer Information or the 12170000 documentation for the printer. If INTRAY is not specified, 12180000 the value specified in the form definition is used. 12190000 12200000 EXAMPLE 12210000 12220000 The following JCL specifies that paper is to be taken from the 12230000 side tray of an IBM 3160 with the optional side tray installed. 12240000 (The optional side tray of a 3160 is identified as tray 4.) 12250000 12260000 //OUT1 OUTPUT INTRAY=4 12270000 //DDN DD SYSOUT=P,OUTPUT=(*.OUT1) 12280000 12290000 8. On page 54 add the following description before OUTBIN= 12300000 12310000 OFFSETXB=nnnn<.mmm>unit 12320000 Specifies the offset in the x direction of the logical page 12330000 origin from the media origin for the back side of each sheet. 12340000 If OFFSETXB is not specified, the value specified in the 12350000 form definition is used. 12360000 12370000 unit=IN|CM|MM|PELS|POINTS 12380000 IN specifies a unit of inches. 12390000 CM specifies a unit of centimeters. 12400000 MM specifies a unit of millimeters. 12410000 PELS specifies a unit of picture elements (1/240 inch). 12420000 POINTS specifies a unit of points (1/72 inch). 12430000 12440000 OFFSETXF=nnnn<.mmm>unit 12450000 Specifies the offset in the x direction of the logical page 12460000 origin from the media origin for the front side of each sheet. 12470000 If OFFSETXF is not specified, the value specified in the 12480000 form definition is used. 12490000 12500000 unit=IN|CM|MM|PELS|POINTS 12510000 IN specifies a unit of inches. 12520000 CM specifies a unit of centimeters. 12530000 MM specifies a unit of millimeters. 12540000 PELS specifies a unit of picture elements (1/240 inch). 12550000 POINTS specifies a unit of points (1/72 inch). 12560000 12570000 OFFSETYB=nnnn<.mmm>unit 12580000 Specifies the offset in the y direction of the logical page 12590000 origin from the media origin for the back side of each sheet. 12600000 If OFFSETYB is not specified, the value specified in the 12610000 form definition is used. 12620000 12630000 unit=IN|CM|MM|PELS|POINTS 12640000 IN specifies a unit of inches. 12650000 CM specifies a unit of centimeters. 12660000 MM specifies a unit of millimeters. 12670000 PELS specifies a unit of picture elements (1/240 inch). 12680000 POINTS specifies a unit of points (1/72 inch). 12690000 12700000 OFFSETYF=nnnn<.mmm>unit 12710000 Specifies the offset in the y direction of the logical page 12720000 origin from the media origin for the front side of each sheet. 12730000 If OFFSETYF is not specified, the value specified in the 12740000 form definition is used. 12750000 12760000 unit=IN|CM|MM|PELS|POINTS 12770000 IN specifies a unit of inches. 12780000 CM specifies a unit of centimeters. 12790000 MM specifies a unit of millimeters. 12800000 PELS specifies a unit of picture elements (1/240 inch). 12810000 POINTS specifies a unit of points (1/72 inch). 12820000 12830000 EXAMPLE 12840000 12850000 The following JCL sets the page origin to .5inches,1.1inches 12860000 on the front side and 1.5inches,1.1inches on the back side. 12870000 12880000 //OUT1 OUTPUT OFFSETXF=0.5IN,OFFSETYF=1.1IN, 12890000 // OFFSETXB=1.5IN,OFFSETYB=1.1IN 12900000 //DDN DD SYSOUT=P,OUTPUT=(*.OUT1) 12910000 12920000 9. On page 55 add the following description before PAGEDEF= 12930000 12940000 OVERLAYB=ovlyname 12950000 Specifies the member name (from 1 to 8 alphanumeric or 12960000 national characters) of a medium overlay to be placed on 12970000 the back side of each sheet, in addition to overlays from 12980000 other sources. The complete name of the overlay member 12990000 must be given; PSF does not add an O1 prefix. 13000000 13010000 OVERLAYF=ovlyname 13020000 Specifies the member name (from 1 to 8 alphanumeric or 13030000 national characters) of a medium overlay to be placed on the 13040000 front side of each sheet, in addition to overlays from other 13050000 sources. The complete name of the overlay member must be 13060000 given; PSF does not add an O1 prefix. 13070000 13080000 EXAMPLE 13090000 13100000 The following JCL requests the overlay O1FOVLY to be placed 13110000 on the front side of each sheet and the overlay O1BOVLY to 13120000 be placed on the back side of each sheet. 13130000 13140000 //OUT1 OUTPUT OVERLAYF=O1FOVLY,OVERLAYB=O1BOVLY 13150000 //DDN DD SYSOUT=P,OUTPUT=(*.OUT1) 13160000 13170000 10. On page 96 replace the entire section Printing a Medium Overlay 13180000 with the following: 13190000 13200000 A medium overlay can be invoked on the JCL OUTPUT statement 13210000 or in the form definition. Printing a medium overlay requires 13220000 the following: 13230000 13240000 1. An overlay resource. You can create an overlay by using 13250000 an AFP utility, such as IBM Overlay Generation Language/370 13260000 (OGL/370). For more information, refer to Overlay 13270000 Generation Language/370: User's Guide and Reference. 13280000 13290000 2. Next use the overlay by either of the following methods: 13300000 13310000 - Specify the overlay name on the OVERLAYF and/or OVERLAYB 13320000 keywords on the JCL OUTPUT statement. 13330000 or, 13340000 - Use a form definition that names that overlay for printing. 13350000 You can create a form definition by using an AFP utility, 13360000 such as IBM Page Printer Formatting Aid (PPFA). For more 13370000 information, refer to Page Printer Formatting Aid: User's 13380000 Guide and Reference. 13390000 13400000 EXAMPLE 13410000 13420000 This example uses two user created medium overlays, O1FRONT 13430000 to be printed on the font side of each sheet and O1BACK to 13440000 be printed on the back side of each sheet. 13450000 13460000 //AFPUSER JOB ..... 13470000 //STEP1 EXEC PGM=MYAPPL 13480000 //OUT1 OUTPUT OVERLAYF=O1FRONT,OVERLAYB=O1BACK 13490000 //PRINT DD SYSOUT=A,OUTPUT=(*.OUT1) 13500000 /* 13510000 13520000 -----------CHANGES FOR OW29993---------------------------------- 13530000 13540000 1. pg 22 Add a new sentence just prior to the last sentence 13550000 in the paragraph under the heading Font Capture: 13560000 In order for a font to be captured it must be marked PUBLIC 13570000 and it must reside in a system library. 13580000 13590000 2. pg 34 Under "Using Resources with the Distributed Print 13600000 Function (DPF) of PSF" add a new sentence after 13610000 the second sentence in the second paragraph: 13620000 13630000 "PSF/MVS will tell DPF not to store resources found in 13640000 user libraries or inline resources." 13650000 13660000 3. pg 62 Add a new paragraph above the heading "Additional 13670000 Parameters to Help in Distributing Output" 13680000 13690000 For security reasons PSF will tell the printer not to 13700000 capture inline resources. If you want them made 13710000 resident in the printer then you must directly install them 13720000 into the printer if your printer has this capability or 13730000 put them in a system library. PSF will only allow PUBLIC 13740000 resources from system libraries to be captured. 13750000 13760000 4. pg 112 Add a new paragraph just prior to the EXAMPLE in the 13770000 "Printing with Resources from a User Library" section: 13780000 13790000 PSF will tell the printer not to capture resources loaded 13800000 from user libraries. If you want them made 13810000 resident in the printer then you must directly install them 13820000 into the printer if your printer has this capability or 13830000 put them in a system library. PSF will only allow PUBLIC 13840000 resources from system libraries to be captured. 13850000 13860000 5. pg 113 Add a new paragraph after the 4th paragraph under 13870000 "Printing with Inline Resources": 13880000 13890000 Even though resident resources can be activated by inline 13900000 resources that are marked PUBLIC, PSF tells the printer 13910000 not to capture them. If you want them made 13920000 resident in the printer then you must directly install them 13930000 into the printer if your printer has this capability or 13940000 put them in a system library. PSF will only allow PUBLIC 13950000 resources from system libraries to be captured. 13960000 13970000 -----------CHANGES FOR OW31424---------------------------------- 13980000 13990000 1. On page 5 replace the paragraph entitled "Logical Unit 14000000 Conversion" with the following. 14010000 14020000 Measurement Unit Conversion 14030000 14040000 PSF accepts text, images, graphics and bar code objects with 14050000 units per unit base values in the range of 1 through 32767 14060000 for a 10 inch unit base. Some printers support only 2400 14070000 units per 10 inches and 14,400 units per 10 inches. For those 14080000 printers, PSF converts the input units per unit base values 14090000 to values supported by the printer. This conversion can 14100000 affect processing performance. Other printers support the 14110000 full range of units per unit base values. For those printers, 14120000 PSF will not convert the input units. 14130000 14140000 14150000 -----------CHANGES FOR OW31717---------------------------------- 14160000 14170000 1. On page 115 following the section titled "Specifying 14180000 Notification When the Prnt Job has Finished Printing", 14190000 add the following new section. 14200000 14210000 Inhibiting Recovery of a Print Job 14220000 14230000 The normal PSF error recovery actions include resetting to 14240000 the point in the data path at which an exception is reported 14250000 and resending data from this point. Any pages which are 14260000 reprinted are in the portion of the paper path of the printer 14270000 where they may be damaged or imperfect and they should be 14280000 discarded. The PSF exit routine, APSUX07, can request that 14290000 PSF inhibit recovery for a job. This means PSF is not to 14300000 resend any portion of the job which has already printed. If 14310000 an error does occur which requires recovery for pages which 14320000 are on paper, such as for a paper jam, the job will be 14330000 terminated. This can be used to prevent the reprinting of 14340000 sensitive data, such as checks. If you need this function, 14350000 consult with your system programmer. 14360000 14370000 -----------CHANGES FOR OW33942---------------------------------- 14380000 14390000 1. On page 28 under "Using Page Segments" change the last 14400000 sentence on the page to read as follows. 14410000 14420000 With IBM printer microcode for extended page segments, the 14430000 maximum number of page segments is extended to a total of 14440000 32511 page segments per sheet. Extended page segments 14450000 are not supported when connected via DPF or RPM3. 14460000 14470000 2. On page 33 under "Using Overlays" change the last sentence 14480000 under the note to read as follows. 14490000 14500000 With IBM printer microcode for extended overlays, the 14510000 maximum number of overlays is extended to 32511 overlays 14520000 per sheet. Extended overlays are not supported when connected 14530000 via DPF or RPM3. 14540000 14550000 3. On page 134 in the new chapter "Handling Job Streams that 14560000 are Formatted at Different Resolutions" that was added 14570000 with apar OW27622, change the 1st 14580000 paragraph under "Printers with Automatic or Auto 14590000 Resolution Mode" to read as follows. 14600000 14610000 PSF/MVS now supports printers operating in automatic or 14620000 auto resolution mode. Printers operating in automatic 14630000 or auto resolution mode are not supported when connected 14640000 via DPF or RPM3. 14650000 14660000 -----------CHANGES FOR OW24360---------------------------------- 14670000 14680000 14690000 Pg 4 Add a new sentence following the first sentence. 14700000 "This output can then also be finished, for example 14710000 stapled in the top left corner." 14720000 14730000 Pg 15 Add a new section before PSF Data Streams that is the same 14740000 level as 'Combining Character, Image, Graphics, and Bar Code 14750000 Data' 14760000 14770000 Finishing your AFP Output 14780000 AFP output can be finished. The capabilities of your 14790000 finisher determine the types of finishing available, 14800000 examples are cornner stapling, edge stitching, 14810000 saddle stitching and Z-folding. Finishing is 14820000 requested via the Medium Finishing Control structured 14830000 field in the form definition. For more information about 14840000 coding finishing in a form definition refer to the 14850000 documentation section of PPFA APAR PQ17083. 14860000 14870000 pg 19 Add a new bullet to the list of printing controls in a 14880000 form definition: 14890000 14900000 o Finishing, for example corner stapling 14910000 14920000 pg 68 Add a new bullet to the list of controls for a copy group: 14930000 14940000 o Medium level finishing (for example z-fold) 14950000 14960000 pg 89 Add a new example to the list: 14970000 14980000 o Finishing your Output 14990000 15000000 pg 118 add a new section for the new example of Finishing 15010000 your Output: 15020000 15030000 Finishing your Output 15040000 When you send output to an AFP printer with finishing 15050000 capabilities (e.g. InfoPrint 60 with the Finisher 15060000 feature) you can specify a 15070000 form definition that requests specific finishing functions. 15080000 15090000 This is an example of a form definition that requests 15100000 that the dataset be stapled in the top left corner. 15110000 15120000 FORMDEF STAPLE REPLACE YES 15130000 FINISH SCOPE ALL OPERATION CORNER REFERENCE TOPLEFT 15140000 BIN 1 DUPLEX NO 15150000 OFFSET 0 0 ; 15160000 15170000 For more information on coding finishing in your form 15180000 definitions, refer to the documentation section of 15190000 PPFA APAR PQ17083. 15200000 15210000 The following example shows the JCL used to call out the 15220000 form definition with the finishing function. 15230000 15240000 //AFPUSER JOB ... 15250000 //STEP1 EXEC PGM=USERA 15260000 //OUT1 OUTPUT FORMDEF=STAPLE 15270000 //PRINT DD SYSOUT=A,OUTPUT=(*.OUT1) 15280000 15290000 15300000 -----------CHANGES FOR OW36168---------------------------------- 15310000 15320000 1. On page 126, under the section titled "Using Shift-Out, Shift-In 15330000 (SOSI) Codes", change the first paragraph to read : 15340000 15350000 A data set that contains both single-byte and double-byte character 15360000 codes may necessitate coding the structured fields in the data set to 15370000 change from 1 kind of character code to the other. To avoid doing this,15380000 you can instruct PSF to provide special processing by specifying 15390000 PRMODE=SOSI1, PRMODE=SOSI2, or PRMODE=SOSI3 in your JCL; or by 15400000 specifying a default PRMODE of SOSI1, SOSI2 or SOSI3 using APSUX07. 15410000 For more information on specifying a default PRMODE in APSUX07, see the 15420000 PSF/MVS System Programming Guide "Considerations Related to Setting a 15430000 a Default for PRMODE" in Chapter 17, "Using Installation Exits". The 15440000 data set can then contain the shift-out code, X'0E', and the shift-in 15450000 code, X'0F', to indicate to PSF when a font change is required. PSF 15460000 converts the shift-out and shift-in codes to Set Coded Font Local text 15470000 controls, described in Mixed Object Document Content Architecture 15480000 Reference. 15490000 15500000 15510000 2. On page 126, under the section titled "Using Shift-Out, Shift-In 15520000 (SOSI) Codes", after the third paragraph, add: 15530000 15540000 Note: When the PRMODE keyword is specified in the OUTPUT JCL, it 15550000 supersedes the default PRMODE specified in APSUX07. 15560000 15570000 When a default PRMODE is specified for both the Initialization 15580000 and the Begin-Data-Set Calls in APSUX07, the Begin-Data-Set 15590000 specification supersedes the Initialization specification of 15600000 PRMODE. 15610000 15620000 -----------CHANGES FOR OW39987---------------------------------- 15310000 15320000 1. On Page 26, Section 'Using Fonts', after the last paragraph, add the following note. NOTE: APSRCF30 converts 240 pel single byte raster fonts to 300 pel raster fonts. It cannot convert 240 pel double byte raster fonts. Higher resolution double byte fonts are available with double byte outline fonts in the AFP Font Collection, Version 2. APSRCF30 converts a 240 pel single byte raster font to a close approximation of the font at 300 pel resolution. However, IBM does not warrant the quality of the resulting character pattern when using this utility. -----------CHANGES FOR OW41705---------------------------------- 00640000 On page 53, under FORMLEN= keyword, added by APAR OW24771, add a new paragraph after third paragraph: The FORMLEN keyword should only be specified in the USER's JCL OUTPUT statement. If the FORMLEN keyword is specified on an OUTPUT statement in the PSF startup procedure, it is ignored. The FORMLEN keyword value specified in the USER's JCL OUTPUT statement is used for all pages in the dataset including the job header, job trailer, dataset header, message dataset, and interrupt message page. The FORMLEN keyword will not be used for JESNEWS pages. JES creates a separate dataset for JESNEWS which does not have the JCL values of the user dataset. JES2 puts the JESNEWS on the the job header page and the form length value comes from the formdef for the job header. JES3 puts the JESNEWS on the job trailer page and the form length value comes from the formdef for the job trailer. Note: PSF uses the XOH Set Media Size (SMS) command to set the printer's physical printable area in the length direction using the FORMLEN value. Although some printers use the SMS values unconditionally, some do not. See your printer hardware manual to determine how SMS is used by the printer.