If you try to use Cyrillic or Japanese characters on PDF banner pages with a workflow
that uses the default values for the Header page configuration file and Trailer page configuration file properties, the characters do not display correctly.
If you click the Jump to control in the Ricoh ProcessDirector user interface and the page where the printer resumes is not the page displayed in
the viewer, check for functions that can introduce inaccurate page counts. Examples
are cut sheet emulation, N_UP printing, and the Duplex and Form definition job properties.
If a job received from Download for z/OS or AFP Download Plus prints on a printer other than the one you expected, you might have to change the
printer properties or your configuration file so that Ricoh ProcessDirector uses the value of the DEST parameter in the job's JCL to select the printer.
If a job goes into an error state and you see message AIWI6416E, there might be a problem with the AFP file or there might have been an error when
Ricoh ProcessDirector tried to connect to the printer.
If a job goes into an error state during the PrintJobs step and you do not see an
error message on the error-message pages or in the printer log, there may be more
information in /var/psf/printernameaiw1/error.log (AIX and Linux) or C:\Program Files (x86)\InfoPrint\PSF\var\psf\printernameaiw1\error.log (Windows). printername is the name of your printer.
The AFP architecture lets applications put multiple documents in a single file. The
document boundaries are marked with Begin Document (BDT) and End Document (EDT) structured
fields. Applications might use this function to cause finishing operations, such as
stapling or binding, to operate on each document separately. However, some steps provided
in many workflows supplied with Ricoh ProcessDirector cannot process files that contain multiple documents.
Usually Ricoh ProcessDirector can resume printing from the last stacked page when a jam is cleared from the printer.
However, for AFP printers only (especially continuous forms printers) follow these
steps if you need to reprint some of the pages that were successfully stacked. For
example, you might need to be certain that you have complete jobs for any post-processing
If AFP support is installed and your job was sent to an AFP printer, where it printed
on the wrong paper (for example green instead of blue paper), you might need to update
some job or printer properties.
If your job was sent to a Ricoh PDF, Custom PDF, or Ricoh TotalFlow printer and it
printed on the wrong paper (for example green instead of blue paper), you might need
to update some job or printer properties.
When a job stops in the No matching device state, check the Requested printer property and make sure that the scheduling properties for the job match the corresponding
properties of the requested printer.
When a job stops and the value of the Current job state details column is No matching media, the media name or media properties in the JDF job ticket or overrides file for the
job cannot be matched to an existing media object.
If you see an out of memory message or encounter slow processing when printing a large
PDF file, you can set the Merge banner pages into PDF print file property to No or increase the Java Virtual Machine (JVM) memory. Merging banner pages on large
PDF files takes more memory and system resources than printing banner pages as separate
files. If you need to merge banner pages, increase the JVM memory.
If you have trouble with document property values that are extracted from PDF files
using Ricoh ProcessDirector Plug-in for Adobe Acrobat, the fonts included in the PDF file might be incomplete or contain different UNICODE
mappings than you expect.