Types of control statements
There are three kinds of Control Statements in a DCF:
- Default statements identify a default parameter for an
mvs_keyword when one is not received from MVS. They
consist of only an mvs_definition.
Note: If you include multiple Default statements that use the same mvs_keyword, InfoPrint only uses the last one.
- Global statements identify an InfoPrint parameter
that should be used on all data set submissions. This statement uses
GLOBAL as the mvs_definition value.
Note: If you include multiple Global statements that use the same infoprint_attribute, InfoPrint only uses the last one.
- Mapping statements match mvs_keyword with their InfoPrint equivalents. These statements
must contain both an mvs_keyword and a control. If there is no Mapping
statement listed in the DCF for one or more of the mvs_keywords and
parameters that are received, InfoPrint adds
those mvs_keywords and parameters as unchanged printer-pass-through
attributes.
- Note:
- If you include multiple Mapping statements that use the same mvs_definition but map to different infoprint_attributes, all of them will be honored.
- If you include multiple Mapping statements that use the same mvs_keyword and map to the same infoprint_attribute, the last one mapped will be used.
- If you define a Mapping statement that maps to an infoprint_attribute that is also used in a Global statement, and the Mapping statement is used due to the MVS keywords in a received file, the Mapping statement will override the Global statement.
- If no matching Mapping statement is found for a received mvs_keyword and parameter, it will automatically be added to the printer-pass-through parameter. A null Mapping statement can be used to throw the mvs_keyword away entirely. A null Mapping statement contains an mvs_definition and a control, but no infoprint_definition.