PAGEDEF
Specifies the file name of the page definition. A page definition defines the page format that ACIF uses to compose line data, XML data, mixed-mode data, and unformatted ASCII data into pages; it is not used with MO:DCA-P data. Page definitions are only used by ACIF at transform time to convert data streams; they are not used by InfoPrint Manager and RICOH ProcessDirector to print the output that is produced by ACIF.
- PAGEDEF=pdefname
- The value is:
- pdefname
- Any valid page definition name. The pdefname can be 1 - 8 alphanumeric characters (a-z, A-Z, 0–9) and special characters (# $
@), including the 2-character prefix, if there is one. ACIF does not require the name to begin with a P1 prefix; however, if the name does begin with
P1, you cannot omit it. For example:
PAGEDEF=P1USER10
- Note:
- In AIX, the pdefname is case-sensitive.
- If the file name of the page definition includes a file extension, do not use the
file extension when you are specifying the page definition. For example, to use a
page definition that is named
MEMO.PDEF38PP, specify PAGEDEF=MEMO. - ACIF does not require a page definition when it is indexing an AFP data stream file. However, ACIF does require a page definition to transform an input file that contains line data, XML data, mixed-mode data, or unformatted ASCII data into MO:DCA-P. If you are transforming such an input file and you do not specify the PAGEDEF parameter, or you specify PAGEDEF without a page definition file name, ACIF reports an error condition and ends processing.
- If you use the PAGEDEF parameter to specify a page definition that names fonts, but you also use the CHARS parameter to specify fonts, the CHARS parameter is ignored. Therefore, if your page definition names fonts, do not use the CHARS parameter.
The page definition that you use can be found in one of these locations:
- Inline in the file
- A page definition can be an inline resource in all data formats except XML. (XML data
cannot have carriage control characters, which are used to identify inline resources.)
If the page definition is an inline resource, you must do these tasks:
- Include an inline form definition in the file.
- Specify CC=YES to indicate that the file contains carriage control characters. If the length of the records in the page definition is less than or equal to the logical-record length defined for the file, you can specify fixed-length records for the record format. If the length of the records in the page definition is greater than the logical-record length defined for the file, you must specify fixed-length records for the record format.
- Specify PAGEDEF with one of these values:
- pdefname
- Indicates the name of the inline page definition. If the name specified in the PAGEDEF parameter does not match the name of an inline page definition, ACIF looks for the page definition in the PAGEDEF search path or uses the page definition from the resource library.
- DUMMY
- If the file does not include an inline page definition, ACIF looks for the page definition
named DUMMY. If ACIF cannot find a page definition that is named DUMMY, it reports
an error and ends processing.
Note: DUMMY must be specified in all uppercase letters.
An input file can contain multiple page definitions, but only one page definition can be used by ACIF. If a file contains more than one inline page definition, and you specify PAGEDEF=pdefname, ACIF uses the first inline page definition named pdefname. If a file contains more than one inline page definition and you specify PAGEDEF=DUMMY, ACIF uses the first inline page definition in the input file. By changing the page definition name in the PAGEDEF parameter on different printing jobs, you can test different page definitions.
- AIX or Windows directory
- Use the USERLIB or PDEFLIB parameter to specify the path to the file.
In AIX, use one of these examples:
pagedef=memo userlib=/usr/afp/resources
pagedef=memo userlib=/usr/afp/resources
pagedef=memo pdeflib=/usr/lib/pagedefns
In Windows, use this example:
pagedef=memo userlib=\install_directory\resources