IBM S544-5285-01 - page 49

with more than one font, then the input file must contain table

reference characters, and you must:

Specify trc=yes.

Use chars to indicate the fonts to be associated with each Table

Reference Character (TRC).

fontname1

is associated with TRC 0,

fontname2

is associated with TRC 1, and so on.

If the page definition does not name any fonts, and you want the

whole file to print with only one font, then you must:

Specify trc=no.

Use chars to indicate the single font in which the file should be

printed.

Consider the following when specifying fonts with the chars

parameter:

If the input file is unformatted ASCII, you can do one of the

following:

– Specify a font that has the appropriate ASCII code points. To

specify a font search path, either use the fontlib parameter to

specify it explicitly, or set the PSFPATH environment variable

to search the appropriate directories. See Chapter 5, “IBM

AFP Fonts for ASCII Data” on page 77 for a list of suggested

ASCII fonts.

– Use the apka2e or asciinpe input record exit programs to

convert the ASCII code points in the input file into EBCDIC,

and use EBCDIC fonts. To do this, use the inpexit parameter,

specifying:

-inpexit=/usr/lpp/psf/bin/apka2e

or

-inpexit=/usr/lpp/psf/bin/asciinpe

See the inpexit parameter on page 39 for a description of

apka2e and asciinpe functions.

You can specify fonts with the chars parameter only if you want

the entire file printed in a single printing direction. The acif

command uses the fonts that have 0° character rotation for the

specified direction. When a file requires fonts with more than one

print direction or character rotation, you must specify the fonts in

the page definition.

You can specify from one to four fonts with the chars parameter.

If you specify more than one font with the chars parameter, then

the input file must contain table reference characters, and you

must specify trc=yes.

If you use chars to specify fonts, but you also use the pagedef

parameter to specify a page definition that names fonts, the chars

parameter is ignored. Therefore, if your page definition names

fonts, you should not use chars.

Chapter 2. Using ACIF Parameters in AIX 29

Contents

