PSF for z/OS: Customization
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Selecting form definitions, page definitions, and fonts

PSF for z/OS: Customization
S550-0427-04

Selecting form definitions, page definitions, and fonts

Hierarchy lists in Form definitions in deferred-printing mode through TrueType and OpenType fonts in deferred-printing mode show how the form definition, page definition, and fonts for a print job are selected. PSF takes the user’s JCL parameters from the DD statement and the first OUTPUT statement found; the search proceeds in the following order:

  1. Explicitly referred to
  2. Implicitly referred to at the step level
  3. Implicitly referred to at the job level

If the same parameter appears both on the DD statement and on the OUTPUT statement, PSF uses the parameter from the DD statement.

An "explicitly referred to" OUTPUT statement is one named by the OUTPUT parameter of a DD statement. An "implicitly referred to" OUTPUT statement must contain a DEFAULT=YES parameter and must not be overridden by any OUTPUT keyword on a DD statement5. In the following example, OUT1 is an OUTPUT statement that is explicitly referred to: 

//JOB01   JOB     MSGCLASS=A
//STEP01  EXEC    PGM=ENDMONTH
//OUT1    OUTPUT  CHARS=60D8
//DD1     DD      SYSOUT=A,OUTPUT=*.OUT1

In the following example, OUTA is an OUTPUT statement that is implicitly referred to: 

//JOB02   JOB     MSGCLASS=A
//OUTA    OUTPUT  DEFAULT=YES,CHARS=60D8
//STEP01  EXEC    PGM=ENDMONTH
//DD1     DD      SYSOUT=A

For more information about the OUTPUT statement, see the z/OS MVS JCL Reference.

Form definitions in deferred-printing mode

This is the hierarchy of form definition selection in deferred-printing mode:

  1. Internal copy group immediately followed by an IMM structured field in the print data set (see Note 1)
  2. FORMDEF= specified on OUTPUT statement of the user JCL:
    1. Explicitly referred to (see Notes 2 and 3)
    2. Implicitly referred to step-level
    3. Implicitly referred to job-level
  3. First inline form definition (see Note 4)
  4. Form definition specified in Printer Inventory or FORMDEF= specified on PRINTDEV statement in the PSF startup procedure
Notes:
  1. Internal copy groups immediately followed by an IMM structured field in the print data set are used before copy groups specified by a form definition.

    An IMM structured field that does not immediately follow an internal copy group cannot reference an internal copy group elsewhere in the document; therefore, PSF assumes that the IMM references a copy group in a form definition.

  2. This includes inline form definitions, which are specified on the OUTPUT statement either by name or with the name DUMMY. If multiple inline form definitions are specified on the OUTPUT statement with the name DUMMY, PSF uses the last inline form definition in the print data set.
  3. This includes a form definition in a user library, which must be specified by name on the OUTPUT statement.
  4. If the user JCL does not specify the form definition parameter and there are inline form definitions, the first inline form definition in the print data set is selected.

Form definitions in direct-printing mode

This is the hierarchy of form definition selection in direct-printing mode:

  1. Internal copy group immediately preceding the IMM record in the print data set (see Note 1)
  2. FORMDEF= specified on explicitly referred to OUTPUT statement of the user JCL (see Note 2)
  3. First inline form definition (see Note 3)
  4. FORMDEF= specified on PRINTDEV statement of the user JCL
Notes:
  1. An IMM structured field that does not immediately follow an internal copy group cannot reference an internal copy group elsewhere in the document; therefore, PSF assumes that the IMM references a copy group in a form definition.
  2. This includes inline form definitions, which are specified on the OUTPUT statement either by name or with the name DUMMY. If multiple inline form definitions are specified on the OUTPUT statement with the name DUMMY, PSF uses the last inline form definition in the print data set.
  3. If the user JCL does not specify the form definition parameter and there are inline form definitions, the first inline form definition in the print data set is selected.
  4. PSF does not use user libraries in direct-printing mode.

Page definitions in deferred-printing mode

This is the hierarchy of page definition selection in deferred-printing mode:

  1. In the user JCL:
    1. PAGEDEF= specified on OUTPUT statement (see Note 1)
    2. FCB= specified on DD statement
    3. FCB= specified on OUTPUT statement (see Note 1)
  2. JES default in the current printer setup (see Notes 2 and 3)
  3. First inline page definition (see Notes 4 and 5)
  4. Page definition specified in Printer Inventory or PAGEDEF= specified on PRINTDEV statement in the PSF startup procedure (see Note 3)
Notes:
  1. The OUTPUT statement used is the first one found from explicit, step-level implicit, and job-level implicit.
  2. Under JES2, the JES default PAGEDEF can be specified by the FCB parameter in the PRTnnnn statement or, if this parameter is not present, by the NIFCB parameter in the PRINTDEF statement.
  3. Under JES3, a page definition specified in the Printer Inventory or the PRINTDEV statement is only selected if PDEFAULT=FCB and WS=C are specified on the DEVICE statement. Otherwise, if PDEFAULT=NONE or PDEFAULT is not specified, a JES3 default page definition is taken from the CARRIAGE parameter on the DEVICE statement or, if this parameter is not present, from the CARRIAGE parameter on the OUTSERVE statement. If the OUTSERV statement has no CARRIAGE parameter, a default of 6 lines per inch (lpi) is used, which selects page definition P16. To use inline page definitions in JES3, the name of the page definition should be specified in the PAGEDEF or FCB of the user JCL.
  4. For JES2, if the user JCL does not specify the PAGEDEF or FCB parameter and inline page definitions exist, the first inline page definition in the print data set is selected unless JES has set a default.
  5. If an inline page definition is included in the print data set, and either its name matches the name selected or the name from the JCL is DUMMY, the inline page definition is used. If multiple inline page definitions are specified as PAGEDEF=DUMMY on the OUTPUT statement, PSF uses the last inline page definition in the print data set.
  6. A page definition from a user library is used if its name matches the name selected.

