Common object containers supported by PSF

PSF supports all object containers that are supported by the printer. These are some of the common object containers that PSF can send to the printer:

• Color management resources
• Color mapping table resources
• Encapsulated PostScript resources
• IOCA tile resource objects
• Microfilm setup resources
• Multiple-image and multiple-page resources
• PDF single-page object resources
• PDF resource objects
• Resident color profile resource objects

For a complete list of object container types that might be supported by PSF and the printer, see registered object-type OIDs in the MO:DCA registry in Mixed Object Document Content Architecture Reference, AFPC-0004.

Color management resource (CMR)

A color management resource is an object that provides color management in presentation environments.

Because CMR objects do not reside in partitioned data sets, a prefix is not needed for the name. For more information, see Color and grayscale printing or see Color Management Object Content Architecture Reference, AFPC-0006.

For print jobs that use CMRs, IBM® recommends you use outline fonts or TrueType and OpenType fonts. See Obtaining and referencing fonts.

Color mapping table (CMT) resource

For some printers, such as the InfoPrint Color 100 and the InfoPrint Color 130 Plus, you can use a color mapping table (CMT) to map non-color fields to color; old color fields to new color fields; and new color fields to different new color fields. Thus, with a CMT, you can specify new color fields in existing applications and documents without changing the documents or applications. You can also use various color mappings with a single document to print the document, specifying color in a variety of ways without changing the original document. CMT resources are stored in the object container library. IBM recommends a prefix of M1 for color mapping tables.

For more information, see the COLORMAP parameter (COLORMAP) and Using color mapping tables.

Encapsulated PostScript (EPS) resource

An EPS resource, which can contain any combination of text, graphics, and images, can be included along with MO:DCA-P data and printed on an IPDS printer that supports this object.

An EPS resource can be a soft or hard resource and is stored in the object container library. If the EPS resource is identified in the print data set by using a Map Data Resource (MDR) structured field, it is considered a hard resource. If the EPS resource is not identified by using the MDR structured field, but is just included through an Include Object (IOB) structured field, it is considered a soft resource.

EPS data does not need to be wrapped in MO:DCA-P structured fields when it is stored as a resource. If EPS data is to be embedded in the data stream, it must be wrapped in MO:DCA-P structured fields.

Because an EPS resource is a type of object container resource, and PSF does not enforce a prefix for the 8-character name of an object container resource, your site can define a naming convention to avoid conflicts with other object container resources. IBM recommends a prefix of E1 for EPS objects. For more information, see Object containers as data object resources.

IOCA tile resource object

An IOCA tile resource object is an IOCA FS45 tile resource. An IOCA tile resource object must be identified in the print data set by using an MDR structured field. An IOCA tile resource object does not need to be wrapped in MO:DCA-P structured fields when it is stored as a resource. If this object is to be embedded in the data stream, it must be wrapped in MO:DCA-P structured fields.

Because an IOCA tile resource object is a type of object container resource, and PSF does not enforce a prefix for the 8-character name of object container resources, your site can define a naming convention to avoid conflicts with other object container resources. IBM recommends a prefix of IT for IOCA tile resource objects. For more information, see Image Object Content Architecture Reference, AFPC-0003.

Microfilm setup resource

To print to a microfilm device, you need to specify a microfilm setup resource for your document. The microfilm setup resource is similar in concept to a form definition. The structure of the object container data field in the microfilm setup resource is defined by the manufacturer of the microfilm device. You can use microfilm setup resources to specify the processing commands for various microfilm device functions, such as titles, format, and extraction masks. Microfilm setup resources are stored in the object container library.

For information about how to use the utility that generates and packages the data in the microfilm setup resource, see PSF for z/OS: Customization. The utility, provided with the microfilm device, places the setup resource information in an AFP object container, which is associated with the AFP print job by using JCL keywords. The resulting microfilm resource object container can be placed in a system library, in a user library, or inline in the data stream. PSF sends the object container setup resource with your data set to the microfilm device. If you do not specify a microfilm setup resource for your document, PSF uses the host default microfilm setup resource that your system programmer created, and your output might not appear as you expected.

For more information about the microfilm setup resource, see the publications provided with the microfilm device.

Because a microfilm setup resource is one type of object container resource, and PSF does not enforce a prefix for the 8-character name of the microfilm setup resource, your site can define a naming convention to avoid conflicts with other object container resources. IBM recommends a prefix of H1 for microfilm setup resources.

For more information about sending print jobs to a microfilm device, see Microfilm device considerations.

Multiple-image and multiple-page resources

PDF multiple-page object resources, which can contain any combination of text, graphics, and images with PDF operators, and TIFF multiple-image object resources can be included along with MO:DCA-P data and printed on an IPDS printer that supports the objects. PDF multiple-page and TIFF multiple-image object resources can be transferred to the printer as one AFP object container, which optimizes file size, reduces processing time, and lets you individually reference and print one or more pages or images.

PDF multiple-page and TIFF multiple-image object resources can be stored inline with the print data, in a user library, or in the system object container library. When a multiple-page or multiple-image object is stored as a resource, it does not need to be wrapped in MO:DCA-P structured fields, but the page or image you want to reference must be included with an Include Object (IOB) structured field and the offset of the page or image must be specified. If the object offset is not specified, the first page or image within the object container is selected. When the object container is embedded in the data stream, it must be wrapped in MO:DCA-P structured fields.

PDF single-page object resource

A PDF single-page object resource, which can contain any combination of text, graphics, and images with PDF operators, can be included along with MO:DCA-P data and printed on an IPDS printer that supports this object. A PDF single-page object resource can be a soft or hard resource that is stored inline with the print data, in a user library, or in the system object container library.

If the PDF single-page object resource is identified in the print data set by using an MDR structured field, it is considered a hard resource. If the PDF single-page object resource is not identified by using the MDR structured field, but is just included through an Include Object (IOB) structured field, it is considered a soft resource.

A PDF single-page object does not need to be wrapped in MO:DCA-P structured fields when it is stored as a resource. If this object is to be embedded in the data stream, it must be wrapped in MO:DCA-P structured fields.

Because a PDF single-page object resource is a type of object container resource, and PSF does not enforce a prefix for the 8-character name of an object container resource, your site can define a naming convention to avoid conflicts with other object container resources. IBM recommends a prefix of PP for PDF single-page object resources. For more information, see Object containers as data object resources.

PDF resource object

A PDF resource object can be referenced by a PDF single-page or multiple-page object. Examples of PDF resource objects are fonts, font descriptors, and raster images. PDF resource objects must be identified in the print data set by using an MDR structured field.

A PDF resource object does not need to be wrapped in MO:DCA-P structured fields when it is stored as a resource. If this object is to be embedded in the data stream, it must be wrapped in MO:DCA-P structured fields.

Because a PDF resource object is a type of object container resource, and PSF does not enforce a prefix for the 8-character name of object container resources, your site can define a naming convention to avoid conflicts with other object container resources. IBM recommends a prefix of PR for PDF resource objects.

Resident color profile resource object

A resident color profile resource object is a device-resident resource object that defines how device-dependent colors in a data object are related to device-independent colors. For example, many data object resources contain colors specified in the CMYK color space but tuned to one of a number of offset press standards that are geography-based. Some examples of resident color profiles are CMYK SWOP (US) and CMYK Euroscale (Europe). A resident color profile resource object defines how to render the colors in the data object resource that references it.

See the printer documentation to determine whether the printer has resident color profile resource objects and which ones are available.