|
|
|
|
|
For the Control‑D ACIF Interface facility, ACIF execution parameters are placed in the Control‑D ACIFPARM library.
Unlike standard executions of ACIF, the Control‑D ACIF Interface facility allows the specification of different parameters for different reports associated with the same job name, printing mission name, and/or recipient (user ID) name, to be kept in a single member of the Control‑D ACIFPARM library.
By default, ACIFPARM member names must be identical to a report’s original job name. However, as an optional enhancement, the ACIF Interface facility can be modified to associate member names with a report’s printing mission name or recipient name.
In each member, one or more sets of ACIF execution parameters can exist for different reports. Each set of parameters, as explained in the table below, must be preceded by a report name (repname) control statement in the following format:
1 2 3 4 5 6 7
12345678901234567890123456789012345678901234567890123456789012345678901
++++repname
unitname pind sind pres sres prep srep c CYL ##
Table 148 Format of Report Name (repname) Control Statement
Field |
Description |
|---|---|
++++ |
Indication that this is a report name (repname) statement. |
repname |
Name of the report (maximum length: 50 characters). The name must be the same as the name of the report specified in parameter DO NAME of the decollation mission that created the report. The report name can be specified explicitly, or can contain the following mask characters:
Examples
|
unitname |
Work unit name to be used by the Control‑D ACIF Interface facility to allocate temporary ACIF index, resource and report data files. |
pind |
Primary space allocation, in tracks, for the temporary ACIF index file. |
pres |
Primary space allocation, in tracks, for the temporary ACIF resource file. |
sind |
Secondary space allocation, in tracks, for the temporary ACIF index file. |
sres |
Secondary space allocation, in tracks, for the temporary ACIF resource file. |
prep |
Primary space allocation, in tracks, for the temporary ACIF report data file. |
srep |
Secondary space allocation, in tracks, for the temporary ACIF report data file. |
c |
JES output class to which ACIF prints its informational or error message report. If left blank or specified as an asterisk (*), the default MSGCLASS of the Printers Control monitor is assigned. |
CYL |
Allocation subparameter. Indicates that Control‑D will perform dynamic allocation in CYLINDERS for pind, sind, pres, sres, prep, and srep. If the CYL subparameter is not specified, Control‑D will request allocation in TRACKS. |
## |
UNIT-COUNT subparameter of the UNIT parameter. Specifies the number of devices for the temporary data set. |
UTIL |
Name of the product used to create the AFPDS file. Valid values are:
The UTIL parameter should be defined as the first parameter in the ACIFPARM library. |
ACIF execution parameters must immediately follow the repname statement.
For more detailed information, see the ACIF Application Programming Guide (IBM publication number G544‑3824) or any subsequent IBM documentation, or PRISMAproduction/MVS CIS-Module User’s Guide (Océ publication number U28117-J-Z247-1-7600) or any subsequent Océ documentation.
An ACIPARM library member can contain any number of repname and ACIF execution parameter groups.
Example
Consider the following decollation mission parameters for two reports:
JOBNAME=jobname-memb
PRINT/CDAM PARMS=ACIF=YES
DO NAME=REPORT‑NAME1
DO NAME=REPORT‑NAME2
Member jobname‑memb in the ACIFPARM library can contain the following:
++++REPORT‑NAME1 ................
ACIF EXECUTION PARAMETER STATEMENTS
.
.
.
++++REPORT‑NAME2 ................
ACIF EXECUTION PARAMETER STATEMENTS
Default member $$$$DFLT in the Control‑D ACIFPARM library contains default ACIF execution parameters. These parameters control how reports with no specifically associated member in the ACIFPARM library are processed by the ACIF Interface facility.
Parent Topic |