Specifying a page definition

If your job requires special page definition options, specify a page definition containing those options in the JCL for the print job. To do this, code the page definition name, without its two-character prefix of "P1", in the PAGEDEF parameter of the OUTPUT statement (see PAGEDEF). For compatibility with non-AFP printers, you can code the page definition name in the FCB parameter of the DD or OUTPUT statement (see FCB). The name coded in the FCB parameter cannot be more than four characters long.

The page definition must be stored in a private user library, a PSF user library (if supported for your system), or inline as part of the print data set (except in XML data). You can create your own page definition or use a page definition already available on your system. To use a page definition from a PSF user library, see Printing with resources from a user library.

PSF provides standard page definitions for traditional line data, which are listed in Page definitions supplied with PSF. Page definitions are provided to fit standard paper sizes for AFP printers. These page definitions provide different combinations of line spacing and print direction, as well as some multiple-up definitions. The page definitions are referred to in the following examples.

Examples:

This example specifies a user-created page definition named P1MYPDEF, as well as a form definition named F1MYFDEF, in the OUTPUT statement. Do not code the prefixes P1 and F1 in your JCL.
```
//AFPUSERA JOB ...
//STEP1 EXEC PGM=USERA
//OUT2  OUTPUT PAGEDEF=MYPDEF,FORMDEF=MYFDEF
//DD2 DD SYSOUT=A,OUT=(*.OUT2)
```
To create a page definition, use an AFP utility product such as IBM® Page Printer Formatting Aid (PPFA). For information about how to use PPFA to create page definitions, see Page Printer Formatting Aid: User’s Guide. For information about form definitions, see Specifying a form definition.
In this example, a page definition named P1STD1, supplied with PSF for compatibility with non-AFP printers, is specified with the FCB parameter in the DD statement. Because no form definition is selected for this job, the PSF default form definition for the printer is used.
```
//AFPUSERB JOB ...
//STEP1 EXEC PGM=USERB
//DD2 DD SYSOUT=A,FCB=STD1
```

In this example, an FCB is specified in the OUTPUT statement:

//AFPUSERD JOB ...
//STEP1 EXEC PGM=USERD
//OUTPUT1 OUTPUT FCB=STD1
//DD1 DD SYSOUT=A,OUTPUT=(*.OUTPUT1)

In this example, page definition P1MYPDEF is coded inline in the print data set that is generated by the program USERC. For information about coding inline resources, see Mixed Object Document Content Architecture Reference, AFPC-0004.
```
//AFPUSERC JOB ...
//STEP1 EXEC PGM=USERC
//OUT1  OUTPUT PAGEDEF=DUMMY
//DD1 DD SYSOUT=A,OUT=(*.OUT1)
```
The PAGEDEF parameter must specify either the resource name of the inline page definition or the keyword DUMMY. If the name in the PAGEDEF parameter does not match the name of an inline page definition, PSF uses the resource from the resource library that matches the name in the JCL. If the PAGEDEF parameter is not specified in the JCL, PSF selects the first inline page definition in the print data set.

For more information about the function of a page definition in printing, see Page definitions.

Using page definitions from a user library

You can instruct PSF to select a page definition from your user library rather than from a system library assigned to PSF. To use a page definition from a user library:

Using inline page definitions

Notes:

If you specify PAGEDEF=DUMMY in your JCL, and you do not include an inline page definition, PSF uses the default page definition for your printer.
If you specify multiple inline page definitions in the print data set and you specify PAGEDEF=DUMMY on the OUTPUT statement, PSF uses the last inline page definition in the print data set.
If you do not specify the PAGEDEF or FCB parameter in your JCL, PSF selects the first inline page definition in the print data set, unless a JES default page definition exists.
You cannot use inline resources in XML data.

You can include more than one inline page definition in a print data set, and you can change the page definition name in the JCL on different printing jobs to test different page definitions. If, however, the name of an inline page definition does not match the PAGEDEF name specified in the JCL, PSF uses the page definition from the resource library that matches the name in the JCL. For more information about using inline page definitions, see Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884.

Using page definitions converted from FCBs

PSF supports line data applications designed for line printers, so that those jobs can be processed on a page printer with no need to change the application program or its JCL. If you do not specify a PAGEDEF parameter, but you do specify a forms control buffer (FCB) parameter, PSF uses the FCB name as the page definition name.

If you are using line printers, you are probably using some of the FCB modules provided by IBM. Those FCBs are converted to page definitions and are provided in the system page definition library. If you used other FCB modules for your line printer, check with your system support group to see whether the FCBs are converted to page definitions before you attempt to use them.