|
|
|
|
|
In data centers that use a relatively small variety of PAGEDEFs and FORMDEFs, one global PAGEDEF and one global FORMDEF are defined. The general idea is to define all original PAGEDEFs in one global PAGEDEF, each as Page Formats in the global PAGEDEF. The same can be done for a global FORMDEF. Define all original FORMDEFs in one global FORMDEF, each as Copy Groups in the global FORMDEF. The main advantage of this method is improved printer performance.
The APAPARM option must be used for correct selection of the required Page Format and/or Copy Group. For a detailed description of this option, refer to The APAPARM Option.
The specific Page Format and Copy Group to be used for each report are specified in the APAPARM library. The Page Format and Copy Group names appear in the PAGEDEF and FORMDEF. If the name is not known, it can easily be displayed by browsing the PAGEDEF or FORMDEF member in the system or user PAGEDEF/FORMDEF library. For PAGEDEFs, the line that displays the Page Format name (in Hex) is the BDM command X‘D3A8CA’ (Begin Data Map). For FORMDEFs, the line that displays the Copy Group name (in Hex) is the BMM command X‘D3A8CC’ (Begin Medium Map). The name itself appears in regular text format on the same line.
IBM supplied PAGEDEFs usually contain a Page Format with the same (or close to the same) name as the PAGEDEF, as do IBM supplied FORMDEFs and Copy Groups. User-defined PAGEDEFs and FORMDEFs usually use the same standard as IBM. For user-defined PAGEDEFs where the original PAGEDEF has more than one Page Format, or for user-defined FORMDEFs where the original FORMDEF has more than one Copy Group, use a logical name for the Page Format/Copy Group. For example, if the original PAGEDEF was named P1STATEM, then you could name the Page Formats as follows: STATEM1, STATEM2, and so on.
Parent Topic |