|
Notes:
|
1. Data sets must be specified as fully-qualified names without quotation
|
marks.
|
2. If the libraries specified for OVLYLIB are not specified in the same order
|
used by the PSF start-up procedure, the printed and converted results may
|
differ. For information on how PSF selects resources, refer to
PSF for
|
OS/390: Customization .
|
3. For systems before MVS/DFP Version 2.3, data sets must be concatenated
|
with the largest block size first.
|
4. This is a required parameter if overlay retrieval is requested and USERLIB
|
is not specified. The RESTYPE value determines whether overlays are to
|
be retrieved for inclusion in the resource data set. If this parameter is not
|
specified, and overlay retrieval is requested, ACIF reports an error condition
|
and terminates processing.
OVLYLIB=
filetype1[,filetype2][,filetype...]
(VM)
Specifies the file types that define the overlay libraries. A maximum of 8 file
types can be specified. The parameter also specifies the search order when
ACIF searches for a particular overlay resource. ACIF first looks for the
resource with a file type of
filetype1. If ACIF cannot find the resource with a file
type of
filetype1, it continues the search with filetype2, and so on, until it either
locates the requested resource or exhausts the list of specified files.
EXAMPLE
OVLYLIB=OVLY38PP,TEMPOVLY
Notes:
1. File types must conform to CMS naming conventions.
|
2. This is a required parameter if overlay retrieval is requested and USERLIB
|
is not specified. The RESTYPE value determines whether overlays are to
|
be retrieved for inclusion in the resource file. If this parameter is not
|
specified, and overlay retrieval is requested, ACIF reports an error condition
|
and terminates processing.
OVLYLIB
This parameter is not used for VSE. Overlay resources are located in the library
defined by the // LIBDEF PHASE,SEARCH=(...) JCL statement. For information
on how PSF/VSE selects resources, refer to
Print Services Facility/VSE:
System Programming Guide.
PAGEDEF=
pdefname
|
Specifies the complete file name (in OS/390, MVS and VSE, the member
|
name) of the page definition, which defines the page format that ACIF uses to
|
compose line data into pages. The
pdefname can be from 1–8 alphanumeric or
|
national characters. Unlike PSF for OS/390, PSF/MVS, PSF/VM, and PSF/VSE,
|
ACIF does not require the name to begin with a P1 prefix, but if the name does
|
begin with P1, you cannot omit it.
|
EXAMPLE
|
The following example specifies
P1USER10 as the page definition:
|
PAGEDEF=P1USER1ð
102
ACIF User’s Guide
Summary of Contents for S544-5285-01
Page 1: ...IBM Print Services Facility IBM AFP Conversion and Indexing Facility User s Guide S544 5285 01...
Page 2: ......
Page 3: ...IBM Print Services Facility IBM AFP Conversion and Indexing Facility User s Guide S544 5285 01...
Page 10: ...viii ACIF User s Guide...
Page 22: ...2 ACIF User s Guide...
Page 40: ...20 ACIF User s Guide...
Page 41: ...Part 2 Using ACIF in the AIX Environment Copyright IBM Corp 1993 1999 21...
Page 42: ...22 ACIF User s Guide...
Page 72: ...52 ACIF User s Guide...
Page 96: ...76 ACIF User s Guide...
Page 99: ...Part 3 Using ACIF in the OS 390 MVS VM and VSE Environments Copyright IBM Corp 1993 1999 79...
Page 100: ...80 ACIF User s Guide...
Page 106: ...86 ACIF User s Guide...
Page 134: ...Figure 24 Example of a Customer s Phone Bill 114 ACIF User s Guide...
Page 142: ...122 ACIF User s Guide...
Page 196: ...176 ACIF User s Guide...
Page 197: ...Part 4 Appendixes Copyright IBM Corp 1993 1999 177...
Page 198: ...178 ACIF User s Guide...
Page 206: ...186 ACIF User s Guide...
Page 210: ...190 ACIF User s Guide...
Page 226: ...206 ACIF User s Guide...
Page 253: ......