Page definitions in direct-printing mode

This is the hierarchy of page definition selection in direct-printing mode:

  1. In the user JCL:
    1. PAGEDEF= specified on explicitly referred to OUTPUT statement of the user JCL (see Note 1)
    2. FCB= specified on DD statement (see Note 1)
    3. FCB= specified on explicitly referred to OUTPUT statement of the user JCL (see Note 1)
  2. First inline page definition (see Note 2)
  3. PAGEDEF= specified on PRINTDEV statement of the user JCL
Notes:
  1. This includes inline page definitions, which are specified by name or with the name DUMMY, on the OUTPUT or DD statement. If multiple inline page definitions are specified as PAGEDEF=DUMMY on the OUTPUT statement, PSF uses the last inline page definition in the print data set.
  2. If the user JCL does not specify the PAGEDEF or FCB parameter and inline page definitions exist, the first inline page definition in the print data set is used.
  3. PSF does not use user libraries in direct-printing mode.

FOCA fonts in deferred-printing mode

When PSF is printing line-format data, this is the hierarchy of FOCA fonts selection in deferred-printing mode:

  1. Fonts specified by the current page definition, including a JES default page definition (see Note 1)
  2. In the user JCL:
    1. CHARS= specified on DD statement
    2. CHARS= specified on OUTPUT statement (see Note 2)
    3. UCS= specified on DD statement
    4. UCS= specified on OUTPUT statement (see Note 2)
  3. JES default font in the current printer setup (see Notes 3 and 4)
  4. Character sets specified in Printer Inventory or CHARS= specified on PRINTDEV statement in the PSF startup procedure
  5. If the Printer Inventory or the PRINTDEV statement of the PSF startup procedure names the active page definition, any fonts specified in that page definition are loaded
  6. Hardware default
Notes:
  1. The current page definition does not include a page definition specified by the Printer Inventory or the PRINTDEV statement of the PSF startup procedure.
  2. The OUTPUT statement used is the first one found from explicit, step-level implicit, and job-level implicit.
  3. Under JES2, you can select fonts with a SET command, the UCS parameter of the PRTnnnn statement, or the NIUCS parameter of the JES2 PRINTDEF statement. To prevent JES2 from sending a default font name to PSF, specify UCS=0 in the PRTnnnn statement. For more information about selecting fonts, see z/OS JES2 Initialization and Tuning Reference or PSF for z/OS: User’s Guide.
  4. Under JES3, you can select fonts with the CH parameter in the *START, *RESTART, and *CALL commands. You can also use the CHARS parameter in the DEVICE, OUTSERV, and SYSOUT statements. If PDEFAULT=CHARS and WS=U are specified in the JES3 DEVICE statement, hardware default fonts or fonts specified in the Printer Inventory or the PRINTDEV statement are selected; otherwise, hardware default fonts or fonts specified in the Printer Inventory or the PRINTDEV statement are never selected. For more information about selecting fonts, see z/OS JES3 Initialization and Tuning Reference or PSF for z/OS: User’s Guide.

FOCA fonts in direct-printing mode

When PSF is printing line-format data, this is the hierarchy of FOCA fonts selection in direct-printing mode:

  1. Fonts specified by the current page definition (unless the current page definition is only specified by the PRINTDEV statement)
  2. In the user JCL:
    1. CHARS= specified on DD statement
    2. CHARS= specified on explicitly referred to OUTPUT statement
    3. UCS= specified on DD statement
    4. UCS= specified on explicitly referred to OUTPUT statement
    5. CHARS= specified on PRINTDEV statement
  3. If the PRINTDEV statement names the active page definition, any fonts specified in that page definition are loaded
  4. Hardware default

TrueType and OpenType fonts in deferred-printing mode

When PSF is printing line-format data, this is the hierarchy of TrueType and OpenType fonts selection in deferred-printing mode:

  1. Fonts specified by the current page definition (the current page definition does not include a page definition specified by the Printer Inventory or the PRINTDEV statement of the PSF startup procedure)
  2. If the Printer Inventory or the PRINTDEV statement of the PSF startup procedure names the active page definition, any fonts specified in that page definition are loaded

TrueType and OpenType fonts in direct-printing mode

When PSF is printing line-format data, this is the hierarchy of TrueType and OpenType fonts selection in direct-printing mode:

  1. Fonts specified by the current page definition (unless the current page definition is only specified by the PRINTDEV statement)
  2. If the PRINTDEV statement names the active page definition, any fonts specified in that page definition are loaded
5.
You cannot use an "implicitly referred to" OUTPUT statement on a printer in direct-printing mode.

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014