Converting Mixed Mode AFP Files into FAP or PDF Files
The MRG2FAP utility includes limited support for converting Mixed Mode AFP source files into FAP or PDF files.
The utility assumes the Mixed Mode AFP source contains AFP commands and line data for one or more pages. A single page/side consists of an AFP Invoke Medium Map command, followed by an AFP Invoke Data Map command, optionally followed by an Invoke Page Segment (IPS) command, followed by a line of actual, unformatted line data. The line data must be formatted using the AFP commands and formatting information contained in the invoked Medium Map and Data Map.
All AFP resources, including the AFP source file, the PageDef (page definition) file, and the FormDef (form definition) file must be in variable block format.
Note | Additional resources, such as AFP overlays and page segments, must also be in variable block format. Only 4-byte variable block format has been tested. |
Keep in mind...
- The utility assumes all medium maps necessary for the conversion are contained in a single external FormDef file and all data maps are contained in a single external PageDef file. Use these INI options to specify the location of these files:
< PrtType:AFP >
FormDef = F1POLL.fde
PageDef = P1POLL.pde
Both files are necessary for converting Mixed Mode AFP into FAP or PDF files.
Note | Although inlined medium maps have been tested in regular AFP conversions, inlined medium maps and inlined data maps have not been tested in a Mixed Mode environment. |
- The first line/record of line data for each invoked data map is preceded by a single byte carriage control. Although ANSI and machine code control characters are supported, only ANSI control characters have been tested. According to IBM AFP documentation, only one of the two kinds of control characters should exist in each Mixed Mode source file.
- You cannot use Table Reference Characters (TRCs).
© Copyright 2020, Oracle and/or its affiliates. All rights reserved. Legal notices.