Printing with resources from a user library

You can access any PSF resource from user libraries that are not defined to other PSF jobs for that printer. You can specify a maximum of eight user libraries in the USERLIB or USERPATH parameter of the OUTPUT statement (see USERLIB or USERPATH).

Because PSF does not retain copies of resources from user libraries between print jobs, user libraries are useful for testing new resources and for protecting secure resources.

PSF does not use resources from user libraries for security page labeling or for processing separator pages or message data sets.

If a resource in a user library is marked PUBLIC and it exists in the printer, PSF uses the resident version of the resource. To use a page definition or a form definition from a user library, you must specify the name of the page definition or form definition in the user JCL.

PSF tells the printer not to capture resources loaded from user libraries. If you want them made resident in the printer, then you must directly install the resources into the printer, if your printer has this capability, or you must put the resources in a system library. PSF allows only PUBLIC resources from system libraries to be captured.

If you are using fonts from user libraries, the font resolution must be supported by the printer. You can look at the IM-IMAGE AND CODED-FONT RESOLUTION SELF-DEFINING FIELD in the PSF display printer information report to determine what pel resolutions the printer supports. If the printer does not support a font resolution, you must scale the font to fit the printer's supported pel resolution. For information about the display printer information function or information about how to convert fonts, see PSF for z/OS: Customization. Converting fonts is a task typically done by a system programmer.

Object container resources and FOCA extended code pages can reside in partitioned data set (PDS or PDSE) libraries and UNIX file path libraries. PSF accesses object containers and extended code pages in user libraries specified with the USERLIB and USERPATH parameters. If both parameters are specified on the OUTPUT statement, PSF uses this order to find the resource:

Examples:

In this example, the USERLIB parameter in the OUTPUT statement tells PSF to search the library specified on the USERLIB statement for the specified data sets. If the data sets are not found, PSF searches the system libraries defined in the startup procedure.
```
//OUT1 OUTPUT USERLIB=('USERA.IMAGES','USER.AFP.RESOURCES')
//DD1 DD SYSOUT=A,OUTPUT=(*.OUT1)
```
In this example, the USERPATH parameter in the OUTPUT statement specifies the path libraries for the TrueType and OpenType fonts and extended code pages that PSF needs to print the document. If the fonts are not found, PSF searches the system libraries defined with the FONTPATH parameter in the PSF startup procedure.
```
//OUT1 OUTPUT USERPATH=('/jdoe/fonts/truetype','/jdoe/fonts/truetype/myfonts/')
//DD1 DD SYSOUT=*,OUTPUT=(*.OUT1)
```
This example specifies user libraries that will be searched for resources before the PSF system libraries are searched. These resources are specified for the print job:
- Form definition F1USERA is in user library USERA.RESOURCE.
- Overlay O1USERA, referenced in F1USERA, is also in user library USERA.RESOURCE.
- Page definition A06462 is in a PSF system library. The page definition identifies the fonts needed to print a job.
- FOCA fonts are in PDS user library USERA.FONTS and extended code pages and TrueType and OpenType fonts are in user path libraries /jdoe/fonts/truetype and /jdoe/fonts/truetype/myfonts/.
- Fonts referenced in the overlay are in the system library.
```
//AFPUSERA JOB ...
//STEP1 EXEC PGM=USERA
//OUT1  OUTPUT FORMDEF=USERA,PAGEDEF=A06462,
//    USERLIB=('USERA.RESOURCE','USERA.FONTS'),
//    USERPATH=('/jdoe/fonts/truetype','/jdoe/fonts/truetype/myfonts/')
//PRINT DD SYSOUT=A,OUTPUT=(*.OUT1)
   /*
```