Main Page Page Page Contents Part 1. Information Common to AIX, OS/390, MVS, VM, and VSE Environments Part 2. Using ACIF in the AIX Environment Part 3. Using ACIF in the OS/390, MVS, VM, and VSE Environments iv Part 4. Appendixes vi Figures Page Notices Programming Interfaces Disclaimer Page unbounded only xii About This Publication Why Should I Read This Publication? What Do I Need To Know? Guide to Advanced Function Presentation Mixed Object Document Content Architecture Reference How This Publication Is Organized xiv S544-5285 What Terms Are Used In This Publication? xvi Italic Related Information Understanding Syntax Notation Notational Conventions code page identifier Page Page Page Chapter 1. Planning Your AFP Conversion and Indexing Facility (ACIF) Application What Can I Do with ACIF? index object file 4 Using ACIF for Different Tasks 6 Page 8 Tasks You Can Do with ACIF Converting Data Streams S/370 Line-Mode Data: Mixed Object Document Content Architecture Data: Mixed Object Document Content Architecture Reference Indexing Documents indexing with data values. indexing with literal values. Indexing with Data Values: Indexing with Literal Values: 12 An Indexing Example Using Data Values: without triggers anchor point Indexing Limitations: Retrieving Resources 14 What Other IBM Products are Related to ACIF? The Workbench Viewer AFP Toolbox for Multiple Operating Systems 16 Document Composition Facility (DCF) Document Composition Facility Script/VS Language Reference (SH35-0070) What are the Systems Considerations for ACIF? System Limitations System Prerequisites 18 also Print Services Facility for AIX: Print Submission only VSE Prerequisites Page Page Page Chapter 2. Using ACIF Parameters in AIX Purpose Syntax 24 are Description IBM AFP Fonts: Font Summary for AFP Font Collection automatically 26 IBM Print Services Facility for AIX: Print Submission conversion Flags and Values after 28 fontname fontname1, fontname2, fontname3, fontname4 Page 30 Mixed Object Document Content Architecture Reference Print Services Facility for AIX: Print Administration literal value record,column,length 32 (newline= (newline= 34 Print Services Facility for AIX: Print Administration Page 36 anything other than must filename not 38 Page 40 IBM Print Services Facility for AIX: Print Administration 42 IBM Print Services Facility for AIX: Print Submission 44 Page 46 Page 48 Examples IBM Print Services Facility for AIX: Print Submission 50 Implementation Specifics InfoPrint Manager for AIX: Administrator's Guide IBM Page Printer Formatting Aid/6000: User's Guide Version 2.1 Files NLS Messages Suggested Reading IBM Print Services Facility for AIX: Print Submission Page Chapter 3. Example of an ACIF Application in AIX Page The Input File Figure 11 shows the line data file currently used to print the telephone bills. Figure 11. Line-Data Telephone Bill Specifying ACIF Processing Parameters for ASCII Input Data Using a Parameter File with ASCII Input Data 56 Page Specifying ACIF Processing Parameters for EBCDIC Input Data 58 Using a Parameter File with EBCDIC Input Data Page 60 Using the Shell with EBCDIC Literal Values must not AIX for RISC System/6000 Commands Reference Identifying the Locations of the Resources Determining the Form Definition and the Page Definition 62 Running the ACIF Job IBM Print Services Facility for AIX: AIX for Users of Print Services Facility Accessing the Document File from the Workstation transfer mount transfer Transfer Mounting the AIX Directory on the Workstation Chapter 4. User Exits and Attributes of the Input Print File in AIX User Programming Exits IBM Print Services Facility for AIX: Print Administration 66 Input Record Exit Page Using the ACIF User Input Record Exits 68 Index Record Exit Output Record Exit 70 Page 72 Resource Exit Page Non-Zero Return Codes 74 Attributes of the Input Print File Page Page Chapter 5. IBM AFP Fonts for ASCII Data without 78 Page Page Chapter 6. Using ACIF in OS/390, MVS, VM, and VSE Using ACIF in the OS/390 and MVS Environments USERAPPL OS/390 MVS JCL Reference Explaining the JCL Statements Using ACIF in the VM Environment 82 Explaining the VM CMS Commands Print Services Facility/VM: Application Programming Guide Using ACIF in the VSE Environment 84 Explaining the VSE JCL Statements Print Services Facility/VSE: Application Programming Guide user print file Page Page 88 Page after 90 fontname4 fontname3 Page 92 Page length 94 data set name1 literal value Page F1USER10 96 Using Inline Form Definitions: Using Form Definitions from an OS/390 or MVS User Library: attribute name attribute name 98 Page 100 DDname data set name1. data set name2 PSF for 102 P1USER10 filetype2 Using Page Definitions from an OS/390 or MVS User Library: Using Inline Page Definitions: 104 data set name2 106 Page 108 Page 110 file name... 112 Chapter 8. Example: ACIF Application in OS/390, MVS, VM, or VSE Page Input File JCL, CMS Commands, and ACIF Processing Parameters OS/390 or MVS JCL to Invoke ACIF Figure 26. Example of a Telephone Bill for an OS/390 or MVSACIF Application 116 VM CMS Commands to Invoke ACIF VSE JCL to Invoke ACIF 118 Page 120 ACIF Output Concatenating Files OS/390 or MVS JCL VM CMS Commands Page Chapter 9. User Exits and Attributes of the Input Print File in OS/390, MVS, VM, and VSE User Programming Exits Input Record Exit 124 Index Record Exit Output Record Exit 126 Page Resource Exit 128 Page User Exit Search Order 130 OS/390 or MVS VM VSE Page Page Chapter 10. ACIF Messages for OS/390, MVS, VM, and VSE Multiple Message Scenarios 134 Structured field name1 name1 General Messages record number sequence token End-type structured field token name resource 136 structured field MVS/Extended Architecture Data Administration Guide structured field name 138 Page 140 identifier value medium map 142 form definition name data map page definition 144 Page 146 id name 148 Page | | | | | | | | | 150 structured field overlay name Mixed Object Document Content Architecture Advanced Function Presentation: Programming Guide and Line Data Reference 152 Mixed Object Document Content Architecture Advanced Function Presentation: Programming Guide and Line Data Reference | | | 154 field name | | | | | | | | | | | number structured field number 156 field number token name number identifier1 158 identifier2 data map CCP identifier number data map name number 160 Function Printing: Diagnosis Guide number Page value1 162 number value2 Advanced Function Presentation: Programming Guide and Line Data Reference channel Advanced Function Presentation: Programming Guide and Line Data Reference record 164 indexn 'xxxxxxxx' storage request size xxxx return code request type 166 module name return code 'ddname' 'member name' program library name parameter = value. 'resource' 168 'value' ddname nn. nn nnn xxxxxxxxnn parameter name xxxxxxxx 170 token2 token1 token offset hex string length 172 rc error text MVS/Extended Architecture Service Aids Logic rc MVS/ESA Component Diagnosis and Logic: Service Aids 174 Page Page Page Page Appendix A. Helpful Hints Working with control statements that contain numbered lines Placing TLEs in named groups Working with file transfer and AIX 180 Understanding how ANSI and machine carriage controls are used Understanding common methods of transferring files to AIX from other systems 182 Physical media PC file transfer program FTP Other Considerations for Transferring Files to AIX Invoke Medium Map (IMM) Structured Field 184 Indexing Considerations Concatenating the Resource Group to the Document Specifying the IMAGEOUT Parameter Page Appendix B. Data Stream Information Mixed Object Document Content Architecture Reference Format of the Resources File 188 Begin Resource Group (BRG) Structured Field Begin Resource (BR) Structured Field End Resource (ER) and End Resource Group (ERG) Structured Fields Page Appendix C. Format of the Index Object File Group-Level Index Element (IEL) Structured Field Page-Level Index Element (IEL) Structured Field 192 Begin Document Index (BDI) Structured Field Index Element (IEL) Structured Field End Document Index (EDI) Structured Field 194 Appendix D. Format of the Output Document File 196 Page 198 Page Groups Begin Document (BDT) Structured Field Begin Named Group (BNG) Structured Field Begin Page (BPG) Structured Field End Named Group (ENG), End Document (EDT), and End Page (EPG) Structured Fields Page Glossary VocabularyInformation Processing Source Identifiers B 202 C D E F G H I J O 204 Adobe Type 1 Font Format P R S T anchor point V W Page Bibliography Print Services Facility (PSF) for OS/390 Advanced Function Presentation (AFP) Advanced Function Presentation (AFP) Architecture 208 Advanced Function Presentation for Microfilm To order any of the following microfilm publications, see your representative for Anacomp, Inc. Text Processing InfoPrint Manager for AIX Print Services Facility (PSF) for AIX Print Services Facility for OS/2 (PSF/2) 210 EDMSuite OnDemand Printers i-data OS/390 Version 2 Release 6 eNetwork Communications Server 212 MVS/Enterprise Systems Architecture (ESA) Version 5 TCP/IP TCP/IP for MVS VTAM and NCP Systems Network Architecture 214 AS/400 Information/System Index A 216 B C D 218 E F G 220 H I Page J 222 L M N O P 224 Page R 226 S T U 228 V W Communicating Your Comments to IBM Readers' Comments We'd Like to Hear from You BUSINESS REPLY MAIL Page IBM