infoprint_definition

The infoprint_definition identifies the attribute and parameter that will be specified on the pdpr command when InfoPrint Manager sends the job to the printer. The infoprint_definition identifies an InfoPrint attribute and (optionally) the value that it should be set to. infoprint_definitions follow this syntax:

infoprint_attribute[=infoprint_parameter]
Note: In Control Statements, mvs_definitions, controls, and infoprint_definitions themselves cannot contain any white space (spaces or tabs). The first occurrence of white space separates the mvs_definition from the control and the second separates the control from the infoprint_definition. As a result, if the elements contain white spaces, the DCF will not complete the mapping correctly.

The infoprint_attribute is the InfoPrint attribute name as it is listed in the InfoPrint Manager: Reference under –x options, plus the specially recognized target-destination-name, which is used to identify the –p option of the pdpr command. The infoprint_parameter is the value that is assigned to that attribute.

infoprint_definitions work differently in each kind of control statement.

  • In Default statements, you cannot specify an infoprint_definition.
  • In Global statements, you must specify an infoprint_definition.
  • In Mapping statements, you should specify an infoprint_definition to map the mvs_definition to. However, if you specify an infoprint_attribute, you do not have to specify an infoprint_parameter with it. If you only list an infoprint_attribute, the mvs_parameter value from the mvs_keyword becomes the infoprint_attribute value.
      Note:
    1. If you do not provide an infoprint_definition in a Mapping statement, the information contained in that mvs_keyword will be discarded.
    2. If you provide multiple Mapping statements that lead to the same attribute only one will be used, but it is impossible to predict which one that will be.
  • To identify an infoprint_attribute that you want to use on the -x option of the pdpr command, omit the -x, for example: media-id.
  • To identify an infoprint_attribute that you want to use on the printer-pass-through attribute of the pdpr command, prefix the infoprint_attribute with an -o flag for example, -ojobid. All generated—o attributes will be collected and added to a single printer-pass-through attribute.
  • To identify an infoprint_attribute that you want to use on the -opa option of the printer-pass-through attribute of the pdpr command, prefix the infoprint_attribute with an -opa, for example, -opa:class. All generated—opa attributes will be collected and added to a single -opa keyword on the printer-pass-through attribute.
  • To identify that the mvs_definition is to map to the name of the target destination for submission, specify target-destination-name, which is a specially-recognized infoprint_attribute that overrides the third parameter that is passed to the sample MVS Download Exit.
  • To handle complex, multi-valued infoprint_attributes, begin the infoprint_parameter with as many colons (:) as necessary to move the parameter into the correct position. For example, the results-profile attribute follows this syntax:
    -x "results-profile=name@node:method:number:'message text':bin"

    In use, the attribute would look like this:

    -x "results-profile=nr645@bld25:pickup:2:'Please read this'"
    So, if you wanted to map the COPIES value to the 'number' parameter of results-profile, you would enter two colons (::) in the mapping statement. The two colons indicate that the program should skip over the first two parameters in the results-profile (name@node and method), and insert the value in the third position (number). The mapping statement would look like this:
    COPIES   ::  results-profile=::
    You can include a hard-coded infoprint_parameter in the statement, but you do not have to. If you do not include one, the normal rules for determining the resulting infoprint_parameter apply.