The search order for AFP resources

This section describes the order and the conditions on which InfoPrint searches for AFP resources:

  1. For fonts, paths specified by the -osrchfontlib keyword on the enq, lp, qprt, or lprafp command
  2. Paths specified by the -oreslib keyword on the enq, lp, qprt, or lprafp command
  3. The path specified by the resource-context-user document attribute.
  4. The paths specified by one of these document attributes, depending on the type of resource:
    • resource-context-font
    • resource-context-form-definition
    • resource-context-overlay
    • resource-context-page-definition
    • resource-context-page-segment
    Note: When one of these document attributes contains a value, InfoPrint ignores any location specified by the same attribute of a default document object if one is used with the job.
  5. The path specified by the resource-context document attribute.
  6. The path specified by the PSFPATH environment variable.

    If you are using OpenType Fonts, you must allow the InfoPrint Fonts product to install its resource access table for keeping track of these fonts in the default directory. On an InfoPrint Manager Windows server, if you change the location of this table from the folder where it was installed, you can update the global search path on your Windows system with the global resource path for these fonts.

  7. The paths specified by the resource-context attributes of the actual destination.
  8. For fonts, the directory where your fonts are installed.

Once a resource is located, the search ends, and the located resource is used to process the job, as long as the user can access the resource. If InfoPrint Manager ultimately cannot find a required resource, it prints an error message advising you of the missing resource. InfoPrint Manager reports that the job completed successfully.

If the only AFP resources you use are the AFP resources that shipped with InfoPrint Manager, there is no need to use resource-context objects. All of your resources are located automatically because these resources reside in the reslib, fontlib, and font directories described above. If, on the other hand, you have custom AFP resources, make sure that you do not store them in the reslib, fontlib, or font directories listed. Any custom resources stored in these locations might be corrupted by installing, uninstalling, or servicing the software. Store any custom AFP resources in a directory outside these locations and use resource-context objects to provide access to them.

When InfoPrint Manager puts together the total of all resource contexts for a particular resource type, InfoPrint Manager tries this list of extensions in order while searching each directory for a particular resource. For example, InfoPrint Manager is searching for a 300–pel raster font named C0H20000 and these conditions are true:

  • Document attributes are set to resource-context-font=\myfonts
  • resource-context=\all_resources
  • The $PSFPATH environment variable has not been set.
  • The resource-context-font actual destination attribute has not been set.
A list of files similar to this would be checked in sequence:
  1. x:\myfonts\C0H20000.300
  2. x:\myfonts\C0H20000.FONT300
  3. x:\myfonts\C0H20000
  4. x:\all_resources\C0H20000.300
  5. x:\all_resources\C0H20000.FONT300
  6. x:\all_resources\C0H20000
  7. With InfoPrint Manager:
    1. The /usr/lpp/psf/reslib directory.
    2. For fonts, the /usr/lpp/afpfonts directory.
    3. For fonts, the /usr/lpp/psf/fontlib directory.
Once InfoPrint Manager finds a matching file, the search ends.

If InfoPrint Manager cannot find the resource in any of the paths, it stops the job and prints an error message at the end of the job.

In this section:

  1. CMRs and data objects search order
    The search order for CMRs and data objects is different from the order used for other AFP resources.
  2. File extensions for resources
Parent topic: Creating and managing resource-context objects