We have AFP data not printing correct logo.
After investigating, it turns out that a pageseg was updated on 11/15/16, but one particular PIOM server was using a VDI with the timestamp of 4/28/16.
After removing this VDI, the server picked up the new pageseg and printed the correct logo.
Doesn't PIOM go out and get the print resources every single time? Why was this server using an old VDI?
In-line resources (p.340)
The AFP and Xerox input modules can also manage jobs using native in‐line
resources. These are jobs where some or all the resources are held within the data
stream. For example, jobs created by the document composition packages PReS and
The input module extracts the native resources from the data stream and places them
in a specified directory. How this extraction is dealt with is specified by the Profile
command INLINE_RESOURCE. The options for this parameter are:
DEFAULT Defaults to the data stream option. With AFP jobs this means
that native resources are always written to the job directory
and deleted after use. See below for Xerox jobs using the
PERMANENT Writes native resources to the central directories only.
TEMPORARY Writes native and virtual resources to the job directory only,
so that they are deleted after job run.
HOLDIFDIF Writes native resources to the central directories, only if they
are different from the resources that are already there.
Virtual resources (VDF, VDI, VDO) for jobs with in‐line resources are always written
to the job directory.
VDD files are written to the directory specified in the SET file.
Search Sequence (p.344)
1.Work through the provided search sequence from left to right. The first item in the search sequence is always the job directory.
2.If the virtual equivalent already exists in the local resource directory, provide that as the result to the calling P/I Output Manager module.
3.If processing a local resource directory, can a virtual resource be created from the native resources in the same local resource directory? If it can, place the resulting virtual resource in the same local resource directory and provide that as the result to the calling P/I Output Manager module.
4.If no native or virtual resource is found in job directory, continue on the next item specified in the search sequence being processed.
5.If the next item is a virtual substitution option, use as is without checking against a native and provide that as the result to the calling P/I Output Manager module.
6.If the next item is not a virtual substitution option and a native exists in one of the central directories, check if there is a virtual equivalent in existence in the VDFP/VDIP/VDOP locations. If there is, convert only if the native is newer than the virtual. If there is not a virtual in existence in the VDFP/VDIP/VDOP locations, convert the native into the virtual, place the virtual in the VDFP/VDIP/VDOP location and provide that as the result to the calling P/I Output Manager module.
7.If no virtual was created or updated, continue with the next item in the search sequence.
8.If the end of the search sequence is reached without successfully identifying a resource, a final check is made to see if there is an existing virtual resource in the VDFP/VDIP/VDOP locations without an associated native, if so this is provided to the calling module. This is necessary for reprints, etc. without an existing native resource.
9.If the end of the search sequence is reached and no preexisting VDF/VDI/VDO has been found, indicate to the calling module that the resource could not be located.
Use INLINE_RESOURCE=HOLDIFDIF in the profile.
UPDATED: December 27, 2016