JCL parameters for the Print Interface subsystem

This section describes how to code the SUBSYS JCL parameter to request that the Print Interface subsystem process a data set. It also describes the parameters of the DD and OUTPUT JCL statements that apply when you use the Print Interface subsystem.

SUBSYS=(subsystem_name[,'[printer_definition_name'][,'attribute=value ...']])

Specifies that the Print Interface subsystem is to process this data set.

The Print Interface subsystem supports these positional subparameters:

subsystem_name

Specifies the name of the Print Interface subsystem. This name must be the same as the Inventory name that is specified in the Infoprint Server configuration file. The Printer Inventory name is usually AOP1.

Default: None.

'printer_definition_name'

Specifies the name of the printer definition in the Printer Inventory that the subsystem uses to process the data set. This name is case-sensitive. If the name includes any lowercase characters or special characters, enclose the name in single quotation marks. If you want to omit this parameter, but still specify job attributes, code a comma to indicate the printer definition name is omitted.

Default: The first printer definition name found, using this order:

1. The printer definition name specified in the FSSDATA parameter on the OUTPUT JCL statement.
2. The Infoprint Server default printer definition. The name of the Infoprint Server default printer definition is specified in the Printer Inventory. The default name is lp1.

'attribute=value ...'

Specifies Infoprint Server job attributes that the subsystem uses to process and print the data set. For a list of valid job attributes, see Using job attributes.

Rules:

• Attribute names and values are case-sensitive. All attribute names are lowercase.
• Enclose the entire list of job attributes in single quotation marks.
• Separate job attributes with one or more spaces.
• If an attribute value contains blanks or special characters, enclose that attribute value in double quotation marks.
• You can specify up to 127 characters of job attributes.
• To continue the SUBSYS parameter on another line, end the first line with a comma at the end of a complete subparameter.
• If you cannot fit all job attributes on one line, see z/OS MVS JCL Reference for information about how to continue a parameter field enclosed in apostrophes.

Tip: If you want to specify more than 127 characters of job attributes, instead, specify the JCL parameter that corresponds to the job attribute. For example, specify the COPIES JCL parameter instead of the copies job attribute. Or, specify the job attributes in an attributes file.

Overrides: Job attributes override values specified in corresponding parameters of the DD and OUTPUT JCL statements. For a list of job attributes and their corresponding JCL parameters, see JCL parameters and corresponding job attributes.

Using an attributes file: You can store attributes and values in an MVS™ data set or in a UNIX file (such as, a zFS file). Follow these rules:

• Specify the MVS data set name or UNIX file name from which attributes are to be read in the attribute called attributes.
• If attributes are in an MVS data set, include a DD statement for the data set and specify the name of the DD statement as shown in this example:

  SUBSYS=(AOP1,'myprinter','attributes=//DD:MYATTR')

• Because Print Interface must be able to read the attributes data set, give the MVS data set RACF® universal read access and set the UNIX file permissions to let everyone read the file.
• For information about how to specify the attributes in the attributes file, see Attributes files.

Default: The first value found for each job attribute, using this order:

1. The value in a corresponding JCL parameter specified on the DD statement.
2. The value in a corresponding JCL parameter specified on the first OUTPUT statement referred to in the OUTPUT parameter on the DD statement.
3. The value in a corresponding JCL parameter specified on the first default OUTPUT statement in the job step.
4. The value in a corresponding JCL parameter specified on the first default OUTPUT statement in the job.
5. The value specified in the printer definition.
6. The JES default value for the corresponding JCL parameter. However, the JES default values for the CHARS, UCS, PAGEDEF, or FCB parameters are not used to transform data.

Examples:

• This example shows how to submit output to the Print Interface subsystem named AOP1:

  //DD1 DD SUBSYS=(AOP1,'myprinter') 

• This example shows how to submit output to the subsystem named AOP1 and specify that the output from the transform should include only pages 1 through 10 and should be printed on both sides of the sheet. The PCL to AFP, PostScript to AFP, and PDF to AFP transforms support the -p option.

  //DD1 DD SUBSYS=(AOP1,'myafpprinter',
  //       'filter-options="-p 1-10" duplex=yes')

• This example shows how to submit output to the subsystem named AOP1 and specify attributes in a UNIX file named /u/myuserid/myattributes:

  //DD1 DD SUBSYS=(AOP1,'myprinter','attributes=/u/myuserid/myattributes')
   

Parameters of the DD JCL statement that the Print Interface subsystem supports

Table 8 summarizes the parameters on the DD JCL statement, other than the SUBSYS parameter, that the Print Interface subsystem supports. It also describes the special considerations that apply when you use the Print Interface subsystem.

Parameters of the OUTPUT JCL statement that the Print Interface subsystem supports

Table 9 summarizes the parameters of the OUTPUT JCL statement that the Print Interface subsystem supports. It also describes some special considerations that apply when you use the Print Interface subsystem.

JCL statements that the Print Interface subsystem does not support

The Print Interface subsystem does not support these JCL statements:

• The JES2 /*OUTPUT JCL statement is ignored.
• The JES3 //*FORMAT JCL statement is ignored.