InfoPrint Manager PSF messages

0420-001

This message identifies the code page that should be used when you print the messages in this product message file.

0420-002

ERROR: Not enough memory is available for data storage.

Explanation:: There is not enough memory available to complete program initialization.
System action:: The program cannot continue.
User response:: Use local problem-reporting procedures to report this message.

0420-003

ERROR: Data cannot be initialized at the actual destination.

Explanation:: The IPDS commands required to erase downloaded resources and page data from the device were not successfully received by the device. A significant communications problem exists between InfoPrint Manager and the device.
System action:: InfoPrint Manager does not complete the requested operation.
User response:: Turn the actual destination power off and back on. Use either the Enable Action icon from the Actions area on the GUI window or the pdenable command to start InfoPrint Manager and ready the device or devices. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-004

InfoPrint Manager encountered a memory constrained condition.

Explanation:: The system encountered a memory constrained condition while processing the current print job.
System action:: The job will continue to be processed, but system performance will be degraded.
User response:: Use local problem-reporting procedures to report this message.

0420-005

ERROR: InfoPrint Manager is out of IPDS buffers.

Explanation:: InfoPrint Manager has run out of IPDS data buffers. All attempts to free unused buffers have failed.
System action:: InfoPrint Manager cannot proceed.
User response:: Use local problem-reporting procedures to report this message.

0420-006

ERROR: The Accounting user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.

Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-007

ERROR: The Accounting user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.

Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-008

ERROR: The Header Page user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-009

ERROR: InfoPrint Manager cannot find the Accounting user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name on the -x option of the pdcreate command is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-010

ERROR: The Accounting user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-011

ERROR: A syntax error was detected with ____ line ____ for value ____.

Explanation:

A syntax error was found in the GRID file specified in the message. Ensure that the value meets the following syntax rules for the appropriate field:

charset: Must not contain more than 8 characters and include characters permitted within resource names by the AFP data stream and within filenames by the operating system.
codepage: Must not contain more than 8 characters and include characters permitted within resource names by the AFP data stream and within filenames by the operating system.
fgid: Must be a numeric decimal value in the range 1 - 65534.
cpgid: Must be a numeric decimal value in the range 1 - 65534.
gcsgid: Must be a numeric decimal value in the range 1 - 65534 or an asterisk (*) which indicates a 'wildcard' or a dash (-) which indicates that no identifer is being specified.
vsize: Must be a numeric decimal value in the range 1 - 65534 or an asterisk (*) which indicates a 'wildcard' or a dash (-) which indicates that no vertical size is being specified.
width: Must be a numeric decimal value in the range 1 - 65534 or an asterisk (*) which indicates a 'wildcard' or a dash (-) which indicates that no width is being specified.
attributes: Must consist either of some combination of the characters 'B' for bold, 'I' for italic, and 'D' for doublewide. Or a dash (-) which indicates that nothing is being specified. These characters are not case-sensitive.

System action:

InfoPrint Manager cannot start this InfoPrint Manager instance.

User response:

Edit the GRID file and ensure that the value that caused the error follows the syntax rules for that field.

0420-012

ERROR: Destination type ____ is not valid.

Explanation:: The actual destination type specified to InfoPrint Manager is not valid.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-013

ERROR: The actual destination reported a configuration that InfoPrint Manager does not support.

Explanation:: The actual destination, specified in an accompanying message, reported that it has a certain hardware or software feature. InfoPrint Manager does not support or cannot communicate with that feature.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-014

ERROR: The specified actual destination does not have full IPDS capability, status code X'____'.

Explanation:

InfoPrint Manager can communicate with the actual destination specified in the accompanying message, but this actual destination does not have complete Intelligent Printer Data Stream (IPDS) capabilities, and the resulting printed output might contain printing errors. The status code in the error message indicates which IPDS capabilities were present or missing. To interpret the status code, first expand each of the three hex bytes into bit representation. For example: X'FF DC 50' expands to '11111111 11011100 01010000'. A '1' indicates that a capability is present. A '0' indicates that a capability expected for this type of actual destination is not present. Starting with the leftmost bit, the capabilities are:

DC1 (Device Control)
PT1 (PTOCA)
IM image
Coded font
Bounded box font
Unordered text
Unordered image blocks
Multiple copy groups
0 degree scan-line direction
90 degree scan-line direction
180 degree scan-line direction
270 degree scan-line direction
0 degree font inline sequence
90 degree font inline sequence
180 degree font inline sequence
270 degree font inline sequence
0, 90 text orientation
90, 180 text orientation
180, 270 text orientation
270, 0 text orientation
Reserved (always 0)
Reserved (always 0)
Reserved (always 0)

System action:

InfoPrint Manager continues processing the print job.

User response:

Note the missing capabilities identified by the status code in the message. Check the printed output, and determine if it is acceptable. If it is not acceptable, either use local problem-reporting procedures to report the actual destination problem or send the print job to a actual destination that has the missing IPDS capabilities. In addition, verify that the target actual destination is supported by the level of InfoPrint Manager you are using.

0420-016

The printer does not support True Type/Open Type fonts as secondary resources in Data Object Resource Equivalence 2 (DORE2) command or in DORE command.

Explanation:

InfoPrint Manager displays this message when the printer does not support True Type/Open Type fonts as secondary resources in DORE2 command or in DORE command and one of the following occurs:

A True Type/Open Type font was specified in Include Object (IOB) structured field for a PDF or SVG object.
A True Type/Open Type font was specified in Preprocess Presentation Object (PPO) structured field for a PDF or SVG object.
A True Type/Open Type font was specified in Map Data Resource (MDR) structured field for a PDF or SVG object.

When support for DORE2 command and/or support for mapping TrueType/OpenType Fonts in the DORE2 command is reported, the property pair X'120B' is retired. The property pair X'120B' indicates support for TrueType/OpenType fonts as secondary resources in the DORE command.

System action:

InfoPrint Manager stops processing the file when the error occurs. InfoPrint Manager cancels the print job.

User response:

Resubmit this print request to a printer that supports True Type/Open Type fonts as secondary resources in DORE2 command or in DORE command.

0420-017

An invalid HAID pool was specified in the Data Object Resource Equivalence 2 (DORE2) command.

Explanation:: The actual destination reported that an invalid or unsupported HAID pool parameter value was specified in the Data Object Resource Equivalence 2 (DORE2) command.
System action:: The printer will search the data-object-resource HAID pool and InfoPrint will try to continue printing.
User response:: Examine the output and the rest of the messages to determine if there were any printing problems.

0420-018

ERROR: InfoPrint Manager could not complete the internal function ____ (return code=____, process=____).

Explanation:: InfoPrint Manager issues this message for time-out conditions. One of the conditions that causes this message is the expiration of the intervention-timer attribute. The timer expires when the actual destination operator does not respond to an operator-intervention condition at the actual destination within the specified amount of time.
System action:: After InfoPrint Manager issues this message, the queue devices associated with the actual destination are brought down. Then InfoPrint Manager disables the actual destination.
User response:: Correct the operator-intervention condition at the actual destination. Check the value specified for the intervention-timer attribute. The maximum amount of time that can be specified is 9998 seconds, or approximately 2.8 hours. If the actual destination is in an area where operator-intervention is likely not to occur within the time limit, change the timer value to 9999, which indicates no time limit. In order for InfoPrint Manager to recognize that the operator-intervention has been corrected, stop and restart InfoPrint Manager. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-019

ERROR: Destination communications initialization was not successful.

Explanation:: A problem occurred while attempting to start the actual destination-communications secondary process.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use either the Enable Action icon from the Actions area on the GUI window or the pdenable command to start InfoPrint Manager and ready the device or devices. After the devices are ready, InfoPrint Manager starts automatically if there are queued jobs or after the first print job is sent. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-020

ERROR: Cannot link to the actual destination at address ____.

Explanation:

The actual destination cannot be reached through the physical attachment or network. The actual destination can be reached, but it will not accept the connection request.

InfoPrint displays this message when one of the following occurs:

The destination is not powered on.
The destination is not physically attached.
The destination TCP/IP attachment has not been enabled.
The destination is not accepting the connection request.
Duplicate IP addresses exist.
InfoPrint writes the trace information to the /var/psf/printername directory. If the /var/psf filesystem is full on InfoPrint Manager for AIX or InfoPrint Manager for Linux, or the <install-path>\var\psf\printername directory is full on InfoPrint Manager for Windows, the trace information is not written.
The wrong Internet address or port number was specified when the TCP/IP-attached destination was configured for use with InfoPrint.
The destination is being used by another InfoPrint instance or by another Print Services Facility program. For example, on InfoPrint Manager, another user used the default setting for the destination-release-timer value of 9999. The default means never release the device. Only one instance of InfoPrint or one instance of another Print Services Facility program can communicate with a destination.

System action:

InfoPrint disables the actual destination.

User response:

Ensure that the destination is powered on and that it is physically connected to the network. To test the integrity of the physical attachment or network on TCP/IP attached printers, use the ping command with the address specified in the message. To test whether the actual destination will accept the connection request, use the telnet command specifying both the IP address in the message and the printer IPDS port number (such as 5001 or 9100). The device must accept this telnet command in order for InfoPrint Manager to communicate with it through the IPDS protocol. For example, a successful connection looks like this:

telnet 9.17.82.238 5001
Trying...
Connected to 9.17.82.238
Escape character is '^]'

Note: To end the telnet session, type exit at the prompt.

When the device rejects the connection request, this is the result:

telnet 9.17.82.238 5001
Trying...
telnet:connect: A remote host refused an attempted connection operation.

When a device fails to connect, there is a physical problem that requires the attention of the service representative or the OEM printer hardware support. When you supply an incorrect IP address or port, this is the result:

telnet 10.0.0.14 5001
Trying...
telnet:connect: A remote host did not respond in the timeout period.

If the destination is connected using TCP/IP, make sure that the Internet address and port number are correct. To test for duplicate IP address conditions: first ping the printer, then turn off the printer, and ping the same IP address again. If both commands are successful, you have another device using the IP address specified for the printer. Contact your local network support personnel. If you have been running a trace, verify that the filesystem or disk partition containing /var/psf on InfoPrint Manager for AIX or InfoPrint Manager for Linux, or <install-path>\var\psf on InfoPrint Manager for Windows is not full. If it is full, then cleanup unneeded files, enlarge the filesystem/disk partition, or process fewer jobs to make space available. Otherwise, your response depends on what kind of destination is at the address in the message. If this destination is being shared by another InfoPrint instance or by another Print Services Facility program increase the value of the destination connection-timeout attribute or decrease the release-timeout on the other printer definition.

0420-021

The printer active setup name has changed.

Explanation:

The active setup name has changed, in one of the following ways:

A change from one active setup name to another active setup name
A change from no active setup name to an active setup name
A change from an active setup name to no active setup name
A change from an active setup name to the same active setup name but the settings corresponding to the setup name have been modified, for example if an operator edits the definition of the active setup name.

System action:

InfoPrint continues processing the print job.

User response:

Examine the printed output to see if it is satisfactory.

0420-022

Unsupported setup name in an Activate Setup Name command. Printing continues.

Explanation:: An Activate Setup Name (ASN) command requested a setup name that is not supported by the printer. Setup names and their meanings are assigned by the printer user and must be known to the printer before the ASN command is issued.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint continues processing the file.
User response:: Examine the printed output to see if it is satisfactory.

0420-023

ERROR: The intervention-timer attribute expired. The actual destination still requires intervention.

Explanation:: The intervention-timer attribute expired while waiting for the actual destination to be ready.
System action:: This InfoPrint instance has ended. InfoPrint may attempt to start printing again. If InfoPrint attempts to print again on an actual destination that requires intervention, it may be unable to communicate with the actual destination until the intervention condition is corrected and the actual destination is ready.
User response:: Correct the intervention condition at the actual destination.

0420-024

Unable to activate a setup name requested by an ASN command. Printing continues.

Explanation:: An Activate Setup Name (ASN) command requested a supported setup name, but the printer cannot activate the setup name without an operator intervention.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint continues processing the file.
User response:: Examine the printed output to see if it is satisfactory.

0420-026

The Activate Setup Name command was not successful. Printing continues.

Explanation:: An Activate Setup Name (ASN) command was issued, but the specified setup name was not activated and the printer did not specify the reason.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint continues processing the print job.
User response:: Examine the printed output to see if it is satisfactory.

0420-027

Invalid query type in an XOA RSNL command.

Explanation:: An invalid query-type value was specified in an XOA Request Setup Name List command.
System action:: InfoPrint continues processing the print job.
User response:: Examine the printed output to see if it is satisfactory.

0420-028

ERROR: The actual destination reported a channel-command that is not valid.

Explanation:: InfoPrint Manager sent a channel command to the actual destination that is not valid.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use either the Enable Action from the Actions area on the GUI or the pdenable command to stop and restart InfoPrint Manager. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-029

ERROR: The actual destination requires intervention.

Explanation:: The actual destination specified in the accompanying message has a problem that must be corrected by the system user.
System action:: After the actual destination problem is corrected, InfoPrint Manager recovers from the point of the error and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-030

The printer does not support Invoke Tertiary Resource (X'A2') triplet.

Explanation:: InfoPrint found an FQN X'EE' triplet, and the actual destination does not support tertiary CMR.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires QR Code with Image tertiary resource support defined under the Device Control Command-Set Vector. Resubmit this print request to an actual destination that supports QR Code with Image tertiary resource.

0420-031

The printer does not support Invoke Tertiary Resource (X'A2') triplet.

Explanation:: InfoPrint found an FQN X'EE' triplet, and the actual destination does not support tertiary CMR. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires QR Code with Image tertiary resource support defined under the Device Control Command-Set Vector. Resubmit this print request to an actual destination that supports QR Code with Image tertiary resource.

0420-032

ERROR: InfoPrint Manager reported an internal error during initialization.

Explanation:: InfoPrint Manager's initialization routine received a null actual destination name.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-033

ERROR: InfoPrint Manager cannot process the print job because there is not enough memory available.

Explanation:: PSF cannot allocate the required memory.
System action:: PSF cannot start this PSF instance or, if PSF is started, the instance that encountered the error terminated because there is not enough available memory.
User response:: Use local problem-reporting procedures to report this message.

0420-034

ERROR: InfoPrint Manager could not generate the name of the actual destination profile for actual destination ____.

Explanation:: InfoPrint Manager tried to process the configuration information for the actual destination, but could not create the actual destinationprofile.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-035

Unsupported setup name in an Activate Setup Name command.

Explanation:: An Activate Setup Name (ASN) command requested a setup name that is not supported by the printer. Setup names and their meanings are assigned by the printer user and must be known to the printer before the ASN command is issued.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint stops processing the file.
User response:: Resubmit the file with a setup name supported by the printer.

0420-036

ERROR: InfoPrint Manager cannot use the actual destination profile ____. Create a new actual destination profile.

Explanation:: When the actual destination was configured for use by InfoPrint Manager, InfoPrint Manager created the actual destination profile file specified in this message. InfoPrint Manager can no longer use this file because of an error in the file's contents. The error must be corrected before configuration changes can be made for any of the actual destinations in the list.
System action:: InfoPrint Manager cannot start this actual destination.
User response:: Delete the actual destination profile file.

Note: You must have root or printq authority to add the actual destination.

0420-037

ERROR: InfoPrint Manager cannot open the actual destination profile ____.

Explanation:: InfoPrint Manager cannot find the actual destination profile file specified in the message. The file might have been deleted or moved to a location that is not valid for actual destination profiles. By default, the file system used for the actual destination profile is /var/psf/printername where printername is the name of the actual destination that was specified when the actual destination was configured through the InfoPrint Manager SMIT configuration panels.
Note: When selected, certain InfoPrint Manager SMIT functions display a list of the available actual destinations to which the function can be applied. For example, selecting the Remove a Printer function from the InfoPrint Manager SMIT Manage a Printer menu causes InfoPrint Manager to display a list of the actual destinations configured for use by InfoPrint Manager. If InfoPrint Manager cannot use the information in the actual destination profile file for any of the listed actual destinations, InfoPrint Manager displays this message. The error must be corrected before configuration changes can be made for any of the actual destinations in the list.
System action:: InfoPrint Manager cannot start this actual destination.
User response:: Exit from the InfoPrint Manager SMIT panels, and return to the AIX command prompt. Check that the actual destination profile file exists and that the file is located in the correct directory. If the file does not exist, create a new actual destination profile file. To create the new profile, edit the /etc/qconfig file, and delete the references to the print queue and devices associated with the actual destination whose profile file is missing. Type smit psfcfg at the command prompt to access the InfoPrint Manager SMIT configuration panels, and use the appropriate InfoPrint Manager SMIT panels, based on the type of actual destination, to add the actual destination again. Adding the actual destination creates a new actual destination profile.

Note: You must have root or printq authority to add the actual destination.

0420-038

ERROR: InfoPrint Manager cannot read the actual destination profile ____.

Explanation:: InfoPrint Manager opened the actual destination profile that contains information about the actual destination. However, the contents of the file are damaged, and InfoPrint Manager cannot read the file.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-039

The copies value ____ specified for this print job is not valid. InfoPrint Manager will use a value of 1.

Explanation:: Valid values for the copy count are in the range of 1 to 255. The copy count value specified with this print request was not within this range.
System action:: InfoPrint Manager ignores the value specified for the number of copies, uses the default value of 1, and continues processing the print job.
User response:: If you need more than one copy, submit the job again, specifying a valid number of copies.

0420-040

The data check value ____ specified for this print job is not valid.

Explanation:: The print request specified a value for data check (DATACK) that was not valid. The valid values are: BLOCK, UNBLOCK, BLKPOS, and BLKCHAR.
System action:: InfoPrint Manager ignores the specified value and uses the default value of BLOCK. This prevents positioning errors and invalid character errors from being reported.
User response:: Check the printed output, and determine if it is acceptable. If it is not, specify a valid data check value and submit the job again.

0420-041

No Job ID parameter was specified for this print job. The Job ID is now zero.

Explanation:: The spooler did not assign a Job ID for the print job.
System action:: The Job ID defaults to zero and processing of the job continues.
User response:: Use local problem-reporting procedures to report this message.

0420-042

The message count value ____ specified for this print job is not valid. InfoPrint Manager will use a value of 9999.

Explanation:: Valid message count values are in the range of 0 to 9999. A 0 value specifies that no messages print; a 9999 value specifies that all messages print. The message count value specified with the print request was not within this range.
System action:: InfoPrint Manager ignores the value specified for the message count, uses the default value of 9999, and continues processing the print job.
User response:: The message count can be specified from the command line with the msgcount keyword or from the SMIT Start an InfoPrint Manager Job Script panel with the Number of MESSAGES to print entry field. Select a value between 0 and 9999 when specifying a message count with a print request.

0420-043

The message level value ____ specified for this print job is not valid. Message level zero will be used.

Explanation:: .* NOT USED IN InfoPrint Manager. You submitted a print request for an InfoPrint Manager destination. However, you used a command other than enq -o or the InfoPrint Manager SMIT panels, or you aren't using the default AIX spooler. Your command specified a message level value that is not between 0 and 16.
System action:: InfoPrint Manager ignores the specified value and uses the default value of 0. Processing of the print job continues.
User response:: Try to find out why your print submission command is not working properly.

0420-044

An attempt was made to use a file stack that was not initialized.

Explanation:: An attempt was made to use an internal InfoPrint Manager control structure, but the control structure was not initialized.
System action:: InfoPrint Manager automatically initializes the control structure and continues processing the print job. If the control structure's function is to end a process, InfoPrint Manager recognizes that a canceled state of a control structure is the same as the state of a control structure that has not been initialized and ignores the request.
User response:: This is an informational message; no response is required.

0420-045

An attempt was made to initialize a file stack that was already initialized.

Explanation:: An attempt was made to initialize an internal InfoPrint Manager control structure, but the control structure was already initialized.
System action:: InfoPrint Manager recognizes that the control structure is already initialized and continues processing the print job.
User response:: This is an informational message; no response is required.

0420-046

An attempt to initialize a file stack list was not successful.

Explanation:: The InfoPrint Manager internal list function did not return the required control structure during the initialization phase of this process.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-047

An attempt was made to use an object stack that was not initialized.

Explanation:: An attempt was made to use an internal InfoPrint Manager control structure, but the control structure was not initialized.
System action:: InfoPrint Manager writes this error to the error log and continues processing the print job.
User response:: This is an informational message; no response is required.

0420-048

The actual destination reported a paper length check. Adjust or change the print media to correct this condition.

Explanation:: The actual destination specified in the accompanying message reported a paper length check error.
System action:: After the actual destination problem is corrected, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-050

Unable to activate a setup name requested by an ASN command.

Explanation:: An Activate Setup Name (ASN) command requested a supported setup name, but the printer cannot activate the setup name without an operator intervention.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint stops processing the file.
User response:: Activate the desired setup name and resubmit the file.

0420-051

An attempt to add an item to a file stack was not successful.

Explanation:: An attempt was made to add an item to an internal InfoPrint Manager control structure, but the add process was not successful.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-052

ERROR: The device support process ended unexpectedly. Return code=____.

Explanation:: The device support process of InfoPrint Manager has ended when it was not expected to end.
System action:: The secondary process ends. The primary process will time out while waiting for the secondary process. InfoPrint Manager logs the error and ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message and the return code it contains.

0420-053

ERROR: A pre-processing or post-processing device that is connected to the actual destination is overloaded.

Explanation:: A pre- or post-processing-device overload means that the device was not able to keep up with the printing requirements of a page.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: Examine the printed output to determine if it is acceptable. If it is not acceptable, simplify the pages that did not print. If the pages still do not print correctly, then consult the pre- or post-processing device documentation for proper procedures.

0420-054

The Activate Setup Name command was not successful.

Explanation:: An Activate Setup Name command was issued, but the specified setup name was not activated and the printer did not specify the reason.
System action:: The actual destination profile controls the continuation of the print request. The default action is to report the error(s) and stop processing the file. InfoPrint Manager stops processing the print job.
User response:: Resubmit the file. If the problem persists, contact your service representative.

0420-055

The actual destination output bin is full; empty the output bin.

Explanation:: The actual destination output bin is full and cannot accept any more printed output.
System action:: After the output bin is emptied, InfoPrint Manager recovers and printing continues.
User response:: Unload the actual destination output bin.

0420-056

An object stack list cannot be initialized.

Explanation:: The InfoPrint Manager internal list function did not return the required control structure during the initialization phase of this process. The required internal control structure could not be initialized.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-057

A message was issued with too many message inserts.

Explanation:: An InfoPrint Manager message was issued with more than the maximum number of nine (9) message inserts.
System action:: InfoPrint Manager recognizes and reports the first nine message inserts in the message and continues processing the print job.
User response:: This is an informational message; no response is required.

0420-058

The actual destination is out of paper in the primary bin; add paper.

Explanation:: The actual destination is out of paper in the primary bin, and printing cannot continue.
System action:: After the primary bin is filled, InfoPrint Manager recovers and printing continues.
User response:: Add paper to the primary bin of the actual destination.

0420-059

The actual destination reported that a medium that is not valid has been selected for duplexing. Change the media in the actual destination to one that supports duplex printing.

Explanation:: The actual destination reports this condition when a medium that is not valid for duplexing is selected for duplex printing.
System action:: After the actual destination problem is corrected, InfoPrint Manager recovers and printing continues.
User response:: Change the media loaded in the actual destination to one that can be duplexed.

0420-060

The error occurred with the object type ____ with token name ____.

Explanation:: This message contains information that supplements other error messages in this error message group. Several messages of this type can occur, reflecting the hierarchical nature of the AFP data stream. Each token name is represented using the standard ASCII character set. EBCDIC token names are translated to ASCII for display purposes. If a structured field contains a token name that cannot be displayed using the standard ASCII character set, a blank identifier will appear in the message insert. For example, a token name of X'FFFFFFFFFFFFFFFF' will display as ' ' because X'FF' does not represent a graphic character in the standard ASCII character set.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-061

The actual destination is out of fuser oil; add fuser oil.

Explanation:: The actual destination is out of fuser oil.
System action:: After fuser oil is added, InfoPrint Manager recovers and printing continues.
User response:: Add fuser oil to the actual destination.

0420-062

The actual destination is out of one or more printer supplies.

Explanation:: The actual destination is out of one or more printer supplies.
System action:: After toner is added, InfoPrint Manager recovers and printing continues.
User response:: Refill or replace the printer supply on the actual destination.

0420-063

The printer does not support Setup Name (X'9E') triplet.

Explanation:: InfoPrint found a Setup Name (X'9E') triplet or a setup name was specified in the print submission command, but the actual destination does not support Setup Name (X'9E') triplet. Processing stops.
System action:: The actual destination profile specifies to stop processing the file. The default action is to report the error(s) and stop processing the file.
User response:: Resubmit this print request to an actual destination that supports Setup Name (X'9E') triplet.

0420-064

The printer does not support Setup Name (X'9E') triplet. Printing continues.

Explanation:: InfoPrint found a Setup Name (X'9E') triplet or a setup name was specified in the print submission command, but the actual destination does not support Setup Name (X'9E') triplet. Processing continues.
System action:: The actual destination profile specifies to continue processing the file. The default action is to report the error(s) and stop processing the file.
User response:: Examine the printed output to see if it is satisfactory.

0420-065

The Set Current Defaults (SCD) Instruction length for ____ attributes is invalid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. The Set Current Defaults (SCD) Instruction length does not match the total length of the attributes described in the set mask.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-066

A Begin Object Container structured field or a Begin Resource structured field specified an invalid object class: ____ for a Data Object Font OID.

Explanation:: InfoPrint Manager requires that the Object Classification Triplet ID X'10' from a Begin Object Container structured field or a Begin Resource structured field contains an object class field (byte 3) of X'41' (Data-object font) for a Data Object Font OID specified starting with byte 8.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Within the Object Classification triplet, set the Object Class field to X'41', to indicate a Data-object font. For more information, consult the Mixed Object Document Content Architecture Reference.

0420-089

An item cannot be added to the object stack.

Explanation:: An attempt to add an item to an internal InfoPrint Manager control structure failed. This is an internal InfoPrint Manager error.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-090

ERROR: The actual destination reported a data received after an acknowledgment required (ARQ) error.

Explanation:: Either a actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-091

A memory allocation error occurred for InfoPrint Manager message services.

Explanation:: InfoPrint Manager cannot obtain required memory from the AIX operating system.
System action:: InfoPrint Manager continues processing the print job and writes any new messages for the print job to the actual destination's error log.
User response:: Make more memory available to InfoPrint Manager by closing any unneeded processes. Check for other error conditions in the actual destination's error log. By default, the path and the name of the error log file are /var/psf/printername/error.log, where printername is the name of the actual destination that was specified when the actual destination was configured with the InfoPrint Manager SMIT configuration panels.

0420-092

InfoPrint Manager cannot open file ____. This file contains the error messages that InfoPrint Manager prints at the end of the print job or logs in the job message log.

Explanation:: If errors occur during the print job, InfoPrint Manager writes the error messages to a temporary file. Depending on the value for the Disposition of job-related messages entry on the InfoPrint Manager SMIT Error Handling Options panel for this actual destination, InfoPrint Manager either prints the contents of this file at the end of the print job or copies this file into the job message log. InfoPrint Manager could not open the temporary file. The file system where InfoPrint Manager attempted to create the temporary file, by default /var/psf/printername (where printername is the name of the actual destination that was specified when the actual destination was configured with the InfoPrint Manager SMIT panels) might be full. If a different path for the error and trace logs was specified on the InfoPrint Manager SMIT Error Log and Trace Options panel, that path might not be valid.
System action:: InfoPrint Manager continues processing the print job. Any additional error messages that occur during the print job will not be recorded.
User response:: Check that the path for error and trace logs specified on the InfoPrint Manager SMIT Error Log and Trace Options panel is correct. If no path is specified, InfoPrint Manager defaults to the root directory when creating the temporary file. If the path is correct or the default path is being used, check that disk space is available in the file system, and make space available as necessary. Examine the printed output produced when the error occurred to determine if the output is acceptable. If it is not acceptable, enter the print request again, and then correct the errors that will now print at the end of the job.

0420-093

The actual destination is not ready and must be made ready before printing can continue.

Explanation:: The actual destination, specified in the accompanying message, reported to InfoPrint Manager that it is in a not-ready state. InfoPrint Manager cannot communicate with the actual destination until the actual destination is made ready.
System action:: After the actual destination is made ready, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-094

The following messages were generated for file ____ with Job ID ____. This file printed on the InfoPrint Manager actual destination ____, which is a ____ actual destination.

Explanation:: This informational message identifies the file name entered with the print request, the job ID assigned by the qdaemon, and the actual destination name and actual destination type obtained from the InfoPrint Manager actual destination profile for the actual destination.
System action:: InfoPrint Manager produces this message only if there are notable exceptions to be reported for the print job. See the system actions for other error messages in this message group.
User response:: This is an informational message; no response is required.

0420-095

ERROR: The actual destination reported an IPDS sequence that is not valid.

Explanation:: Either a actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-096

ERROR: The actual destination reported an IPDS command code error that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-097

ERROR: Looping was detected during error recovery. Destination communications are ending.

Explanation:: Looping was detected during error recovery. This usually indicates that the actual destination and InfoPrint Manager are not able to communicate because the actual destination is not of the type specified in the actual destination profile file.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Check that the actual destination is of the type specified in the actual destination profile file. If it is, use local problem-reporting procedures to report this condition.

0420-098

The error occurred while printing page ____ of copy ____ of this print job.

Explanation:: This message identifies the copy set number and the page on which an error described in an accompanying message occurred.
System action:: See the system actions for other error messages in this message group.
User response:: This is an informational message; no response is required.

0420-099

InfoPrint Manager found an error on a page that no longer exists (return code=____).

Explanation:: An error occurred on a specific page, but InfoPrint Manager cannot find the internal representation of this page. Other errors might have occurred due to this problem.
System action:: InfoPrint Manager writes this message to the actual destination's error log and continues processing the print job.
User response:: Save the error log for the actual destination, and use local problem-reporting procedures to report this message. By default, the path and the name of the error log file are /var/psf/printername/error.log, where printername is the name of the actual destination that was specified when the actual destination was configured with the InfoPrint Manager SMIT configuration panels.

0420-100

ERROR: The Message user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-101

ERROR: The actual destination reported a disabled input bin. Bin number ____ cannot be used until the bin has been enabled or repaired.

Explanation:: The bin specified in the message has been disabled from the actual destination-operator panel or by a hardware problem that requires service.
System action:: InfoPrint Manager stops processing the file at the point of the error. Any page processed for the disabled bin is flushed; this includes the header page. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job, but the output will be printed on media fed from another bin. If there are no other files in this print job, InfoPrint Manager cancels the job. No jobs will be printed on this actual destination using the disabled bin until the actual destination operator enables the bin.
User response:: If the actual destination reporting the error can have bins disabled from the operator panel, determine why the specified bin was disabled and enable the bin. In order for InfoPrint Manager to recognize that the bin problem has been corrected, you must stop and restart InfoPrint Manager. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-102

ERROR: The actual destination reported a duplexing error. The actual destination can print only in simplex mode.

Explanation:: The actual destination's duplex paper-path has been disabled from the operator panel or by a hardware problem that requires service. The actual destination can produce only simplex printed output until the duplex paper-path problem is corrected.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job, but the output will be printed on one side only. If there are no other files in this print job, InfoPrint Manager cancels the job. No jobs will be printed in duplex on this actual destination until the actual destination operator enables the duplexing function.
User response:: If the actual destination reporting the error can have the duplex paper path disabled using the operator panel, determine why the duplex paper path was disabled and enable it. In order for InfoPrint Manager to recognize that the duplex paper path has been enabled, you must stop and restart InfoPrint Manager. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-103

ERROR: The actual destination reported an offset-stacker error. Printing will continue without offset stacking.

Explanation:: The actual destination's offset stacker has been disabled from the operator panel or by a hardware problem that requires service. The actual destination cannot offset stack the printed output until the offset-stacker problem is corrected.
System action:: InfoPrint Manager continues processing the print job. Printed output will not be offset.
User response:: Correct the offset-stacker problem, and restart the actual destination. In order for InfoPrint Manager to recognize that the offset-stacker problem has been corrected, you must stop and restart InfoPrint Manager. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-104

ERROR: The actual destination reported an image generator error.

Explanation:: An image generator is part of the actual destination's hardware that processes images, graphics, and text to compose the page and transfer the page to the print media. The actual destination reported a problem with its image generator.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: Check the printed output, and determine if it is acceptable. If the printed output is not acceptable, use local problem-reporting procedures to report this message.

0420-105

ERROR: The actual destination reported an IPDS negative acknowledgement (NACK) that caused InfoPrint Manager to end unexpectedly.

Explanation:: An IPDS negative acknowledgement caused InfoPrint Manager to end.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-106

ERROR: The actual destination reported a printing overrun error.

Explanation:: The actual destination reported a printing overrun error while attempting to position image or text on a page at a location that had already passed. Examples of conditions that can cause this error are attempts to place too many images on a page or requesting too many overstrikes on a page.
System action:: InfoPrint Manager ends the print job.
User response:: Simplify the page that caused the error, and submit the print request again. This page might print correctly, without any simplification, on a different type of actual destination.

0420-107

ERROR: The actual destination reported a printing overrun error.

Explanation:: The actual destination reported a recoverable hardware error to InfoPrint Manager.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: Check the printed output, and determine if it is acceptable. If the results are not acceptable, send the print job again. If the hardware error occurs again, use local problem-reporting procedures to report this message.

0420-108

InfoPrint Manager could not write to the file ____. This file contains error messages that print out at the end of the print job or are logged in the job message log.

Explanation:: If errors occur while InfoPrint Manager processes the print job, InfoPrint Manager collects the errors in a temporary file. However, InfoPrint Manager cannot put any more data into this temporary file. The file system where the temporary file resides might be out of space.
System action:: InfoPrint Manager continues processing the print job, but any errors that were written to the temporary file are lost. InfoPrint Manager writes any new error messages to the actual destination's error log.
User response:: Check that the file system where the file specified in the message resides has enough space. Check the error log for any other errors that might have occurred during the print job. By default, the path and the name of the error log file are /var/psf/printername/error.log, where printername is the name of the actual destination that was specified when the actual destination was configured with the InfoPrint Manager SMIT configuration panels.

0420-109

ERROR: The actual destination reported a channel sequence error.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-113

ERROR: The extension field length of a Structured-Field Introducer contains the value X'____', which is not valid.

Explanation:: A Structured-Field Introducer (SFI) flag byte indicates that an SFI extension is present (SFI flag byte bit 0 is on), but the SFI extension field length is not valid. The extension field length must be greater than zero but cannot be larger than the overall structured field length in bytes 0-1. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-114

ERROR: The padding length field of a Structured-Field Introducer contains the value X'____', which is not valid.

Explanation:

A Structured-Field Introducer (SFI) flag byte indicates that the structured field contains padding (SFI flag byte bit 4 is on), but the padding length specified is not valid. This is caused by either of the following conditions:

The 3-byte form of the padding length is used, and the padding length specified is less than 3.
The padding length specified is larger than the total structured field length in bytes 0-1. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-115

ERROR: The actual destination cannot be initialized.

Explanation:: The actual destination, specified in an accompanying message, cannot be initialized, and no printing can occur.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Check the actual destination for an operator-intervention condition. Follow the instructions in the documentation for the actual destination to correct this problem. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-120

An empty page queue was not expected.

Explanation:: An internal InfoPrint Manager control structure contains no entries, and entries were expected.
System action:: InfoPrint Manager writes this error to the error log and continues processing the print job. Immediately following this message in the error log is the error that was being processed when this condition occurred.
Note: Any other errors that occur following this error might not be reported in as much detail as they would have been reported had this error condition not occurred.
User response:: Correct all other errors that occurred during this print job.

0420-122

A actual destination door is open; close the door.

Explanation:: The actual destination specified in an accompanying message reported to InfoPrint Manager that one of its doors or covers is open. InfoPrint Manager cannot communicate with the actual destination until the door or cover is closed.
System action:: After the door or cover is closed, InfoPrint Manager recovers and printing continues.
User response:: Close the actual destination door or cover.

0420-124

ERROR: Structured field ____ (____) was received when one of the following structured fields was expected: ____.

Explanation:: A structured field was read that is not valid at the current point within the data stream. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-127

Because of the error reported below, InfoPrint Manager cannot process the font made up of the code page ____ and the font character set ____.

Explanation:: InfoPrint Manager detected an error or errors that prevented the font specified in the message from being processed. Other error messages in this message group provide further information on the cause of the error.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-128

ERROR: InfoPrint Manager cannot find or cannot access the ____ resource named ____.

Explanation:

The print job requires a resource, but either InfoPrint Manager cannot locate the resource in the expected path, or you do not have read access to the resource. The resource file might have been moved or deleted, or it might have a different name than was supplied to InfoPrint Manager. If the resource is a Data Object font, then there are the following possibilities:

The RAT (Resource Access Table) is not in the resource path.
The RAT does not contain the data object font.
The data object font is not contained in any collection listed in the RAT.
The data object font is a linked font, but that font does not occur in the RAT as a separate entry.

Note: If a structured field contains a resource file name that cannot be displayed using the standard ASCII character set, blanks appear instead of the resource file name.

System action:

If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.

User response:

Check that the name of the requested resource supplied to InfoPrint Manager is correct and that you have read permission for the resource. If the name and permission level are correct, locate the resource and note its path. Then, use the GUI window to specify the resource's location through the resource-context object. Also, resource path information can be specified with the PSFPATH environment variable. If the resource does not exist, it must be either created or installed before it can be used by InfoPrint Manager.

0420-129

ERROR: Auxiliary-sheet data cannot print because InfoPrint Manager cannot open a system buffer.

Explanation:: Data supplied by an auxiliary-sheet object is normally copied into a system buffer before it is converted and printed. InfoPrint Manager could not open this buffer. The file system that contains the actual destination profile or the temporary files might be full.
System action:: InfoPrint Manager continues processing the print job, but any data created by an auxiliary-sheet object will not print.
User response:: Check that the file system containing the actual destination profile has enough space. By default, the file system used for the actual destination profile is /var/psf/printername where printername is the name of the actual destination that was specified when the actual destination was configured. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-130

ERROR: The name of the resource in error is ____.

Explanation:: The resource specified in this message is either causing the error or is associated with the cause of the error. If the resource is an overlay, the error can be caused by a font or another resource used by that overlay.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-131

ERROR: InfoPrint Manager cannot open the file ____ with job number ____.

Explanation:: The file specified in the message cannot be opened for processing. Possible causes include the file does not exist, you do not have read permission for the file, or the file was deleted from the print queue before the print job was sent to the InfoPrint Manager actual destination. Another possible cause is that the file is already open and in use by another program.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Check that the file exists and that you have the permission level required to read the file; x permission is required for the directory containing the file and r permission is required for the file itself. If the file is in use by another application, wait until the other application has completed its use of the file.

0420-133

ERROR: The triplet length field ____ for the triplet with identifier X'____' on the ____ structured field is not valid.

Explanation:: The length of the triplet specified in the message is not correct. Either the triplet length is too long, so that the triplet would extend beyond the end of the enclosing structured field or Map Coded Font Format 2 (MCF-2) repeating group, or the triplet length is less than the minimum length for that triplet. If the triplet length appears to be correct, check for an error in the structured field length or MCF-2 repeating group length. If the triplet hex ID is '?', one extraneous byte was found at the end of a structured field or MCF-2 repeating group. This byte was then interpreted as a triplet length byte without an accompanying ID byte. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-134

ERROR: The actual destination reported an error with a resource that InfoPrint Manager cannot identify.

Explanation:: InfoPrint Manager cannot identify a resource required by the print job.
System action:: InfoPrint Manager continues with error recovery. See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-136

ERROR: The repeating group length ____ for repeating group name ____ in a ____ structured field is not valid.

Explanation:

A structured field contains an incorrect value for the size of its own repeating groups, or for the repeating groups of another structured field. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again. For informational purposes, this situation can occur in the following cases:

The Map Coded Font format 1 (MCF-1) structured field contains a field that specifies the length of each of its repeating groups. This value must be either 30 (so that the character rotation is explicitly specified in the repeating group) or 28 (so that the character rotation is not explicitly specified in the repeating group).
The Map Coded Font format 2 (MCF-2) structured field has variable-length repeating groups. The first 2 bytes of each repeating group contain the repeating group length. The value in these 2 bytes must be greater than or equal to 2. A value of 2 indicates that the repeating group contains no data other than its own length. The repeating group length must also not be greater than the number of parameter bytes that, according to the Structured-Field Introducer length field, appear within or following the repeating group.
The Map Medium Overlay (MMO) structured field contains a field that specifies the length of each of its repeating groups. This value must be greater than or equal to 12.
The Map Page Overlay (MPO) structured field has a field in each of its repeating groups that specifies the repeating group length. This value must be greater than or equal to 18. The repeating group length must not be greater than the number of parameter bytes that, according to the Structured-Field Introducer length field, appear within or following the repeating group.
The Map Page Segment (MPS) structured field contains a field that specifies the length of each of its repeating groups. This value must be greater than or equal to 12.
The Font Control (FNC) structured field contains a field that specifies the length of the Font Orientation structured field repeating groups. This value must be 26.
The FNC structured field contains a field that specifies the length of the Font Index (FNI) structured field repeating groups. This value must be 28.
The FNC structured field contains a field that specifies the length of the Font Patterns Map (FNM) structured field repeating groups. This value must be 8.
The Code Page Control (CPC) structured field contains a field that specifies the length of the Code Page Index (CPI) structured field repeating groups. This value must be 10.

0420-137

ERROR: The Image Output Control (IOC) structured field scale factor X'____' is not valid.

Explanation:: The Image Block Scale Factor field in the Image Output Control (IOC) structured field must contain values for the horizontal and vertical scale factors of either X'03E803E8', indicating no scaling, or X'07D007D0', indicating enlargement of the image. An IOC structured field was encountered with scale factor values that are not valid. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-138

ERROR: The repeating group number ____ for a Map Coded Font format 1 (MCF-1) or a Map Coded Font format 2 (MCF-2) structured field does not identify a font.

Explanation:

There are two ways to identify a font in a Map Coded Font (MCF-1 or MCF-2) structured field:

With a coded font name.
With a code page name and a font character set name.

If a coded font name is specified and the coded font name field contains a value other than X'FFFFFFFFFFFFFFFF', then neither a code page name nor a font character set name can be specified. The code page name field and the font character set name field must both be set to X'FFFF...'. An MCF-1 or MCF-2 structured field was encountered that contains a coded font name that is not X'FFFF...', and either a code page name or a font character set name that is not X'FFFF...'. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-139

ERROR: The repeating group number ____ for a Map Coded Font format 1 (MCF-1) or a Map Coded Font format 2 (MCF-2) structured field does not contain enough information to identify the font.

Explanation:

There are two ways to identify a font in a Map Coded Font (MCF-1 or MCF-2) structured field:

With a coded font name.
With a code page name and a font character set name If a coded font name is not specified and the coded font name field contains X'FFFF...', both a code page name and a font character set name must be specified (both must contain values other than X'FFFF...'). A Map Coded Font (format 1 or format 2) structured field was encountered that contained a coded font name that was set to X'FFFF...' and either a code page name or a font character set name that was also set to X'FFFF...'. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-140

ERROR: The section identifier X'____' in a Map Coded Font format 1 (MCF-1) or a Map Coded Font format 2 (MCF-2) structured field repeating group number ____ is not valid.

Explanation:

The Coded Font Resource Section Identifier in an MCF-1 structured field or the Resource Section Number in an MCF-2 structured field must one of the following:

X'00' indicating a single-byte font.
X'41' through X'FE', indicating a double-byte, bounded box coded font o
X'41' through X'7F', indicating a double-byte, unbounded box font.

Note: InfoPrint Manager does not support unbounded box fonts. An MCF-1 or MCF-2 structured field was encountered that specified a section identifier that was not valid. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-141

ERROR: The local identifier X'____' in a Map Coded Font format 1 (MCF-1) or a Map Coded Font format 2 (MCF-2) or a Map Data Resource (MDR) structured field repeating group number ____ is not valid.

Explanation:: A Coded Font Local Identifier in an MCF-1 structured field or a Resource Local Identifier in an MCF-2 or MDR structured field can either be in the range of 1 to 127 or if the local identifier will be used for resource-management purposes in the Active Environment Group (AEG), the value can be X'FE'. An MCF-1 or an MCF-2 or an MDR structured field was encountered that had a local identifier value that was not valid. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-142

ERROR: The Unit Base field X'________' in a ________ structured field is not valid.

Explanation:: The Unit Base field must contain the value X'00', indicating a ten-inch unit base, in both the X and Y directions, or the value X'01', indicating a ten-centimeter unit base, in both the X and Y directions. The structured field specified in the message contained a different value. For the image resolution triplet on the CDD, IOB, and PPO structured fields, the unit base value must be X'00' or X'01'. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-143

ERROR: The L-units-per-unit-base field X'____' in a ____ structured field is not valid.

Explanation:: The L-Units-per-Unit Base field must contain one of two values: 2,400 or 14,400 (for both the X-direction and Y-direction). Also, the X-direction and Y-direction values must be the same. The structured field specified in the message contains a value for the L-Units-per-Unit-Base field that is not valid. For the image resolution triplet on CDD, IOB, and PPO structured fields, this is an invalid value in the number of image points in the x and y directions value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-144

ERROR: The X-direction and Y-direction L-unit-per-unit-base fields in a ____ structured field do not match. The X-direction value is X'____' and the Y-direction value is X'____'.

Explanation:: The X-direction and Y-direction L-Units per Unit Base values must both be 2,400 or 14,400. The values in the structured field specified in the message do not match. For the image resolution triplet on CDD, IOB, and PPO structured fields, this is a mismatch of the number of image points in the x and y direction values. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-145

ERROR: The required Self-Identifying Parameter (SIP) with ID X'____' is missing from the ____ structured field.

Explanation:: The required self-identifying parameter does not appear in the structured field specified in the message. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-146

ERROR: The required triplet with ID X'________' is missing, it has an invalid format, or a wrong position on the ________ structured field.

Explanation:: The required triplet has an invalid format, a wrong order position, or does not appear in the structured field specified in the message. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-148

ERROR: The Medium Orientation X'____' value in the Triplet Group of the Medium Descriptor (MDD) structured field is not valid.

Explanation:: The Medium Orientation field of the Triplet Group in the Medium Descriptor (MDD) structured field must contain one of the following values: X'00' (Portrait), X'01' (Landscape), X'02' (Reverse Portrait), X'03' (Reverse Landscape), X'04' (Portrait90), or X'05' (Landscape90). An MDD structured field was encountered that contains a different value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-149

ERROR: A duplicate overlay local identifier X'____' was found in repeating group number ____ of a Map Medium Overlay (MMO) structured field.

Explanation:: A Map Medium Overlay (MMO) structured field was encountered that contains the same overlay local ID in two different repeating groups. Overlay local IDs must be unique within all MMO repeating groups. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-150

ERROR: The Overlay Local Identifier X'____' in repeating group number ____ of a Map Medium Overlay (MMO) structured field is not valid.

Explanation:: An Overlay Local Identifier must be in the range of 1 through 127. A Map Medium Overlay (MMO) structured field was encountered that contains an Overlay Local Identifier value that is outside this range. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-151

ERROR: The Medium Copy Count (MCC) structured field repeating group number ____ contains a value for the Starting Copy Number ____ or the Stopping Copy Number ____ that is not valid.

Explanation:

For each repeating group in a Medium Copy Count (MCC) structured field, the Starting Copy Number and Stopping Copy Number must conform to the following rules:

The Starting Copy Number for the first repeating subgroup must be 1.
The number of copies requested by the copy subgroup, called the copy count, which is defined by (stopnum - startnum) + 1, must be less than or equal to 255.
The Stopping Copy Number must be greater than or equal to the Starting Copy Number. See the 'MO:DCA Reference' for further information on this structured field.

System action:

If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.

User response:

Correct the structured field in the form definition and submit the print job again.

0420-152

ERROR: More than eight overlays are specified in the Medium Modification Control (MMC) structured field with MMC ID X'____'.

Explanation:: No more than eight Medium Modification Control (MMC) repeating groups can specify overlay local identifiers. The MMC structured field specified in the message contains more than eight repeating groups specifying this type of identifier. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-153

ERROR: More than eight suppressions are specified in the Medium Modification Control (MMC) structured field with MMC ID X'____'.

Explanation:: No more than eight Medium Modification Control (MMC) repeating groups can specify suppression local identifiers. The MMC structured field specified in the message contains more than eight repeating groups specifying this type of identifier. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-154

ERROR: The Overlay Local Identifier X'____' in a Medium Modification Control (MMC) structured field with MMC ID X'____' repeating group number ____ is not valid.

Explanation:: An Overlay Local Identifier must be in the range of 1 through 127. A Medium Modification Control (MMC) structured field was encountered that specified an overlay local ID that is outside this range. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-155

ERROR: The simplex or duplex value X'____' in the Medium Modification Control (MMC) structured field with MMC ID X'____' and repeating group number ____ is not valid.

Explanation:: The Medium Modification Control structured field value that controls whether both sides of the paper are printed on must contain one of the following values: X'01' (simplex), X'02' (normal duplex), or X'03' (tumble duplex). The MMC structured field specified in the message contains a different value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-158

ERROR: The Suppression Local Identifier X'____' in a Medium Modification Control (MMC) structured field with MMC ID X'____' and repeating group number ____ is not valid.

Explanation:: A Suppression Local Identifier must be in the range of 1 through 127. A Medium Modification Control (MMC) structured field was encountered that contains a Suppression Local Identifier value that is outside of this range. See the 'MO:DCA Reference' for further information on this structured field.
System action:: If this is the only file in the print job, InfoPrint Manager cancels the job. If there are multiple files in the print job and you specified a form definition with the print request, InfoPrint Manager processes each subsequent file but issues this error for each file. If there are multiple files in the print job and the default form definition is causing the error, only files that specify valid inline form definitions will print. The default form definition is specified as an attribute of the actual destination.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-160

ERROR: The Pattern Technology field in a Font Control (FNC) structured field contains the value X'____', which is not valid.

Explanation:: The Pattern Technology field in the Font Control (FNC) structured field must contain a value of X'05'. An FNC structured field was encountered that contains a different value in this field. See the 'FOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the structured field in the font character set and submit the job again.

0420-164

ERROR: The Pattern Data Address Alignment field in a Font Control (FNC) structured field contains the value X'____', which is not valid.

Explanation:: The Pattern Data Address Alignment field in the Font Control (FNC) structured field must contain a value of X'00' (patterns aligned on byte boundaries), X'02' (patterns aligned on 4-byte boundaries), or X'03' (patterns aligned on 8-byte boundaries). An FNC structured field was found that contains a different value in this field. See the 'FOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the structured field in the font character set and submit the job again.

0420-166

ERROR: InfoPrint Manager cannot open message catalog ____.

Explanation:

The InfoPrint Manager message catalogs hold the text and explanations of the InfoPrint Manager error messages. InfoPrint Manager cannot access one of these catalogs; any InfoPrint Manager messages in this catalog cannot be viewed or printed. Possible causes are:

The InfoPrint Manager message catalogs were deleted or moved.
The InfoPrint Manager message catalogs exist, but you don't have permission to read them.
The message catalogs are not in the location specified with the NLSPATH environment variable.

System action:

InfoPrint Manager cannot start this InfoPrint Manager instance.

User response:

Check that the InfoPrint Manager message catalogs, psf.cat and psfdesc.cat, either exist in the default path, /usr/lib/nls/msg, or in the path specified by the NLSPATH environment variable (use the AIX env command to view the settings of the environment variables). To read the message catalogs, you must have x (execute) permission for the directory containing the messages and r (read) permission for the message files themselves..

0420-167

ERROR: The Code Page Control (CPC) structured field contains a null value for the Default Graphic Character name.

Explanation:: The Code Page Control (CPC) structured field must not contain a null value for the Default Graphic Character name. A null value is any 8-byte value where the first 2 bytes are X'FFFF'. See the 'FOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job. The printing continues with the next job in the print queue.
User response:: Correct the structured field in the code page and submit the job again.

0420-168

ERROR: The section identifier X'____' in repeating group number ____ of a Coded Font Index (CFI) structured field is not valid.

Explanation:: A section identifier must either be X'00', indicating a single-byte font, or must be in the range of X'41'-X'FE', inclusive. A Coded Font Index (CFI) structured field was encountered that specifies a section identifier that is neither X'00' nor in the range of X'41'-X'FE'. See the 'FOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the coded font and submit the job again.

0420-169

ERROR: The parameter data length ____ is not valid in a ____ structured field. The correct length is probably ____.

Explanation:

The parameter data length of the structured field specified in the message is not correct. The structured field parameter data is the data that follows the Structured Field Introducer. The message estimates what the correct parameter data length should be. This error can occur in the following cases:

The length of a Begin or End structured field is nonzero but is less than 8. If a Begin or End structured field contains any parameter bytes, it must include at least an 8-byte token name.
A structured field is missing one or more required parameters, including required triplets or required self-identifying parameters.
A Map Coded Font format 2 (MCF-2) structured field repeating group length is less than 2. The MCF-2 repeating group length is contained in the first 2 bytes of each repeating group.
A Map Page Overlay (MPO) structured field repeating group length is less than 18. The MPO structured field repeating group length is contained in the first 2 bytes of each repeating group. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-170

ERROR: The parameter data length ____ is not a multiple of the repeating group length ____ in a ____ structured field.

Explanation:: The length of the parameter data of the structured field specified in the message is not a multiple of the repeating group length (after subtracting out the lengths of optional variable data in the parameters). See the 'MO:DCA Reference' or the 'Font Object Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-171

ERROR: The repeating group number ____ in a ____ structured field contains a length value ____ that is greater than the remaining parameter bytes in the ____ structured field.

Explanation:: TThe structured field specified in the message contains multiple repeating groups, each of which contains its own length field. A repeating group was encountered that contained a length value that is greater than the total number of parameter bytes appearing after the previous repeating group. The structured field was either truncated or damaged in some way. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-172

ERROR: A Coded Font Index (CFI) structured field contains more than one repeating group, but the section identifier in the first repeating group is X'00'.

Explanation:: The presence of more than one repeating group in a Coded Font Index (CFI) structured field indicates that the coded font is used to specify multiple sections of a double-byte font. Double-byte font section IDs must be in the range of X'41'-X'FE', inclusive. A CFI structured field was encountered that contained more than one repeating group, yet the section ID in the first repeating group was X'00'. See the 'Font Object Content Architecture ( FOCA ) Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the coded font and submit the job again.

0420-173

ERROR: A Coded Font Index (CFI) structured field with repeating group number ____ is missing either a code page or character set name.

Explanation:: A Coded Font Index (CFI) structured field was encountered that contains either a code page name that was set to X'FFFF...' or a character set name that was set to X'FFFF...'. See the 'FOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the coded font and submit the job again.

0420-177

ERROR: The Output Option field ____ in the ____ structured field is not valid.

Explanation:

The Output Option field in the Map Graphic Object (MGO), the Include Object (IOB), Map Bar Code Object (MBC), Map Container Data (MCD), Map Graphics Object (MGO), Map Image Object (MIO), Preprocess Presentation Object (PPO), Map Presentation Text (MPT) or Map Image Object (MIO) structured fields must contain one of the following values:

X'00' (Position)
X'10' (Position-and-trim)
X'20' (Scale-to-fit)
X'30' (Center-and-trim)
X'41' (Image point-to-pel)
X'42' (Image point-to-pel double dot)
X'60' (Scale-to-fill)

The structured field specified in the message contains an invalid or unsupported value. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-178

ERROR: The Coded Font Index (CFI) structured field repeating groups that map sections of a double-byte font are not in ascending order by section number. Repeating group number ____ contains a section number ____ that is smaller than the section number of ____ in the previous repeating group.

Explanation:: The Coded Font Index (CFI) structured field repeating groups are not in ascending order by section number. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the coded font and submit the job again.

0420-182

ERROR: The X-direction and Y-direction L-unit-per-unit-base fields in the Image Input Descriptor (IID) structured field do not match. The X-direction value is ____ and the Y-direction value is ____.

Explanation:: The values for the L-unit-per-unit-base fields must match in the X- and Y-directions in the Image Input Descriptor (IID) structured field. An IID structured field was encountered where these fields do not match. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-183

ERROR: The repeating groups in the Map Coded Font format 1 (MCF-1) or the Map Coded Font format 2 (MCF-2) structured field that map sections of a double-byte font do not contain the character rotation value. Repeating group number ____ contains a character rotation ____ that is different from that of the previous repeating group ____.

Explanation:: The Map Coded Font format 1 (MCF-1) or Map Coded Font format 2 (MCF-2) structured field was used to select the sections of a double-byte font, but the repeating groups do not all contain the same character rotation value. All sections must contain the same character rotation value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-184

ERROR: The repeating groups in the Map Coded Font format 1 (MCF-1) or Map Coded Font format 2 (MCF-2) structured field that map sections of a double-byte font are not in ascending order by section number. Repeating group ____ contains a section number X'____' that is smaller than or equal to the section number in the previous repeating group X'____'.

Explanation:: The Map Coded Font format 1 (MCF-1) or Map Coded Font format 2 (MCF-2) structured field lists the sections of a double-byte font, but the repeating groups are not sorted by section number. At least one repeating group contains a section number that is less than or equal to the section number in the previous repeating group. These repeating groups must be sorted in ascending order by section number. Two repeating groups cannot contain the same section number. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-185

ERROR: Repeating group number ____ in a Map Coded Font format 1 (MCF-1) or Map Coded Font format 2 (MCF-2) structured field contains a local ID ____ that was also used in a previous repeating group, number ____.

Explanation:: A Map Coded Font format 1 (MCF-1) or Map Coded Font format 2 (MCF-2) structured field was encountered that specified the same local ID for two different fonts. The same local ID can be used to map different sections of a double-byte font, but each single-byte font (and each complete set of double-byte font sections) must be assigned a local ID that is unique not only within the same structured field but across all structured fields within the same Active Environment Group or Object Environment Group. There is one exception to this rule: local ID 254 can appear any number of times in an Active Environment Group. Any fonts mapped with local ID 254 in an Active Environment Group should be mapped again to a different local ID in the Object Environment Group within the same page or overlay. See the 'MO:DCA Reference' for further information on this structured field.
System action:: This message is informational only.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-186

The Image Input Descriptor (IID) structured field image resolution (______ pels per inch) does not match the actual destination image resolution (____ pels per _____).

Explanation:: The image resolution specified in bytes 14 through 17 of an Image Input Descriptor (IID) structured field does not match the actual destination image resolution. The image is printed at the desired origin, but the image size will not be correct because of the difference in pel sizes. See the Mixed Object Document Content Architecture Reference for further information on this structured field.
System action:: InfoPrint Manager continues processing and prints the image using the actual destination resolution specified in the message. The resulting image will be the wrong size.
User response:: Check the printed output to determine if the image that printed is acceptable. If you send this print job to an actual destination that supports the Image Object Content Architecture (IOCA) data stream, the image will be scaled automatically to the correct size.

0420-188

The print job has been canceled.

Explanation:: The print job was canceled by pressing the cancel button on the actual destination operator panel or through use of an AIX command, such as lprm.
System action:: InfoPrint Manager stops sending file data to the actual destination. When the actual destination has printed all of its buffered file data from InfoPrint Manager, the print job ends.
User response:: If the job was canceled in error, send the print job again.

0420-189

ERROR: InfoPrint Manager cannot find the Audit user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name specified on the -x option of the pdcreate command is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-190

ERROR: The Audit user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start the actual destination.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-191

ERROR: The Audit user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-192

ERROR: The Audit user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-193

ERROR: InfoPrint Manager cannot find the Header Page user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name on the -x option of the pdcreate command is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-194

ERROR: The Header Page user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start the actual destination.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-195

ERROR: The Header Page user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-196

ERROR: The Header Page user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-197

ERROR: InfoPrint Manager could not find the Input Data user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name on the -x option of the pdcreate command is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-198

ERROR: The Input Data user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-199

ERROR: The Input Data user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start the InfoPrint Manager actual destination.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-200

ERROR: The Input Data user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-201

ERROR: The Input Data user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-202

ERROR: InfoPrint Manager could not find the Message Page user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-203

ERROR: The Message Page user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-204

ERROR: The Message Page user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.

0420-205

ERROR: The Message Page user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.

0420-206

ERROR: The Message Page user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-207

ERROR: InfoPrint Manager could not find the Output Data user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name specified on the InfoPrint Manager SMIT Output Data User Exit Options panel is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-208

ERROR: The Output Data user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-209

ERROR: The Output Data user-exit program ____ reported a recoverable error.

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-210

ERROR: The Output Data user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-211

ERROR: The Output Data user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-212

ERROR: InfoPrint Manager cannot find the Separator Page user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name specified on the InfoPrint Manager SMIT Separator Page User Exit Options panel is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-213

ERROR: The Separator Page user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-214

ERROR: The Separator Page user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-215

ERROR: The Separator Page user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-216

ERROR: The Separator Page user-exit program ____ ended the print job.

Explanation:: The user-exit program specified in the message ended the print job based on conditions defined by the user-exit program.
System action:: The print job ends. InfoPrint Manager leaves the user-exit program active in memory.
User response:: Contact the person who developed the user-exit program for more information on the cause of this error.

0420-217

ERROR: InfoPrint Manager could not find the Trailer Page user-exit program ____ in the expected path ____ (return code=____).

Explanation:: InfoPrint Manager dynamically loads a user-exit program into memory prior to running the program. The user-exit program was not in the path specified in this message.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Look at the PATH statement in the /etc/environment file. Check that the PATH statement includes the directory in which the user-exit program is located. In addition to the path specified in the /etc/environment file, /usr/lpp/psf/bin is also a valid directory location for the user-exit program. Check that the user-exit program name specified on the InfoPrint Manager SMIT Trailer Page User Exit Options panel is correct. If both the path and the program name are correct, use local problem-reporting procedures to report this message and the return code number that it contains.

0420-218

ERROR: The Trailer Page user-exit program ____ refers to a function ____ that cannot be found (return code=____).

Explanation:: InfoPrint Manager successfully loaded the user-exit program into memory, but the user-exit program made a function call to a function that cannot be found.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Contact the person who developed the user-exit program. The program might have been compiled incorrectly, or the name of the function that cannot be found might have been misspelled. Use local problem-reporting procedures to report this message and the return code that it contains.

0420-219

ERROR: The Trailer Page user-exit program ____ reported a recoverable error (return code=____).

Explanation:: The user-exit program specified in the message reported a recoverable job completion error.
System action:: InfoPrint Manager records the error in the error log and continues processing the print job. The user-exit program remains active.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program to determine the meaning of the return code specified in the message.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-220

ERROR: The Trailer Page user-exit program ____ reported an error from which it cannot recover.

Explanation:: The user-exit program specified in the message reported an error that caused the user-exit program to end.
System action:: InfoPrint Manager records this error message in the error log and continues processing the print job. The user-exit program ends, and InfoPrint Manager removes it from memory. This program will not be called again for this InfoPrint Manager instance.
User response:: See the documentation for the user-exit program or the person who developed the user-exit program for further information on the cause of this error.
Note: The sample user-exit program supplied with InfoPrint Manager does not generate this error.

0420-221

ERROR: The message service shared-memory segment ____ cannot be allocated. The AIX error code is ____.

Explanation:: The DosAllocShrSeg request during message service initialization failed. This prevented the message service from successfully initializing.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-222

ERROR: AIX cannot create a message service shared-memory segment access semaphore ____. The AIX error code is ____.

Explanation:: The DosCreateSem request during message service initialization failed. This prevented the message service from successfully initializing.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-223

ERROR: The message service shared memory segment ____ cannot be opened. The AIX error code is ____.

Explanation:: The DosGetShrSeg request during message service initialization failed. This prevented the message service from successfully initializing.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-224

ERROR: The open message service shared memory segment access semaphore ____ cannot be opened. The AIX error code is ____.

Explanation:: The DosOpenSem request during message service initialization failed. This prevented the message service from successfully initializing.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance. InfoPrint Manager initialization failed.
User response:: Use local problem-reporting procedures to report this message.

0420-225

The error occurred in the resource ____ in file ____. The structured field in error was a ____ structured field (____) with sequence number ____ located at file offset ____.

Explanation:

This message is intended to help identify the structured field that caused a previous error message. The information provided includes:

The resource name of the resource containing the structured field in error
The fully qualified path to the file containing the structured field in error
The acronym used to refer to the structured field; for example: IOC for the Image Output Control structured field
The 3-byte hexadecimal code by which InfoPrint Manager identifies the structured field; for example: X'D3A77B' for the Image Output Control structured field
The 2-byte sequence number of the structured field in error; all structured fields contain a 2-byte sequence number in bytes 6-7 of the structured field introducer
The offset within the input file where the first byte of the record containing the structured field appears
Note: The offset starts at zero.

This message can appear several times. When an error is detected, the message is issued first for the structured field in error, then once for each structured field that caused InfoPrint Manager to process an additional structured field. For example, if an error occurs in a CFI structured field of a coded font that is specified with an MCF-1 structured field in a page overlay, the message is issued once for the CFI structured field in the coded font and again for the MCF-1 structured field in the overlay. A similar message is then issued for the MPO structured field in the print file. The set of messages establishes a 'chain' from the structured field in error, back through each resource file. See the 'MO:DCA Reference' for further information on this structured field.

System action:

See the system actions for other error messages in this message group.

User response:

See the responses for other error messages in this message group.

0420-228

ERROR: InfoPrint Manager cannot open the resource ____ referenced in the file ____.

Explanation:: InfoPrint Manager cannot access the resource file specified in the message. Someone might have deleted or moved the resource file. If the resource is located in a network file system, you may not have the required root permission to read the file. The file might not have been exported correctly across the network.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Check that the reference to the resource name is spelled correctly in the file. Check that the resource exists in the path /usr/lpp/psf/reslib or in the resource search paths specified when the print job is submitted. The resource path can also be specified with the PSFPATH environment variable. Use the AIX env command to view the settings of the environment variables. When specifying multiple paths, separate the paths with colons. In network environments, check that the owner, group, and others have permission to read the file.

0420-229

ERROR: InfoPrint Manager cannot read the file ____.

Explanation:: InfoPrint Manager opened the file but could not read it. If this error occurred in a network environment, the file might not have been exported correctly. If the file is on a remotely-mounted file system, the network itself might not be functioning correctly.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If this error is happening within a network, check that the file was exported correctly, and check that the network is working correctly. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-231

ERROR: The resource ____ in file ____ is not an AFP data stream resource.

Explanation:: The file does not contain a valid AFP data stream resource. Specifically, an AFP data stream resource must contain a Begin (Bxx) structured field; this structured field must be the first structured field, other than No operation (NOP) structured fields, in the file. The file specified in the message did not contain a Bxx structured field as the first non-NOP structured field. See the 'MO:DCA Reference' for further information on these structured fields.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the resource and send the file again.

0420-232

ERROR: The resource ____ in file ____ does not contain the expected type of AFP data stream resource. InfoPrint Manager expected to find ____ and found ____ instead.

Explanation:: InfoPrint Manager opened a file to process a specific type of AFP data stream resource. The file's Begin structured field, such as Begin Page Segment (BPS), is used to determine the type of resource. The file contains a different type of AFP resource than InfoPrint Manager expected.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Check that the resource matches the type of resource specified by its Begin structured field. Check that any reference to the resource specifies the correct type of resource. For example, a default form definition might have been specified on the InfoPrint Manager SMIT Processing Options panel, but the specified file is not a form definition.

0420-233

ERROR: The character set ____ contains a Font Orientation (FNO) structured field where repeating group number ____, which is used for character rotation X'____', contains the Font Index (FNI) number ____, but there are only ____ FNI structured fields in the character set.

Explanation:: Each Font Orientation (FNO) structured field repeating group contains a zero-based font index (FNI) number that indicates which FNI structured field is to be used in loading a font. For example, if an FNO repeating group contains an FNI number of three, the fourth FNI is used in loading the font. In this case, the FNO repeating group contained an FNI number that was equal to or greater than the total number of FNI structured fields in the character set. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the font character set and send the job again.

0420-234

ERROR: InfoPrint Manager cannot find a ____ structured field in the font character set in file ____.

Explanation:: A font character set must contain certain required structured fields. A font character set does not contain the structured field specified in the message.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0420-235

InfoPrint Manager Error Log created for actual destination ____.

Explanation:: InfoPrint Manager writes this message as the first entry in the error log to identify the actual destination to which the error log belongs.
System action:: InfoPrint Manager writes this message to the error log when InfoPrint Manager initializes.
User response:: This is an informational message; no response is required.

0420-236

The Error Log has wrapped.

Explanation:: When the WRAP error log field of the InfoPrint Manager SMIT Error Log and Trace Options panel is set to Yes, InfoPrint Manager wraps the error log for the actual destination when the maximum error log size, specified on the same panel, is reached. This message indicates that an error log wrap occurred and InfoPrint Manager is writing over messages previously recorded in the error log.
System action:: InfoPrint Manager writes this message to the error log.
User response:: This is an informational message; no response is required.

0420-237

Starting the Error Log for actual destination ____.

Explanation:: InfoPrint Manager issues this messages when restarting after an error condition.
System action:: InfoPrint Manager writes this message to the error log.
User response:: This is an informational message; no response is required.

0420-238

Stopping the Error Log for actual destination ____.

Explanation:: InfoPrint Manager issues this messages when stopping because of an error condition.
System action:: InfoPrint Manager writes this message to the error log.
User response:: This is an informational message; no response is required.

0420-239

A print position adjustment was made by the actual destination operator.

Explanation:: The actual destination reported that a print position adjustment was made to the actual destination's continuous-forms paper supply during the print job. Printed output should be acceptable.
System action:: After the print position adjustment is made, InfoPrint Manager recovers and printing continues.
User response:: Examine the printed output to determine if the forms adjustment caused any printing problems. If any problems are found, send the print job again.

0420-240

The statistics file was created on ________.

Explanation:: Indicates the date and time that the statistics file was created. This message is used in the header of the statistics file only.
System action:: Processing continues.
User response:: This is an informational message; no response is required.

0420-241

The statistics file last changed ____.

Explanation:: Indicates the date and time that the statistics file was last changed. This message is used in the header of the statistics file only.
System action:: Processing continues.
User response:: This is an informational message; no response is required.

0420-242

ERROR: The Default Graphic Character ID '____', which is specified in the Code Page Control (CPC) structured field, cannot be found in the Font Index (FNI) structured field number '____'.

Explanation:: The Code Page Control (CPC) structured field contains the 8-byte ID of the default graphic character to be used for any code point that is not specified in the Code Page Index (CPI) structured field, and for any code point in the CPI structured field whose corresponding graphic character ID cannot be located in any repeating group of the Font Index (FNI) structured field. InfoPrint Manager requires that the default graphic ID specified in the CPC structured field appears in the FNI structured field. In this case, an FNI structured field was searched, but no repeating group was found that contained the default graphic character ID. The CPC and CPI structured fields are contained in the code page; the FNI structured field is contained in the font character set. See the 'Font Object Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the code page or character set and send the job again.

0420-243

ERROR: The Font Index (FNI) structured field number ____ with repeating group number ____ and graphic character ID ____ contains a value ____ for the FNM index field that is not valid. The number of FNM repeating groups is ____.

Explanation:: The Font Index (FNI) structured field contained at least one repeating group that contained an Font Patterns Map (FNM) index field that was too large The FNM index field is a zero-based index into the data from the FNM structured field, and therefore must contain a value that is less than the number of FNM repeating groups. See the ' Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNI structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-244

InfoPrint Manager Statistics File

Explanation:: This is the first line of the InfoPrint Manager statistics file.
System action:: This message is informational only.
User response:: Review the other entries in the statistics file.

0420-245

InfoPrint Manager Error Log

Explanation:: This is the first line of the InfoPrint Manager statistics file.
System action:: This message is informational only.
User response:: Review the other entries in the error log.

0420-246

Message from actual destination: ____

Explanation:: An InfoPrint Manager error has occurred with the InfoPrint Manager actual destination specified in the message. Other error messages in this message group provide more details about the problem.
System action:: See the system actions for other error messages in this message group.
User response:: Use the InfoPrint Manager SMIT List All Printers Defined to InfoPrint Manager panel to determine which actual destination corresponds to the actual destination name specified in this message.

0420-247

Job Name=____ Job ID=____ Node ID=____ User ID=____

Explanation:: This is an additional information message that is concatenated with error log messages associated with a print job or page.
System action:: InfoPrint Manager writes this message to the error log.
User response:: This is an informational message; no response is required.

0420-248

ERROR: The actual destination reported an error, but InfoPrint Manager cannot recover because there is not enough memory.

Explanation:: InfoPrint Manager ran out of memory and cannot correct an actual destination error.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Send the job again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-249

InfoPrint Manager received IPDS exception X'____..____', action code X'____' from the actual destination.

Explanation:: This message identifies the IPDS exception that was reported to InfoPrint Manager by the actual destination. See the 'IPDS Reference' for specific information on the Exception ID and the Action Code contained within this message.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-250

In the font character set named ____ , the projected font byte count ____ does not match the actual count ____ .

Explanation:: The length of all the FNG (Font Patterns) structured fields is less than the length, in bytes, of the font pattern data (when the pattern technology identifier is set to X'1E' or X'1F') specified in bytes 28-31 of Font Control (FNC) structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job. Otherwise, InfoPrint Manager cancels the job.
User response:: If you created the FCS, correct the error by consulting font data stream references. Otherwise, notify the person who administers your system or the owner of the FCS and have the error corrected.

0420-251

ERROR: The actual destination reported an error condition that is not recognized.

Explanation:: The actual destination reported an IPDS exception that InfoPrint Manager does not recognize. The actual destination microcode might have been updated to a level not supported by or known by the installed version of InfoPrint Manager.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-252

The sense bytes received from the actual destination are X'____'.

Explanation:: This message identifies the sense bytes that the actual destination reported. The IPDS exception was generated from the actual destination sense bytes. See the 'IPDS Reference' for details about actual destination sense and IPDS exceptions.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-253

InfoPrint Manager canceled printing of the file.

Explanation:: InfoPrint Manager stops processing the file as part of InfoPrint Manager error recovery. See the explanations for other error messages in this message group.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the causes of the other error messages in this message group.

0420-254

The actual destination reported an error that caused InfoPrint Manager to stop processing the page.

Explanation:: InfoPrint Manager stops processing the page as a part of InfoPrint Manager error recovery. However, the page containing the error might appear to be complete. See the explanations for other error messages in this message group.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: See the responses for other error messages in this message group.

0420-255

ERROR: InfoPrint Manager has lost contact with the actual destination. InfoPrint Manager cannot recover from the reported actual destination errors.

Explanation:: InfoPrint Manager lost contact with the actual destination during error recovery. There might be a problem with the actual destination cable connection or the actual destination might have entered a not ready state. InfoPrint Manager cannot communicate with the actual destination until contact is restored.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Determine why the destination contact was lost, and correct the problem.

0420-256

ERROR: The actual destination restarted while printing this job.

Explanation:: Destination restarts can occur because the power to the actual destination is interrupted, or because of certain error conditions. When an actual destination restarts, InfoPrint Manager cannot determine how much of the print job information previously sent to the actual destination by InfoPrint Manager was printed before the restart occurred.
System action:: After the actual destination restart is complete, InfoPrint Manager resumes sending print job information to the actual destination. The resulting printed output might contain duplicate pages.
User response:: Check the printed output and remove any duplicate pages.

0420-257

The actual destination Cancel key was pressed.

Explanation:: Someone pressed the Cancel key on the actual destination while a job was printing.
System action:: InfoPrint Manager cancels the print job in progress at the time the Cancel key is pressed. InfoPrint Manager ignores the actual destination Cancel key during the processing of a trailer page.
User response:: If the Cancel key was pressed intentionally, no action is required. Otherwise, send the print job again.

0420-258

ERROR: The actual destination reported a text-control code that is not valid.

Explanation:: The actual destination reported an embedded Intelligent Printer Data Stream (IPDS) text control code that is either not valid or not supported. InfoPrint Manager might not support this actual destination, or the actual destination might not have the appropriate hardware or microcode installed.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Check that the actual destination is one of the models that InfoPrint Manager supports and is equipped as specified in the documentation for the actual destination. If necessary, use local problem-reporting procedures to report this message.

0420-259

ERROR: InfoPrint Manager cannot assign a resource ID to the resource named ____.

Explanation:: InfoPrint Manager assigns a resource ID to each actual destination resource. Destination resources include single-byte fonts, double-byte fonts, data-object-resources, overlays, and page segments. A page required more resources of a certain type than could be assigned resource IDs. The page cannot be printed. For more information on actual destination resources, see the 'IPDS Reference'.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Reduce the number of resources (of the type specified in the message text) used by the page.

0420-260

The actual destination reported an out-of-storage condition. Recovery was performed.

Explanation:: The actual destination reported to InfoPrint Manager that it ran out of storage while trying to print the current job. InfoPrint Manager recovers from this problem by deleting unneeded actual destination resources and retrying the print job from the point of the reported error. This message goes to the error log only.
System action:: InfoPrint Manager deletes the resources and processes the page again.
User response:: This is an informational message; no response is required.

0420-261

ERROR: The actual destination reported that it has insufficient memory to print a page. InfoPrint Manager cannot correct the problem.

Explanation:: When the actual destination first notifies InfoPrint Manager that an out-of-memory condition occurred for a given page in the print job, InfoPrint Manager deletes all resources from memory except those required by that page and tries to print the page. If, after the unneeded resources are deleted, the actual destination reports a second out-of-memory condition for the same page, the page is too large or too complex to print on this actual destination, and InfoPrint Manager issues this message.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job to a different actual destination that has more memory, or make the page less complicated by reducing the number of resources required by the page. Some actual destinations return this error when the page size defined for a page is larger than a pre-defined maximum page size. This maximum page size can be changed in the actual destination as part of the actual destination configuration. In this situation, you can correct the problem either by creating smaller pages before printing the job (e.g have the transform program generate smaller output pages), or you can increase the maximum page size in the actual destination configuration. See your actual destination documentation to determine whether and how you can do this.

0420-262

ERROR: The actual destination reported an IPDS command length that is either not valid or not supported.

Explanation:: The actual destination reported an IPDS command length that is either not valid or not supported. See the 'IPDS Reference' for more information on valid command lengths.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-263

ERROR: The actual destination reported a data structured field that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-264

Check the printed output for duplicate pages.

Explanation:: Because of another error or errors, such as an actual destination restart or a power failure, InfoPrint Manager has moved the point within the print job from which it starts sending information to the actual destination after error recovery. Printing continues, but duplicate pages might be printed. This message only appears when InfoPrint Manager cannot determine what has already been printed.
System action:: See the system actions for other error messages in this message group.
User response:: Check the printed output and remove any duplicate pages.

0420-265

ERROR: The actual destination reported a block orientation that is either not valid or not supported.

Explanation:: The reported problem is in an image, graphics, object container or presentation text block. The block is part of the page in error or is contained in a page segment, overlay, or data-object-resource used on the page in error. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-266

ERROR: The actual destination reported that an End Page or END command was received before a text suppression ended.

Explanation:: An End Page or END command was encountered before a text suppression ended. See the 'IPDS Reference' for a description of text suppressions and the End Page and END commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-267

ERROR: The actual destination reported an Image, Presentation Text or Object Container Position that is either not valid or not supported.

Explanation:: There is a problem in either the Image Area Position self-defining field, the Write Object Container Control(WOCC) command, the Text Area Position self-defining field of Write Text Control (WTC) command, or the Include Data Object (IDO) command . The Image Area Position self-defining field is part of the Write Image Control 2 (WIC2) command. See the 'Intelligent Printer Data Stream Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again. If the error still occurs, use local problem-reporting procedures to report this message.

0420-268

ERROR: The actual destination reported a spanning sequence that is not valid.

Explanation:: See the 'IPDS Reference' for a description of the spanning sequences for the Write Text (WT) command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-269

ERROR: The actual destination reported the unit base of a structured field that is either not valid or not supported.

Explanation:: See the 'MO:DCA Reference' for a description of structured field unit bases.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again. If the error still occurs, use local problem-reporting procedures to report this message.

0420-270

ERROR: The actual destination reported that the length of the IPDS command header is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-271

ERROR: The actual destination reported a Begin Suppression text control that is not valid.

Explanation:: The reported error indicates that a Begin Suppression text control was received by the actual destination in a page, a page segment, or an overlay before a previous suppression ended. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-272

ERROR: The actual destination reported structured field L-units that are either not valid or not supported.

Explanation:: See the 'MO:DCA Reference' for a description of structured field L-units.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-273

ERROR: The actual destination reported structured field extents that are either not valid or not supported.

Explanation:: See the 'MO:DCA Reference' for a description of structured field extents.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-274

ERROR: The actual destination reported a mapping option that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-275

ERROR: The actual destination reported axis offsets that are either not valid or not supported.

Explanation:: The axis offset values specified in the output-control structured field of an image, graphics, presentation text or object container block are either not valid or not supported. The block is part of the page in error or is contained in a page segment, overlay, or data-object-resource used on the page in error. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-276

ERROR: The actual destination reported an image block positioned outside of the valid printable area.

Explanation:: The reported problem is in an image or graphics block. An image or graphics block includes the white space surrounding the image or graphic. This error can be caused by any part of the image or graphics block, including the white space, extending off of the logical page. See the 'MO:DCA Reference' for more information on image and graphics blocks.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-277

ERROR: The actual destination reported a structured field identifier that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-278

ERROR: The actual destination reported a local font identifier that is either not valid or not supported.

Explanation:: A local font identifier in a Set Coded-Font Local text control or in a Load Page Descriptor command is either not valid or not supported. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-279

ERROR: The actual destination reported a Set Text Orientation text control that is either not valid or not supported.

Explanation:: There is a problem with the inline direction value, the baseline direction value, or the combination of inline and baseline direction values that were specified. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-280

ERROR: The actual destination reported a Set Inline Margin text control that is either not valid or not supported.

Explanation:: The inline margin value specified in a Set Inline Margin text control or in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported. The Set Inline Margin control sequence is part of the Write Text (WT) command. See the 'Intelligent Printer Data Stream Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-281

ERROR: The actual destination reported a Set Baseline Increment text control that is either not valid or not supported.

Explanation:: The baseline increment value specified in a Set Baseline Increment text control sequence or in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported. The Set Baseline Increment control sequence is part of the Write Text (WT) command. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-282

ERROR: The actual destination reported an intercharacter adjustment that is either not valid or not supported.

Explanation:: The intercharacter adjustment value specified in a Set Intercharacter Adjustment text control sequence or in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported. The Set Intercharacter Adjustment control sequence is part of the Write Text (WT) command. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-283

ERROR: The actual destination reported an Absolute Move Baseline text control value that is either not valid or not supported.

Explanation:: Valid values for the Absolute Move Baseline text control are 0 to 5,461 when using 240 L-units per inch and 0 to 32,767 when using 1440 L-units per inch. The position value specified in an Absolute Move Baseline text control is not in these ranges. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-284

ERROR: The actual destination reported an Absolute Move Inline text control value that is either not valid or not supported.

Explanation:: Valid values for the Absolute Move Inline text control are 0 to 5,461 when using 240 L-Units per inch and 0 to 32,767 when using 1440 L-units per inch. The Absolute Move Inline text control value is not in these ranges. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-285

ERROR: A delete request was sent to the actual destination for a font that was not loaded.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-286

ERROR: The actual destination received a Delete Font command that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-287

ERROR: The actual destination reported a Set Variable-Space Character Increment text control value that is either not valid or not supported.

Explanation:: Valid values for the Set Variable-Space Character Increment text control are 0 to 5,461 when using 240 L-units per inch and 0 to 32,767 when using 1440 L-units per inch. The value specified for the Set Variable-Space Character Increment text control is not within these ranges. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-288

ERROR: The actual destination reported a value in a Delete Font command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-289

ERROR: The actual destination reported a font identifier that is not valid for this print job.

Explanation:: The actual destination reported an error condition that usually indicates an identifier that is either not valid or not supported, that a font identifier used during font loading is not recognized, or that an actual destination resident font Global Resource ID (GRID) is not supported. See the 'IPDS Reference' for a description of the conditions that can cause an actual destination to report this error.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job. Depending on the point that the error occurred, part of the page containing the error might print.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-290

ERROR: The actual destination reported a value for a Repeat String repeat length that is either not valid or not supported.

Explanation:: The repeat length in a Repeat String text control is either not valid or not supported. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-291

ERROR: The actual destination reported multiple occurrences of the same font-equivalence number in a Load Font Equivalence command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-292

ERROR: The actual destination reported a Repeat String or a Transparent Data error.

Explanation:: The source-string length for the Repeat String or Transparent Data text controls must be an even number of bytes for double-byte fonts or if it is an odd number of bytes, the font specified must not be double-byte code points. The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-293

ERROR: The actual destination reported a length error for the Repeat String target string.

Explanation:: The target-string length for the Repeat String text control must be an even number for double-byte fonts. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-294

ERROR: The actual destination reported a Load Font Control unit base that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-295

ERROR: The actual destination reported an escape sequence that is not valid for the Write Text or Write Text Control command.

Explanation:: On a Write Text or Write Text Control command , the second byte of X'2BD3' is not the expected value of X'D3'. See the 'IPDS Reference' for a description of the Write Text command and escape sequences.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-296

ERROR: The actual destination reported a text-control length for a Write Text or Write Text Control command that is not valid.

Explanation:: The length of a Write Text or Write Text Control command text control is not supported. See the 'IPDS Reference' for a description of this command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-297

ERROR: The actual destination reported an exception in a Repeat String length.

Explanation:: The Repeat String text control in a Write Text command has a nonzero fill count but has a zero string length. See the 'IPDS Reference' for a description of this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-298

ERROR: The actual destination reported a Load Font Control font stageability byte that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-299

ERROR: The actual destination reported a value for a Load Font Control font index format that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-300

ERROR: The actual destination reported a value for a data pattern format of a Load Font Control command that is either not valid or not supported.

Explanation:: The pattern-data format value specified in a Load Font Control command is either not valid or not supported. The value must be X'05'. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-301

ERROR: The actual destination reported an error in an End Suppression text control.

Explanation:: The internal suppression value specified in the active Begin Suppression text control for the current page, a page segment, or an overlay is not the same as the internal suppression value specified in the End Suppression text control. The values must match. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-302

ERROR: The actual destination reported a font type value for a Load Font Control that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-303

ERROR: The actual destination reported a size for a Load Font Control X-box that is either not valid or not supported.

Explanation:: The constant character-box X size in an LFC command is not valid, not supported, or not compatible with the specified font. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-304

ERROR: The actual destination reported a size for a Load Font Control Y-box that is either not valid or not supported.

Explanation:: The constant character-box Y size in an LFC command is not valid, not supported, or not compatible with the specified font. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-305

ERROR: The actual destination reported a value for the L-units per unit base in the X-direction for a Load Font Control command that is either not valid or not supported.

Explanation:: The X-density value in a Load Font Control command is either not valid or not supported. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-306

ERROR: The actual destination reported a value for the L-units per unit base in the Y-direction for a Load Font Control command that is either not valid or not supported.

Explanation:: The Y-density value in a Load Font Control command is either not valid or not supported. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-307

ERROR: The actual destination reported a value for a character-data alignment in a Load Font Control command that is either not valid or not supported.

Explanation:: The character-data alignment in a Load Font Control command is either not valid or not supported. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-308

ERROR: The actual destination reported that insufficient font data was received.

Explanation:: The actual destination received less font data than was specified in the Load Font Control or Load Font Character Set Controll command. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-309

ERROR: The actual destination reported a number of copies value on a Load Copy Control command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-310

ERROR: The actual destination reported a keyword in a copy-group entry in a Load Copy Control command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-311

ERROR: The actual destination reported that extra font data was received.

Explanation:: The actual destination received more font data than was specified in the Load Font Control or Load Font Character Set Control command. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-312

ERROR: The actual destination reported a baseline extent value on a Load Font Index command that is either not valid or not supported.

Explanation:: A maximum baseline extent value in a Load Font Index command is either not valid or not supported.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the coded font and send the job again.

0420-313

ERROR: The actual destination reported a copy-group byte count on a Load Copy Control command that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-314

ERROR: The actual destination reported a simplex-duplex parameter on a Load Copy Control command that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-315

ERROR: The actual destination reported that more overlays were specified on a Load Copy Control command than are allowed in a copy group.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-316

ERROR: The actual destination reported that the number of suppressions allowed in a Load Copy Control command copy group was exceeded.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-317

ERROR: The actual destination reported that the font identifier on a Load Font Control command was already assigned.

Explanation:: The actual destination already has a font with the same identifier as the identifier specified in a Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again. If the error still occurs, use local problem-reporting procedures to report this message.

0420-318

The actual destination reported that the maximum number of fonts that can be downloaded to the actual destination was reached.

Explanation:: An attempt was made to download more fonts to the actual destination than the actual destination can support.
System action:: InfoPrint Manager deletes any unneeded fonts from the actual destination's memory and continues processing the print job, starting with the page that caused the error.
User response:: This is an informational message; no response is required.

0420-319

ERROR: The actual destination reported that a page in the print job requires more fonts than can be downloaded to the actual destination.

Explanation:: The first time this error occurs, InfoPrint Manager deletes any unneeded fonts from the actual destination's memory and attempts to process the page that caused the error. When the actual destination reports the second occurrence of this error for the same page, the actual destination is unable to print the page because it requires more fonts than the actual destination can store in memory at one time.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job to an actual destination that supports more fonts, or reduce the number of fonts required by the page.

0420-320

ERROR: The actual destination reported a command length that is not consistent with the number of commands.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-321

ERROR: The actual destination reported a double-byte character flag that is not valid.

Explanation:: A character flag bit entry that is not valid was received within a font index for a double-byte font. See the 'IPDS Reference' for a description of double-byte fonts, and the correct settings for character flag bits.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the coded font and send the job again.

0420-322

ERROR: The actual destination reported that a Load Font Index command contains a value that is either not valid or not supported.

Explanation:: A value was sent to the actual destination in a Load Font Index command is either not valid or not supported. See the 'IPDS Reference' for a description of the Load Font Index command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the coded font and send the job again.

0420-323

ERROR: The actual destination reported a character-pattern address in a Load Font Control command contains a value that is either not valid or not supported.

Explanation:: A problem exists with the character-pattern addresses in the Character Pattern-Descriptor List of a Load Font Control command. See the 'IPDS Reference' for a description of the Load Font Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the coded font and send the job again.

0420-324

ERROR: The actual destination reported a mismatch among the values in the Set Text Orientation, Set Coded Font Local, Write Text Control and Load Font Equivalence commands.

Explanation:: A mismatch exists among the Set Text Orientation, Set Coded Font Local, Write Text Control and Load Font Equivalence commands, which resulted in the actual destination not being able to print with the specified font. See the 'IPDS Reference' for a description of these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-325

ERROR: The actual destination reported a value for a font inline sequence that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-326

ERROR: The actual destination reported a pel count for a Write Image Control command that was less than the supported minimum.

Explanation:: The target or source pel-count value in a Write Image Control command is less than one. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-327

ERROR: The actual destination reported a pel count for a Write Image Control command that was greater than the supported maximum.

Explanation:: The target or source pel-count value in a Write Image Control command is greater than the valid or supported maximum. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-328

ERROR: The actual destination reported a font section identifier for a double-byte font that is not valid.

Explanation:: The section identifier in a Load Font Control or Load Font Index command could not be used with the specified font. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem in the coded font and send the job again.

0420-329

ERROR: The actual destination reported a scan count on a Write Image Control command that was less than the supported minimum.

Explanation:: The target or source scan-count value in a Write Image Control command is less than one. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-330

ERROR: The actual destination reported a mismatch in the values specified for the sections of a double-byte font.

Explanation:: Font sections in a double-byte font are required to have identical values for several parameters from the structured fields that make up the font character set, code page, and coded font. One or more of these parameters changed between font sections. See the 'Advanced Function Printing: Host Font Data Stream Reference' for more information about the parameters that must match across sections in a double-byte font.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the font character set, code page, or coded font and send the print job again.

0420-331

ERROR: The actual destination reported a scan count on a Write Image Control command that was greater than the supported maximum.

Explanation:: The target or source scan count value in a Write Image Control command is greater than the valid or supported maximum. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-332

ERROR: The actual destination reported a source image format on a Write Image Control command that is not valid.

Explanation:: The source image format specified in a Write Image Control command is not valid. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-333

ERROR: The actual destination reported a parameter that is not valid in a Load Font Index command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-334

ERROR: The actual destination reported a pel-magnification factor value in a Write Image Control command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-335

ERROR: The actual destination reported a font inline sequence parameter value in a Load Font Equivalence command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-336

ERROR: The actual destination reported a scan-line direction value in a Write Image Control command that is either not valid or not supported.

Explanation:

Valid scan-line direction values are:

X'0000', indicating 0 degrees
X'2D00', indicating 90 degrees
X'5A00', indicating 180 degrees
X'8700', indicating 270 degrees

The scan-line direction value in the Write Image Control command is either not valid or not supported. See the 'IPDS Reference' for a description of the Write Image Control command.

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-337

ERROR: The actual destination reported a scan-line sequence direction value in a Write Image Control command that is either not valid or not supported.

Explanation:

Valid scan-line sequence direction values are:

X'0000', indicating 0 degrees
X'2D00', indicating 90 degrees
X'5A00', indicating 180 degrees
X'8700', indicating 270 degrees

The scan-line sequence direction value in the Write Image Control command is either not valid or not supported. See the 'IPDS Reference' for a description of the Write Image Control command.

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-338

ERROR: The actual destination reported an output image location value in a Write Image Control command that is either not valid or not supported.

Explanation:: The output image location is the coordinate position of the top-left corner of the image output block on the logical page. The output image location value in a Write Image Control command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-339

ERROR: The actual destination reported an invalid or unsupported image color.

Explanation:: The image color in a Write Image Control (WIC) command is invalid or unsupported. See the 'IPDS Reference' for a description of the Write Image Control command.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the error in the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-340

ERROR: The actual destination reported a value for text color that is either not valid or not supported.

Explanation:: The text color value in a Load Page Descriptor or Write Text Control command is either not valid or not supported. The problem might be caused by the text color value in a Set Text Color text control. See the 'IPDS Reference' for a description of the Load Page Descriptor command. The text control is contained in a Presentation Text (PTX) structured field. See the 'PTOCA Reference' for further information on this text control.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-341

ERROR: The actual destination reported that the Define User Area command contains a parameter that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-342

ERROR: The actual destination reported that the L-units per unit base in the X-direction of the Load Page Descriptor command contains a value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-343

ERROR: The actual destination reported that the L-units per unit base in the Y-direction of the Load Page Descriptor command contains a value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-344

ERROR: The actual destination reported a value for the Xp-extent that is either not valid or not supported.

Explanation:: The Xp-extent in a Load Page Descriptor or Execute Order Homestate - Set Media Size command is either not valid or not supported. See the 'IPDS Reference' for a description of these commands and the correct values for Xp-extents.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-345

ERROR: The actual destination reported a value for the Yp-extent that is either not valid or not supported.

Explanation:: The Yp-extent in a Load Page Descriptor or Execute Order Homestate - Set Media Size command is either not valid or not supported. See the 'IPDS Reference' for a description of these commands, and the correct values for Yp-extents.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-346

ERROR: The actual destination reported a unit base value in a Load Page Descriptor command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-347

ERROR: The actual destination reported a control in a Load Page Descriptor command that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-348

ERROR: The actual destination reported a unit base value in a Load Page Descriptor command that is either not valid or not supported.

Explanation:: The inline sequence direction value in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for a description of the Load Page Descriptor command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-349

ERROR: The actual destination reported a value for a baseline sequence direction Load Page Descriptor command or a Write Text Control command that is either not valid or not supported.

Explanation:: The baseline sequence direction value in a Load Page Descriptor command or in a Write Text Control command is not valid when taken in combination with the inline sequence direction value. See the 'IPDS Reference' for a description of the Load Page Descriptor and Write Text Control commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-350

ERROR: The number of image bytes contained in the Image Raster Data (IRD) structured field or fields was less than the number specified in the Input Image Descriptor (IID) structured field.

Explanation:: The number of source image bytes received by the actual destination is less than the number specified in the IID structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-351

ERROR: The number of image bytes contained in the Image Raster Data (IRD) structured field or fields was greater than the number specified in the Input Image Descriptor (IID) structured field.

Explanation:: The number of source image bytes received by the actual destination is greater than the number specified in the IID structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-352

ERROR: The actual destination reported a media origin parameter that is not valid in an Execute Order Homestate - Set Media Origin command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-353

ERROR: The actual destination reported a rule width that is either not valid or not supported.

Explanation:: A specified rule width is either not valid or not supported. See the 'IPDS Reference' for a description of valid rule widths.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job. Depending on where the error occurred, part of the page containing the error might print.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-354

ERROR: The actual destination reported a value for an overlay identifier of a Delete Overlay command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-355

ERROR: The actual destination reported a page segment identifier value in a Delete Page Segment command that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-356

ERROR: The actual destination reported an overlay identifier value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-357

ERROR: The actual destination reported a Begin Overlay command overlay identifier already loaded error.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-358

ERROR: The actual destination reported a value that is either not valid or not supported in an Execute Order Anystate - Request Resource List command order.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-359

ERROR: The actual destination reported that an overlay identifier was not loaded.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-360

ERROR: The actual destination reported a recursive overlay invocation error.

Explanation:: A recursive nesting loop has occurred with an Include Overlay command. This means that the overlay resource specified in the Include Overlay command references itself or references another overlay that references itself. See the 'IPDS Reference' for more information about the Include Overlay command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the overlay problem.

0420-361

ERROR: The actual destination reported a page segment identifier that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-362

ERROR: The actual destination reported a page segment identifier already loaded error.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-363

ERROR: The actual destination reported an identifier that is not valid in an Execute Order Homestate - Page Counters Control order.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-364

ERROR: The actual destination reported that a page segment identifier was not loaded.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-365

ERROR: The actual destination reported that the overlay-nesting limit was greater than the supported maximum.

Explanation:: The actual destination cannot include a needed overlay or page segment because the actual destination nesting limit has been exceeded. This means that the specified overlay is too complex for this actual destination's available memory to process.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job to an actual destination that supports a larger nesting level (that is, an actual destination with more memory). If no such actual destination is available, simplify the overlay.

0420-366

ERROR: The actual destination reported a suppression number that is either not valid or not supported.

Explanation:: The suppression number in a Load Copy Control command or Write Text command is either not valid or not supported. See the 'IPDS Reference' for a description of the commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-367

ERROR: The actual destination reported an edge-mark parameter that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-368

ERROR: The actual destination reported an error in a page boundary in the X-direction.

Explanation:: The sum of the Xp-extent value in the Load Page Descriptor command or the Xp-coordinate value in the Load Page Position command (indicating logical page or overlay origin) exceeded the maximum supported value. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-369

ERROR: The actual destination reported an error in a user printable area (UPA) boundary in the X-direction.

Explanation:: The sum of the Xm-coordinate of the user printable area origin and the Xm-extent of the user printable area specified in a Define User Area command exceeded the maximum value that can be represented in the actual destination. See the 'IPDS Reference' for more information about the Define User Area command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-370

ERROR: The actual destination reported an error in a page boundary in the Y-direction.

Explanation:: The sum of the Yp-extent value in the Load Page Descriptor command or the Yp-coordinate value in the Load Page Position command (indicating logical page or overlay origin) exceeded the maximum supported value. See the 'IPDS Reference' for more information about these commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-371

ERROR: The actual destination reported an error in a user printable area (UPA) in the Y-direction.

Explanation:: The sum of the Ym-coordinate of the user printable area origin and the Ym-extent of the user printable area specified in a Define User Area command exceeded the maximum value that can be represented in the actual destination. See the 'IPDS Reference' for more information about the Define User Area command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-372

ERROR: The actual destination reported that there is not sufficient memory to print a page.

Explanation:: The actual destination could not print the specified page because there was not enough storage in the actual destination for the page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Either send the file to an actual destination that has more storage, or simplify the page. If the file was printing as duplex, the file might print successfully if it is sent as a simplex job.

0420-373

ERROR: The actual destination reported a value that is either not valid or not supported for a Load Page Position command.

Explanation:: The X-coordinate or Y-coordinate in a Load Page Position command is either not valid or not supported. See the 'IPDS Reference' for more information about the Load Page Position command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-374

ERROR: The actual destination reported a parameter in the Include Overlay command that is either not valid or not supported.

Explanation:: A parameter in an Include Overlay command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for more information about the Include Overlay command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the input file or in the form definition.

0420-375

ERROR: The actual destination reported a mixture of Xm-axis and Ym-axis duplex copy groups in a Load Copy Control command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-376

ERROR: The actual destination reported a mixture of Xm-axis and Ym-axis duplex copy groups in a Load Copy Control command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-377

ERROR: The actual destination reported an internal value that is not unique in a Load Equivalence command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-378

ERROR: The actual destination reported an odd number of duplex copy groups in a Load Copy Control command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-379

ERROR: The actual destination reported a mixture of simplex and duplex parameters in a Load Copy Control command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-380

ERROR: The actual destination reported copy counts that are not equal in a Load Copy Control command.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-381

ERROR: The actual destination reported that it was not able to delete a resource.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-382

ERROR: The actual destination reported a mapping type in a Load Equivalence command that is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-383

ERROR: The actual destination reported a value in a Load Equivalence command that is either not valid or not supported.

Explanation:: The internal or external value in a Load Equivalence command is either not valid or not supported. See the 'IPDS Reference' for more information about the Load Equivalence command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-384

ERROR: The actual destination detected additional exceptions that were not specifically reported to InfoPrint Manager.

Explanation:: Storage was not available for all of the exceptions detected by the actual destination; therefore, some of them were not reported to InfoPrint Manager.
System action:: InfoPrint Manager recovers from the most important error that is reported by the actual destination.
User response:: InfoPrint Manager will base its error recovery on the most important error that was reported. However, because some errors have not been reported, you should examine your output carefully. After correcting all errors that were reported, send the print job again to determine any problems that remain.

0420-386

ERROR: The paper in the actual destination input bin has changed.

Explanation:: The actual destination reported that the paper changed in an input bin. InfoPrint Manager reports this message for the user's information in case the new media is not satisfactory for the print job.
System action:: InfoPrint Manager recovers and printing continues.
User response:: Examine the printed output to determine if the new paper is satisfactory for the print job. If the printed output is not satisfactory, change the actual destination paper supply to the appropriate type, and send the print job again.

0420-391

ERROR: A problem occurred when processing code page ____ .

Explanation:: The LCPC (Load Code Page Control) Bytes 4–7 specifies an invalid value of zero for the number of data bytes to be transmitted for this code page in subsequent LCP (Load Code page) commands.
System action:: InfoPrint Manager stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job. Otherwise, InfoPrint Manager cancels the job.
User response:: If you created the code page, correct the error by consulting font data stream references. Otherwise, notify the person who administers your system or the owner of the code page to correct the error.

0420-392

ERROR: There is additional information about the exception received. This information is found in the following messages.

Explanation:: This message is informational only.
System action:: This message is informational only.
User response:: Look at the following messages.

0420-395

________

Explanation:: This message contains the additional information reported by the printer for the exception you have just received. This message is recorded for your information only.
System action:: The host PSF gathers the additional exception information and writes it to the error log and job message log.
User response:: This is an informational message; no response is required.

0420-465

ERROR: The actual destination reported a paper-width check; adjust or change the actual destination medium.

Explanation:: The actual destination specified in the accompanying message reported a paper width check error. The paper might be too wide, not wide enough, or not properly loaded in the actual destination.
System action:: After the paper problem is corrected, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-466

ERROR: The actual destination reported a paper jam; clear the jam.

Explanation:: One or more pages are jammed in the actual destination's paper path. Printing cannot continue until the paper jam is cleared.
System action:: After the paper jam is cleared, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-467

ERROR: A paper jam occurred in the actual destination while printing this job. The jam occurred at document page ____ of copy ____. Inspect the output to determine if it is complete and that all printed pages are acceptable.

Explanation:: Most actual destination paper jams can be cleared without the loss of pages in the job or any reduction in print quality. However, a paper jam can occasionally result in smeared toner on pages or lost pages. Printed output should be carefully inspected after a paper jam has occurred.
System action:: This is an informational message. The system action was defined in another error message about the paper jam.
User response:: Inspect the printed output, and determine if all pages are acceptable.

0420-468

ERROR: The actual destination is out of paper in an alternate bin; add paper.

Explanation:: The actual destination's alternate bin is empty.
System action:: After the alternate bin is filled with paper, InfoPrint Manager recovers and printing continues.
User response:: Add paper to the alternate bin of the actual destination.

0420-469

ERROR: The actual destination transport mechanism requires corrective action.

Explanation:

The term transport mechanism used in this message is actually a term that applies to the entire printer excluding the control unit and the MIC (Mechanism Interface Card). There are over 100 conditions in the printer that can generate the X'40E2..02' IPDS NACK that leads to this message. Imbedded in the 24 bytes of sense data in bytes 6 and 7 is the SRC (System Reference Code) that identifies the specific printer mechanism with the problem. However, the 24 bytes of sense data are not included in a PSF message in the actual destination error.log for these conditions because this is not labeled as an Error. To see the sense data, you need to run a trace of InfoPrint Manager with 'GROUP TO TRACE' of 'IPDS data' on the 'Error Log and Trace Options' panel in SMIT for InfoPrint Manager for AIX and using the MMC for InfoPrint Manager for Windows.

To use the MMC, complete these steps:

In the Debug menu, select Control Destination Tracing.
On the Select Destination dialog, select the actual destination associated with this message.
On the Control Tracing dialog, check Enable tracing, and under Trace Groups, select IPDS data.

System action:

After the transport problem is corrected, InfoPrint Manager recovers and printing continues.

User response:

Many of the device conditions covered by this message are self-correcting (such as, a tension arm adjustment), and therefore, the messages can be ignored. However, if the messages become chronic (for example a bad NIC that causes the printer to turn yellow in the InfoPrint Manager GUI), it may be necessary to view the Error Log on the Continuous Forms printer to determine the specific cause of this message. At the printer console, select the Maintenance button at the top center of the screen, and then select the Logs button on the lower left of the screen. This displays an Error Log button just to the right of the Logs button. Select the Error Log button to list problems with a date and time stamp. Compare the date and time stamps listed with the date and time stamps for this message in your actual destination's error.log file to identify the mechanism problem and follow the instructions in the documentation for the actual destination. Correct the problem if possible; otherwise contact your service representative if necessary.

0420-470

ERROR: The actual destination fuser requires corrective action.

Explanation:: The actual destination fuser requires corrective action. Please correct the actual destination fuser.
System action:: After the problem is corrected, InfoPrint Manager will recover from the point of the error, and printing will continue normally.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-471

ERROR: The actual destination reported a paper specification error.

Explanation:: The actual destination has reported a mismatch between the actual print medium in the drawer and the type of print medium specified for that drawer either from the actual destination operator panel or switches in the drawer.
System action:: After the mismatch is corrected, InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-472

ERROR: The actual destination reported a channel-command-parity error.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-473

ERROR: The actual destination reported a channel-data-parity error.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-474

ERROR: The actual destination reported a channel adapter check.

Explanation:: This is a hardware error that requires corrective service before printing is possible.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-475

ERROR: The actual destination reported a problem with a two-channel switch adapter.

Explanation:: This is a hardware error. Printing cannot continue until the problem is corrected.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-476

ERROR: The actual destination reported a recoverable hardware error.

Explanation:: The actual destination notified InfoPrint Manager that an actual destination hardware error from which the actual destination could recover occurred.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: Multiple occurrences of this message could indicate that a hardware problem requiring service exists. If this error has occurred a multiple number of times, use local problem-reporting procedures to report this message.

0420-477

ERROR: The actual destination reported a hardware error that could not be automatically corrected.

Explanation:: This is a hardware error that requires corrective service before printing is possible.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use local problem-reporting procedures to report this message.

0420-478

ERROR: The actual destination reported a character that was not defined in the code page.

Explanation:: Either the code page did not include a code point for a character contained in the print job or the character assigned to the code point did not exist in the font character set. In either case, InfoPrint Manager attempted to use the Default Graphic Character specified in the Code Page Control (CPC) structured field, but the Flag parameter in the CPC structured field defined the default character as not valid. When the job containing this error was sent, either the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel was set to All or Invalid Character, or the DATACK keyword value submitted with the enq -o command was set to UNBLOCK or BLKPOS. The undefined character could be in presentation text, bar code data, bar code HRI or graphics character string data.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
Note: Depending on the point at which the error occurred, InfoPrint Manager might have printed part of the page that caused the error.
User response:: Check that the code point for the character in the print job is correct. If the code point is correct, correct the error in the code page, and send the print job again. If the output is acceptable without the missing character, send the print job again, and specify that errors for undefined characters are not to be reported. To suppress the errors, either set the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel to None or Positioning, or set the DATACK keyword value entered with the enq -o command to BLOCK or BLKCHAR.

0420-479

ERROR: The actual destination reported a recoverable printing overrun error.

Explanation:: The actual destination reported a printing overrun error while attempting to position image or text on a page.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: This is an informational message; no response is required.

0420-480

ERROR: The magnet settings were changed during printing.

Explanation:: A recoverable change in actual destination magnets occurred during printing. A retransmission of pages is required to correct this.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: This is an informational message; no response is required.

0420-481

ERROR: The actual destination reported a recoverable serializer-parity error.

Explanation:: The actual destination reported a serializer-parity error from which it could recover by transmitting certain pages again.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: This is an informational message; no response is required.

0420-482

ERROR: The actual destination reported a recoverable image-generator error.

Explanation:: The actual destination reported an image-generator error from which it could recover.
System action:: InfoPrint Manager recovers from the point of the error, and printing continues.
User response:: This is an informational message; no response is required.

0420-483

ERROR: The actual destination reported a double-byte font section that is not loaded or a double-byte font section ID that is not valid.

Explanation:: Either a double-byte coded font section specified in a Write Text (WT) command is not loaded or a double-byte coded font section ID in the command is not valid. Certain restrictions apply if the double-byte character code information spans WT commands. See the 'IPDS Reference' for more information about these restrictions. Bytes 16-17 of the exception shown in a previous message (0420-249) should contain the font section (byte 16) and code point (byte 17) that caused the error. Some older IPDS printers do not include this code point in the sense data and place X'0000' in this field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-484

ERROR: The actual destination reported a numeric-representation precision-check error.

Explanation:: A print position cannot be represented within the actual destination.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-485

ERROR: The actual destination reported that an attempt was made to print outside of the valid printable area.

Explanation:: An attempt was made to print outside of the valid printable area. This area is the intersection (common space) of the physical page with the logical page or of the physical page with an overlay. One or more characters, rules, or images fall at least partially outside of the valid printable area. When the print job containing this error was sent, either the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel was set to All or Positioning, or the DATACK keyword value entered with the enq -o command was set to UNBLOCK or BLKCHAR.
System action:: First, InfoPrint Manager prints a print-error marker at the location on the page where the error was detected. Then InfoPrint Manager stops processing the page containing the error. Printing continues with the next page in the print job.
User response:: Check that the correct form was loaded in the actual destination. If it was and if the printed output would be acceptable without the printer-error markers, send the print job again and specify that positioning errors are not to be reported. To suppress these types of errors, either set the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel to None or Invalid character, or specify DATACK=BLOCK or DATACK=BLKPOS at the command line with the enq -o command.
Note: To correct the source of the problem, check for other error messages, and see their system actions and responses.

0420-486

ERROR: The actual destination reported an IOCA self-defining field code that is either not valid or not supported.

Explanation:: The error occurred in an IOCA image. See the 'IOCA Reference' for further information on this field. Bytes 16-17 of the exception in the preceding 0420-249 message contain the IO-image self-defining field code that cause the error. For one-byte codes, byte 16 contains X'00' and byte 17 contains the code.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-487

ERROR: The actual destination reported an IOCA self-defining field length that is not valid.

Explanation:: The error occurred in an IOCA image. See the 'IOCA Reference' for further information on this field. Bytes 16-17 of the exception in the preceding 0420-249 message contain the IO-image self-defining field code that cause the error. For one-byte codes, byte 16 contains X'00' and byte 17 contains the code.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-488

ERROR: The actual destination reported an IOCA self-defining field value that is either not valid or not supported.

Explanation:: The error occurred in an IOCA image. See the 'IOCA Reference' for further information on this field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-489

ERROR: The actual destination reported an IOCA Begin Segment out-of-sequence error that is either not valid or not supported.

Explanation:: The IOCA Begin Segment command is out of sequence. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job, unless the error is in an overlay or data-object-resource. If the error is in an overlay or data-object-resource that must be downloaded, InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the image-data problem.

0420-490

ERROR: The actual destination reported an IOCA image End Segment out-of-sequence error that either is not valid or is not supported.

Explanation:: The IOCA End Segment command is out of sequence. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-509

ERROR: A Begin Medium Map (BMM) structured field with token name ____ cannot be found in form definition ____.

Explanation:: An Invoke Medium Map (IMM) structured field specified a certain medium map name, but no Begin Medium Map (BMM) structured field with a matching token name could be found in the current form definition. The medium map name or the token name in the Begin Medium Map structured field might have been misspelled. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager cancels the print job.
User response:: Check that the form definition you specify for the print job contains the medium map referenced by the print job. If it does not, either add the medium map to the form definition or change the name of the medium map referred to by the print job to match the name of a medium map present in the form definition.

0420-510

ERROR: A Medium Copy Count (MCC) structured field specified an MMC ID of X'____' but no MMC structured field with a matching ID was received.

Explanation:: Each Medium Copy Count (MCC) structured field repeating group contains an ID field that refers to a Medium Modification Control (MMC) structured field. If a nonzero ID appears in an MCC structured field repeating group, an MMC structured field with a matching ID must appear in the same medium map. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager cancels the print job.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-511

ERROR: The duplex specification in the Medium Map structured field is not valid. The number of repeating groups in the Medium Copy Count (MCC) structured field is ____. The MCC structured field must contain an even number of repeating groups.

Explanation:: When duplex is specified in a Medium Map structured field, the Medium Copy Count (MCC) structured field must contain an even number of repeating groups. Each odd-numbered repeating group applies to the front of a sheet, and each even-numbered repeating group applies to the back of a sheet. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager cancels the print job.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-513

ERROR: Two Medium Modification Control (MMC) structured fields contain the same ID X'____'. MMC IDs must be unique.

Explanation:: Each Medium Modification Control (MMC) structured field contains an ID field. These IDs must be unique across all MMC structured fields in a medium map. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager cancels the print job.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-514

ERROR: A Medium Modification Control (MMC) structured field specified an overlay local ID X'____', but this was not mapped to an overlay name in either the Document Environment Group or the current medium map.

Explanation:: A Medium Modification Control (MMC) structured field specified an overlay local ID that was not mapped by any Map Medium Overlay (MMO) structured field in the Document Environment Group or the current medium map. Any overlay local IDs specified in the MMC structured field must be mapped to an overlay name in an MMO structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the print job at the point of the error. If this is the only file in the print job, InfoPrint Manager cancels the job. If there are other files in this print job, InfoPrint Manager will begin processing and then issue this message for each of the other files in the job.
Note: It is important to correct this error when it first occurs to prevent InfoPrint Manager from processing and issuing this error for other print jobs in the print queue that use the form definition causing the problem.
User response:: Correct the structured field in the form definition and submit the print job again.

0420-515

ERROR: The actual destination cannot print duplex sheets from bin ____. The print job will be printed simplex.

Explanation:

Duplex was specified either in the medium map of the form definition or when the print job was sent and:

A specific bin number was specified, but the actual destination cannot print on both sides of the medium in that bin.
No bin number was specified, but the actual destination cannot print on both sides of the medium in any of the available bins.

In either case, InfoPrint Manager prints the job in functional duplex mode. This means that the job prints in simplex mode (single-sided), but that any modifications intended for the front side of each sheet are applied to the odd-numbered pages, and any modifications intended for the back side of each sheet are applied to the even numbered pages. Thus each individual page prints correctly. This message is not issued in all cases where InfoPrint Manager performs functional duplexing. It is issued only if the actual destination is capable of duplexing, but reports that it cannot print duplexed sheets from the requested bin.

System action:

InfoPrint Manager processes the print request and prints the job on single-sided pages.

User response:

If duplexing is required, send the print job to an actual destination that supports duplexing, and specify the appropriate bin on that actual destination.

0420-535

ERROR: One or more ____ objects were encountered. The actual destination does not support this type of object.

Explanation:: The print job contains a Bar Code, Graphics, Presentation Text or IO Image (bitmap) object. The actual destination does not support this type of object. If the object is an IO Image object, InfoPrint Manager attempted to convert it to an IM Image, but it cannot be converted.
System action:: Depending on the type of object causing the error, the setting of either the Report errors in BAR CODE data field or the Report errors in IMAGE and GRAPHICS data field on the InfoPrint Manager SMIT Error Handling Options panel determines the system action. If the field setting is Yes, InfoPrint Manager stops processing the file containing the object causing the error. If the field setting is No, InfoPrint Manager skips the object causing the error but prints all other information on that page. There is no Report errors in PTOCA with OEG data field on the InfoPrint Manager SMIT Error Handling Options panel, so InfoPrint Manager stops processing the file containing the PTOCA object causing the error.
User response:: Delete the object from the file, or send the file to an actual destination that can print the object. If you are printing PostScript data, try to print the file as IM uncompressed data. (To do this, use the -a IM1 flag with the ps2afp command, or select IM uncompressed on the 'Type of IMAGE DATA' field of the SMIT 'Submit an InfoPrint Manager Print Job' panel).

0420-576

ERROR: The current medium map specified Constant Forms Control for both sides of the duplex sheet, or for the front of the simplex sheet, when a Begin Page (BPG) structured field was received.

Explanation:: At the point where a Begin Page (BPG) structured field is received, the current medium map must not specify that only overlay data is to be printed. This means that if an Invoke Medium Map (IMM) structured field is used to specify a medium map with Constant Forms Control active for both sides of a duplex sheet, or for the front of a simplex sheet, then another IMM structured field must be issued before the next BPG structured field, so that the current medium map is one that allows input data to be printed on at least one side of the sheet. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Either change the Invoke Medium Map structured field so that constant forms are not enabled or include another Invoke Medium Map structured field.

0420-583

ERROR: The bin value of ____ specified for this print job is not valid.

Explanation:: Valid bin values are in the range of 1 to 255. The bin value was not within this range.
System action:: InfoPrint Manager ignores the specified value and uses the bin value contained in the form definition associated with the print job.
User response:: Check the printed output to determine if it is acceptable. If it is not acceptable and printing from a different bin is required, enter a valid value for the required bin number, and send the print job again.

0420-584

ERROR: The duplex value ____ specified for the print job is not valid.

Explanation:: The print profile contained a duplex value that was not valid. The value, if specified, must be Yes, No, or Tumble.
System action:: InfoPrint Manager ignores the duplex value specified and uses the default duplex value contained in the form definition used by the print job.
User response:: Check the printed output, and determine if it is acceptable. If it is not acceptable, specify a valid duplex value and submit the print job again.

0420-585

ERROR: All attempts to open resource ____ in file ____ were unsuccessful.

Explanation:: InfoPrint Manager cannot open the file specified in the message, which contains the indicated resource.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Check for other error messages that may be issued for this print job, and correct the problems identified by those messages. If you are using Color Management resources or Data Object resources with a resource access table, the table must be found in the same directory as the resource.

0420-586

ERROR: An Include Page Overlay (IPO) structured field specified an overlay name of ____, but this overlay was not mapped within the containing page or overlay.

Explanation:: An Include Page Overlay (IPO) structured field specified an overlay name that was not mapped by any Map Page Overlay (MPO) structured field in the Active Environment Group of the containing page or overlay. To include a page overlay with the IPO structured field, the containing page or overlay must be mapped with an MPO structured field in the Active Environment Group of the page or overlay. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-593

ERROR: This print job cannot continue because of an internal error in InfoPrint Manager.

Explanation:: InfoPrint Manager found an internal logic error and cannot continue processing the print job.
System action:: InfoPrint Manager ends this InfoPrint Manager instance. Printing resumes with the next print job on the print queue.
User response:: Use local problem-reporting procedures to report this message.

0420-606

ERROR: The character set ____ does not support the character rotation X'____'.

Explanation:: A specific character set and character rotation were specified, but the character set does not contain a Font Orientation (FNO) structured field repeating group for that rotation. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-608

ERROR: Text control code X'____' is not valid. Text control ID X'____'.

Explanation:: While attempting to convert text from one L-unit base to another, InfoPrint Manager encountered an AFP data stream text control code that is not valid. A block of text might be missing from the printed output.
System action:: InfoPrint Manager ignores the block of text that is not correct and continues processing the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-609

ERROR: Text control length X'____' is not valid. Text control ID X'____'.

Explanation:: While attempting to convert text from one L-unit base to another, InfoPrint Manager encountered an AFP data stream text control that was too long or too short. A block of text might be missing from the printed output.
System action:: InfoPrint Manager ignores the block of text that is not correct and continues processing the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-610

ERROR: Text control parameter X'____' is not valid. Text control ID X'____'.

Explanation:: While attempting to convert text from one L-unit base to another, InfoPrint Manager encountered an AFP data stream text control parameter that is not valid. A block of text might be missing from the printed output.
System action:: InfoPrint Manager ignores the block of text that is not correct and continues processing the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-611

ERROR: A text control is not valid.

Explanation:: While attempting to convert text from one L-unit base to another, InfoPrint Manager encountered an AFP data stream text control that is not valid. This might be caused by an incomplete text control within the final Presentation Text Data (PTX) structured field. A block of text might be missing from the printed output. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-612

ERROR: Parameter X'____' is out of range for an L-unit conversion. Text control ID X'____'.

Explanation:: While attempting to convert text from one L-unit base to another, InfoPrint Manager encountered an AFP data stream text control parameter that has a valid value, but that is too large or too small to be converted to IPDS. A block of text might be missing from the printed output.
System action:: InfoPrint Manager ignores the block of text that is not correct and continues processing the print job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-613

ERROR: The text control is located at file offset ____, in the structured field with sequence number ____.

Explanation:: The previous message indicated that an error was encountered during an attempt to convert text from one L-unit base to another. This message provides information about the location of the error within the input file.
System action:: See the system actions for other error messages in this message group.
User response:: This is an informational message; no response is required.

0420-616

ERROR: The actual destination reported that an actual destination resource might have an error.

Explanation:: The actual destination detected the reported error within a resource at print time. Any print file that uses this resource will not print until the resource is corrected.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-622

ERROR: The actual destination reported that an IOCA Image Begin Image Content structured field was out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Begin Image Content structured field appeared out of sequence or appeared more than once. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-623

ERROR: The actual destination reported that an IOCA Image Data self-defining field was out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-624

ERROR: The actual destination reported that an IOCA Image End Image Content structured field was out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The End Image Content structured field appeared out of sequence or appeared more than once. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-625

ERROR: The actual destination reported an IOCA Image Size Parameter value and image data that are not consistent.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The value specified in the Image Size Parameter in an Image Picture Data (IPD) structured field did not match the horizontal and vertical size found in the image data. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-626

ERROR: The actual destination reported that an IOCA Image Size parameter is either missing or out of sequence in an Image Picture Data structured field.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Size Parameter image self-defining field is missing, appears out of sequence, or appears more than once. The Image Size Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-627

ERROR: The actual destination reported that an IOCA Image Size parameter value is either not supported or not valid.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Size Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-628

ERROR: The actual destination reported that an IOCA Image Size parameter and an Image Encoding parameter are not consistent.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Size Parameter image self-defining field and the Image Encoding Parameter image self-defining field are part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-629

ERROR: The actual destination reported that an IOCA Image Encoding parameter is out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Encoding Parameter image self-defining field appeared out of sequence or appeared more than once. The Image Encoding Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-630

ERROR: The actual destination reported that an IOCA Image Encoding parameter value is not supported or not valid.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Encoding Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field. You can also get this error when printing PostScript data with IOCA group 4 compression on an IBM 3812 or 3816 actual destination. These actual destinations do not support IOCA group 4 compression.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem. If you are printing PostScript data, try printing the file with IOCA-MMR compression instead. (To do this, use the -a IO1_MMR flag with the ps2afp command, or select IOCA-MMR compression at the 'Type of IMAGE DATA to produce' field of the 'Start an InfoPrint Manager Print Job' SMIT panel).

0420-631

ERROR: The actual destination reported that an IOCA Image Data Element Size parameter is out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Data Element Size Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-632

ERROR: The actual destination reported that an IOCA Image Data Element Size parameter value is not supported or not valid.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Data Element Size Parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-633

ERROR: The actual destination reported that an IOCA Image Look-Up Table ID parameter is out of sequence.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Look-Up Table ID parameter image self-defining field appeared out of sequence or appeared more than once. The Image Look-Up Table ID parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-634

ERROR: The actual destination reported that an IOCA Image Look-Up Table ID parameter value is not supported or not valid.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. The Image Look-Up Table ID parameter image self-defining field is part of the Image Picture Data (IPD) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-635

ERROR: The actual destination reported that an IOCA image has data that appears outside of the image presentation space.

Explanation:: The error occurred in an Image Object Content Architecture (IOCA) image. See the 'IOCA Reference' for further information about image presentation space.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-636

ERROR: The actual destination reported a Channel Overrun error.

Explanation:: The actual destination reported a Channel Overrun error.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-637

ERROR: The actual destination reported a GOCA object with a graphics order that is either not allocated or not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-638

ERROR: The actual destination reported a GOCA object with a reserved-byte exception or an attribute set that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-639

ERROR: The actual destination reported a GOCA object with a drawing-order length that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-640

ERROR: The actual destination reported a GOCA object with an attribute value that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-641

ERROR: The actual destination reported a GOCA object with a Truncated Order exception condition.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-642

ERROR: The actual destination reported a GOCA object with a segment prolog exception error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-643

ERROR: The actual destination reported a GOCA object with a virtual graphics presentation space overflow error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-644

ERROR: The actual destination reported a GOCA object with an attribute value that is not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-645

ERROR: The actual destination reported a GOCA object with a default that is either not valid or not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-646

ERROR: The actual destination reported a GOCA object with a Segment Characteristics drawing order that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-647

ERROR: The actual destination reported a GOCA object with a character angle value that is not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-648

ERROR: The actual destination reported a GOCA object with an end prolog that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-649

ERROR: The actual destination reported a GOCA object with an area bracket exception error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-650

ERROR: The actual destination reported a GOCA object with a begin area that was not received correctly.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-651

ERROR: The actual destination reported a GOCA object with an area truncation exception error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-652

ERROR: The actual destination reported a GOCA object supported order in an area that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-653

ERROR: The actual destination reported a GOCA object with a pattern symbol set that is not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-654

ERROR: The actual destination reported a GOCA object with a pattern symbol that is not defined.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-655

ERROR: The actual destination reported a GOCA object with a temporary-storage overflow while drawing an area.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-656

ERROR: The actual destination reported a GOCA object with a "begin segment introducer segment" flag that is not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-657

ERROR: The actual destination reported a GOCA object with a "begin segment introducer" flag that is not valid.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-658

ERROR: The actual destination reported a GOCA object whose "begin segment introducer" length is incorrect.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-659

ERROR: The actual destination reported a GOCA object with insufficient segment data.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-660

ERROR: The actual destination reported a GOCA object with a "graphics image order sequence exception" error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-661

ERROR: The actual destination reported a GOCA object with an image data discrepancy.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-662

ERROR: The actual destination reported a GOCA object with a graphics image bracket exception error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-663

ERROR: The actual destination reported a GOCA object with an incorrect number of Image Data drawing orders.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-664

ERROR: The actual destination reported a GOCA object with a marker symbol set that is not supported.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-665

ERROR: The actual destination reported a GOCA object with an undefined marker code.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-666

ERROR: The actual destination reported that a font is not available for a GOCA object.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-667

ERROR: The actual destination reported that a graphics character code is not defined for a GOCA object.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-668

ERROR: The actual destination reported a GOCA object with an arc drawing check error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-669

ERROR: The actual destination reported a GOCA object with a truncated graphics image exception error.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-670

ERROR: The actual destination reported a GOCA object with an order that is not valid in a graphics image.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-671

ERROR: The actual destination reported a GOCA object with an unsupported graphics image format.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-672

ERROR: The actual destination reported a GOCA object with a relative line outside of its coordinate space.

Explanation:: The error occurred in a Graphics Object Content Architecture (GOCA) image. See the 'GOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the graphics data problem.

0420-673

ERROR: The metric unit base X'____' in a Font Control (FNC) structured field is not valid.

Explanation:: The Metric Unit Base parameter in the Font Control (FNC) structured field must contain one of two values: X'0000', indicating fixed metrics, or X'0202', indicating relative metrics. An FNC structured field was encountered that contained a different value in this field. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-678

ERROR: The Metric Units per Unit Base value X'____' in a Font Control (FNC) structured field is not valid for a fixed-metric font character set.

Explanation:: The font character set is identified as fixed-metric by the Metric Unit Base field in the Font Control (FNC) structured field. A Metric Unit Base value of X'0000' indicates a fixed-metric font character set. A fixed-metric font character set must have the value X'09600960', indicating 240 pels per inch, or the value X'0BB80BB8', indicating 300 pels per inch. The Metric Units per Unit Base field in the FNC structured field contains a value that is not valid for a fixed-metric font character set. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-679

ERROR: The Metric Units per Unit Base value X'____' in a Font Control (FNC) structured field is not valid for a relative-metric font character set.

Explanation:: The font character set is identified as relative-metric by the Metric Unit Base field of the Font Control (FNC) structured field. A Metric Unit Base value of X'0202' indicates a relative-metric font character set. A relative-metric font character set must have the value X'03E803E8' in the Metric Units per Unit Base field. The Metric Units per Unit Base field in the FNC structured field contains a value that is not valid for a relative-metric font character set. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-680

ERROR: The Font Control (FNC) structured field length ____ is not valid for a relative-metric font character set.

Explanation:: The font character set is identified as relative metric by the Metric Unit Base field in the Font Control (FNC) structured field. A Metric Unit Base field of X'0202' indicates a relative-metric font. The FNC structured field within a relative-metric font character set must contain a Pattern Resolution Unit Base field in bytes 22-23 and a Pattern Resolution Units per Unit Base field in bytes 24-27. The length of the FNC parameter data must be at least 28 bytes. An FNC structured field within a relative-metric font character set was encountered with a length that is less than 28 bytes. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-681

ERROR: The Pattern Unit Base X'____' in a Font Control (FNC) structured field is not valid.

Explanation:: The Pattern Unit Base in the Font Control (FNC) structured field must contain X'0000'. An FNC structured field was encountered that contained a different value in this field. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-682

ERROR: InfoPrint Manager cannot print the file because of an internal error.

Explanation:

Portions of the InfoPrint Manager code are not communicating correctly with each other.

System action:

Depending on the problem that occurred:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing, starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
InfoPrint Manager ends the current InfoPrint Manager instance.

User response:

Depending on the system action there are two options:

Send the print job again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.
Use local problem-reporting procedures to report this message.

0420-683

ERROR: The font metric resolution X'____' does not match the font pattern resolution X'____' in the Font Control (FNC) structured field.

Explanation:: If a font character set contains metrics expressed in pels, then for the font to be used on a actual destination that supports only metrics expressed in pels, the font metric resolution in bytes 6-9 of the Font Control (FNC) structured field must match the font pattern resolution in bytes 24-27. The value in bytes 4-5 indicates whether the font metrics are expressed in pels or in relative units. If bytes 4-5 contain the value X'0000', then the font metrics are expressed in pels. If these bytes contain X'0202', then the font metrics are expressed in relative units. An FNC structured field was encountered that had different values for the font metric resolution and font pattern resolution. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-684

ERROR: The font pattern resolution X'____' in the Font Control (FNC) structured field does not match the actual destination font pattern resolution X'____'.

Explanation:: The font pattern resolution in bytes 24-27 of an Font Control (FNC) structured field must match the font pattern resolution of the actual destination. This font character set cannot be used on this actual destination. See the 'Advanced Function Printing: Host Font Data Stream Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Either change the font pattern resolution so that it matches the actual destination's resolution or send the print job to an actual destination that supports the character set specified in the structured field.

0420-694

ERROR: The Image Points field X'____' in the structured field ____ is not valid.

Explanation:: The Image Points per Unit Base field must contain a value in the range X'0001' - X'7FFF'. The structured field specified in the message contains a different value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the reported problem.

0420-695

ERROR: The Image Size field ____ in the structured field ____ is not valid.

Explanation:: The Image Size field must contain a value in the range 1 through 32,767. The structured field specified in the message contains a different value. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the reported problem.

0420-698

ERROR: An error occurred during communications with the Print Service Adapter Device Driver. Error code ____.

Explanation:: InfoPrint Manager ends this InfoPrint Manager instance.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-699

ERROR: InfoPrint Manager cannot communicate with the Print Service Adapter Device Driver. Error code ____.

Explanation:: InfoPrint Manager is unable to open communication with the Print Service Adapter Device Driver. The Print Service Adapter Device Driver may not be loaded.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Make sure the following line is in the CONFIG.SYS file: DEVICE=pathAIN1VDD.SYS where path is the fully qualified path name where the Print Service Adapter Device Driver is stored.

0420-700

ERROR: No Print Service Adapter adapter was found in slot ____.

Explanation:: InfoPrint Manager is not able to find a Print Service Adapter in the specified slot number.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use the PSF/AIX Printer Colon File to set the Print Service Adapter slot number correctly.

0420-707

ERROR: One of the InfoPrint Manager user-exit programs produced a page that contains an error. Check the error log for this actual destination.

Explanation:: The Header, Trailer, Separator, Audit, or Accounting auxiliary-sheets produced a page that had an error. InfoPrint Manager cannot print the page. The auxiliary-sheet might have referred to a resource (font, overlay, data-object-resource or page segment) that cannot be found in InfoPrint Manager's resource path or a form definition might have been specified as an actual destination attribute for the user-exit program that InfoPrint Manager cannot locate. Another cause might be that the auxiliary-sheet produced a print data stream that is not valid.
System action:: InfoPrint Manager stops processing the page containing the error.
User response:: For more information about the problem, see the error log for the actual destination, by default /var/psf/printername/error.log (where printername is the actual destination name specified when the actual destination was created). Resource paths can be checked by viewing the PSFPATH environment variable. You can also check that the resource exists in the /usr/lpp/psf/reslib directory and, if the resource is a form definition, that the resource name was spelled correctly.

0420-729

The error occurred in file ____. The structured field in error was structured field ____ with code ____ and sequence number ____ located at file offset ____.

Explanation:

This message identifies the structured field that caused a previous error message. The information provided includes:

The name of the file being printed.
If you entered the enq -o command (or its InfoPrint Manager SMIT equivalent) from a machine other than the machine on which InfoPrint Manager is installed or piped input to the enq command, this file name is assigned by enq. Otherwise, this is the name of the file as you know it or the job name that you entered when the print job was sent.
The acronym used to refer to the structured field; for example: IOC for the Image Output Control structured field.
The 3-byte hexadecimal code by which InfoPrint Manager identifies the structured field; for example: X'D3A77B' for the Image Output Control structured field.
The 2-byte sequence number of the structured field. All structured fields contain a 2-byte sequence number in bytes 6 and 7 of the structured-field introducer.
The offset within the input file at which the first byte of the structured field appears.
Note: The offset starts at zero. See the 'MO:DCA Reference' for further information on this structured field.

System action:

See the system actions for other error messages in this message group.

User response:

See the responses for other error messages in this message group.

0420-742

The actual destination reported that an IOCA image's Data Element Size parameter and Encoding parameter were inconsistent.

Explanation:: The value of the Image Data Element Size parameter is not consistent with the IOCA image compression algorithm specified in the Image Encoding parameter. See the 'IOCA Reference' for a description of these parameters.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the reported problem.

0420-743

The actual destination reported a bar-code type that is either not valid or not supported.

Explanation:: The actual destination does not support the bar code specified in the print job.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Print the bar code on an actual destination that supports bar codes.

0420-744

The actual destination reported a bar-code object with a font identifier that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the reported problem.

0420-745

The actual destination reported a bar-code object with a color that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-746

The actual destination reported a bar-code object with a module width that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-747

The actual destination reported a bar-code object with an element height that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-748

The actual destination reported a bar-code object with a height multiplier that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-749

The actual destination reported a bar-code object with a wide-to-narrow ratio that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-750

The actual destination reported a bar-code object with a symbol origin that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-751

The actual destination reported a bar-code object with a modifier that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-752

The actual destination reported a bar-code object with a data length that is either not valid or not supported.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-753

The actual destination reported a check-digit calculation problem in a bar-code object.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-754

The actual destination reported an attempt to position a bar-code object outside of the bar-code block or valid printable area.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-755

The actual destination reported an attempt to position a symbol outside of the bar-code block asynchronously.

Explanation:: The error occurred in a Bar Code Object Content Architecture object. See the 'BCOCA Reference'.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the error in the bar code object.

0420-756

The actual destination reported a Relative Move Inline (RMI) text control that is either not valid or not supported.

Explanation:: The Inline Print Position Move parameter value in the Relative Move Inline (RMI) text control is not valid. The text-control sequence is located in a Presentation Text (PTX) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-757

The actual destination reported a Relative Move Baseline (RMB) command that is either not valid or not supported.

Explanation:: The Baseline Print Position Move parameter value in the Relative Move Baseline (RMB) text control is not valid. The text-control sequence is located in a Presentation Text (PTX) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-758

The actual destination reported a rule length that is either not valid or not supported.

Explanation:: The Length parameter value in the Draw Inline Rule (DIR) text control is outside of the valid range. The text-control sequence is located in a Presentation Text (PTX) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-759

The actual destination reported a Temporary Baseline Move (TBM) text control sequence that is either not valid or not supported.

Explanation:: The Temporary Baseline Move (TBM) text control has a value that is not valid for the direction parameter, the precision parameter, or both parameters. The text-control sequence is located in a Presentation Text (PTX) structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-777

The print job contains an image that is too large for the printable area of the page.

Explanation:: Either the file contains an image that is too large to fit on the page or the page presentation specified in the form definition caused a printable area dimension that is too small for the image. InfoPrint Manager displays this message only when the value of the STOP when errors found in IMAGE and GRAPHICS data? field on the InfoPrint Manager SMIT Error Handling Options panel is Yes.
System action:: The output produced will vary based on the type of actual destination and setting of the data check keyword. Data check can be specified with the DATACK keyword at the command line or with the Type of print data errors to report on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel. Some actual destinations will produce no output when this error occurs, while others will print the portion of the image that fits on the page.
User response:: Change the value of the STOP when errors found in IMAGE and GRAPHICS data? field on the InfoPrint Manager SMIT Error Handling Options panel to No, and send the print job again. InfoPrint Manager will print as much of the image as possible. Check that the page presentation (portrait or landscape) specified in the form definition is correct. If it is, you may need to scale or trim the image so that it fits in the printable area of the page.

0420-781

ERROR: The actual destination reported a Load Page Descriptor command or a Write Text Control command initial inline coordinate that is either not valid or not supported.

Explanation:: An initial inline coordinate value in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for a description of the Load Page Descriptor and a Write Text Control commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-782

ERROR: The actual destination reported a Load Page Descriptor command or a Write Text Control command initial baseline coordinate that is either not valid or not supported.

Explanation:: An initial baseline coordinate value in a Load Page Descriptor command or in a Write Text Control command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for a description of the Load Page Descriptor and Write Text Control commands.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the reported problem.

0420-783

ERROR: The actual destination reported an Execute Order Homestate Set Media Size command contained an L-units value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-784

ERROR: The actual destination reported an Execute Order Homestate Set Media Size command contained an x-extent value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-785

ERROR: The actual destination reported an Execute Order Homestate Set Media Size command contained a y-extent value that is either not valid or not supported.

Explanation:: A form length value specified in this job is outside of the allowable range for the actual destination.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Change the form-length-range-supported attribute value to reflect the appropriate allowable range for the actual destination. Ensure that the form-length value specified in the job or command line lies within this range.

0420-786

ERROR: The actual destination reported an Execute Order Homestate Set Media Size command contained a unit base value that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-787

ERROR: The actual destination reported that a double-byte font has one section specified for MICR printing, but not all sections.

Explanation:: All the sections of a double-byte font must be marked consistently for MICR printing to occur.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Specify all sections of the double-byte font for MICR printing.

0420-788

ERROR: The actual destination reported that MICR printing has been disabled.

Explanation:: The actual destination attachment for MICR (magnetic ink character recognition) printing might have been disconnected.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
Note: Printed output will be in non-MICR form.
User response:: Send the print job to a different MICR actual destination, or correct the problem with this MICR actual destination.

0420-789

The actual destination reported that MICR printing is now available.

Explanation:: A previously reported actual destination error has been corrected.
System action:: InfoPrint Manager recovers and printing continues.
User response:: This is an informational message; no response is required.

0420-790

ERROR: The MICR actual destination reported a paper jam; clear the jam.

Explanation:: The MICR (magnetic ink character recognition) actual destination, or its attachment, has one or more pages jammed in the paper path. Printing cannot continue until the paper jam is cleared.
System action:: After the paper jam is cleared, InfoPrint Manager recovers and printing continues.
User response:: Follow the actual destination or actual destination attachment instructions to clear the paper jam.

0420-791

ERROR: The MICR actual destination reported that printing outside of the page boundaries has occurred.

Explanation:: The MICR (magnetic ink character recognition) actual destination, or its attachment, reported data that printed outside of the page boundaries. The pages might not be aligned properly.
System action:: After the error condition is corrected at the actual destination, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-794

ERROR: The actual destination reported a Select Input Media Source command that selected a medium which is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-795

ERROR: The actual destination reported a use of the Acknowledgement Continuation flag which is not valid.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-796

The actual destination reported an IOCA image decompression error.

Explanation:: The error occurred in an Image Object Content Architecture image. See the 'IOCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the image-data problem.

0420-797

ERROR: The actual destination reported a Load Font Equivalence GRID value that is either not valid or not supported.

Explanation:: A GRID value in a Load Font Equivalence command is either not valid or not supported by the actual destination. See the 'IPDS Reference' for a description of the LFE command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Examine the page in error to determine if the error was caused by the page or by a resource that is used on the page. If the error occurred in a resource that does not belong to you, contact the person who administers your system or the owner of the resource, and have the error corrected.

0420-798

ERROR: The actual destination reported that a Load Font Control (LFC) command contained a relative-metric multiplying factor that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-800

ERROR: This print file requires double-byte fonts. Double-byte fonts are not supported by the actual destination.

Explanation:: The file contains a character or characters that require a double-byte font (for example, an Arabic, Korean, or Japanese font). However, the actual destination selected for the print job cannot print double-byte fonts.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again, and specify an actual destination that supports double-byte fonts.

0420-803

ERROR: The specified character set is required to be in ____ pels-per-inch resolution. This character set, in this resolution, cannot be located in the InfoPrint Manager resource directories. A version of this character set might exist in the ____ pels-per-inch resolution, but it cannot be used with this type of actual destination.

Explanation:: The requested font character set, at the resolution required by the actual destination, cannot be located in the InfoPrint Manager resource directories. Someone might have moved or deleted the character set. The resource search path specified might not be correct.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Check that the font character set exists in the resource directories (by default, /usr/lpp/psf/reslib), and that the owner, group, and others have permission to read it. Check that the resource search paths are correct. The resource path can be specified with the PSFPATH environment variable. Use the AIX env command to view the settings of the environment variables. When specifying multiple paths, separate the paths with colons. If necessary, add the required font character set to the InfoPrint Manager resource directories in the correct resolution for the actual destination.

0420-836

InfoPrint Manager cannot continue processing the DPF job because a file access error occurred.

Explanation:: A control file for this Distributed Print Facility (DPF) job cannot be accessed. The DPF file is required to successfully continue processing the job.
System action:: InfoPrint Manager stops processing the job when the error is detected and cancels the job.
User response:: Report the problem to your local system administrator who might need to contact your service representative.

0420-837

ERROR: The actual destination reported that a Define Group Boundary command was received that attempts to terminate a group that is not yet initiated.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-838

ERROR: The actual destination reported a Define Group Boundary command order that is either not valid or not supported.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-839

ERROR: The actual destination reported that a Define Group Boundary command was received that had an incorrect length.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-840

ERROR: The actual destination reported an IPDS command was received that had an incorrect number of data bytes.

Explanation:: The actual destination reported either the number of data bytes specified in an IPDS triplet length field is greater than the number of bytes remaining in the IPDS command or the number of data bytes specified in a triplet length field is different from the number of bytes in the Resource ID field of an IPDS XOA-RRL command. This message could be issued as a result of corrupted print data, an actual destination internal microcode error or an InfoPrint Manager internal logic error.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0420-842

ERROR: There is not enough memory to convert an image into a form that can be printed.

Explanation:: There is not enough memory available to convert an image in IM format to an image in Image Object Content Architecture (IOCA) format (IO1). The conversion is required for this actual destination to print the original image at the proper size.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the AIX ps command to view a list of processes, and then use the AIX kill command to stop any unneeded processes. Send the print job again. If the error still occurs, increase the system paging space (the AIX lsps -a command lists the current usage of paging space).

0420-846

The font in error consists of the code page ____ and the font character set ____.

Explanation:: This message provides more information about the code page and character set causing the font problem.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0420-847

InfoPrint Manager cannot convert an IM image object to IPDS IO image format for printing.

Explanation:: InfoPrint Manager tried to convert an IM image object to IO format in order to print the image. The image could not be converted, because (1) The X or Y image size specified in Image Input Descriptor structured field is zero, or (2) the image is positioned and rotated so that no part of the image fits on the valid printable area of the media.
System action:: InfoPrint Manager does not print the image.
User response:: Verify that the image position and rotation are specified correctly. If possible, correct the image object, and submit the print job again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0420-851

The actual destination requires operator intervention.

Explanation:: A condition has occurred at the actual destination that requires operator action to correct.
System action:: After the actual destination problem is corrected, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0420-870

Because of an error reported below, InfoPrint Manager cannot process the double-byte font whose first section is made up of the code page ____ and the font character set ____.

Explanation:: InfoPrint Manager detected an error that prevented processing of the double-byte font specified in the message.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: See the responses for other error messages in this message group.

0420-873

ERROR: The Font Control (FNC) structured field in double-byte font section X'____' specifies a character box size that is not uniform. Double-byte font sections X'45'-X'FE' must have a uniform character box size.

Explanation:: If a Font Control (FNC) structured field exists within a double-byte font section with a section number greater than X'44', then the FNC structured field must specify a uniform character box size. Double-byte font sections X'41'-X'44' can have box sizes that are not uniform, but any sections with section numbers in the range of X'45'-X'FE' must have a uniform character box size. FNC byte 6, bit 3 specifies that a font character set has a uniform character box size. See the 'FOCA Reference' for further information on the FNC structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the font character set and send the job again.

0420-877

ERROR: There is no ____ structured field to match the ____ structured field with token name ____ at file offset ____.

Explanation:: A file contained a Begin structured field to mark the beginning of an object, but did not contain the matching structured field to mark the end of the object. If the Begin structured field is present, the End structured field must also be present. See the 'Mixed Object Document Content Architecture Reference' for further information on these structured fields.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the reported problem.

0420-878

ERROR: InfoPrint Manager cannot continue processing this print job: The STOP when errors found in IMAGE or GRAPHICS data field on the InfoPrint Manager SMIT Error Handling Options panel is set to Yes.

Explanation:

The handling of certain errors depends on the setting of the STOP when errors found in IMAGE and GRAPHICS data? field on the InfoPrint Manager SMIT Error Handling Options panel. Depending on the setting:

If a soft page segment cannot be located in the InfoPrint Manager resource library, then processing continues if the field setting is No; processing stops if the setting is Yes. A page segment is considered a soft page segment if it is specified only through the Include Page Segment (IPS) structured field, and not through the Map Page Segment (MPS) structured field. Page segments specified through the MPS structured field are considered hard page segments.
If the print job contains GOCA or IOCA data and the actual destination does not support that data type, processing of the job continues if the field setting is No. Processing stops if the setting is Yes.
If a GOCA object contains a Map Coded Font (format 1 MCF-1 or format 2 MCF-2) structured field, syntax errors in that structured field are handled according to the field setting. If the setting is No, InfoPrint Manager ignores syntax errors in an MCF-1 or MCF-2 structured field of a GOCA object and continues processing the print job. If the setting is Yes, InfoPrint Manager stops processing the print job when the same types of syntax errors are encountered.

Secondary resource errors are not under control of this setting.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

See the responses for other error messages in this message group.

0420-879

InfoPrint continues processing the print job: The STOP when errors found in IMAGE and GRAPHICS can be set if desired. Please contact support for instructions on your platform.

Explanation:

The handling of certain errors depends on the setting of the STOP when errors found in IMAGE and GRAPHICS data? field on the InfoPrint Manager SMIT Error Handling Options panel. Depending on the setting:

If a soft page segment cannot be located in the InfoPrint Manager resource library, then processing continues if the field setting is No, but processing stops if the setting is Yes. A page segment is considered soft if it is specified only through the Include Page Segment (IPS) structured field, and not through the Map Page Segment (MPS) structured field. Page segments specified through the MPS structured field are considered hard page segments.
If the print job contains GOCA or IOCA data and the actual destination does not support that data type, processing of the job continues if the field setting is No. Processing stops if the setting is Yes.
If a GOCA object contains a Map Coded Font (format 1 MCF-1 or format 2 MCF-2) structured field, syntax errors in that structured field are handled according to the field setting. If the setting is No, InfoPrint Manager ignores syntax errors in an MCF-1 or MCF-2 structured field of a GOCA object and continues processing the print job. If the setting is Yes, InfoPrint Manager stops processing the print job when the same types of syntax errors are encountered.

Secondary resource errors are not under control of this setting.

System action:

InfoPrint Manager continues processing the print job.

User response:

See the responses for other error messages in this message group.

0420-880

ERROR: There is no End structured field to match the Begin structured field X'____' at file offset ____.

Explanation:: InfoPrint Manager found a structured field that begins an AFP data stream object. Begin structured fields contain the value X'A8' in the second byte. When InfoPrint Manager finds a Begin structured field that it does not recognize, it attempts to skip the unrecognized object by finding the matching End structured field. End structured fields contain the value X'A9' as the second byte of the structured-field code, with the third byte being the same as that of the Begin structured field. InfoPrint Manager could not find an End structured field to match an unrecognized Begin structured field. See the 'MO:DCA Reference' for further information on these structured fields.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If an application other than InfoPrint Manager produced the AFP data stream, contact the author of that application. Otherwise, use local problem-reporting procedures to report this message.

0420-882

ERROR: The Image Output Control (IOC) orientation X'____' is not valid.

Explanation:

Valid orientation values for the Image Output Control (IOC) structured field are:

X'0000 2D00' (0, 90 degrees)
X'2D00 5A00' (90, 180 degrees)
X'5A00 8700' (180, 270 degrees)
X'8700 0000' (270, 0 degrees)

The IOC orientation value is not valid. See the 'MO:DCA Reference' for further information on this structured field.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0420-885

InfoPrint Manager is establishing communications with ____.

Explanation:: InfoPrint Manager establishes communications with the actual destination specified in the message.
System action:: InfoPrint Manager writes this message to the error log.
User response:: This is an informational message; no response is required.

0420-886

The PCL Secondary UFST configuration directory was not found.

Explanation:: The initialization process failed during the configuration portion of the Universal Font Scaling Technology (UFST) application.
System action:: Verify if the directory exists. Reinstall the product if necessary.
User response:: Contact your support representative.

0420-887

The PCL Secondary process failed to initialize.

Explanation:: The initialization process failed during the configuration portion of the Universal Font Scaling Technology (UFST) application.
System action:: The process failed.
User response:: Contact your support representative.

0421-001

This DPF print job specifies a MICR font but the actual destination does not support MICR fonts.

Explanation:: InfoPrint Manager has detected that this DPF (Distributed Print Facility) job uses a MICR (Magnetic Ink Character Recognition) font. The actual destination either does not have MICR capability or the MICR processing unit is not active.
System action:: InfoPrint Manager stops processing the job when the error is detected and cancels the job.
User response:: Modify the print job so that it does not use MICR fonts, submit the print job to an actual destination which supports MICR fonts, or set the actual destination force-micr-font-print attribute to true (which will force the MICR font print on a non-MICR printer).

0421-010

The font inline sequence X'____' received from the host PSF is not valid.

0421-011

The host receiver ended the SNA communication session with the host system because the "Inactivity limit" was exceeded.

Explanation:: The 'Inactivity limit' configured for the host receiver was exceeded. The communication session with the host system ended.
System action:: The communication session ends.
User response:: If you want your host receiver's communication session to end when no jobs are being received from the host system, no response is necessary. If you would like the communication session to stay active even when jobs are not being received, change the host receiver's 'Inactivity limit' to 9999.

0421-012

The Load Resource Equivalence command entry X'____' received from the host PSF was not valid.

0421-013

The Request Resource List command entry X'____' received from the host PSF was not valid.

0421-014

There is not enough memory available for the DPF host receiver to initialize.

Explanation:: The Distributed Print Function (DPF) host receiver cannot obtain enough memory to begin processing.
System action:: The host receiver stops processing and is disconnected.
User response:: Report this error to your service representative. There might be a software error in DPF.

0421-015

A system error was detected while attempting to resize the file ____. The operatingsystem return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to resize a file. The SetFilePointer or SetEndOfFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there is insufficient space available on the disk. Ensure that the disk has sufficient space available then restart the host receiver. If the error persists, report it to your service representative.

0421-016

A system error was detected while attempting to move the read/write pointer of the file ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to move the read/write pointer of a file. The SetFilePointer call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: Report this error to your service representative.

0421-017

A Load Resource Equivalence command entry X'____' for a font index has been received, but the required font has not been activated, or is not in the DPF resource library.

0421-018

A resource table entry was not found for a request to delete a resource.

0421-019

A Load Equivalence command for page segment identifiers is not valid. The maximum number of page segment equivalences was exceeded. The number provided was ____.

0421-020

The host PSF requested that all previous resource-load requests be cleared. Some requests were discarded without processing.

0421-021

There are too many active IPDS resources.

0421-022

The DPF host receiver was not able to copy a file from ____ to ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to copy a file. The CopyFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there is insufficient space available on the disk or the disk permissions do not allow the host receiver to read or write the files specified. Ensure that the disk has sufficient space and the host receiver has permission to read and write the indicated files. Then restart the host receiver. If the error persists, report it to your service representative.

0421-023

The DPF host receiver deleted IPDS resources to make space available on drive ____.

0421-024

The acknowledgment reply generated by the DPF host receiver exceeds the maximum size. ____ is the number of bytes in the reply.

Explanation:: The Distributed Print Function (DPF) host receiver has built an IPDS acknowledgment that is longer than 256 bytes. Acknowledgments longer than 256 bytes can be generated for the Sense Type and Model (STM) command and for the Obtain Printer Characteristics (OPC) command. This message is issued when the acknowledgment was built for some command other than the STM or OPC.
System action:: The host receiver stops processing and is disconnected.
User response:: Report this error to your service representative. There might be a software error in the DPF host receiver.

0421-025

The DPF host receiver deleted fonts to make host-assigned IDs available.

0421-026

The Internet Protocol (IP) address ____ is not a valid dotted decimal address or host name address. InfoPrint Manager cannot connect to the actual destination.

Explanation:: You tried to submit a print job to a TCP/IP-connected actual destination. However, InfoPrint Manager could not find the address of this actual destination in the IP name server or the /etc/hosts file.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: On the pSeries where the print job was submitted, use the TCP/IP 'ping' command with the address to see whether the address is valid. If the address is valid, then there may be a problem with the TCP/IP network. If the address is not valid, the 'ping' command will not complete; ask your network administrator for the correct address. To change the default address for a TCP/IP-attached InfoPrint Manager destination, Select Show/Change Characteristics of a Printer, select Device Options, then choose a TCP/IP-attached destination from the list that displays. Change the Internet Address field on the TCP/IP-Attached Printer Device Options panel for that destination. You may also need to modify the address in the IP name server or the /etc/hosts file.

0421-027

The DPF host receiver attempted to assign a new receiver-assigned ID to a resource, but no ID was available.

Explanation:: There is no available receiver-assigned ID (RAID) for a resource. The Distributed Print Function (DPF) host receiver must assign a RAID to each resource that is sent from the host PSF.
System action:: While this message remains posted, the host receiver will periodically check to see if RAIDs have become free due to jobs being printed. If a RAID is freed, this message is cleared and processing continues, although this error will be encountered again quickly. Selecting RETRY also causes the host receiver to check to see if a RAID is free. If you select CANCEL, the host receiver stops processing and is disconnected. Then as jobs are printed, a large number of RAIDs can be freed.
User response:: Select CANCEL to stop the host receiver. Select EXIT from the spool pull-down of the DPF spool manager, to exit from DPF. Delete the DPF resources from the PSF/2 resource library. (These resources will be sent again from the host PSF if they are required by another print job). Then restart the spool manager.

0421-028

The DPF host receiver attempted to assign a new host-assigned ID to a font, but no ID was available.

Explanation:: There is no available host-assigned ID (HAID) for a font. The Distributed Print Function (DPF) host receiver must assign a HAID to each font that is sent from the host PSF.
System action:: While this message remains posted, the host receiver will periodically check to see if HAIDs have become free due to jobs being printed. If a HAID is freed, this message is cleared and processing continues. Selecting RETRY also causes the host receiver to check to see if a HAID is free. If you select CANCEL, the host receiver stops processing and is disconnected. Then as jobs are printed, a large number of HAIDs can be freed.
User response:: Select CANCEL to stop the host receiver. Select EXIT from the spool pull-down of the DPF spool manager, to exit from DPF. Delete the DPF resources from the PSF/2 resource library. (These resources will be sent again from the host PSF if they are required by another print job). Then restart the spool manager.

0421-029

The DPF host receiver attempted to assign a file name to a print job, but no file name was available.

Explanation:: There is no available file name to assign a print job. The Distributed Print Function (DPF) host receiver must assign a file name to each print job that is sent from the host PSF.
System action:: While this message remains posted, the host receiver will periodically check to see if file names have become free due to jobs being printed. If a file name is freed, this message is cleared and processing continues, although this error will be encountered again quickly. Selecting RETRY also causes the host receiver to check to see if a file name is free. If you select CANCEL, the host receiver stops processing and is disconnected. Then as jobs are printed, a large number of file names can be freed.
User response:: Select CANCEL to disconnect the host receiver from the host system. Then allow DPF to print jobs. As each job is printed, a file name will become available. After a large number (100 or greater) of jobs have been printed, restart the host receiver from the host PSF, using the appropriate command from your host system.

0421-030

The DPF host receiver deleted resources to make receiver-assigned IDs available.

0421-031

ERROR: The datastream transform '____' found an error while processing the print job.

Explanation:: An error has been reported by a transform set up for this device. The requested transformation cannot be performed.
System action:: ********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)
User response:: Consult the documentation for the named transform program. There may be an error log or other file generated by the transform which will aid in problem diagnosis. Correct the problem and submit the job again. NEED AIX EQUIVALENT FOR THE FOLLOWING: If the problem persists, delete the transform from the transform sequence in the PSF/AIX Printer Colon File. Select Change from the profile pull-down. Then select Transform Options to delete the transform sequence. Contact the author of the transform program for further assistance.

0421-033

A Load Font Equivalence command received from the host PSF contains a font inline sequence value X'____' that is not valid.

0421-034

The length of the IPDS command with command code X'D6____' is not valid.

0421-035

ERROR: The datastream transform '____' has reported a conversion error.

Explanation:: The transform program was not able to successfully complete the transformation of the print file.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Consult the documentation on the transform program to further diagnose the error. The transform may have produced an error log which will indicate the source of the problem. Correct the problem and submit the print job again. If the problem persists, try re-booting the system and submitting the job again. If the problem still persists, contact the author of the transform program.

0421-036

The Load Copy Control command, copy group entry X'____', received from the host PSF was not valid. The command contains both simplex and duplex copy groups.

0421-037

The host PSF did not properly identify the beginning of a print job.

0421-038

An option specified for a datastream transform program was in error. The transform has used a default value for the option.

Explanation:: At least one of the options specified in the Add Transform panel contained an error, and the transformation program used a default value for the option. The output may not be as expected.
System action:: The transformed file will be printed.
User response:: Refer to the documentation for the datastream transformation program and correct the option in the Add Transform panel. The Add Transform panel can be reached through the PSF/AIX Printer Colon File Options pulldown under Setup Transforms.

0421-040

A font member name ____ does not match the font index member name ____.

Explanation:: The resource library member name assigned to a font does not match the member name assigned to a font index.
System action:: The host receiver stops processing and is disconnected.
User response:: Report this error to your service representative. There might be a software error in DPF.

0421-041

The datatype ____ associated with this print job is not supported by this instance of InfoPrint Manager.

0421-042

A system error was detected while attempting to open the file ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to open a file. The CreateFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there is insufficient space available on the disk or the disk permissions do not allow the host receiver to read or write the files specified. Ensure that the disk has sufficient space and the host receiver has permission to read and write the indicated files. Then restart the host receiver. If the error persists, report it to your service representative.

0421-043

A system error was detected while attempting to read the file ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to read a file. The ReadFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there the disk permissions do not allow the host receiver to read the file specified. Ensure that the host receiver has permission to read the indicated file. Then restart the host receiver. If the error persists, report it to your service representative.

0421-044

A system error was detected while attempting to write the file ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to write to a file. The WriteFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there is insufficient space available on the disk or the disk permissions do not allow the host receiver to write the file specified. Ensure that the disk has sufficient space and the host receiver has permission to write the indicated file. Then restart the host receiver. If the error persists, report it to your service representative.

0421-045

A system error was detected while attempting to close the file ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to close a file. The CloseHandle call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: Report this error to your service representative. There might be a software error in DPF.

0421-046

A system error was detected while attempting to delete the file ____. The operating system return code is ____.

0421-047

A system error was detected while attempting to find the file ____. The operating system return code is ____.

0421-049

ERROR: A communications error occurred with the actual destination at address ____.

Explanation:

InfoPrint Manager can no longer communicate with the TCP/IP-attached destination. This could be a problem with the network hardware, the network software, the actual destination, or the actual destination's TCP/IP attachment.

System action:

InfoPrint Manager ends this InfoPrint Manager instance.

User response:

Check that this actual destination is powered on and that the actual destination's TCP/IP attachment is physically connected and enabled. Make sure that the Internet address and port number on the SMIT panel or GUI are correct. To test whether the actual destination will still accept a connection request, use the telnet command specifying both the IP address in the message and the printer IPDS port number (such as 5001 or 9100). The device must accept this telnet command in order for InfoPrint Manager to communicate with it through the IPDS protocol. For example, a successful connection looks like this:

telnet 9.17.82.238 5001
Trying...
Connected to 9.17.82.238
Escape character is '‸]'

Note: To end the telnet session, type exit at the prompt.

When the device rejects the connection request, it looks like this:

telnet 9.17.82.238 5001
Trying...
telnet:connect: A remote host refused an attempted
connection operation.

When a device refuses the connection, a problem exists with the physical device that requires the attention of your service representative or the OEM printer hardware support.

Due to the transient nature of network problems, using the telnet command as shown in these examples may not be able to determine the cause of this message. This message may be caused by a short-lived network device or printer hardware error that has been corrected by the time the telnet command is run.

It may become necessary to obtain a Network Trace along with concurrent software and hardware traces to identify where and why communications were interrupted. This means recreating the problem with tracing active. If appropriate, consult with your site network administrator to diagnose network problems.

0421-050

ERROR: The actual destination reported that an Activate Resource parameter value is not valid or is not supported.

Explanation:: InfoPrint Manager converted your print file to an IPDS datastream. However, InfoPrint Manager sent an IPDS Activate Resource value that is not valid or is not supported by the actual destination. The print file may be damaged. This error can occur if there are out of range values in a font.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again. If the error still occurs, use local problem-reporting procedures to report this message.

0421-065

ERROR: The actual destination reported that the Load Font Equivalence command Host-Assigned ID was already assigned.

Explanation:: InfoPrint Manager converted your print file to an IPDS datastream. InfoPrint Manager sent an IPDS Host-Assigned ID for a new font to the actual destination, but the actual destination reported that the ID had already been assigned to another font that was still active in the actual destination. The print file may be damaged.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job again. If the error still occurs, use local problem-reporting procedures to report this message.

0421-066

The DPF host receiver was not able to move the file ____ to ____. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to move a file. The CopyFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: This error may be received if there is insufficient space available on the disk or the disk permissions do not allow the host receiver to read or write the files specified. Ensure that the disk has sufficient space and the host receiver has permission to read and write the indicated files. Then restart the host receiver. If the error persists, report it to your service representative.

0421-071

The DPF host receiver was not able to completely write the file ____ because there is not enough disk space on drive ____.

Explanation:: The operating system reported that a disk is full.
System action:: If RETRY is selected, the host receiver attempts to write the file to the disk and continue processing. If CANCEL is selected, the host receiver stops processing and is disconnected.
User response:: Delete files to clear space on the disk. Then select RETRY to allow the host receiver to continue processing. Or if you wish to stop the host receiver, select CANCEL.

0421-072

The available resource IDs for this DPF job have been exceeded.

Explanation:: InfoPrint Manager cannot assign a printer resource ID to an IPDS resource required for this DPF (Distributed Print Facility) job. At least one page requires more than the maximum number of fonts, page segments, or overlays.
System action:: InfoPrint Manager stops processing the job when the error is detected and cancels the job.
User response:: Reduce the resource requirements for the page in error and then resubmit the job.

0421-075

The file ____ is missing or damaged. This file is required for DPF operation. The operating system return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver was not able to access a file. The CreateFile call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: Delete the host receiver. Create a new host receiver with the same configuration parameters as the original host receiver. If the error persists, report it to your service representative.

0421-078

The host receiver ____ has paused.

0421-112

A syntax error was detected in a DPF IPDS file at offset ____.

Explanation:: A syntax error was detected in an IPDS input file at the indicated offset.
System action:: InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.
User response:: Report the problem to your local system administrator who may need to contact your service representative.

0421-117

The destination detected an error in the IPDS resource ____. This resource was sent from a host PSF to DPF.

Explanation:: The destination detected an error in an IPDS resource. This resource was sent from a host PSF to Distributed Print Function (DPF). The message page includes other error messages identifying the error.
System action:: InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.
User response:: Report the problem to your local system administrator who may need to contact your service representative.

0421-118

The DPF file ____ is not valid.

Explanation:: A Distributed Print Function (DPF) system file is not valid. The file may have been damaged, truncated, or built incorrectly by the DPF Host Receiver.
System action:: InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.
User response:: Resubmit the job from the host PSF system to InfoPrint Manager. If the error still occurs, report the problem to your local system administrator who might need to contact your service representative.

0421-120

The host receiver is stopping due to an unrecoverable IPDS processing error.

0421-122

Due to a previous error, the DPF host receiver cannot obtain the printer characteristics.

Explanation:: Because of a previously reported error, the Distributed Print Function (DPF) host receiver did not communicate with the printer to obtain the printer characteristics.
System action:: The host receiver stops processing and is disconnected.
User response:: This message should be preceded by other messages, issued to the screen or to the error log. Check the response to those messages for help in correcting the problem.

0421-123

The DPF host receiver detected a configuration area access error. The host receiver return code is ____.

Explanation:: The Distributed Print Function (DPF) host receiver detected a configuration area access error. The RequestSemaphore call failed.
System action:: The host receiver stops processing and is disconnected.
User response:: Restart the host receiver. If the error persists, report it to your service representative.

0421-124

Printer backup information was recovered.

Explanation:: The Distributed Print Function (DPF) host receiver failed to obtain the printer characteristics. The host receiver was able to locate a copy of the printer characteristics saved from a previous session.
System action:: The host receiver stops processing and is disconnected.
User response:: If you wish for the host receiver to return a copy of the printer characteristics to the host PSF, then deselect OBTAIN PRINTER INFORMATION from the Receiver configuration in the InfoPrint Manager Management console. Then restart the host receiver and the host PSF.

0421-125

The host receiver could not locate printer backup information.

Explanation:: The Distributed Print Function (DPF) host receiver could not communicate with the printer and could not locate a copy of printer characteristics saved from a previous session.
System action:: The host receiver stops processing and is disconnected.
User response:: InfoPrint Manager should have reported an error that prevented communication with the printer. Respond to any previous error messages and correct any problems with the printer attachment. Then restart the host receiver.

0421-130

DPF could not obtain the printer characteristics.

Explanation:: The Distributed Print Function (DPF) host receiver could not communicate with the printer to obtain the printer characteristics.
System action:: The host receiver stops processing and is disconnected.
User response:: InfoPrint Manager should have reported an error that prevented communication with the printer. Respond to any other error messages and correct any problems with the printer attachment. Then restart the host receiver.

0421-131

The reported error occurred within a resource, ____, which was downloaded from the host. This resource is a private resource, and will have a different name on the host.

0421-149

ERROR: The datastream transform '____' has reported an error.

Explanation:: The named transformation program has encountered an error and has requested that the operator be notified.
System action:: ********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)
User response:: Consult the documentation on the transformation program. The program may have generated an error log or other file which will aid in problem diagnosis. Correct the problem and submit the print job again. NEED AIX EQUIVALENT FOR THE FOLLOWING: If the problem persists, delete the transform from the transform sequence in the PSF/AIX Printer Colon File. Select Change from the profile pull-down. Then select Transform Options to delete the transform sequence. Contact the author of the transform program for further assistance.

0421-150

ERROR: The datastream transform '____' has run out of disk space and could not complete the transformation of the print file.

Explanation:: The named transform could not complete transforming this print file because it ran out of disk space.
System action:: ********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)
User response:: Clear some disk space and submit the job again. If the problem persists, increase the total disk space available to the system and submit the job again.

0421-151

ERROR: The datastream transform '____' has run out of memory and could not complete the transformation of the print file.

Explanation:

The named transform program ran out of memory before it could complete the transformation of the print file.

System action:

********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)

User response:

Take one or more of the following actions:

Allow more space on disk for your OS/2 SWAPPER.DAT file
Stop some of the other programs you are running
Increase the total amount of memory available to the system

Then submit the job again.

0421-152

ERROR: The transform program ____ has reported an error put in the file ____.

Explanation:: The named transform program encountered an error while attempting to read the named input file.
System action:: ********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)
User response:: Ensure that the Spool file was not erased accidentally. Submit the job again. If the problem persists, consult the documentation for the transform program. NEED AIX EQUIVALENT FOR THE FOLLOWING: If the problem persists, delete the transform from the transform sequence in the PSF/AIX Printer Colon File. Select Change from the profile pull-down. Then select Transform Options to delete the transform sequence. Contact the author of the transform program for further assistance.

0421-153

ERROR: The transform program '____' has reported an error with the output file '____'.

Explanation:: The named transform program encountered an error while attempting to write to the named output file.
System action:: ********** NOT USED IN PSF ********** The print job is held in the print queue. Printing continues with the next job in the print queue. (THE NEXT JOB, OR THE NEXT FILE IN THE JOB?)
User response:: Ensure that there is adequate disk space for the output of the transformation. Submit the job again. If the problem persists, consult the documentation for the transform program. NEED AIX EQUIVALENT FOR THE FOLLOWING: If the problem persists, delete the transform from the transform sequence in the PSF/AIX Printer Colon File. Select Change from the profile pull-down. Then select Transform Options to delete the transform sequence. Contact the author of the transform program for further assistance.

0421-184

ERROR: An error occurred within the font resource, ____, which was downloaded from the host. This resource consists of host character set ____, and host code page ____.

Explanation:: This message follows other messages that describe an error in an IPDS font. The font was sent from a host PSF to the Distributed Print Function (DPF). The message inserts provide the name of the host code page and host font character set used to build the IPDS font.
System action:: This message is informational only.
User response:: The message page should describe the error in the font. The font in error must be fixed on the host system. Correct the error and submit the job again to the host PSF.

0421-185

ERROR: The reported error occurred within a resource, ____, which was downloaded from the host. This resource contains host resource ____.

Explanation:: This message follows other messages that describe an error in an IPDS page segment or overlay sent from a host PSF to the Distributed Print Function (DPF). The name of the host page segment or overlay is provided.
System action:: This message is informational only.
User response:: The message page should describe the error in the page segment or overlay. The resource in error must be fixed on the host system. Correct the error and submit the job again to the host PSF.

0421-190

The host receiver is stopping due to an unrecoverable resource library error. The host receiver return code is ____.

0421-192

The host receiver has requested printer characteristics.

0421-194

The Save Resources check box setting was changed.

0421-195

The double-byte font section number X'____' in the DPF file ____ is not valid. This section number appears at file offset ____ within the list of resources to be loaded for page ____.

Explanation:: The printer detected an error in an IPDS resource. This resource was sent from a host PSF to the Distributed Print Function (DPF). The message page includes other error messages identifying the error.
System action:: InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.
User response:: The message page should describe another error that prevented the resource from being loaded. The resource in error must be fixed on the host system. Correct the error and submit the job again on the host PSF system.

0421-210

ERROR: The transform exit '____' failed while processing this job.

Explanation:: The named transform exit failed while attempting to process this print job.
System action:: The job is held on the print queue. Printing continues with the next job in the queue.
User response:: Submit the print job again. If the error persists, there may be a logic error in the transform exit. Contact the author of the transform exit for further assistance.

0421-211

The job requires bin ____. This bin either does not exist or is disabled in the actual destination.

Explanation:

The job was sent from a host system to Distributed Print Facility (DPF). At the time the job was sent, the bin was available for the printer associated with the DPF target actual destination. However, prior to printing the job, either a different printer was associated with this actual destination or the indicated bin was disabled at the target actual destination.

System action:

InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.

User response:

In order to print the job you must do one of the following:

Send the job again from the host PSF when the printer is configured correctly.
Move the job to a printer for which the bin is available.
Enable the disabled bin and resubmit the job.

0421-212

The job requires duplexing. Duplexing is not supported by the printer, is not supported for bin ____, or is disabled.

Explanation:

The job has been sent from a host PSF system. At the time the job was sent, duplexing was enabled for the printer associated with the DPF target actual destination and supported for the bin. However, prior to printing the job, either a different printer was associated with the DPF spool or duplexing was disabled.

System action:

InfoPrint Manager stops processing the (DPF) Distributed Print Facility job when the error is detected and cancels the job.

User response:

In order to print the job you must do one of the following:

Send the job again from the host PSF when the printer is configured correctly.
Move the job to a printer for which duplexing with the required bin is available.
Enable duplexing at the printer and resubmit the job.

0423-001

ERROR: The information provided by the printer exceeds the PSF buffer. This information was truncated to fit the buffer.

Explanation:: This message is informational only.
System action:: This message is informational only.
User response:: This is an informational message; no response is required.

0423-002

ERROR: The path specified with the command ____ cannot include spaces.

Explanation:: Any search path associated with a command must be a string that has no spaces in it. This includes leading spaces before the path.
System action:: InfoPrint Manager cannot run the command.
User response:: Enter the command again, and supply a valid search path that does not contain spaces.

0423-003

psfctl is not a supported InfoPrint Manager command. Refer to the Using InfoPrint Manager for Production Printing or the InfoPrint Manager Reference Guide to determine the appropriate action.

0423-004

psfctl: This program must be run by the root system user or a user authorized by the InfoPrint Manager administrator.

Explanation:: You do not have the correct permissions to issue the psfctl command. Permission to issue the psfctl is available to users with root authority and to users defined in the AIX access control lists for the command. The InfoPrint Manager administrator determines the contents of the access control lists for each InfoPrint Manager actual destination. A separate access control list can be used for each flag on the psfctl command. For more information, see the InfoPrint Manager publications.
System action:: The psfctl program ends.
User response:: Login as the root system user (or other authorized user) or use the AIX su command to switch to an authorized user (which includes root) and repeat the command.

0423-005

The printer does not support triplet extender.

Explanation:: InfoPrint displays this message when the printer does not support a triplet extender.
A triplet extender is specified on the IOB or PPO structured field to extend FQN X'BE' triplet.
System action:: InfoPrint stops processing the file when the error occurs. InfoPrint cancels the print job.
User response:: Remove the SVG object container with all the secondary resources and resubmit the job. Otherwise, resubmit this print request to a printer that supports an SVG object container and triplet extender.

0423-006

The printer does not support the Object Container Presentation Space.

Explanation:: The Object Container Presentation Space Size triplet was specified for the SVG object in an IOB, CDD, or PPO structured field. The printer does not support the Object Container Presentation Space Size (X'9C') triplet for the SVG object.
System action:: InfoPrint stops processing the file when the error occurs. InfoPrint cancels the print job.
User response:: Remove the SVG object and resubmit the job. Otherwise, resubmit the print request to a printer that supports an SVG object container and a triplet extender.

0423-092

ERROR: The keyword in ____ is not valid. Valid keywords are: ACCOUNT, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, BIN, BUILDING, CODEPAGE, CDP, COPIES, DATACK, DATATYPE, DEPARTMENT, DISTRIBUTION, DOCNAME, DUPLEX, FONTFIDELITY, FONTRESOLUTION, FORMDEF, HEADER, JOBNAME, MSGCOUNT, NAME, NODEID, OUTBIN, OVERLAY, PASSTHRU, PROGRAMMER, RESPATH, RESUME, ROOM, SEPARATOR, SETUPFILE, SRCHFONTLIB, SFO, SRCHOVLYLLIB, SOV, SRCHPSEGLIB, SPS, SRCHSETUPFILE, SSF, TITLE, TRAILER, USERID, WRITER, XOFFSET, AND YOFFSET

Explanation:: The command entered uses a keyword=value pair (for example, bin=2). The keyword is not valid.
System action:: InfoPrint Manager cannot run the command.
User response:: Change the keyword that caused the error to one of the keywords specified in the message.

0423-093

ERROR: The value in ____ is too long. This value cannot exceed ____ characters.

Explanation:: The command entered uses a keyword=value pair (for example, bin=2). The value is too long. If the keyword is for a resource, such as a form definition, a path might have been specified with the form definition name causing the value to exceed the maximum length.
System action:: InfoPrint Manager cannot run the command.
User response:: Supply a keyword value of valid length.

0423-094

ERROR: The value in ____ is not valid. Valid values are: ____

Explanation:: The command entered uses a keyword=value pair (for example, datatype=ascii). The value is not correct.
System action:: InfoPrint Manager cannot run the command.
User response:: Supply a keyword value of valid length.

0423-095

ERROR: The value in ____ must be in the range ____ to ____.

Explanation:: The command entered uses a keyword=value pair, for example, copies=2, or a flag and value pair such as -N 5. A value outside of the valid range was entered with the command. Values must be in the range specified in the message.
System action:: InfoPrint Manager cannot run the command.
User response:: Supply a keyword or flag value within the specified range.

0423-096

ERROR: The parameter ____ must be of the form keyword=value.

Explanation:: A value containing a blank was entered for the keyword=value pair.
System action:: InfoPrint Manager cannot run the command.
User response:: Use the correct format for the keyword and value pair.

0423-097

ERROR: No file was specified with the print command.

Explanation:: A print request was made with no file specified for the print job.
System action:: InfoPrint Manager cannot run the command.
User response:: Enter the print request again and supply a file name.

0423-098

ERROR: An actual destination must be specified.

Explanation:: No actual destination was specified with the print command for the print job.
System action:: InfoPrint Manager cannot run the command.
User response:: Enter the print request again and supply an actual destination file name.

0423-099

ERROR: InfoPrint Manager cannot continue. ____ does not have an effective user id of root.

Explanation:: When InfoPrint Manager was installed, the InfoPrint Manager ainbe backend file had a user ID of root. Someone has copied or moved this file so that the user ID is no longer root.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Use the AIX chown and chmod commands to change the ainbe file's ownership back to root.

0423-100

ERROR: File ____ does not exist or does not have the permission levels set so that the file can be read.

Explanation:: You submitted a job to print a file, and one of the following has caused an error: The file specified does not exist. If AIX, you do not have read permission for the file. A valid AIX flag was entered with the print command; InfoPrint Manager does not recognize the AIX flag and has interpreted the flag as the file name.
System action:: InfoPrint Manager cannot run the command.
User response:: Check that the file exists. If AIX, ensure you have permission to read the file. To read the file, you must have x (execute) permission and r (read) permission for the file itself. See 'Using InfoPrint Manager for Production Printing' for a list of the AIX print command flags that are not recognized by InfoPrint Manager.

0423-101

ERROR: ____ must be specified as an absolute path.

Explanation:: You tried to run the InfoPrint Manager backend program, ainbe, as a separate command. However, you specified the ainbe name incorrectly.
System action:: The InfoPrint Manager backend cannot run.
User response:: Running the backend as a separate program is not recommended and not documented. However, if you intend to do this, specify the full, absolute pathname of the backend program. To see what this pathname is, try the command: which ainbe

0423-104

ERROR: InfoPrint Manager cannot access the actual destination configuration file ____ (return code=____).

Explanation:: For each InfoPrint Manager actual destination, InfoPrint Manager expects to find an actual destination profile in the path /var/psf/printername (for example, /var/psf/3825491/3825491.profile). Either the actual destination profile does not exist in that path, or InfoPrint Manager does not have permission to read it. The return code in the message is defined in the AIX /usr/sys/include/errno.h file.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Check that the actual destination profile exists with 'read' permission in the proper directory. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message. When reporting this message, include the return code it contains.

0423-106

ERROR: InfoPrint Manager cannot access the actual destination profile in directory ____ (return code=____).

Explanation:: InfoPrint Manager used the AIX chdir command to access the actual destination profile, but could not change to the directory where the actual destination profile resides (for example, /var/psf/3831). Someone might have moved or deleted this directory, or you may not have read permission for the directory. The return code in the message is defined in the AIX /usr/sys/include/errno.h file.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Check that the directory exists, and that the owner, group, and others have permission to read it.

0423-107

ERROR: The PPDS/PCL output command ____ was not successful.

Explanation:: The InfoPrint Manager SMIT Add a Printer panels for PPDS and PCL actual destinations contain a Command to Execute for actual destination output entry field. This field specifies the command that InfoPrint Manager runs when directing output to a PPDS or PCL actual destination. InfoPrint Manager cannot run the command contained in this field, either because the command does not exist or because it is not specified correctly.
System action:: InfoPrint Manager cannot run the output command.
User response:: Use the InfoPrint Manager SMIT panels to correct the entry in the Command to Execute for actual destination output entry field.

0423-108

ERROR: InfoPrint Manager could not find the actual destination environment file ____ or the system environment file /etc/environment (return code=____).

Explanation:: InfoPrint Manager needs information from the InfoPrint Manager actual destination environment file or from the /etc/environment file. One or both of these files are missing. If the environment files are remotely mounted, they may not have the permission levels required for InfoPrint Manager to access the information. The return code in the message is defined in the AIX /usr/sys/include/errno.h file.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Check that the environment file exists as either /etc/environment or /var/psf/printername/environment (for example, /var/psf/3831/environment), and that InfoPrint Manager has read access to the file. If necessary, restore your /etc/environment file from a backup copy. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message and the return code it contains.

0423-110

ERROR: InfoPrint Manager is unable to execute process ____. Return code=____.

Explanation:: InfoPrint Manager attempted to start another process but was unable to locate the executable file specified in the message. The return code in the message is defined in the AIX /usr/include/sys/errno.h file.
System action:: InfoPrint Manager does not complete the operation.
User response:: Check that all InfoPrint Manager files are in the correct directories and have the correct permission levels. If the problem cannot be corrected, use local problem-reporting procedures to report this message and the program name and return code it contains.

0423-111

ERROR: Unable to fork a child process from ____. Return code=____.

Explanation:: The executable program specified in the message attempted to create and start a child process, but could not complete the fork. The return code in the message is defined in the AIX /usr/sys/include/errno.h file.
System action:: InfoPrint Manager does not complete the operation.
User response:: The number of processes that can be run are controlled by values in the /etc/security/limits file. Contact the person who administers your system for assistance.

0423-113

ERROR: An error occurred on a ____ operation with ending status ____.

Explanation:: This message provides additional information about a previously reported device error.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0423-116

ERROR: The InfoPrint Manager internal converter program ____ might have an error (return code=____).

Explanation:: To process your request, InfoPrint Manager tried to use an internal converter program. However, the converter program might have an error.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Try your request again. If the problem cannot be corrected, use local problem-reporting procedures to report this message and the return code it contains.

0423-117

ERROR: The InfoPrint Manager transform program ____ received an unexpected return code (return code=____).

Explanation:: The InfoPrint Manager transform program specified in the message encountered an unexpected error while processing the file. Other error messages in this message group provide further explanation of the error condition.
System action:: InfoPrint Manager does not complete the requested transform operation. If more than one file was submitted with the transform command, InfoPrint Manager will continue processing with the next file.
User response:: See the responses for other error messages in this message group.

0423-197

ERROR: psfctl: Destination ____ is not defined in directory ____

Explanation:: The psfctl program must be able to change to the directory that contains the actual destination profile. By default, the file system used for the actual destination profile is /var/psf/printername where printername is the name of the actual destination that was specified when the actual destination was configured through the InfoPrint Manager SMIT configuration panels. InfoPrint Manager generates this message if the actual destination name specified in the message does not exist. The actual destination name might not be spelled correctly.
System action:: The psfctl program ends.
User response:: Check that you are using the actual destination name that was specified when the actual destination was configured for use by InfoPrint Manager, not the AIX queue name, and that you have typed the actual destination name correctly.

0423-208

ERROR: db2afp: "____" is not a valid language with the -l flag.

Explanation:: The -l flag of the db2afp transform accepts files from three languages: Japanese, Chinese, and Korean. You used the -l flag with a language that db2afp does not accept.
System action:: The command does not complete.
User response:: Use one of the following with db2afp -l: ja (for Japanese), ch (for Chinese), or ko (for Korean).

0423-210

ERROR: db2afp: The Korean language requires the -e flag.

Explanation:: For Korean, the db2afp transform only supports Extended UNIX Character (EUC) files. Therefore, whenever you transform Korean-language files, you must use the db2afp -e flag.
System action:: The command does not complete.
User response:: Use db2afp -l ko -e.

0423-211

ERROR: db2afp: cannot open fontmap file ____.

Explanation:: The db2afp transform cannot get to the fontmap file /usr/lpp/psf/db2afp/afpdfont.rc.
System action:: The command does not complete.
User response:: Make sure that /usr/lpp/psf/db2afp/afpdfont.rc exists, and that you have permission to read it. If the permissions are not correct or if the file does not exist, notify your system administrator.

0423-212

ERROR: db2afp: Cannot open converter file ____.

Explanation:: The db2afp transform cannot open the AIX code page converter file specified in the message. The file does not exist, or does not have the correct permissions.
System action:: The command does not complete.
User response:: Make sure that the converter file /usr/lib/nls/loc/iconv/ filename exists, and that you have permission to read it. If the permissions are wrong or the converter file is not installed, notify your system administrator. If the converter is installed and accessible, make sure that your LOCPATH environment variable contains /usr/lib/nls/loc. To do this, type echo !L!OCPATH at a command line. If LOCPATH does not contain /usr/lib/nls/loc, type LOCPATH=!L!OCPATH:/ usr/lib/nls/loc at a command line to change LOCPATH for your current login session. To change LOCPATH permanently, put the LOCPATH= statement into your .kshrc file (for Korn shell users) or .profile file (for C shell and Bourne shell users), or contact your system administrator to change it for the entire system.

0423-213

ERROR: db2afp: Byte number ____ is not a valid EUC character.

Explanation:: The db2afp transform detected an incorrect Extended UNIX Character (EUC) in the file you are trying to print or transform. The incorrect character starts at byte number in the file. The file may be damaged.
System action:: The command does not complete.
User response:: If you can identify the number of bytes from the beginning of the file, then you can find the exact character that is incorrect. Remove this character from the input. Otherwise, recreate the file, and try to print or transform it again. If you still get this message, the program that created the file may have an error.

0423-214

ERROR: db2afp: The db2afp transform cannot complete because of insufficient resources or a missing input file. Check your filesystem space and system limits.

Explanation:

The db2afp transform experienced an internal error. Possible causes include:

No more files can be opened.
There is not enough space in the filesystem you're submitting the job from, in /tmp, or in /var/psf/tmp.
The pSeries is out of memory.

System action:

The transform either produces no output, or produces incorrect output.

User response:

Ask your system administrator to verify that there are sufficient inodes and disk space on the filesystem (df command), and that no system limits (as defined in /etc/security/limits) have been exceeded. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-215

ERROR: db2afp: The db2afp transform could not use a temporary file. Make /tmp or /var/psf/tmp larger, or split your input file into two pieces.

Explanation:: The db2afp transform needs to use a temporary file in /tmp or in /var/psf/tmp. However, db2afp could not open, write, or close the temporary file. Your input file is probably too big for db2afp to process, given the current size of the /tmp or /var/psf/tmp filesystem.
System action:: The transform either produces no output, or produces incorrect output.
User response:: Ask your system administrator if there is adequate temporary file space in /tmp or in /var/psf/tmp. If there is not adequate space, ask your system administrator to increase the size of the filesystem. Otherwise, divide your file into two or more pieces, and transform or print them separately.

0423-216

ERROR: db2afp: Cannot open the input file. Check that it exists with read permission.

Explanation:: The db2afp transform could not open the input file specified on the command line. The file does not exist, or you don't have permission to read it.
System action:: The command does not complete.
User response:: Verify that the input file exists, and that you have permission to read the file. If the file exists with the correct permissions, the AIX system resources may be insufficient; contact your system administrator.

0423-217

ERROR: db2afp: Cannot access the output file. Make sure you have permission to write to the output file's directory; also check the filesystem space.

Explanation:: The db2afp transform could not open the output file, or could not write to the output file. You may not have permission to write to the file or the file's directory, or there may not be enough space in the file's filesystem.
System action:: The transform either produces no output, or produces incorrect output.
User response:: Make sure that you have permission to write to the output file and the directory that contains the output file. If the permissions appear correct, ask your system administrator to verify there is enough space in the filesystem (using the df command).

0423-218

ERROR: db2afp: You must use the -l flag with the -e flag.

Explanation:

You tried to print or transform an EUC (Extended UNIX Code) file, and you used the db2afp -e flag to specify that your input file is an EUC file. However, the db2afp -l flag, which specifies the language of the input file, is missing from the command line.

System action:

InfoPrint Manager does not complete the requested transform operation.

User response:

Specify a language by doing one of the following:

At the command line, specify the db2afp flag -l japanese , -l chinese , or -l korean. (If the input file is Japanese EUC, Chinese EUC, or Korean EUC, you must also specify the -e flag.)
Set the PSFDBLANG environment variable to j (for Japanese code page 932), je (for Japanese EUC), c (for Chinese code page 932), ce (for Chinese EUC), or ke (for Korean EUC). Don't use the db2afp -l or -e flags.

0423-219

ERROR: db2afp: Use the -l (and -e for EUC) flag, or set the PSFDBLANG environment variable.

Explanation:

You tried to print or transform a double-byte ASCII file or an EUC file. However, the PSFDBLANG environment variable was not set, and the db2afp -l flag (to indicate the language of the input file) and -e flag (to indicate whether the input file is EUC data) are missing from the command line.

System action:

InfoPrint Manager does not complete the requested transform operation.

User response:

Specify a language by doing one of the following:

At the command line, specify the db2afp flag -l japanese, -l chinese, or -l korean. (If the input file is Japanese EUC, Chinese EUC, or Korean EUC, you must also specify the -e flag.)
Set the PSFDBLANG environment variable to j (for Japanese code page 932), je (for Japanese EUC), c (for Chinese code page 932), ce (for Chinese EUC), or ke (for Korean EUC). Don't use the db2afp -l or -e flags.

0423-220

ERROR: db2afp: "____" is not a valid value of the PSFDBLANG environment variable.

Explanation:

You tried to print or transform a double-byte ASCII file or an EUC file. You didn't use the db2afp -l flag (and -e flag for EUC input data) on the command line, so db2afp tried to use the language and EUC values that are specified by PSFDBLANG. However, PSFDBLANG was set to something other than j, c, je, ce, or ke.

System action:

InfoPrint Manager does not complete the requested transform operation.

User response:

Specify a language by doing one of the following:

At the command line, specify the db2afp flag -l japanese, -l chinese, or -l korean. (If the input file is Japanese EUC, Chinese EUC, or Korean EUC, you must also specify the -e flag.)
Set the PSFDBLANG environment variable to j (for Japanese code page 932), je (for Japanese EUC), c (for Chinese code page 932), ce (for Chinese EUC), or ke (for Korean EUC). Don't use the db2afp -l or -e flags.

0423-240

ERROR: The actual destination reported an error in an outline font.

Explanation:: The outline font in error was either downloaded by InfoPrint Manager or was resident in the actual destination and activated by InfoPrint Manager.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If the font in error is a printer-resident font, contact your actual destination hardware service representative. If you created the font, correct the error by consulting font data stream references. Otherwise, notify the person who administers your system or the owner of the font and have the error corrected.

0423-241

ERROR: The actual destination reported an error which indicates an InfoPrint Manager or actual destination problem.

Explanation:: Either an actual destination internal microcode error or an InfoPrint Manager internal logic error occurred.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0423-245

ERROR: The actual destination resolution has changed.

Explanation:: The actual destination reported that the printing resolution has changed. InfoPrint Manager reports this message for the user's information in case the new resolution is not satisfactory for the print job..
System action:: InfoPrint Manager recovers and printing continues.
User response:: Examine the output to determine if the new actual destination resolution is satisfactory for the print job.

0423-246

ERROR: The actual destination has discarded buffered pages.

Explanation:: The actual destination has discarded buffered pages due to an internal actual destination operation.
System action:: InfoPrint Manager recovers and printing continues.
User response:: This is an informational message; no response is required.

0423-247

ERROR: The actual destination reported invalid data in a non-presentation object container.

Explanation:: The data in a non-presentation object container resource sent in a Write Object Container command is invalid.
System action:: If this error occurs within a page, InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job. Otherwise, InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job
User response:: If you created the container data in the object container resource, correct the error. Refer to the appropriate documentation for the data stream carried within the object container resource. If you used a program to create the structured fields and object container data, contact the program owner.

0423-248

ERROR: The actual destination reported that the object container presentation data extends outside the defined object area.

Explanation:: A portion of the object container presentation data extends beyond the intersection of the mapped presentation space and object container area. For more information, refer to the documentation that describes the data carried in the object container resource.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the object container problem.

0423-249

ERROR: The actual destination reported an invalid font global identifier.

Explanation:: The actual destination detected one or more of the following errors while receiving a loaded coded font, font character set, or code page: (1) an invalid Font Global Resource Identifier (GRID), (2) an invalid Font Typeface Global Identifier (FGID), (3) an invalid Code Page Global Identifier (CPGID), or (4) an invalid Graphic Character Set Global Identifier (GCSGID). Various combinations of these IDs are used to request that the actual destination use a specific printer-resident font.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem by ensuring that the global IDs used to request a font are valid and present in the actual destination.

0423-267

ERROR: The actual destination setup has changed. Partial or duplicate pages may be printed.

Explanation:: The actual destination setup, or actual destination characteristics, were changed while InfoPrint Manager was sending print data to the actual destination.
System action:: InfoPrint Manager repositions and continues processing the print file using the updated actual destination characteristics.
User response:: Examine the printed output and remove any partial or duplicate pages.

0423-268

ERROR: The medium modification ____ specified in the MMC structured field is not currently available at the actual destination.

Explanation:: The Medium Modification ID in the Medium Modification Control (MMC) structured field contains a modification ID that is not currently available at the actual destination or the actual destination does not support medium modifications. The MMC structured field is contained in the form definition.
System action:: InfoPrint Manager cancels the print job.
User response:: To receive printed output with the medium modification, either ensure that the medium modification is made available on the actual destination or submit the job to an actual destination that contains the medium modification. To receive printed output without the medium modification, specify a different form definition that does not contain this medium modification.

0423-269

ERROR: A GRID file syntax error was detected.

Explanation:: An invalid GRID field value was found in the specified GRID file.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: See the error log for further information on the cause of this error. Contact the person who administers your system for assistance, if necessary.

0423-270

ERROR: The character ____ on line ____ in file ____ is not allowed.

Explanation:

These field values are not allowed in the following types of GRID files:

File	Field	Value
CHARSET	width	asterisk (*)
CODEPAGE	gcsgid	asterisk (*)
FGID	gcsgid	dash (-)
FGID	gcsgid	dash (-)
CPGID	gcsgid	dash(-)

System action:

InfoPrint Manager cannot start this InfoPrint Manager instance.

User response:

Correct the reported problem.

0423-271

ERROR: An insufficient number of fields were found in file ____ on line number ____.

Explanation:

Insufficient data was found in the specified GRID file. For the following types of GRID files, the required number of fields are:

GRID File	Required number of fields
CHARSET	6
CODEPAGE	3
FGID	5
CPGID	3

System action:

InfoPrint Manager cannot start this InfoPrint Manager instance.

User response:

Correct the reported problem.

0423-272

ERROR: Line number ____ in file ____ exceeds the maximum line length of 254 characters.

Explanation:: The maximum line length allowed in the GRID file is 254. Data may have been lost. Please check your GRID file.
System action:: InfoPrint Manager cannot start this InfoPrint Manager instance.
User response:: Correct the reported problem.

0423-275

ERROR: InfoPrint Manager cannot use the printer-resident code page identified by Code Page Global ID ____ and Graphic Character Set Global ID ____ together with the FOCA2 raster font character set file ____.

Explanation:: A Map Coded Font (MCF) structured field specified a code page name and a font character set name. InfoPrint Manager mapped the code page name to a printer-resident code page <CPGID, GCSIGD> combination, using the CODEPAGE.GRD mapping table. However, the font character set specified is in raster format. A raster font character set cannot be combined with a printer-resident code page.
System action:: InfoPrint Manager will attempt to complete processing of the font reference by substituting a FOCA2 code page file for the printer-resident code page. If InfoPrint Manager can substitute a code page file, it will download a raster coded font using the code page file and the font character set file.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-277

ERROR: InfoPrint Manager cannot use the FOCA2 raster FCS file with the name ____ together with the printer-resident code page identified by Code Page Global ID ____ and Graphic Character Set Global ID ____. InfoPrint Manager also cannot substitute a code page file for the resident code page. InfoPrint Manager will therefore attempt to substitute a FOCA2 outline FCS file, or resident FCS, to use with the resident code page.

Explanation:: InfoPrint Manager could select only a printer-resident code page to process a Map Coded Font (MCF) structured field. Because a raster font character set cannot be combined with a printer-resident code page, InfoPrint Manager must attempt to substitute an outline FCS file or a resident FCS for the raster FCS file.
System action:: InfoPrint Manager will attempt to complete processing of the font reference by substituting a FOCA2 outline FCS file.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-278

ERROR: InfoPrint Manager mapped the CPGID, GCSGID combination: ____, ____ to the code page name ____. The CPGID.GRD mapping file specified that this mapping be performed.

Explanation:: As specified by the CPGID.GRD mapping file, InfoPrint Manager mapped a resident code page to a code page name.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-279

ERROR: InfoPrint Manager mapped the code page name ____ to the CPGID, GCSGID combination: ____, ____. The CODEPAGE.GRD mapping file specified that this mapping be performed.

Explanation:: As specified by the CODEPAGE.GRD mapping file, InfoPrint Manager InfoPrint Manager mapped a code page name to a resident code page.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-280

ERROR: The code page ____, located inline at offset ____ will be used.

Explanation:: InfoPrint Manager found a code page inline within the print file. It was specified on the Map Coded Font structured field within the print file.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: None.

0423-281

ERROR: A code page with the name ____ was specified by name on a Map Coded Font or Coded Font Index structured field, but could not be located in the resource library.

Explanation:: In an attempt to process a font reference, InfoPrint Manager searched the resource library for a code page file. The code page is not in the library.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-282

ERROR: An FCS with the name ____ was specified by name on a Map Coded Font structured field, but could not be located in the resource library. The FCS may exist in the resource library in a different pel resolution, but does not exist in a pel resolution supported by the actual destination. The actual destination accepts raster fonts in the ____ pel / inch resolution.

Explanation:: In an attempt to process a font reference, InfoPrint Manager searched the resource library for a font character set file that matches the actual destination pel resolution. The font character set is not in the library. When driving an actual destination that accepts only raster fonts, InfoPrint Manager searches for a font character set that matches the pel resolution of the actual destination. When driving an actual destination that accepts outline or raster fonts, InfoPrint Manager searches first for an outline font character set, and will use the outline font character set, if it is found. If the outline font character set is not found, InfoPrint Manager will then search for a font character set that matches the pel resolution of the actual destination. If the actual destination is in auto resolution mode, InfoPrint Manager searches first for an outline font character set. If the outline font character set is not found, InfoPrint Manager will then search for a font character in 240 pel resolution. If not found, InfoPrint Manager will then search for an FCS in 300 pel resolution. When the actual destination is set to auto resolution mode, the pel resolution displayed in the message is the largest resolution the device supports.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-283

ERROR: InfoPrint Manager mapped the FCS name ____ to the FGID, GCSGID, vertical size, width, attribute combination: ____, ____, ____, ____, ____ . The CHARSET.GRD mapping file specified that this mapping be performed.

Explanation:: In an attempt to process a font reference, InfoPrint Manager mapped a font character set name to a printer-resident font character set identifier.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-284

ERROR: InfoPrint Manager mapped the FGID, GCSGID, width, vertical size combination: ____, ____, ____, ____ to the FCS name ____. The FGID.GRD mapping file specified that this mapping be performed.

Explanation:: In an attempt to process a font reference, InfoPrint Manager mapped a printer-resident font character set identifier to a font character set name.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-285

ERROR: The 240-pel raster FCS with the name ____ appeared inline in the print file at offset ____, but was not used.

Explanation:: A font character set appeared inline with the print file. InfoPrint Manager did not use this font character set because its font resolution is not supported by the actual destination.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-286

ERROR: The 300-pel raster FCS with the name ____ appeared inline in the print file at offset ____, but was not used.

Explanation:: A font character set appeared inline with the print file. InfoPrint Manager did not use this font character set because its font resolution is not supported by the actual destination.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-287

ERROR: The outline FCS with the name ____ appeared inline in the print file at offset ____, but was not used.

Explanation:: A font character set appeared inline with the print file. InfoPrint Manager did not use this font character set because it is in outline format, and outline fonts are not supported by the actual destination.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-290

ERROR: A Map Coded Font (MCF) or Map Data Resource (MDR) structured field could not be processed because InfoPrint Manager could not locate the code page ____.

Explanation:: InfoPrint Manager could not select any code page to use in processing a font reference. A code page name may be specified on the MCF, MDR or Coded Font Index (CFI) structured field, or in the CPGID.GRD mapping table. A printer-resident code page can be specified on the MCF, MDR or in the CODEPAGE.GRD mapping table.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF or MDR font reference successfully. Read all of the messages to determine how to change the appropriate structured field, font mapping files or font fidelity so that the font reference can be processed successfully.

0423-291

ERROR: Map Coded Font (MCF) structured field could not be processed because InfoPrint Manager could not locate the font character set ____ in the resource libraries or GRID mapping tables.

Explanation:

InfoPrint Manager could not select any font character set (FCS) to use in processing a font reference. InfoPrint Manager lists the attempted and supported resolutions. If the attempted resolution or type is 'none', it is because the actual destination does not support the requested resolution. An FCS name may be specified on the MCF or Coded Font Index (CFI) structured fields, in the GRID mapping tables, or for the IBM 6400 printer, in the charset.64xx.grd mapping table..

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job off the printer.

User response:

This message will be accompanied by other messages that will indicate what InfoPrint Manager did to try to resolve the MCF font reference when it could not find the FCS. This can include messages about attempts to use printer resident or library outline font character sets. An example of one of these messages is: 0423-292: InfoPrint Manager cannot use a resident outline FCS nor a library outline FCS because no width or vertical size was provided, either on a Map Coded Font (MCF) structured field, or in the charset.grd mapping table.

Message 0423-292 explains that InfoPrint Manager tried to resolve the font reference with printer resident or host outline fonts, which may not have been requested in the MCF font reference.

Note: A multiple-resolution device set incorrectly is the most common explanation for issuing messages 0423-292 and 0423-291.

The MCF structured field can invoke a font using one of these methods:

Using a Coded Font reference.
Using a Code Page and Character Set pair reference.
Using GRID parts (FGID, CPGID, GCSGID, width and vertical size) to invoke a printer resident outline font.

If the MCF font reference used a Coded Font (X0nnnnnn) or Character Set/Code Page pair (C0nnnnnn/T1nnnnnn) invocation, the following lists possible explanations for these messages:

The Font Character Set (FCS) is not in the library specified in the font resource path.
The Font Character Set (FCS) is in the library specified in the font resource path, but not in the resolution required for this job.
The printer is a multiple-resolution (multi-res) device, and it is not set to the correct resolution required for this job.

If the MCF font reference is intentionally designed to use GRID font mapping tables to activate a printer resident outline font, read all of the messages to determine how to change the font mapping files or MCF structured field.

MCF structured fields can occur in MO:DCA files, page definition object files, or overlay object files. It is often possible to use the InfoPrint Manager afpsplit, afpdmp, or b2a+ utilities to collect detailed information about the contents of MCF and many other structured fields. These tools reside in /usr/lpp/psf/bin in InfoPrint Manager for AIX. InfoPrint Manager for Windows does not include afpdmp, but the other utilities are available in <install-path>\bin. Use of the -dx flag with afpdmp will provide both human readable detail and hexadecimal contents for the structured fields the tool currently understands. The afpsplit utility can be used to extract the page containing the error, which is identified in accompanying messages, so that afpdmp or b2a+ can be run against a single page, instead of the entire file.

Note:

The afpsplit, afpdmp, and b2a+ utility programs are provided on an as is basis.
The afpdmp utility can issue the following message if it encounters a valid AFPDS structured field it has not been enhanced to support: Input may not be valid AFPDS.

0423-292

ERROR: InfoPrint Manager cannot use a resident outline FCS nor a library outline FCS, because no width or vertical size was provided, either on a Map Coded Font (MCF) structured field or in the CHARSET.GRD mapping table.

Explanation:: InfoPrint Manager could not use the FOCA2 outline font character set because no width or vertical size value was provided on the MCF structured field. At least one of the two size fields must be specified on the MCF when an outline font character set is specified.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-295

InfoPrint Manager will use the code page ____.

Explanation:: InfoPrint Manager will use the code page identified in the message text.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: None.

0423-296

InfoPrint Manager will use the font character set ____ at resolution/type ____. This FCS name was specified on a Map Coded Font (MCF) or Coded Font Index (CFI) structured field

Explanation:: InfoPrint Manager will use the font character set named in the message text.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: None.

0423-299

InfoPrint Manager will activate the resident raster coded font made up of the CPGID, GCSGID, FGID, and width combination: ____, ____, ____, ____ .

Explanation:: InfoPrint Manager will activate the resident raster coded font identified in the message text.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: None.

0423-300

InfoPrint Manager will activate the resident code page made up of the CPGID, GCSGID combination: ____, ____ .

Explanation:: InfoPrint Manager will activate the resident code page identified in the message text.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-301

InfoPrint Manager will activate the resident FCS made up of the FGID, GCSGID combination ____, ____ .

Explanation:: InfoPrint Manager will activate the resident font character set identified in the message text.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-302

The font with local identifier ____ referenced in the ____ structured field could not be processed successfully. Additional error and diagnostic messages follow.

Explanation:: A font reference could not be resolved.
System action:: InfoPrint Manager stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job. Otherwise, InfoPrint Manager cancels the job.
User response:: This message is accompanied by other messages that indicate why InfoPrint Manager could not process the font reference successfully. Some of the additional messages are issued only if they are requested through a print server parameter that enables additional font processing messages. Read all of the messages to determine how to change the MCF (Map Coded Font) or MDR (Map Data Resource) structured field or font mapping files so that the font reference can be processed successfully.

0423-303

No AFP COM Setup file was specified for the print job.

Explanation:: When printing to an AFP-COM device, InfoPrint Manager requires a COM Setup file for every print file. No COM Setup file was specified for this job, either through the actual destination profile, on the Enqueue command, or inline within the print file.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Specify a Setup file, either through the actual destination profile, or on the Enqueue command when submitting the print job.

0423-304

A Begin Object Container structured field specified object structure flags ____, which are not valid.

Explanation:: InfoPrint Manager requires that the Begin Object Container structured field Object Classification Triplet, triplet ID X'10', contain flag bytes (byte 6) with bits 0-1 set to B'11', and bits 4-5 also set to B'11'.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the Begin Object Container structured field. Within the Object Classification triplet Structure Flags, set bits 0-1 to B'11' to indicate that the data within the Object Container is in MODCA format, and set bits 4-5 to B'11' to indicate that the object data is carried in Object Container Data structured fields. For more information consult the Mixed Object Document Content Architecture Reference.

0423-305

A Begin Object Container structured field specified object class: ____, which is not valid. The object class must be X'30' (Set-up file).

Explanation:: InfoPrint Manager requires that the Begin Object Container structured field Object Classification Triplet triplet ID X'10', contain an object class field (byte 3) of X'30' (Set-up file).
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the Begin Object Container structured field. Within the Object Classification triplet, set the Object Class field to X'30', to indicate a Set-up file. For more information consult the Mixed Object Document Content Architecture Reference.

0423-306

A Begin Object Container structured field within a print file specified a registered object ID: ____, which is not valid. The registered object ID must be the Tape Label Setup File ID. Consult the Mixed Object Document Content Architecture Reference for this ID.

Explanation:: InfoPrint Manager supports only the Tape Label Object Container within a print file. Any Begin Object Container structured field within a print file must specify the Tape Label Setup File registered object ID
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If the object container represents a Tape Label Setup File, correct the Begin Object Container structured field. If the object container does not represent a Tape Label Setup File, remove it from the print file. Consult the Mixed Object Document Content Architecture Reference for more information, and for the value of the Tape Label Setup File ID.

0423-307

ERROR: A page segment, specified on the Map Page Segment (MPS) structured field, could not be processed. The MPS structured field appeared at file offset ____, with sequence number ____. The MPS repeating group in error was repeating group ____.

Explanation:: A page segment, specified on a Map Page Segment structured field, could not be processed. ID
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Read the error messages that accompany this message for an explanation of the error, and correct the error accordingly.

0423-308

ERROR: Output bin ____ was requested but cannot be used with input bin ____ on this device.

Explanation:: The output bin is specified is not compatible (on this device) with the input bin selected for this print file. The input bin may be the actual destination default input bin or another input bin as specified with the printer-pass-through attribute or in the form definition (FORMDEF). The output bin may be the actual destination default output bin or another output bin as specified with either the output-bin attribute or in the form definition (FORMDEF).
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise; InfoPrint Manager cancels the job.
User response:: Modify your print submission command or FORMDEF to specify input and output bins that are compatible on this device.

0423-309

The Font Library Utility was unable to create the system font mapping tables.

Explanation:: The system font mapping files must be installed to run the Font Library Utility.
System action:: The Font Library Utility does not complete processing. No character sets or code pages are updated.
User response:: Use local problem-reporting procedures to report this message.

0423-310

Not enough memory was available for the Font Library Utility to complete processing.

Explanation:: There is not enough memory available to complete processing. The Font Library Utility cannot complete processing.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-311

Error was detected when opening directory ____.

Explanation:: An error occurred when the Font Library Utility attempted to open a directory specified on the command line.
System action:: The Font Library Utility does not complete processing. No character sets or code pages are updated.
User response:: Enter the correct directory name or names and run the Font Library Utility again.

0423-312

Error was detected when closing file ____.

Explanation:: An error occurred when the Font Library Utility attempted to close a file.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-313

Error was detected when opening file ____.

Explanation:: An error occurred when the Font Library Utility attempted to open a file.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-314

Error was detected when reading file ____.

Explanation:: An error occurred when the Font Library Utility attempted to read a file. A code page or character set structured field may be missing or the length of the structured field is incorrect.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-315

Error was detected when data was being written to the buffer for file ____.

Explanation:: An error occurred when the Font Library Utility attempted to write data to the record in a file being updated.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-316

Processing completed and GRID data added in font resource ____.

Explanation:: This message indicates processing completed without errors.
System action:: The Font Library Utility continues processing. The font resource FND or CPD is updated with valid GRID values
User response:: No response is necessary.

0423-317

Old character set GRID values: FGID=____ GCSGID=____ Width=____

Explanation:: Indicated GRID values are in the GRID fields in the FND structured field in the character set prior to processing.
System action:: This message is informational only.
User response:: No response is necessary.

0423-318

New character set GRID values: FGID=____ GCSGID=____ Width=____

Explanation:: Indicated updated GRID values are in the GRID fields in the FND structured field in the character set.
System action:: This message is informational only.
User response:: No response is necessary.

0423-319

Old code page GRID values: CPGID=____ GCSGID=_____

Explanation:: Indicated GRID values in the GRID fields in the CPD structured field in the code page prior to processing.
System action:: This message is informational only.
User response:: No response is necessary.

0423-320

New code page GRID values: CPGID=____ GCSGID=____

Explanation:: Indicated updated GRID values are in the GRID fields in the CPD structured field in the code page.
System action:: This message is informational only.
User response:: No response is necessary.

0423-321

Usage: flu -d directory1[:directory2:directory3...]

Explanation:: The syntax of the flu command is shown. The -d flag must be specified with at least one directory. If multiple directories are specified, they are separated by colons (:), similar to the PATH environment variable format.
System action:: The flu usage message is displayed; processing stops.
User response:: Follow the command syntax detailed in this message.

0423-322

Error was detected when buffered data was being written to file ____.

Explanation:: An error occurred when the Font Library Utility attempted to output the updated record to the file.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-323

No available user range GRID values available for code pages.

Explanation:: The Font Library Utility is unable to assign a user range GRID value for a code page because all available user range GRID values for code pages have already been assigned.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-324

No available user range GRID values available for character sets.

Explanation:: The Font Library Utility is unable to assign a user range GRID value for a character set because all available user range GRID values for character sets have already been assigned.
System action:: The Font Library Utility does not complete processing. Some character sets or code pages may have been updated.
User response:: Use local problem-reporting procedures to report this message.

0423-325

ERROR: An overlay, specified on the Map Medium Overlay (MMO) or Map Page Overlay (MPO) structured field, could not be processed. The MMO/MPO structured field appeared at file offset ____, with sequence number ____. The repeating group in error was repeating group ____.

Explanation:: An overlay, specified on a Map Medium Overlay or Map Page Overlay structured field, could not be processed.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Read the error messages that accompany this message for an explanation of the error, and correct the error accordingly.

0423-326

The font character set found inline within the print file, at offset ____, with token name ____, is not valid.

Explanation:: InfoPrint Manager found a font character set inline within the print file, but could not identify the font character set as a 240-pel raster, a 300-pel raster, or an outline font character set.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the inline font character set problem.

0423-327

The Code Page Index repeating group length, ____, specified on the Code Page Control structured field, is not valid within a double-byte code page. The CPI repeating group length must be 11.

Explanation:: The Code Page Control structured field within a double-byte code page specified a CPI repeating group length, byte 9, other than 11. The CPI repeating group length within a double-byte code page must be 11. A code page is identified as a double-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor (CPD) structured field. If the low-order four bits of byte 42 contain X'2', then the code page is a double-byte code page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the code page problem.

0423-328

The Code Page Index repeating group length, ____, specified on the Code Page Control structured field, is not valid within a single-byte code page. The CPI repeating group length must be 10.

Explanation:: The Code Page Control structured field within a single-byte code page specified a CPI repeating group length, byte 9, other than 10. The CPI repeating group length within a single-byte code page must be 10. A code page is identified as a single-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor (CPD) structured field. If the low-order four bits of byte 42 does not contain X'2', then the code page is a single-byte code page. If byte 42 of the CPD is not present, the code page is a single-byte code page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the code page problem.

0423-329

The double-byte code page is not sorted by code point.

Explanation:: The Code Page Control structured field within a double-byte code page does not indicate that the Code Page Index (CPI) repeating groups are sorted by code point. Within a double-byte code page, bit 0 of byte 12 must be on, to specify that the CPI repeating groups are sorted by code point. A code page is identified as a double-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor structured field. If the low-order four bits of byte 42 contain X'2', then the code page is a double-byte code page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the code page problem.

0423-330

The single-byte code page is not sorted by graphic character ID.

Explanation:: The Code Page Control structured field within a single-byte code page indicates that the Code Page Index (CPI) repeating groups are sorted by code point. The CPI repeating groups within a single-byte code page must be sorted by graphic character ID, not by code point. Within a single-byte code page, bit 0 of byte 12 must be off, to specify that the CPI repeating groups are sorted by graphic character ID. A code page is identified as a single-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor (CPD) structured field. If the low-order four bits of byte 42 does not contain X'2', then the code page is a single-byte code page. If byte 42 of the CPD is not present, the code page is a single-byte code page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the code page problem.

0423-331

A double-byte code page cannot be used with a raster font.

Explanation:: A Map Coded Font 1, Map Coded Font 2, or Coded Font Index structured field specified that a double-byte code page be used with a raster font character set. A double-byte code page may be used only with an outline font character set.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Be sure your font character sets, codepages and coded fonts have the correct file extensions. Correct the problem with the MCF-1, MCF-2, or CFI structured field. If the MCF-1, MCF-2, or CFI contains a coded font Global ID (GRID), it's possible that the GRID was mapped to a double-byte code page file name via the CPGID.GRD mapping table. Check the first two bytes of the GRID, that is, the Graphic Character Set Global ID (GCSGID) and the Code Page Global ID (CPGID). If the CPGID.GRD mapping table file maps the GCSGID, CPGID combination to a code page file name, verify that the code page is not a double-byte code page. A code page is identified as a double-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor structured field. If the low-order four bits of byte 42 contain X'2', then the code page is a double-byte code page.

0423-332

Character rotation ____ is not supported by the actual destination.

Explanation:: Only character rotations: X'0000' (0 degrees), X'2D00' (90 degrees), X'5A00', (180 degrees), and X'8700' (270 degrees) are supported by actual destinations driven by InfoPrint Manager. A Map Coded Font format 1 (MCF-1), Map Coded Font format 2 (MCF-2), or Map Data Resource structured field specified a character rotation other than one of these four values.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the MCF-1, MCF-2, or MDR structured field.

0423-333

The Font Control structured field Pattern Technology Identifier: ____ is not valid for an extension font character set. The Pattern Technology Identifier for an extension font character set must be X'1E' or X'1F'.

Explanation:: A font character that is to be used as an extension of a printer-resident font character set must contain a Pattern Technology Identifier of X'1E' or X'1F', both of which indicate outline technology. In particular, a raster font character set (Pattern Technology Identifier X'05') cannot be used as an extension font character set. The Pattern Technology Identifier is specified on the Font Control structured field, byte 1. A font character set is identified as an extension font character set by the Font Control structured field, byte 3, bit 1.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-334

A Font Control structured field specified a Font Name Map data count value ____ that is not valid.

Explanation:: The Font Name Map data count field within the Font Control (FNC) structured field contains a value less than two. The Font Name Map data count is in FNC bytes 36-39.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-335

A Font Control structured field specified a Font data length value ____ that is not valid.

Explanation:: The Font data length field within the Font Control (FNC) structured field contains a value less than ten. The Font data length is in FNC bytes 28-31.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-336

A Font Control structured field specified a Font Resolution value ____ that is not valid.

Explanation:: The Font Resolution field within the Font Control structured (FNC) field of a raster font character set must contain X'09600960', indicating a raster density of 240 pels per inch, or X'0BB80BB8', indicating a raster density of 300 pels per inch. The Font Resolution is in FNC bytes 22-27.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-337

The length ____ of a Font Control structured field within an outline font character set is less than the minimum valid length ____.

Explanation:: The Font Control structured field within an outline font character set must include the optional fields (bytes 22-41).
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-338

A Font Control structured field within an outline font character set contains a Pattern Technology Identifier ____ that is not valid

Explanation:: The Font Control structured field within an outline font character set must contain a Pattern Technology Identifier, byte 1, of X'1E' or X'1F', both of which indicate outline technology. PSF processed a font character set file with a file extension of 'FONTCOLN', indicating an outline font character set, but the Pattern Technology Identifier was not X'1E' or X'1F'.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem. It's possible that the font character set file has the wrong file extension, that is, the file was assigned the 'FONTCOLN' extension when it should instead have the extension 'FONT3820' (for a 240-pel raster font character set) or 'FONT300' (for a 300-pel raster font character set). A Pattern Technology value of X'05' indicates a raster font character set.

0423-339

A Font Control structured field within a raster font character set contains a Pattern Technology Identifier ____ that is not valid.

Explanation:: The Font Control structured field within a raster font character set must contain a Pattern Technology Identifier, byte 1, ofX'05'. InfoPrint Manager processed a font character set file with a file name extension of '240', 'FONT3820', 'FONT38PP', '300', 'FONT300', or with no file name extension, but the Pattern Technology Identifier was not X'05'.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem. It's possible that the font character set file has the wrong file extension, that is, the file was assigned one of the raster font character set extensions when it should instead have the 'FONTCOLN' extension. A Pattern Technology value of X'1E' or X'1F' indicates an outline font character set.

0423-340

A font character set contained fewer bytes of FNN structured field data than was indicated by the Font Control structured field FNN data count.

Explanation:: The Font Control structured field within an outline font character set contained an FNN data count (bytes 36-39) that is greater than the total number of data bytes in all Font Name Map (FNN) structured fields.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the font character set problem.

0423-341

A Map Coded Font format 2, Coded Font Index, or Map Data Resource structured field, repeating group number ____, specified a horizontal scale factor ____, that is not valid.

Explanation:: An MCF-2 or MDR structured field specified a horizontal scale factor greater than 32,767.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the MCF-2, CFI, or MDR structured field.

0423-342

A Map Coded Font format 2 structured field, repeating group number ____, specified a horizontal size value ____ that is not valid.

Explanation:: An MCF-2 structured field specified a horizontal size value greater than 32,767. The horizontal size field is in bytes 6-7 of the Font Descriptor triplet, triplet ID X'1F'.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the MCF-2 structured field.

0423-343

A Map Page Segment structured field contained ____ repeating groups. The maximum number of repeating groups allowed is 127.

Explanation:: A Map Page Segment (MPS) structured field contained more than 127 repeating groups.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the MPS structured field.

0423-344

A Map Coded Font format 2 structured field or Map Data Resource, repeating group number ____, specified a vertical size value ____ that is not valid.

Explanation:: An MCF-2 or MDR structured field specified a vertical size value greater than 32,767.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the problem with the MCF-2 or MDR structured field.

0423-345

____ Code Page Index repeating groups were specified within a single-byte code page. All repeating groups after the first 256 were ignored

Explanation:: Only 256 Code Page Index (CPI) structured field can be processed within a single-byte code page. Any repeating groups after the first 256 are ignored. A code page is identified as a single-byte code page by the encoding scheme, bytes 42-43 of the Code Page Descriptor (CPD) structured field. If the low-order four bits of byte 42 does not contain X'2', then the code page is a single-byte code page. If byte 42 of the CPD is not present, the code page is a single-byte code page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the code page problem.

0423-346

The afpsplit forward space flag page value is past the end of the input file.

Explanation:: The number of pages specified with the afpsplit -f flag exceeded the number of pages in the input file.
System action:: The afpsplit program terminates; partial output may be produced.
User response:: Specify a valid page number with the -f flag.

0423-347

The afpsplit program detected invalid input.

Explanation:: The afpsplit program requires AFP input. Each structured field must begin with a X'5A'.
System action:: The afpsplit program terminates; partial output may be produced.
User response:: Ensure that only valid AFP input files are supplied to afpsplit

0423-348

The afpsplit program could not obtain system memory required for processing.

Explanation:: The afpsplit program could not obtain required memory because a malloc system call failed.
System action:: The afpsplit program terminates; partial output may be produced.
User response:: Ensure that sufficient memory is available in the system.

0423-349

Usage: afpsplit [-f<#>] [-p<#>] [-r#:#<,#:#,...>] [-fext <Formdef> [def] ] [-c <paths>] [-o <outfile>] [infile]. afpsplit reads and writes AFP files only. afpsplit reads from infile, or stdin if an infile is not specified. afpsplit writes to outfile, or stdout if an outfile is not specified with the -o option. afpsplit error messages are written to stderr. -fext is used to specify an external formdef as source for the medium controls. In this case, the medium controls are read only from the specified formdef. Any medium controls invocation in the InputFile need to refer to a medium map defined in the external formdef. Any medium controls defined inline, in the input document inline resource group, are ignored. If the external Formdef is not located in the default system resources directory, use the -c flag for defining custom resource paths. -def flag is used to specify that the external formdef is a default formdef for the medium controls. In this case, the medium controls are first searched inline, in the input document inline resource group. If any medium maps are found, they are used in the output document. Any medium map invocation need to refer a medium map defined here. If no medium maps are found in the document resource group, then the search continues in the external formdef. The -def flag can only be used together with the -fext flag. Otherwise, no medium controls are applied to the output document, even if the input file contains medium maps. -c specifies custom paths to search for the external formdef. One or more paths can be specified. The <paths> have the following format: path:path:path for AIX and Linux, path;path;path for Windows. The -c flag can only be used together with the -fext flag. At least one path needs to be defined for afpsplit to search for it. If the -fext flag is not used, then the -c flag has no effect. If no formdef is found in any of the path supplied, an error is triggered. -r#:#<,#:#,...> is used to specify the page ranges that can be extracted from the input file, where the ranges syntax is -rs1:e1,s2:e2..., is is the start value and ei is the end value of the i interval. Up to 10 intervals can be specified with this parameter. If the -fext flag is used, then the start and end interval values might be modified internally by the medium controls. As a result, some pages can appear more than once in the MO:DCA-P output. The delimitator between start and end value is ‘:’. The delimitator between page ranges is ‘,’. If no start value is specified for an interval, the first page is considered as start value. If no end value is specified for an interval, 999999999 is considered as end value. There must be at least one valid interval for the -r flag to work properly. The intervals are sorted ascending internally. This flag cannot be used in combination with -mm, -f, and -p flags. -f<#> uses the forward space function, where # is the number of pages to forward space (0 to 999999999) from the beginning of the input file to start extracting the page or range of pages. To start extracting on page n, forward space n-1 pages. If you do not specify the -f flag, the extraction starts at the beginning of the file. If you specify more than one -f flag, the last one you specify is used. -p<#> uses the page end function, where # is the number of pages to output before terminating (1 to 999999999). If you do not specify the -p flag, all pages from the forward space point to the end of the input file are included in the output file. If you specify more than one -p flag, the last one you specify is used.

Explanation:: The afpsplit command must be in the format described in the usage message. An afpsplit command was entered that did not comply with this format.
System action:: The afpsplit program terminates and no output is produced.
User response:: Use the syntax shown in this message.

0423-351

The ____ field has an invalid value, ____, for an actual destination profile.

Explanation:: The field named in the message contains an invalid value for an actual destination profile.
System action:: The requested operation is not performed.
User response:: If this message was displayed when you were adding an actual destination, return to the InfoPrint Manager SMIT Add a Printer panel and supply a valid value for the field. If this message was displayed when you were viewing or changing the contents of an actual destination profile, the profile can no longer be used with InfoPrint Manager. You must remove the actual destination and then add it again to create an acceptable actual destination profile.

0423-352

MVS Download Object: ____ - MVS Download connection error - Server "bind", "listen", or "accept" failure.

Explanation:: A communications failure occurred.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: Make sure the communications controller between the MVS system and pSeries is online. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-353

MVS Download Object: ____ - The MVS Download server cannot allocate working storage to receive a file. errno=____.

Explanation:: A system error has occurred.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-354

MVS Download Object: ____ - The MVS Download server cannot allocate working storage to receive a file. errno=____.

Explanation:: A communications problem has occurred.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-355

MVS Download Object: ____ - MVS Download communication error - Server "receive" or "send" error.

Explanation:: A communications error has occurred..
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: Make sure the communications controller between the MVS system and the client operating system is online.

0423-357

MVS Download Object: ____ - No file system is available for MVS Download processing.

Explanation:: There is no available free disk space in the file systems selected for use with MVS Download.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: Select file systems with reasonable available free space with which to start the MVS Download server.

0423-359

MVS Download Object: ____ - The MVS Download client sent an invalid buffer length (____.) to the server.

Explanation:: An error occurred during MVS Download processing.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-360

MVS Download Object: ____ - MVS Download file transmission was cancelled by the client.

Explanation:: The message is informational.
System action:: MVS Download stops processing the file that was cancelled by the client.
User response:: No response is required.

0423-361

MVS Download Object: ____ - The MVS Download server encountered a ____ error when restarting from a checkpoint, errno=____.

Explanation:: An MVS Download processing error occurred.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-362

MVS Download Object: ____ - The MVS Download server encountered a ____ error when checkpointing, errno=____.

Explanation:: An MVS Download processing error occurred.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-363

MVS Download Object: ____ - The MVS Download server encountered an error when executing the exit routine, errno=____.

Explanation:: The MVS Download server program could not run the exit routine.
System action:: None.
User response:: Ensure that the exit routine is installed in a directory within the system path and that the name specified with the -x flag of the MVS Download server invocation is correct. Check file system(s) to manually process the unprocessed received files that resulted from the failure of the MVS Download server to execute the exit routine.

0423-364

The InfoPrint Manager demonstration key is invalid or has expired.

Explanation:: The InfoPrint Manager program running on this machine is a demonstration version. The demonstration key is found in the file /var/psf/demokey. This file must contain exactly 28 lowercase alphabetic characters as supplied by InfoPrint Manager to the installer of InfoPrint Manager. In addition, each key has an encoded expiration date when it was created by InfoPrint Manager. Either the key file is invalid or the key has expired.
System action:: The InfoPrint Manager program ends.
User response:: To gather additional information, run the /usr/lpp/psf/bin/checkpsfkey program. Report this problem to your service representative.

0423-366

The output bin number ____, specified on the pdpdr command, is not supported or not available.

Explanation:: An output bin number was specified on the pdpr print submission. This bin is not available.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Specify a different output bin on the pdpr command, or do not specify an output bin. If no output bin is specified, InfoPrint Manager will select an output bin.

0423-367

The actual destination does not support duplex printing with more than one page on a side of a sheet.

Explanation:: A FORMDEF specified duplexing, or duplexing was specified on the pdpr command, and the FORMDEF specified than more than one page should be printed on a sheet side. The actual destination will not duplex when more than one page is placed on a sheet side.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Do not specify duplexing, or choose a FORMDEF that specifies that only one page should be placed on a sheet side.

0423-368

The actual destination does not support explicit page placement.

Explanation:: A FORMDEF specified explicit page placement, but the the actual destination does not support explicit page placement.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that does not specify explicit page placement, or choose an actual destination that supports explicit page placement.

0423-369

InfoPrint Manager will not print the print job in simplex mode because explicit page placement was specified by the FORMDEF.

Explanation:: A FORMDEF specified explicit page placement, and also specified duplex printing. Simplexing was specified on the pdpr command, or the actual destination cannot duplex. Normally, InfoPrint Manager would print in simplex mode while simulating duplexing by performing 'functional duplexing'. However, InfoPrint Manager cannot perform functional duplexing when explicit page placement is specified.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that does not specify explicit page placement, or choose an actual destination that can duplex, and make sure that simplexing is not specified on the pdpdr command.

0423-370

InfoPrint Manager will not print the print job in simplex mode because duplexing was specified on the pdpr command.

Explanation:: Duplexing was specified on the pdpr command, but the actual destination can not duplex. Normally, InfoPrint Manager would print in simplex mode while simulating duplexing by performing 'functional duplexing'. However, InfoPrint Manager will not perform 'functional duplexing' when duplexing is specified on the pdpr command.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If simplex printing is acceptable, then submit the job for printing again, but do not specify duplexing on the pdpr command. If simplex printing is not acceptable, choose an actual destination that can duplex.

0423-371

InfoPrint Manager will not substitute another bin number for bin number ____ because Media Selection Format 1 was specified by the FORMDEF.

Explanation:: A FORMDEF specified a specific input bin number, and also specified Media Selection Format 1. The bin cannot be used. Normally, InfoPrint Manager would substitute another bin. However, InfoPrint Manager will not substitute another bin when Media Selection Format 1 is specified.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that specifies a different input bin, or choose a FORMDEF that does not specify Media Selection Format 1. If printing from a different input bin is not acceptable, then if possible, correct the problem that prevents InfoPrint Manager from using the original bin.

0423-372

InfoPrint Manager will not print the print job in simplex mode because Media Selection Format 1 was specified by the FORMDEF, and the manual-feed or envelope bin was specified by the FORMDEF.

Explanation:: A FORMDEF specified duplex printing, but simplexing was specified on the pdpr command, or the actual destination can not duplex. Normally, InfoPrint Manager would print in simplex mode while simulating duplexing by performing 'functional duplexing'. However, InfoPrint Manager will not perform functional duplexing when Media Selection Format 1 is specified, and the manual-feed or envelope bin is also specified.
System action:: InfoPrint Manager stops processing the document at the point of the of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If printing from a different input bin is acceptable, choose choose a FORMDEF that specifies a different input bin. If simplex printing is acceptable, choose a FORMDEF that specifies simplex printing.

0423-373

The actual destination does not report any available output bin.

Explanation:: The actual destination does not indicate that any output bin is available.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Contact your system administrator.

0423-374

The actual destination does not report any available manual-feed bin. Media Selection Format 1 was specified, and an envelope bin was specified, by the FORMDEF.

Explanation:: A FORMDEF specified the manual-feed input bin, but the manual-feed input bin is not available.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If printing from a different input bin is acceptable, choose a FORMDEF that specifies a different input bin. If printing from a different input bin is not acceptable, choose an actual destination with an operational envelope bin.

0423-375

The actual destination does not report any available manual-feed bin. Media Selection Format 1 was specified, and an envelope bin was specified, by the FORMDEF.

Explanation:: A FORMDEF specified the manual-feed input bin, but the manual-feed input bin is not available.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: If printing from a different input bin is acceptable, choose a FORMDEF that specifies a different input bin. If printing from a different input bin is not acceptable, choose an actual destination with an operational manual-feed bin.

0423-376

The actual destination does not support printing more than one page on a side of a sheet.

Explanation:: A FORMDEF specified that more than one page should be printed on a sheet side. The actual destination will not place more than one page on a sheet side.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that specifies that only one page should be placed on a sheet side, or choose an actual destination that will place more than one page on a sheet side.

0423-377

The actual destination does not support page rotation.

Explanation:: A FORMDEF specified that a page should be rotated. The actual destination will not rotate pages.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that does not specify page rotation, or choose an actual destination that will rotate pages.

0423-379

Output bin number ____, specified on the output-bin or output-bin-numbers attribute is not supported or not available.

Explanation:: An output bin number was specified on the output-bin or output-bin-numbers attribute. This bin is not available.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Specify a different output bin, or do not specify an output bin. InfoPrint Manager will select an output bin.

0423-380

A simplex Medium Map was specified, but at least one PGP repeating group specified that a page should be placed on the back of the sheet.

Explanation:: A FORMDEF specified simplex printing, but also specified that at least one page should be placed on the back of the sheet. This is not a valid FORMDEF, and cannot be used.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing, starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the FORMDEF, or choose a different FORMDEF.

0423-381

InfoPrint Manager cannot open the file "pif". The system return code is ____

Explanation:: InfoPrint Manager attempted to open the pif file in the actual destination queue directory, but could not.
System action:: Initialization of the actual destination queue fails, and the job is left in the queue.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem.

0423-382

InfoPrint Manager cannot reinitialize the file "pif". The system return code is ____.

Explanation:: InfoPrint Manager closed the pif file, and attempted to reopen it in the actual destination queue directory, but could not.
System action:: Printing of the current job continues. However, InfoPrint Manager will not be able to honor any backspace or pause operator requests for this job.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem.

0423-383

InfoPrint Manager cannot read the file "pif". The system return code is ____.

Explanation:: InfoPrint Manager attempted to read the pif file, but could not.
System action:: Printing of the current job continues. However, InfoPrint Manager will not complete any pending backspace or pause operator requests for this job.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-384

InfoPrint Manager cannot complete a pause or backspace)operator request because the pif file does not contain any processing information in it.

Explanation:: InfoPrint Manager attempted to read the pif file to obtain necessary processing information for the operator request, but determined that the pif file is empty.
System action:: InfoPrint Manager terminates its processing of any pending pause or backspace operator requests. Subsequent backspace or pause operator requests will be ignored.
User response:: The pif file may have been corrupted in the filesystem. Stop the actual destination by using either the Disable Action icon on the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command. If the error persists, contact your service representative.

0423-385

InfoPrint Manager cannot complete a backspace operator request because the necessary processing information for the target backspace sheet is no longer available.

Explanation:: InfoPrint Manager attempted to locate the necessary backspace information in the pif file, but could not find it.
System action:: InfoPrint Manager terminates its processing of the pending backspace operator request.
User response:: If the print job is a large print job, InfoPrint Manager may have pruned the pif file because it grew to be too large in the filesystem. InfoPrint Manager issues message 0423-386 whenever it prunes the pif file because file space is constrained. If desired, increase the size of the filesystem, or redefine the maximum threshold value to a larger value.

0423-386

InfoPrint Manager cannot update the pif file because it is too large for the filesystem. Backspace and pause operator requests for this job may be ignored.

Explanation:: InfoPrint Manager attempted to update the pif file but could not. InfoPrint Manager resized the pif file to a size of 0, but still could not update the pif file.
System action:: Printing of the current job continues and subsequent backspace and pause requests for the current job are ignored.
User response:: The filespace threshold for the filesystem has been reached. Increase the size of the filesystem, or redefine the threshold value to a larger value.

0423-387

InfoPrint Manager cannot write to the file "pif". The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the pif file, but could not.
System action:: InfoPrint Manager terminates its processing of the pending backspace or pause operator requests. Subsequent backspace or pause operator requests for this job will be ignored.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the Actions Area on the GUI window or the pdshutdown command. Then restart the actual destination by using either using the Enable Action icon or the pdenable command.

0423-388

InfoPrint Manager cannot open the file ____. The system return code is ____.

Explanation:: InfoPrint Manager attempted to open the specified jif filename but could not.
System action:: InfoPrint Manager terminates its processing of the pending pause request. If the job is being resumed, InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem.

0423-389

InfoPrint Manager cannot open the /var/psf/interrupt/interrupt.xref file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to open the file /var/psf/interrupt/interrupt.xref but could not.
System action:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem..
User response:: InfoPrint Manager terminates its processing of the pending pause request. If the job is being resumed, InfoPrint Manager terminates its processing of the resume function.

0423-390

InfoPrint Manager cannot resume a paused job because the necessary job information file for the paused job cannot be found.

Explanation:: InfoPrint Manager attempted to locate the name of the paused job's job information file, but could not find it in the /var/psf/interrupt/interrupt.xref file.
System action:: InfoPrint Manager terminates processing of the resume function for this job.
User response:: Verify that the job was previously paused successfully. Examine the contents of the interrupt.xref file. If the filename of the job is found in the interrupt.xref file, the next entry in the interrupt.xref file will identify the name of the job information file corresponding to the paused job name. The job information file will have a suffix of 'jif'. If no such entry follows the job filename in the interrupt.xref file, then the interrupt.xref file is corrupted. Do not write to the interrupt.xref file while InfoPrint Manager operator requests are issued. While operator requests are not being issued, remove the entry corresponding to the filename of the job that could not be resumed. If the error persists, contact your service representative.

0423-391

InfoPrint Manager cannot read the /var/psf/interrupt/interrupt.xref file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to read the /var/psf/interrupt/interrupt.xref file, but could not.
System action:: InfoPrint Manager terminates its processing of a pending pause operator request. If the job is being resumed, InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-392

InfoPrint Manager cannot open the temporary file /var/psf/interrupt/interrupt.xref.bak. The system return code is ____.

Explanation:: InfoPrint Manager attempted to open the file /var/psf/interrupt.xref.bak, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem.

0423-393

InfoPrint Manager cannot write to the temporary file /var/psf/interrupt/interrupt.xref.bak. The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the /var/psf/interrupt/interrupt.xref.bak file, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-394

InfoPrint Manager cannot write to the /var/psf/interrupt/interrupt.xref file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the /var/psf/interrupt/interrupt.xref file, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function if the job is being resumed. Otherwise, InfoPrint Manager terminates its processing of the pending pause or backspace operator request.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-395

InfoPrint Manager cannot read the temporary file /var/psf/interrupt/interrupt.xref.bak. The system return code is ____.

Explanation:: InfoPrint Manager attempted to read the /var/psf/interrupt/interrupt.xref.bak file, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-396

InfoPrint Manager cannot write to the file ____. The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the specified jif file but could not.
System action:: InfoPrint Manager terminates its processing of the interrupt operator request.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window, or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-397

InfoPrint Manager cannot read the file ____. The system return code is ____.

Explanation:: InfoPrint Manager attempted to read to the file specified in the message, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window, or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-398

InfoPrint Manager cannot interpret data read from the /var/psf/interrupt/interrupt.xref file. The file may have been corrupted.

Explanation:: InfoPrint Manager read the /var/psf/interrupt/interrupt.xref file but did not recognize the data obtained from the file.
System action:: IInfoPrint Manager terminates its processing of the resume function if the job is being resumed. Otherwise, InfoPrint Manager terminates it processing of the pending interrupt operator request.
User response:: The /var/psf/interrupt/interrupt.xref file is corrupted. Report this problem to your service representative.

0423-399

InfoPrint Manager cannot read the file ____. The system return code is ____.

Explanation:: InfoPrint Manager attempted to read the segment list file named in the message, but could not.
System action:: InfoPrint Manager terminates its processing the file or the operator request at the point of the error.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action or the pdenable command.

0423-400

InfoPrint Manager cannot complete a backspace request because required print job data has been deleted to free up filespace in the filesystem.

Explanation:: One or more segment files in this segmented job has been deleted. These segment files are required to successfully complete the backspace request.
System action:: InfoPrint Manager terminates its processing of the pending backspace request
User response:: InfoPrint Manager deleted the print job data because it detected that filespace in the filesystem was approaching or had reached a maximum threshold. If necessary, increase the amount of space allotted for the filesystem.

0423-401

InfoPrint Manager cannot write to the file ____. The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the segment list file specified in the message, but could not.
System action:: InfoPrint Manager terminates its processing of the resume function if the job is being resumed. Otherwise, InfoPrint Manager terminates its processing of the pending pause or backspace operator request.
User response:: The return code in the message is defined in the AIX /usr/include/sys/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-402

Job-related messages have been written to the Job Message Log.

Explanation:: InfoPrint Manager stored job-related messages in the Job Message Log. Job-related messages will be logged and not printed.
System action:: None.
User response:: See the Job Message Log for the job-related messages.

0423-403

InfoPrint Manager could not write the job-related messages into the Job Message Log.

Explanation:: InfoPrint Manager could not write the job related messages into the Job Message Log. These messages will be logged and not printed.
System action:: InfoPrint Manager issues additional messages to the error log to further describe the error.
User response:: Examine the error log for related messages and correct the problem.

0423-404

InfoPrint Manager could not write the job-related messages into the Job Message Log because of a previously reported error.

Explanation:: InfoPrint Manager could not write the job-related messages into the Job Message Log because of a previously reported error. The job-related messages will be logged and not printed..
System action:: InfoPrint Manager does not print the job related messages.
User response:: Examine the error log for previously reported errors regarding the Job Message Log.

0423-406

InfoPrint Manager is processing a backspace request.

Explanation:: InfoPrint Manager has received a backspace request and is processing it. Another message will be issued when the processing of the request is complete.
System action:: InfoPrint Manager processes the backspace request.
User response:: This is an informational message; no response is required.

0423-407

InfoPrint Manager is unable to perform the requested backspace operation because of an error.

Explanation:: InfoPrint Manager encountered an error which prevented it from performing the requested backspace operation. The error has been reported in the InfoPrint Manager error log.
System action:: InfoPrint Manager stops processing the backspace request and continues printing the current job.
User response:: Check the InfoPrint Manager error log to determine the specific error which prevented processing of the request.

0423-408

InfoPrint Manager has backspaced job ID ____ from side ____ to side ____.

Explanation:: InfoPrint Manager has processed the backspace request and is backspacing the specified job from the specified side number.
System action:: InfoPrint Manager continues to print the job from the specified side number.
User response:: This is an informational message; no response is required.

0423-409

InfoPrint Manager is processing a pause request.

Explanation:: InfoPrint Manager has received a pause request and is processing it. Another message will be issued when the processing of the request is complete.
System action:: InfoPrint Manager processes the pause request.
User response:: This is an informational message; no response is required.

0423-410

InfoPrint Manager is unable to perform the requested pause operation because of an error.

Explanation:: InfoPrint Manager encountered an error which prevented it from performing the requested pause operation. The error has been reported in the InfoPrint Manager error log.
System action:: InfoPrint Manager stops processing the pause request and continues printing the current job.
User response:: Check the InfoPrint Manager error log to determine the specific error which prevented processing of the request.

0423-411

InfoPrint Manager is ignoring the requested pause operation because the actual destination is already at a job boundary.

Explanation:: InfoPrint Manager has received a pause request, but there is no job to pause because the actual destination is already at a job boundary.
System action:: InfoPrint Manager ignores the pause request and continues printing the next job, if any.
User response:: If you still need to pause the actual destination, resend the pause request. Before sending the request, ensure that the job that you want to print next on the actual destination you are pausing has the lowest priority level of the jobs on the queue for that actual destination.

0423-412

InfoPrint Manager has paused job ID ____ at document page ____ of copy ____.

Explanation:: InfoPrint Manager has processed the pause request and has paused the specified job at the specified side number.
System action:: InfoPrint Manager has saved information about the paused job so that the job can be resumed later from the point of interruption. InfoPrint Manager continues with the next job in the queue..
User response:: This is an informational message; no response is required. You can resume the paused job by selecting the Resume Action icon on the GUI window.

0423-413

InfoPrint Manager cannot resume job ID ____. The job will print from the beginning.

Explanation:: InfoPrint Manager encountered an error which prevented it from resuming the specified job. The error has been reported in the InfoPrint Manager error log.
System action:: InfoPrint Manager prints the job from the beginning..
User response:: Check the InfoPrint Manager error log to determine the specific error which prevented resuming the job.

0423-414

InfoPrint Manager has resumed job ID ____ at document page ____ of copy ____.

Explanation:: InfoPrint Manager has resumed the specified job at the specified document page number. The job was resumed using the information that was saved at the time the job was paused.
System action:: InfoPrint Manager begins printing the job at the specified document page number. InfoPrint Manager deletes the saved pause information so the job cannot be resumed again without being interrupted again.
User response:: This is an informational message; no response is required.

0423-415

InfoPrint Manager cannot find job name ____ in the /var/psf/interrupt/interrupt.xref file.

Explanation:: InfoPrint Manager attempted to resume the job, but the specified job name did not exist in the /var/psf/interrupt/interrupt.xref file.
System action:: InfoPrint Manager ignores the resume request and prints the job from the beginning.
User response:: Most likely, the job cannot be resumed because it was not paused successfully or has already been resumed. Otherwise, if you have not manually edited the /var/psf/interrupt/interrupt.xref file, report this problem to your service representative.

0423-416

InfoPrint Manager cannot complete printing of job ID ____ because a segment file required for the job has been deleted.

Explanation:: InfoPrint Manager attempted to print the specified job, but one or more of the segment files containing the print data (in directory /var/psf/segments) have been deleted. InfoPrint Manager may have deleted the segment files because Input Manager needed room in its work area to continue creating segment files.
System action:: InfoPrint Manager terminates printing of the job, and continues with the next job, if any.
User response:: Use the InfoPrint Manager SMIT Miscellaneous Configuration panel to access the Customize Input Manager panel. From here, you can determine what path(s) Input Manager is using for its work space. Either make more space available in that path, add another directory to the path, or increase the percentage of Input Manager work area reserved for retained jobs.

0423-417

The output bin value of ____ specified for this print job is not valid.

Explanation:: Valid output bin values are in the range of 1 to 65535. The output bin value was not within this range
System action:: InfoPrint Manager ignores the specified value and uses the output bin value specified in the actual destination profile.
User response:: Check the printed output to determine if it is acceptable. If it is not acceptable and printing from a different bin is required, enter a valid value for the required bin number, and send the print job again.

0423-420

The value of ____ specified for the x-image-shift is not valid.

Explanation:: The x-image-shift value is specified in millimeters and must be in the range -577.991 to 577.973 (approximately).
System action:: InfoPrint Manager ignores the x-image-shift specified and uses the equivalent offset value contained in the form definition associated with the print job.
User response:: Check the printed output to determine if it is acceptable. If it is not acceptable and printing from a different x-image-shift is required, enter a valid x-image-shift value and send the print job again.

0423-421

The value of ____ specified for the y-image-shift is not valid.

Explanation:: The y-image-shift value is specified in millimeters and must be in the range -577.991 to 577.973 (approximately).
System action:: InfoPrint Manager ignores the y-image-shift specified and uses the equivalent offset value contained in the form definition associated with the print job.
User response:: Check the printed output to determine if it is acceptable. If it is not acceptable and printing from a different y-image-shift is required, enter a valid y-image-shift value and send the print job again.

0423-422

InfoPrint Manager could not write the job-related messages into the Job Message Log because the maximum size for the Job Message Log has been reached, and wrapping of the Job Message Log was not enabled.

Explanation:: InfoPrint Manager could not write the job-related messages into the Job Message Log because the maximum size for the Job Message Log was reached. Wrapping of the Job Message Log is not enabled. The job-related messages will be logged and not printed.
System action:: InfoPrint Manager does not print the job-related messages and disables further use of the Job Message Log for the print queue.
User response:: Enable the wrap option for the Job Message Log.

0423-423

where: Name=Value have the following defaults:

Explanation:: Second part of three, for extended help when typing jsprof -h
System action:: None.
User response:: None.

0423-424

Usage: segprof [[

Explanation:: Usage statement for segprof. This command is not documented as an InfoPrint Manager feature and is subject to change.; segprof [[ [-f ] | (cancel job) [-i] | (show job status) [-o] | (delete retained jobs) [-p] | (clean up leftover segments) [-u] | (display usage statement) [-v] | (display contents of a segment list) [-x] | (delete job regardless of status) ] <filename(s)>]
System action:: Usage statement for segprof. This command is not documented as a InfoPrint Manager feature and is subject to change.
User response:: None.

0423-425

InfoPrint Manager cannot open file ____, which is a segment list file created by Input Manager.

Explanation:: The segment list file named in the message does not exist. Usually this is because InfoPrint Manager finished processing the job and Input Manager deleted the segment list file. However, the file could have been deleted accidentally by a user with write access to the file. Another possibility is that the permissions on the /usr/lpp/psf/bin/segprof file are not -r-sr-sr-x or the owner/group of that file is not root/printq.
System action:: The requested operation is not performed.
User response:: Back out of the current panel and request a list of jobs for the operation again. If the same job appears in the list again and the same error occurs when the action is performed, the segment list file has probably been deleted. The operation can no longer be performed on that job.

0423-426

File ____ does not have the correct format for a segment list.

Explanation:: The file you selected for the operation is not a valid segment list file.
System action:: The requested operation is not performed.
User response:: Back out of the current panel and request a list of jobs for the operation again. The job that caused the error should not appear in the list. If it does, use AIX commands to delete the file. If the error occurs again, use local problem-reporting procedures to report this message.

0423-428

InfoPrint Manager cannot complete your request for job ____ because the segment list cannot be updated.

Explanation:: When you attempt to resume, cancel, rerun, move, or pause the input for a job, InfoPrint Manager must update information in the segment list file for the job. InfoPrint Manager was unable to perform the update for the job you selected.
System action:: The requested operation is not performed.
User response:: Back out of the current panel and request a list of jobs for the operation again. If the same job appears in the list again and the same error occurs when the action is performed, use local problem-reporting procedures to report this message.

0423-430

You are not authorized to cancel jobs.

Explanation:: Your user ID is not authorized to cancel jobs. Authorization is granted by having execute authority on the file /var/psf/seglist/auth/cancel.
System action:: The job is not cancelled.
User response:: Your system support group can give you authority by modifying the access control list for the file /var/psf/seglist/auth/cancel. For more information, see the Using InfoPrint Manager for Production Printing publication.

0423-433

InfoPrint Manager cannot delete the retained job ____ because it is no longer in retained state.

Explanation:: Between the time that you displayed the list of retained jobs that could be deleted and the time that you selected a job, the state of the job you selected changed from retained to something else. Another user could have requested that the job be cancelled or rerun.
System action:: The retained job is not deleted.
User response:: Back out of the current panel and request a list of jobs for the operation again. The job that caused the error should not appear in the list. If it does, use local problem- reporting procedures to report this message.

0423-434

InfoPrint Manager cannot read Input Manager's work area path from the Input Manager customization file.

Explanation:: InfoPrint Manager cannot read the path specified as the Path used for work area on the SMIT Customizing the Input Manager panel. Perhaps no value was supplied for this option on that panel.
System action:: The Clean up operation is not performed.
User response:: Have your system support group enter a valid path in the Path used for work area field on the SMIT Customize InfoPrint Manager Input Manager panel.

0423-440

Your cancel request for job ____ was submitted successfully.

Explanation:: This message is displayed when a request has been submitted successfully but no immediate feedback is available on the final success of the request.
System action:: Your request will be processed and additional messages will be issued indicating whether the request failed or succeeded.
User response:: This is an informational message; no response is required.

0423-443

Your delete request for job ____ was submitted successfully.

Explanation:: This message is displayed when a request has been submitted successfully but no immediate feedback is available on the final success of the request.
System action:: Your request will be processed and additional messages will be issued indicating whether the request failed or succeeded.
User response:: This is an informational message; no response is required.

0423-444

InfoPrint Manager submitted your request for job ____ even though errors were encountered.

Explanation:: Processing continued on your request to resume or cancel a job despite errors that were reported previously.
System action:: See the other messages issued prior to this one to determine what action the system took.
User response:: See the user response for the other messages issued prior to this one to determine what action to take.

0423-445

Segment files have been successfully cleaned up.

Explanation:: The Cleanup request completed successfully.
System action:: None.
User response:: This is an informational message; no response is required.

0423-447

An error occurred while opening a file, popen errno=____.

Explanation:: The segprof program is unable to complete normal processing because of an error executing a popen( ) subroutine. The popen( ) subroutine call failed with errno indicated.
System action:: The requested operation is not performed.
User response:: Enter the man popen command to determine what action to take for the errno value shown in the message.

0423-448

Insufficient memory is available to perform your request.

Explanation:: InfoPrint Manager was unable to allocate sufficient memory to perform your request.
System action:: The requested operation is not performed.
User response:: Close some of the applications running on the system or add more memory to the pSeries.

0423-450

____ fields marked by asterisk must be present.

Explanation:: Third part of three, for extended help when typing jsprof-h
System action:: None.
User response:: None.

0423-451

The ____ keyword has an invalid value, ____, in a job script.

Explanation:: The job script keyword named in the message has an invalid value.
System action:: InfoPrint Manager checks the rest of the job script for errors and then stops processing.
User response:: You can edit the job script file directly to correct the error.

0423-452

The job script contains an invalid keyword, ____.

Explanation:: The keyword named in the message is not a valid keyword in an InfoPrint Manager job script.
System action:: InfoPrint Manager checks the rest of the job script for errors and then stops processing.
User response:: If you used an editor to create the job script, correct the keyword name in the job script file. If you used the InfoPrint Manager SMIT panels to create the job script, use local problem-reporting procedures to report this message.

0423-453

Keyword ____ in the job script is missing an equals sign.

Explanation:: The job script contains an entry for the keyword named in the message, but no equals sign follows the keyword. Keywords and values must be separated with an equals sign in job scripts.
System action:: InfoPrint Manager checks the rest of the job script for errors and then stops processing.
User response:: If you used an editor to create the job script, add the equals sign after the keyword name in the job script file. If you used the InfoPrint Manager SMIT panels to create the job script, use local problem-reporting procedures to report this message.

0423-454

Required keyword ____ was not found in the job script.

Explanation:: The job script does not have an entry for the required keyword named in the message.
System action:: InfoPrint Manager checks the rest of the job script for errors and then stops processing.
User response:: You can edit the job script file directly to correct the error.

0423-455

Insufficient memory is available to perform your request.

Explanation:: InfoPrint Manager was unable to allocate sufficient memory to perform your request.
System action:: The requested operation is not performed.
User response:: Close some of the applications running on the system or add more memory to the pSeries.

0423-456

The InfoPrint Manager SMIT code passed an invalid keyword, ____, to jsprof.

Explanation:: The keyword specified in with the -F flag to the jsprof program is not valid. This is an error in the InfoPrint Manager SMIT code.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-457

InfoPrint Manager cannot read job script file ____.js.

Explanation:: Either InfoPrint Manager could not open the job script file named in the message or the job script file contains errors. If job script file contains errors, InfoPrint Manager issued messages prior to this one describing those errors.
System action:: The requested operation is not performed.
User response:: Ensure that the job script file you specified exists and that you have read permission for the file. Use the information provided in previously issued messages to correct any errors in the job script.

0423-458

InfoPrint Manager cannot write to job script file ____, fopen errno=____.

Explanation:: The job script file named in the message cannot be opened for writing. The fopen( ) subroutine call failed with errno indicated.
System action:: The requested operation is not performed.
User response:: Enter the man fopen command to determine what action to take for the errno value shown in the message.

0423-459

Usage: .mkprof [-h] | [Name=Value...] | [[-F Name1:. ... :.NameN | -v] [printer.profile]]

Explanation:

This command is not documented as an InfoPrint Manager feature and is subject to change.

Where:

-h: Display the 'Name=' portion of valid Name=Value pairs along with an asterisk next to required pairs.
Name=Value...: These are the name and value pairs that make up an actual destination profile.
-F Name1:. ... :NameN: Formats output for use in SMIT stanzas.
-v: View actual destination profile.
printer.profile: Name of an actual destination profile with the .profileextension.

System action:

None.

User response:

None.

0423-460

where: Name=Value have the following defaults:.

Explanation:: Second of three parts to the extended usage message.
System action:: None.
User response:: None.

0423-461

____ fields marked by asterisk must be present.

Explanation:: Third part of three, for extended help when typing mkprof -h.
System action:: None.
User response:: None.

0423-462

InfoPrint Manager encountered an internal error. Field ____ contained an invalid default value ____ in an actual destination profile.

Explanation:: The default values in a code module are invalid.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-464

InfoPrint Manager encountered an internal error. An invalid field, ____, was found in an actual destination profile.

Explanation:: The mkprof program discovered a field that it did not recognize in an actual destination profile. The fields are created by the InfoPrint Manager SMIT code.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-465

InfoPrint Manager encountered an internal error. A field, ____, is missing an equals sign in an actual destination profile.

Explanation:: InfoPrint Manager encountered an internal error. A field, ' ', is missing an equals sign in an actual destination profile..
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-466

InfoPrint Manager encountered an internal error. A required field,____, is missing from an actual destination profile.

Explanation:: The mkprof program discovered a required field was not present in an actual destination profile. The fields are created by the InfoPrint Manager SMIT code.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-467

Insufficient memory is available to perform your request.

Explanation:: InfoPrint Manager was unable to allocate sufficient memory to perform your request.
System action:: The requested operation is not performed.
User response:: Close some of the applications running on the system or add more memory to the pSeries.

0423-468

The InfoPrint Manager SMIT code passed an invalid field, ____, to mkprof.

Explanation:: The field specified in with the -F flag to the mkprof program is not valid. This is an error in the InfoPrint Manager SMIT code.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-469

InfoPrint Manager encountered an internal error. A value ____ is invalid in an actual destination profile.

Explanation:: The field named in the message contains an invalid value in an actual destination profile.
System action:: The requested operation is not performed.
User response:: The profile can no longer be used with InfoPrint Manager. You must remove the actual destination and then add it again to create an acceptable actual destination profile.

0423-470

InfoPrint Manager cannot read actual destination profile ____.

Explanation:: The actual destination profile file named in the message could not be opened for reading.
System action:: The requested operation is not performed.
User response:: Ensure that the file exists and the user has read permission for the file. If those conditions are met, you may need to remove the actual destination and then add it again to create an acceptable actual destination profile.

0423-471

InfoPrint cannot open printer profile ____.

Explanation:: The printer profile file could not be opened for reading.
System action:: The requested operation is not performed.
User response:: Ensure that the file exists and the user has read permission for the file. If those conditions are met, you might need to remove the actual destination and then add it again to create an acceptable actual destination profile.

0423-472

The InfoPrint Manager SMIT code passed a PrinterName value that is greater than ____ characters long to mkprof.

Explanation:: The value specified for the PrinterName field is more than 8 characters long. This is an error in the InfoPrint Manager SMIT code.
System action:: The requested operation is not performed.
User response:: Use local problem-reporting procedures to report this message.

0423-473

Input Manager cannot open the job script named ________.

Explanation:: The job script named in the message was supplied on a psfin command. The job script either does not exist or you do not have read permission for the job script.
System action:: The psfin program terminates without processing any jobs.
User response:: Check that the job script exists and file permissions are set so that you can read the job script.

0423-474

Input Manager encountered an error while processing the job script.

Explanation:: The job script cannot be processed because of an error reported previously.
System action:: The psfin program terminates without processing any jobs.
User response:: Correct the error in the job script and submit the job again.

0423-475

Input Manager could not open the job script, open errno=____.

Explanation:: Input Manager was unable to open the job script file. The open( ) subroutine call failed with errno indicated.
System action:: The psfin program terminates without processing any jobs.
User response:: Enter the man open command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-477

The job script does not name any input files.

Explanation:: You submitted a print job with a job script that specifies file or tape input, but no file names are specified.
System action:: The psfin program terminates without processing any jobs.
User response:: If you are using the InfoPrint Manager SMIT panels, specify the names of the files you want to print in the Names of files to be submitted in the job field.

0423-478

Input Manager could not find any of the input files named in the server attributes file. The input files do not exist or you do not have read permission for them.

Explanation:: The job script specifies input files, but the files could not be found on the system where the pdpr program is running.
System action:: The psfin program terminates without processing any jobs.
User response:: Make sure the files specified for the job exist and are accessible on the system where the pdpr program is running. Check that the file permissions are set so that you have read permission for the files. Specify the files in either the Name of the InfoPrint Manager Attribute File field on the SMIT Submit an InfoPrint Manager Job panel or on the -X option of the pdpr command.

0423-479

Input Manager could not find server attribute file ________ to process file ____.

Explanation:: A server attribute file to process a file was not found. The server attribute file that was used to submit the print job specified the name of another server attribute file to be used for one or more input files. The server attribute named inside the originally submitted job script could not be found.
System action:: The program stops processing the file on which this error occurred. Any files processed by this program prior to this file are not affected. The program does not process any more files.
User response:: Ensure that any server attribute files named in either the Name of the InfoPrint Manager Attribute File field on the SMIT Submit an InfoPrint Manager Job field or the -X option on the pdpr command exist.

0423-480

Skipping to next file.

Explanation:: The server attribute file submitted with the print job specifies a wild card character in the -X option on the pdpr command, which names the input files for the job. When Input Manager resolves the wild card character, it assumes the character represents the first or last character in the file name. No matches were found for the file name pattern resolved from the wild card specification.
System action:: The program skips the file specified with this error and continues processing with any additional files specified in this server attribute file.
User response:: If you are missing output from some files, submit the job again, specifying the input file names explicitly. If you are using the InfoPrint Manager SMIT panels, specify the file names in the Names of files to be submitted in the job field. If you are using the -X option on the pdpr command, specify the file names there.

0423-481

Input Manager is processing file ____ with job script ________.

Explanation:: This status information informs the submitter which job script is being used to process a file.
System action:: The psfin program continues processing the file.
User response:: This is an informational message; no response is required.

0423-482

Input Manager could not open file ____, open errno=____..

Explanation:: Input Manager was unable to open an input file. The open( ) subroutine call failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man open command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-483

Input Manager processing for file ____ is complete.

Explanation:: All processing for an input file has been completed and the segment list file for the job has been placed on a print queue.
System action:: The psfin program continues processing with the next file.
User response:: This is an informational message; no response is required.

0423-484

Input Manager has completed processing for the job script.

Explanation:: Input Manager has completed its processing of the job script.
System action:: The instance of the psfin program created to process this job script closes.
User response:: This is an informational message; no response is required.

0423-486

Invalid sequence number ____ detected. The sequence number for the last volume read and processed was ____. Load the volume with sequence number ____ into tape drive ____. Waiting for tape drive ____ to be made ready.

Explanation:: The tape that is labeled in the drive indicated in the message does not have the sequence number that Input Manager expected. Most probably, the wrong tape was loaded in the tape drive.
System action:: The psfin program waits until the user loads another volume and makes the tape drive ready. Then the program checks the new volume for the correct sequence number.
User response:: Locate and load the correct volume. The correct volume will have a sequence number one greater than the last volume processed. After you load the volume, make sure the tape drive is in the ready state.

0423-487

Input Manager could not find job script "________" to process file #____ named ____.

Explanation:: A job script to process a file was not found. The job script that was used to submit the print job specified the name of another job script to be used for one or more input files. The job script named inside the originally submitted job script could not be found.
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If you are using the InfoPrint Manager SMIT panels, ensure that any job scripts named in the Names of files to be submitted in the job field exist. If you are using a job script with the psfin command, ensure that any job scripts named with the i_Filenames keyword exist.

0423-488

Skipping files #____ (header label), #____ (data file named ____) and #____ (trailer label).

Explanation:: The job script used to submit the job does not specify the next data file on the tape as part of the print job. This data file, its header label file, and its trailer label file are being skipped.
System action:: The psfin program skips over the indicated files and continues processing with the next file.
User response:: If you wanted this file to be printed, specify it in the list of files to be submitted in the job using the InfoPrint Manager SMIT panels or the i_Filenames keyword in the job script.

0423-489

Input Manager is processing file #____ (named ____) with job script ________.

Explanation:: This status information informs the submitter which job script is being used to process a file.
System action:: The psfin program continues processing the file.
User response:: This is an informational message; no response is required.

0423-490

Input Manager is advancing the tape to the next set of header labels.

Explanation:: A user cancelled the job that was being read from the tape. The psfin program is skipping over the rest of the cancelled data file and its corresponding trailer label.
System action:: The psfin program skips over the cancelled data file and its corresponding trailer label. The psfin program continues processing with the next file
User response:: This is an informational message; no response is required.

0423-491

Input Manager encountered an error while reading a trailer label, read errno=____.

Explanation:: Input Manager was unable to read the trailer label from a tape. The read( ) subroutine call failed with errno indicated..
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man read command to determine what action to take for the errno value shown in the message. The trailer label may not exist, or the tape may have been created incorrectly. Correct the tape and submit the job again.

0423-492

The number of blocks read in does not match the block count in the trailer label. Blocks read in: ____. Block count in trailer label: ____

Explanation:: Input Manager was processing data from a tape with IBM standard labels in the fixed block or variable block format. The number of blocks specified in the trailer label did not match the number of blocks Input Manager read.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Examine the output, if any, and determine if it is acceptable. Determine why there was a mismatch between the blocks on the tape and the block count in the trailer labels. The tape was probably created incorrectly. Correct the tape and submit the job again.

0423-493

Input Manager processing for file #____ (named ____) is complete.

Explanation:: All processing for an input file has been completed and the segment list file for the job has been placed on a print queue.
System action:: The psfin program continues processing with the next file.
User response:: This is an informational message; no response is required.

0423-494

Load the next tape in the sequence into tape drive ____. Waiting for tape drive ____ to be made ready.

Explanation:: Input Manager is waiting for you to load the next tape in a sequence of tapes for the job. After you load the tape, make sure the tape drive is ready.
System action:: The psfin program waits until the user loads another volume and makes the tape drive ready. Then the program checks the new volume for the correct sequence number.
User response:: Locate and load the correct volume. The correct volume will have a sequence number one greater than the last volume processed. After you load the volume, make sure the tape drive is in the ready state.

0423-495

Input Manager could not find job script "________" to process file #____..

Explanation:: A job script to process a file was not found. The job script that was used to submit the print job specified the name of another job script to be used for one or more input files. The job script named inside the originally submitted job script could not be found.
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If you are using the InfoPrint Manager SMIT panels, ensure that any job scripts named in the Names of files to be submitted in the job field exist. If you are using a job script with the psfin command, ensure that any job scripts named with the i_Filenames keyword exist.

0423-496

Input Manager is processing file #____ with job script ________.

Explanation:: This status information informs the submitter which job script is being used to process a file.
System action:: The psfin program continues processing the file.
User response:: This is an informational message; no response is required.

0423-497

Input Manager processing for file #____ is complete.

Explanation:: All processing for an input file has been completed and the segment list file for the job has been placed on a print queue..
System action:: The psfin program continues processing with the next file..
User response:: This is an informational message; no response is required.

0423-498

Input Manager is skipping file #____.

Explanation:: The job script used to submit the job does not specify the next data file on the tape as part of the print job. This data file is being skipped.
System action:: The psfin program skips over the indicated file and continues processing with the next file
User response:: If you wanted this file to be printed, specify it in the list of files to be submitted in the job using the InfoPrint Manager SMIT panels or the i_Filenames keyword in the job script

0423-499

Input Manager is advancing the tape to the next file..

Explanation:: A user cancelled the job that was being read from the tape. The psfin program is skipping over the rest of the cancelled data file..
System action:: The psfin program skips over the cancelled data file and continues processing with the next file.
User response:: This is an informational message; no response is required.

0423-500

Input Manager encountered an error while attempting to create a pipe, pipe errno=____.

Explanation:: Input Manager was unable to create a communications pipe. The pipe( ) subroutine call failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred and cancels the job, if one was created. Any files specified in the job script prior to this file will be processed normally. Any files specified in the job script following this file will not be processed.
User response:: Enter the man pipe command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-501

Input Manager encountered an error while attempting to create segment list ____.

Explanation:: Input Manager was unable to create a segment list file because the fopen ( ) or fclose( ) subroutine call on this segment list file name failed.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man fopen and man fclose commands to determine what action to take for the error.

0423-502

Input Manager encountered an error while attempting to write the header for segment list ____.

Explanation:: Input Manager was unable to write the header for this segment list file because the fwrite ( ) subroutine call on this segment list file name failed.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man fwrite command to determine what action to take for the error.

0423-503

InfoPrint Manager could not map the font character set FGID, GCSGID, width, vertical size combination to a font character set name.

Explanation:: InfoPrint Manager attempted to map a resident font character set to a font character set name, using information in the CHARSET.GRD mapping file. The CHARSET.GRD file did not contain a font character set name for the resident font character set.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-504

Input Manager encountered an error while attempting to load program ____, execv errno = ____

Explanation:

Input Manager was unable to load its segmenter program, an InfoPrint Manager transform program, a user exit program, or the InfoPrint Manager segprof program. The execv( ) subroutine call failed with errno indicated.

System action:

The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.

User response:

Enter the man execv command to determine what action to take for the errno value shown in the message. Some possible sources of error are:

The seg, segprof, or InfoPrint Manager transform program has been moved from the /usr/lpp/psf/bin directory.
psfin could not find the user exit program specified in the job script.
The permissions and ownership of the named program are incorrect.
The system does not have enough memory to execute the named program.

0423-505

Input Manager cannot process either a pause or cancel request at this time.

Explanation:: Input Manager has read in all the data for a job. You cannot interrupt or cancel the job at this point.
System action:: Input Manager ignores the interrupt or cancel request and continues processing the job.
User response:: If you need to cancel the job, hold down the Ctrl key and press the 'C' key to stop Input Manager. After pressing Ctrl-C, cancel the job.

0423-506

InfoPrint Manager could not map the code page name ____ to a CPGID, GCSGID combination.

Explanation:: InfoPrint Manager attempted to map a code page name to a resident code page, using the information in the CPGID.GRD mapping file. The CODEPAGE.GRD file did not contain a resident code page ID for the code page name.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-507

Tape drive ____ is in use.

Explanation:: Input Manager attempted to read data from the tape drive named in the message, but that tape drive is being used.
System action:: If this error occurs when Input Manager starts processing a job script, the psfin program terminates without processing any jobs. If this error occurs after Input Manager has already begun processing a job script, Input Manager attempts to access the tape drive again after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: If Input Manager did not process the job script, submit the job again when the tape drive is available.

0423-508

Tape drive ____ is not ready.

Explanation:: Input Manager attempted to read data from the tape drive named in the message, but that tape drive is not ready.
System action:: If this error occurs when Input Manager starts processing a job script, the psfin program terminates without processing any jobs. If this error occurs after Input Manager has already begun processing a job script, Input Manager attempts to access the tape drive again after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: If Input Manager did not process the job script, ensure that the tape drive is ready and submit the job again.

0423-509

Input Manager cannot find tape drive ____.

Explanation:: Input Manager attempted to read data from the tape drive named in the message, but the attempt failed because the tape drive is not defined to AIX.
System action:: If this error occurs when Input Manager starts processing a job script, the psfin program terminates without processing any jobs. If this error occurs after Input Manager has already begun processing a job script, Input Manager attempts to access the tape drive again after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: Ensure that you have specified a valid tape drive name in the job script or with the psfin command. If the tape drive name appears valid, determine why the system cannot locate the tape drive. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-510

Input Manager encountered an error while opening tape drive ____, open errno=____.

Explanation:: Input Manager was unable to open the tape drive specified in the job script or on the psfin command. The open( ) subroutine call on this tape drive failed with the errno indicated.
System action:: If this error occurs when Input Manager starts processing a job script, the psfin program terminates without processing any jobs. If this error occurs after Input Manager has already begun processing a job script, Input Manager attempts to access the tape drive again after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: Enter the man open command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-511

Input Manager encountered an error while setting the block size on tape drive ____, ioctl errno=____.

Explanation:: Input Manager was unable to set the block size for the tape drive specified in the job script or on the psfin command. The ioctl( ) subroutine call on this tape drive failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred and cancels the job for the file if one was created. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man ioctl command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-512

InfoPrint Manager cannot open the segment list file named ____.

Explanation:: InfoPrint Manager cannot open the segment list file named in the message because a malloc( ) or fopen( ) subroutine call failed.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Ensure that the segment list file named in the message exists in the /var/psf/seglist directory and that you have read and write permissions for the file. Enter the man fopen and man malloc commands to determine why each of those commands may have failed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-515

The object x or y origin ____, or ____ is out of range.

Explanation:: Both the X and Y coordinates of the page segment or object specified on the IPS, IOB or PPO structured field must be in the range of 0 - 32767. An IPS, IOB or PPO structured field was specified with an origin valued outside this range.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the print file and submit the print job again.

0423-517

The HDR2 label on the tape contains an unsupported value (____) in the Job/Job Step Identification field for a tape with UNKNOWN format

Explanation:: Tapes using the JES2 spool offload format have a format of UNKNOWN in the header label. The tape Input Manager was processing was identified as UNKNOWN, but the Job/Job Step Identification field in the HDR2 label does not contain the valid value (JES2) for a JES2 spool offload tape.
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Ensure that the correct tape is loaded in the tape drive. If the tape is in JES2 spool offload format, recreate the tape with the Job/Job Step Identification field set to JES2. If the tape is not in JES2 spool offload format, change the value of the i_Format keyword in the job script to passthrough and provide a user exit program to read the data from the tape. Supply the name of the user exit program in the i_Exit keyword in the job script.

0423-518

The format value (____) in the header label is not supported by Input Manager.

Explanation:: The format in the header label is not a supported format. InfoPrint Manager Input Manager supports IBM Fixed block, IBM Variable block, and UNKNOWN (used for JES2 spool offload)
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Ensure that the correct tape is loaded in the tape drive. If the correct tape is loaded, change the value of the i_Format keyword in the job script to a value supported by Input Manager. If the tape you want to process does not use one of those formats, specify Passthrough for the i_Format keyword and provide a user exit program to read the data from the tape. Supply the name of the user exit program in the i_Exit keyword in the job script.

0423-521

Input Manager detected that the ____ program terminated abnormally. The low-order 8 bits of the return code are ____.

Explanation:: A process started by the psfin program terminated abnormally. The name of the process is included in the message. The low-order 8 bits of the return code from the terminated process are included in the message.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If the process that terminated is an InfoPrint Manager transform program or the Input Manager seg program, consult the messages issued by those programs to determine the cause of the error. If the process that terminated is a user exit program, contact the author of the user exit program to report the error. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-522

Input Manager detected that the ____ program was unexpectedly terminated by signal #____.

Explanation:: A process started by the psfin program unexpectedly terminated because it received the signal specified in the message. The name of the process is included in the message.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Use the information in the /usr/include/sys/signal.h file to find out more about the signal named in the message. If the process that terminated is an InfoPrint Manager transform program or the Input Manager seg program, consult the messages issued by those programs to determine the cause of the error. If the process that terminated is an InfoPrint Manager transform program, you can try executing the transform program using its command interface (without submitting a print job) to receive more information about the cause of the error. If the process that terminated is a user exit program, contact the author of the user exit program to report the error. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-523

Input Manager is rewinding the tape..

Explanation:: The job script used for this job specified i_RewindBefore=yes, so Input Manager is rewinding the tape before attempting to read any data from it.
System action:: Input Manager rewinds the tape before performing any operations.
User response:: No response is necessary.

0423-524

A rewind failure occurred on tape drive ____, ioctl errno=____.

Explanation:: Input Manager was attempting to rewind the tape, as instructed by the job script, but an error occurred. The ioctl( ) subroutine call on this tape drive failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred and cancels the job for the file if one was created. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man ioctl command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-525

An attempt to rewind and unload a tape from tape drive ____ failed, ioctl errno=____.

Explanation:: Input Manager was attempting to rewind and unload the tape, as instructed by the job script, but an error occurred. The ioctl ( ) subroutine call on this tape drive failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred and cancels the job for the file if one was created. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man ioctl command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-526

InfoPrint Manager could not map the font character set name ____ to a resident font character set ID.

Explanation:: InfoPrint Manager attempted to map a font character set name to a resident font character set, using the information in the CHARSET.GRD mapping file. The CHARSET.GRD file did not contain a resident font character set ID for the font character set name.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-527

Load the tape with serial number ____ into tape drive ____ and press Enter when the tape drive is ready.

Explanation:: You requested that Input Manager resume processing a job that had been interrupted. To resume the job, you need to load the tape described in the message in the tape drive named in the message.
System action:: The psfin program waits for the Enter key to be pressed.
User response:: Load the tape described in the message into the tape drive named in the message. When you press the Enter key, processing of the job will resume.

0423-528

Load the tape containing the interrupted job into tape drive ____ and press Enter when the tape drive is ready.

Explanation:: You requested that Input Manager resume processing a job that had been interrupted. To resume the job, you need to load the tape containing the data for the interrupted job in the tape drive named in the message.
System action:: The psfin program waits for the Enter key to be pressed.
User response:: Load the tape for the interrupted job into the tape drive named in the message. When you press the Enter key, processing of the job will resume.

0423-529

Input Manager was expecting an IBM standard labeled tape, but a VOL1 header label was not found on the tape.

Explanation:: When you resume or cancel an interrupted job, Input Manager rewinds the tape and reads the VOL1 header label to determine if the correct tape is loaded in the tape drive. After rewinding the tape, Input Manager did not find a VOL1 header label on the tape.
System action:: Input Manager attempts to resume the interrupted job after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: Ensure that the correct tape is loaded in the tape drive before responding to the next Input Manager message.

0423-530

The wrong tape is loaded in the tape drive. The serial number of the tape in the tape drive is ____. Input Manager was expecting a tape with a serial number of ____.

Explanation:: When you resume or cancel an interrupted job, Input Manager rewinds the tape and reads the VOL1 header label to determine if the correct tape is loaded in the tape drive. After rewinding the tape and reading the VOL1 header label, Input Manager determined that the serial number of the tape loaded in the tape drive does not match the serial number of the tape that was loaded when the job was interrupted.
System action:: Input Manager attempts to resume the interrupted job after you respond to another Input Manager message requesting that you ensure that the correct tape is loaded in the drive and that the tape drive is ready.
User response:: Ensure that the correct tape is loaded in the tape drive before responding to the next Input Manager message.

0423-531

Input Manager is repositioning the tape to the file for the interrupted job.

Explanation:: When you resume an interrupted job, Input Manager repositions the tape to the file for the interrupted job. When you cancel an interrupted job, Input Manager repositions the tape to the point of interruption and then advanced to the next file on the tape that is specified in the job script.
System action:: When the repositioning is complete, Input Manager will attempt to resume processing the appropriate job.
User response:: No response is necessary.

0423-532

Input Manager is advancing the tape to the block on the tape where the job was interrupted.

Explanation:: When you resume an interrupted job, Input Manager repositions the tape to the file for the interrupted job. Input Manager has located the file and is now advancing to the block in the file where the job was interrupted.
System action:: When the repositioning is complete, Input Manager will attempt to resume processing the interrupted job.
User response:: No response is necessary.

0423-534

Input Manager encountered an error while attempting to read the header for segment list ____.

Explanation:: Input Manager was unable to read the header for this segment list file because the header was not in the correct format or insufficient memory was available.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Determine why the header for the segment list was incorrect or use the man malloc command to determine why insufficient memory was available for the psfin process. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-535

Input Manager has received a request to cancel a job.

Explanation:: Input Manager received a request to cancel a job.
System action:: The psfin program will stop processing the specified job only if the cancel request was received before input processing for the job was completed.
User response:: Wait for another message from Input Manager indicating whether the cancellation was successful or not.

0423-536

Input Manager cancelled the job.

Explanation:: Input Manager received a cancel request and has successfully cancelled the specified job.
System action:: The psfin program will continue processing the job script to determine if any additional input files were specified for processing.
User response:: No response is necessary.

0423-537

Input Manager processing continues with the next file specified in the job script.

Explanation:: After an interrupted job is cancelled, Input Manager processes any additional files specified in the job script named on the psfin command. For file input, the next file processed is the next file specified with the i_Filenames keyword in the job script. For tape input, the next file processed is the next file on the tape that was specified with the i_Filenames keyword.
System action:: Input Manager repositions the job to the start of the interrupted file, advances to the end of the interrupted file, and resumes its processing as instructed by the job script.
User response:: If you want to stop all processing for the tape currently loaded in the tape drive, cancel each job as Input Manager creates it.

0423-538

Input Manager is trying to resume the job again.

Explanation:: After the first attempt to resume the job failed, Input Manager is trying to resume the job again.
System action:: Input Manager attempts to resume the job.
User response:: Wait for another message from Input Manager indicating whether the resume request was successful or not.

0423-539

Input Manager has resumed the job.

Explanation:: Input Manager has successfully repositioned the tape to the point where the job was interrupted and is processing the job again.
System action:: The psfin program continues processing the job from the point of interruption.
User response:: No response is necessary.

0423-540

Input Manager cannot interrupt the job because it was already interrupted.

Explanation:: Input Manager received a request to interrupt the current job, but that job is already interrupted.
System action:: The psfin program ignores the interrupt request.
User response:: Someone else may have interrupted the job before you did. If you think the job should have a status other than Interrupted, use local problem-reporting procedures to report this message.

0423-541

Input Manager has received a request to interrupt the current job.

Explanation:: Input Manager received a request to interrupt the job that is currently being processed.
System action:: The psfin program records information about where its processing was interrupted so that the job can be resumed.
User response:: Wait for another message from Input Manager indicating whether the interrupt request was processed successfully or not.

0423-542

Input Manager has interrupted the job it was processing.

Explanation:: Input Manager received an interrupt request and has successfully interrupted the job it was processing.
System action:: Input Manager waits for a resume or cancel request for the interrupted job.
User response:: You can now use the input device that you interrupted to start another job. You can cancel or resume the interrupted job using the InfoPrint Manager SMIT Work with Jobs menu.

0423-543

Input Manager cannot resume the job because it is not interrupted.

Explanation:: Input Manager received a request to resume a job, but that job does not have a status of Interrupted.
System action:: The psfin program ignores the interrupt request.
User response:: Someone else may have resumed the job before you did. If you think the job should have a status of Interrupted, use local problem-reporting procedures to report this message.

0423-544

Input Manager has received a request to resume an interrupted job

Explanation:: Input Manager received a request to resume an interrupted job.
System action:: The psfin program attempts to resume processing at the point where the job was interrupted.
User response:: Wait for another message from Input Manager indicating whether the resume request was processed successfully or not.

0423-545

Input Manager was instructed to look for an interrupt, resume, or cancel request for job ____, but none was found.

Explanation:: InfoPrint Manager uses AIX signals to communicate job management requests to Input Manager. Input Manager received a signal, but no interrupt, resume, or cancel request was found.
System action:: The signal is ignored.
User response:: If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-546

Input Manager encountered an error while reading file ____, read errno=____.

Explanation:: Input Manager was unable to read data from the file specified in the message. The read( ) subroutine call on this file failed with the errno indicated.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man read command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-547

Input Manager detected an invalid record in AFP data.

Explanation:

The job script specified when this job was submitted specified a data type of AFPDS or MODCAP. The format of these files requires a 2-byte Length field followed by a data record whose length is the same as that specified in the Length field and where the first byte of data is a X'5A' character. Input Manager did not find the X'5A' character after the Length field. Possible causes of this error are:

The file containing the data stream was not edited correctly, and structured field information might have been deleted or modified to include unrecognizable data.
The file containing the data stream was not downloaded correctly from a host system (AFP files must be downloaded as binary files or translation errors occur).
The application that produced the data stream might be in error.
The wrong data type was specified for the input file.

See the 'MO:DCA Reference' for further information about the format of AFP structured fields.

System action:

The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.

User response:

If the input file does not contain an AFP data stream, change the data type specification and submit the job again. If the input file does contain AFP data, correct the process used to create or transfer the file and submit the job again.

0423-548

Input Manager encountered an error while writing to a pipe. ____ of ____ bytes were successfully written, write errno=____.

Explanation:: Input Manager was unable to complete writing data to its Segmenter program, an InfoPrint Manager transform program, or the Input Manager user exit. The write( ) subroutine call on this file failed with the errno indicated.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man write command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-550

Input Manager encountered an error while opening a process, popen errno=____.

Explanation:: Input Manager was unable to open a process to get a list of files. The popen( ) subroutine call failed with errno indicated.
System action:: The psfin program terminates without processing any jobs.
User response:: Ensure that the /etc/environment file does not contain any blank lines or invalid entries. Enter the man fork and man pipe commands to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-551

Input Manager could not find the file named ____..

Explanation:: Input Manager could not find the input file named in the message, which was specified with the i_Filenames keyword in a job script. If the file named in the message contains a wild card character, Input Manager executed an AIX ls command with that string and no file names matching that pattern were found. Wild card characters can only be used in the i_Filenames keyword to substitute for the first and last character position of a file name.
System action:: The psfin program terminates without processing any jobs.
User response:: Ensure that the file exists and that you have write permission for it. If necessary, change the wild card specification in the i_Filenames keyword in the job script.

0423-552

Input Manager encountered an error, fgets errno=____.

Explanation:: Input Manager was unable to read the results of an ls command. The fgets( ) subroutine call failed with errno indicated.
System action:: The psfin program terminates without processing any jobs.
User response:: Enter the man fgets command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-553

InfoPrint Manager could not map the code page CPGID, GCSGID combination ____, ____ to a code page name.

Explanation:: InfoPrint Manager attempted to map a resident code page to a code page name, using the information in the CPGID.GRD mapping file. The CPGID.GRD file did not contain a code page name for the resident code page.
System action:: InfoPrint Manager will attempt to complete processing of the font reference.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the MCF font reference successfully. Read all of the messages to determine how to change the MCF structured field or font mapping files so that the font reference can be processed successfully.

0423-554

** Press 'c' to continue, 'n' to load ** next volume, or 'q' to quit. ** Then press the Enter key.

Explanation:: Input Manager has detected a tape mark while reading data from tape.
System action:: Input Manager waits for a response.
User response:: Type c to request that Input Manager continue with the same tape, n to indicate that you want to load a new volume, or q to indicate that you want to stop processing the tape.

0423-555

Input Manager encountered an error which should cancel the job, but Input Manager was unable to change the input status of the job to Cancelled in the segment list file.

Explanation:: An error occurred which caused Input Manager to attempt to change the input status for the current job to Cancelled. Input Manager was unable to change the status in the segment list file for the job because the segment list file is not in the correct format.
System action:: Input Manager attempts an alternate method to cancel the job.
User response:: Use the information provided in previous Input Manager messages to correct the error that caused Input Manager to attempt to cancel the job.

0423-556

Input Manager encountered an error which should cancel the job, but Input Manager was unable to open the segment list file to change the input status to Cancelled.

Explanation:: An error occurred which caused Input Manager to attempt to change the input status for the current job to Cancelled. Input Manager was unable to change the status in the segment list file for the job because an open failure occurred.
System action:: Input Manager attempts an alternate method to cancel the job.
User response:: Use the information provided in previous Input Manager messages to correct the error that caused Input Manager to attempt to cancel the job.

0423-557

Input Manager is attempting to cancel job ____.

Explanation:: An error occurred which caused Input Manager to attempt to change the input status for the current job to Cancelled. Input Manager is now attempting to change the print status to Cancelled.
System action:: Input Manager attempts to cancel the job.
User response:: Use the information provided in previous Input Manager messages to correct the error that caused Input Manager to attempt to cancel the job.

0423-558

The Include Page Overlay (IPO) overlay origin ____, ____ is not valid.

Explanation:: Both the X and Y coordinates of the overlay origin specified on the IPO structured field must be in the range of 0 - 32767. An IPO was specified with an origin value outside of this range.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the overlay origin on the IPO structured field.

0423-560

An invalid value was supplied for the segment file size. The value must be between 1 and 102400.

Explanation:: The requested segment file size was invalid. This value was requested either by specification of a s_SegSize job script keyword or by specification of a s_SegmentSize in the /var/psf/js/system.option file. Valid values are from 1 to 102400 Kbytes. The field on the SMIT Submit an InfoPrint Manager Job panels that corresponds to the job script keyword is named Size of the AFP segment file created by InfoPrint Manager. The field on the SMIT Customize the Input Manager panel that corresponds to the Input Manager configuration file is named Default Segment File Size (K Bytes).
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Edit the job script to provide a valid value for the keyword.

0423-561

Usage: seg seg [-c < COM setup overrides job script >][-d < job script file descriptor >][-f < segment list file name >][-h < header labels file descriptor >][-j < job script name >][-q < print queue overrides job script >][-s < segment size (Kbytes) >][-t < trailer labels file descriptor >][-?]

Explanation:

This message should not be displayed if the psfin program is invoked with the -s flag. This is not a documented command and is not meant to be invoked by anyone or any program other than psfin. This command syntax is subject to change.

The command flags are used as follows:

-c < COM setup overrides job script>: Specified if (psfin -s -c setupfile)
-d < job script file descriptor >: Specified if (psfin -d -s)
-f < segment list file name >: Always specified if (psfin -s)
-h < header labels file descriptor >: Sometimes specified if (psfin -s)
-j < job script name >: Always specified if (psfin -s)
-q < print queue overrides job script >: Specified if (psfin -s -q queuename)
-s < segment size (Kbytes) >: Sometimes specified if (s_SegSize= and psfin -s)
-t < trailer labels file descriptor >: Sometimes specified if (psfin -s)
-?: Displays this usage message

System action:

The program reports message without further action.

User response:

None.

0423-562

The job cannot be submitted because no print queue was specified.

Explanation:: A print queue must be specified when a job is submitted. A queue name was not specified in the job script with the -p option on the pdpr command.
System action:: The print job is cancelled because of this error and the print job ends.
User response:: Submit the job again, ensuring that a print queue is specified.

0423-563

InfoPrint Manager cannot read the header of segment list file ____.

Explanation:: The header of the segment list could not be read because either the size of the header was incorrect or insufficient memory was available. The size of the header can change with corrective service to InfoPrint Manager.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: If corrective service was recently applied to InfoPrint Manager, ensure that the installation of that service completed normally. If that is not the problem, determine if sufficient memory is available to the seg program. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-564

An error occurred while opening segment file ____, fopen errno=____.

Explanation:: The seg program is unable to complete normal processing because of an error executing a fopen( ) subroutine. The fopen( ) subroutine call failed with errno indicated.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man fopen command to determine what action to take for the errno value shown in the message.

0423-565

The job has been placed on a print queue successfully.

Explanation:: InfoPrint Manager Input Manager has successfully enqueued the segment list for the job. Input Manager enqueues the segment list after the first segment file is written, so additional segment files may remain to be created..
System action:: Input Manager processing of the job continues.
User response:: This is an informational message; no response is required.

0423-566

A MODCA structured field does not have a carriage control character of X'5A'. The error occurred at byte number ____ in the data stream.

Explanation:: MODCA structured fields can optionally be identified with a carriage control character value of X'5A'. InfoPrint Manager Input Manager requires the X'5A' carriage control character, but one was not found at the location indicated in the message. You may have specified the wrong data type or tape format when you submitted the job.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Ensure that you specified the correct value for the type of data in the print file and the tape format, if the input file was read from tape. Determine if the structured field causing the error is in the input file or in a resource referenced by the input file. If the error is in the input file and the file provided to Input Manager was not MODCA or AFP data stream, the error resulted from an internal error in the InfoPrint Manager transform program that produced the MODCA output. If the error is in a MODCA or AFP data stream input file, the method used to produce the input file caused the error. If the error is in a resource, the method used to produce the resource caused the error. If the source of the error may be an InfoPrint Manager transform program, use local problem-reporting procedures to report this message. If the source of the error is not InfoPrint Manager, try creating the input file or resource again and submit the job again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-567

InfoPrint Manager Input Manager attempted to enqueue the segment list file with the command ____. The enq command failed.

Explanation:: The enq command issued by Input Manager to submit the print job failed. The command is shown in the message. The enq command issued a previous message indicating the cause of the failure.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Follow the information provided by the message issued by the enq command to determine the cause of the problem.

0423-568

An error occurred while opening a file, popen errno=____.

Explanation:: The seg program is unable to complete normal processing because of an error executing a popen( ) subroutine. The popen( ) subroutine call failed with errno indicated..
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man popen command to determine what action to take for the errno value shown in the message.

0423-569

An error occurred while reading ProPrinter ASCII data from standard input, read errno=____.

Explanation:: Input Manager encountered an error from the read subroutine when attempting to read ProPrinter ASCII data from standard input. The read subroutine call failed with errno indicated.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man read command to determine what action to take for the errno value shown in the message.

0423-570

An error occurred while writing to a temporary file, write errno=____.

Explanation:: Input Manager was attempting to write a file to standard output piped to the enq command. The write subroutine call failed with errno indicated. The /var/spool/qdaemon directory is probably out of space.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man write command to determine what action to take for the errno value shown in the message.

0423-571

The job has been placed on a print queue successfully.

Explanation:: The job containing ProPrinter ASCII data has been enqueued successfully.
System action:: The instance of InfoPrint Manager Input Manager associated with this job closes.
User response:: This is an informational message; no response is required.

0423-572

An error occurred while attempting to read a header or trailer tape label resource from a pipe, read errno=____.

Explanation:: InfoPrint Manager Input Manager encountered an error when it was reading a header or trailer tape label resource. Input Manager creates these resources as MODCA object containers when the tape label information is read from the tape. The read( ) subroutine call failed with errno indicated.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man read command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-573

InfoPrint Manager could not find the Input Manager customization file, fopen errno=____.

Explanation:: The seg program could not find the file that contains the customization settings for Input Manager. The fopen( ) subroutine call failed with errno indicated.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Enter the man fopen command to determine what action to take for the errno value shown in the message. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0423-574

The Input Manager customization file does not have an entry for write path.

Explanation:: An entry for the write path field is required in the file containing Input Manager customization settings. No entry was found. Someone may have edited the field and accidentally deleted the entry.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to define a path to Input Manager's work area.

0423-575

The value for the percentage of Input Manager's work area to use for retained jobs is not valid in the Input Manager customization file. A value of 50 is assumed.

Explanation:: The value provided on the SMIT Customize InfoPrint Manager Input Manager panel for the Percentage of work area for retained jobs option is not valid. Valid values range from 1 through 99..
System action:: Processing of the file continues. Input Manager uses 50 as the default value for this option.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to provide a valid value for this option.

0423-576

The value for the Path used for work area and percent to use threshold is not in the correct format in the Input Manager customization file.

Explanation:: The value provided on the SMIT Customize InfoPrint Manager Input Manager panel for the Path used for work area and percent to use threshold is not in the correct format. The format is: directory1 percent1:directory2 percent2.... where: directory is any valid directory on the system and percent is a whole number ranging from 1 through 99.
System action:: The print job is cancelled because of this error and the psfin program terminates.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to provide a value in the correct format for this option.

0423-577

The value for the percent to use threshold ____ for directory ____ is not valid in the Input Manager customization file. This directory is not used for the write path.

Explanation:: The value provided on the SMIT Customize InfoPrint Manager Input Manager panel for the Path used for work area and percent to use threshold contains an invalid value for the percent field. Valid values range from 1 through 99. The format for entering this value for a directory is: directory1 percent1:directory2 percent2.... where: directory is any valid directory on the system and percent is the percent of that directory that Input Manager can use as work area.
System action:: Processing of the file continues. Input Manager does not write any files to the directory named in the message.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to provide a valid value for this option.

0423-578

Directory ____ is specified in Input Manager's work area path in the Input Manager customization file, but the directory does not exist.

Explanation:: A directory specified in the Path used for work area option on the SMIT Customize InfoPrint Manager Input Manager panel does not exist.
System action:: Processing of the file continues. Input Manager does not write any files to the directory named in the message.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to correct the directory name.

0423-579

You specified more than the maximum number of file systems (____) in Input Manager's work area path in the Input Manager customization file. Directory ____ will not be used for the work area.

Explanation:: On the SMIT Customize InfoPrint Manager Input Manager panel, the entry for the Path used for work area option specifies more than the maximum number of file systems allowed for this option.
System action:: Processing of the file continues. Input Manager does not write any files to the directory named in the message.
User response:: Use the SMIT Customize InfoPrint Manager Input Manager panel to reduce the number of file systems specified for this option.

0423-580

InfoPrint Manager cannot open the /var/psf/interrupt/keys file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to open the /var/psf/interrupt/keys file, but could not.
System action:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem.
User response:: InfoPrint Manager terminates its processing of the pending interrupt operator request. If the job is being resumed, InfoPrint Manager terminates its processing of the resume function.

0423-581

InfoPrint Manager cannot read the /var/psf/interrupt/keys file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to read the keys file, but could not.
System action:: InfoPrint Manager terminates its processing of a pending interrupt operator request.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, stop the actual destination by using either the Disable Action icon from the GUI window or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-582

InfoPrint Manager cannot write to the /var/psf/interrupt/keys file. The system return code is ____.

Explanation:: InfoPrint Manager attempted to write to the /var/psf/interrupt/keys file, but could not.
System action:: InfoPrint Manager terminates its processing of the pending interrupt operator request.
User response:: The return code in the message is defined in the AIX /usr/sys/include/errno.h file. Determine the cause of the error and correct the problem. If necessary, terminate the actual destination by using either the Disable Action icon from the GUI window, or the pdshutdown command. Then restart the actual destination by using either the Enable Action icon or the pdenable command.

0423-607

Input Manager's work area is full and it cannot create any more data to send to output devices. The work area management method specified on the SMIT Customize InfoPrint Manager Input Manager panel determines whether Input Manager creates space automatically or if you have to manually create space.

Explanation:

Input Manager waits until space becomes available. If your work area management method is set to automatic, Input Manager may create space by deleting retained print jobs.

System action:

Input Manager waits until space becomes available. If your work area management method is set to automatic, Input Manager may create space by deleting retained print jobs.

User response:

If your work area management method is set to manual, you must create space in Input Manager's work area by deleting a job in retained state. To delete a job in retained state, use the SMIT Administer the InfoPrint Manager System panel. If your work area management method is set to automatic, Input Manager will create space by deleting jobs as they move to retained state, requiring no action on your part. To determine what work area management method is specified for your system, use the SMIT Customize InfoPrint Manager Input Manager panel. If Input Manager waits for long periods of time (for example, Input Manager doesn't access the tape drive very often or small jobs take a long time to process), you may have to create space in the work area by:

Cancelling jobs that show a status of *** error *** on the InfoPrint Manager SMIT Job Status panels
Deleting a job in retained state using the SMIT Administer the InfoPrint Manager System panel
Contacting your system administrator to expand the work area as described in Using InfoPrint Manager for Production Printing publication
Contacting your system administrator to decrease the percentage of the work area devoted to retained jobs on the SMIT Customize InfoPrint Manager Input Manager panel.

0423-610

Names of data files.

--------------------

0423-616

The auto-detect format cannot be used for nonstandard or unlabeled tapes.

Explanation:: The job script used for the job specifies i_Format=a, requesting that Input Manager auto-detect the tape format and i_Labeled=no, indicating that the file does not contain IBM standard labels. Input Manager can only perform auto-detection of the tape format on IBM standard labeled tapes.
System action:: The psfin program terminates without processing any jobs.
User response:: If the tape contains IBM standard labels, change the value for the i_Labeled keyword in the job script to yes and submit the job again. If the tape does not contain IBM standard labels, change the value for the i_Format keyword in the job script to another value. If the tape does not use one of the formats Input Manager supports, specify i_Format=p and supply a user exit program to read the data from the tape.

0423-618

InfoPrint Manager cannot open file ____, which is a segment list file created by Input Manager.

Explanation:: The segment list file named in the message does not exist. Usually this is because InfoPrint Manager finished processing the job and Input Manager deleted the segment list file. However, the file could have been deleted accidentally by a user with write access to the file.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Submit the job again.

0423-619

Insufficient memory is available to perform your request.

Explanation:: Input Manager was unable to allocate sufficient memory to perform your request.
System action:: The psfin program terminates without processing any jobs.
User response:: Close some of the applications running on the system or add more memory to the pSeries.

0423-620

No data was sent to Input Manager's segmenter program.

Explanation:: If you submitted a job containing PCL, PostScript, ditroff, line, DBCS ASCII, EUC, or unformatted ASCII data, the InfoPrint Manager transform program invoked by psfin did not produce any output. If you submitted a job containing AFPDS or MODCA-P data, the file was empty. If you invoked the Input Manager user exit, the exit program did not produce any output.
System action:: The psfin program cancels the job on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If an InfoPrint Manager transform program was run, look for messages issued by the transform program in its error log, if any. If the input file contained AFPDS or MODCA-P, determine why the file was empty. If the user exit program produced no output, report the error to the author of the user exit program.

0423-621

Input Manager encountered an error while skipping by tape marks on the tape loaded in drive ____, ioctl errno=____.

Explanation:: Input Manager was unable to skip to the desired location on the tape because of an error. The ioctl( ) subroutine call on this tape drive failed with errno indicated.
System action:: The psfin program stops processing the file on which this error occurred and cancels the job for the file if one was created. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Enter the man ioctl command to determine what action to take for the errno value shown in the message.

0423-622

Directory ____ does not contain any files.

Explanation:: The Font Library Utility determined that a directory specified on the command line does not contain any files except for parent or current directories.
System action:: The Font Library Utility does not complete processing. No character sets or code pages have been updated.
User response:: Ensure that directory name is correct. If the directory does not contain files to be processed, do not include it on the command line.

0423-623

The N-up format value ____, specified on the Medium Modification Control (MMC) structured field with ID ____, repeating group number ____, is not valid.

Explanation:: The MMC N-up format value must be in the range of 1 - 4. An MMC structured field specified an N-up format value that is outside of this range.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other documents in this print job, InfoPrint Manager resumes processing starting with the next document in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the MMC structured field within the FORMDEF.

0423-624

A Map Coded Font (MCF) structured field in a graphic or bar code or presentation text object specifies a font reference that is not duplicated in the Active Environment Group of the page or overlay.

Explanation:: If a graphic or bar code or presentation text object contains an MCF structured field, then each font reference in the MCF must be duplicated in an MCF in the Active Environment Group of the enclosing page or overlay, and the MCF repeating group in the Active Environment Group must specify local ID 254.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the page or overlay in error.

0423-625

The FORMDEF input bin ____ was overridden by the bin ____ specified on the enqueue command.

Explanation:: This is a supplemental message to aid in the analysis of a primary error message written to the message page.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the print job successfully. Read all of the messages to determine how to proceed.

0423-626

The duplexing specification ____ in the form definition was overridden by the value of ____ specified with the print request.

Explanation:: This is a supplemental message to aid in the analysis of a primary error message written to the message page.
System action:: InfoPrint Manager continues to process the print job.
User response:: This message will be accompanied by other messages that will indicate why InfoPrint Manager could not process the print job successfully. Read all of the messages to determine how to proceed.

0423-648

SNA Server/6000 is not running. It must be running.

Explanation:: The SNA Server/6000 product provides the data communication facilities used by this InfoPrint Manager instance. Therefore, this InfoPrint Manager instance requires that SNA Server/6000 be running.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Start SNA Server/6000. Root authority is normally required.

0423-649

The remote logical unit rejected the allocation request from this InfoPrint Manager instance because the user id and password in the allocation request are invalid or missing.

Explanation:: The user id and password specified in the configuration for this InfoPrint Manager instance are not valid on the remote system.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Correct the user id and password specified in the configuration for this InfoPrint Manager instance. They must be valid for the remote system with which this InfoPrint Manager instance tries to communicate.

0423-650

The remote logical unit rejected the allocation request from this InfoPrint Manager instance because it did not recognize the transaction program (TP) name in the allocation request.

Explanation:: The SNA Server/6000 side information profile for this InfoPrint Manager instance specifies a transaction program (TP) name that has not been defined to the remote system. The SNA Server/6000 side information profile for this InfoPrint Manager instance has the same name as the InfoPrint Manager actual destination.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Define the TP name on the remote system. For example, TP names can be defined to APPC/MVS by using the APPC/MVS Administration Utility to add a TP profile. If a usable TP name has already been defined on the remote system, refer to it in the SNA Server/6000 side information profile for this InfoPrint Manager actual destination.

0423-651

An SNA Server/6000 side information profile has not been added for this InfoPrint Manager instance or a profile has been added but is invalid.

Explanation:: The SNA Server/6000 side information profile indicates to this InfoPrint Manager instance the partner logical unit name, the mode name, and the remote transaction program (TP) name. So, to successfully communicate, this InfoPrint Manager instance requires the side information profile to exist and to be valid. The side information profile must have the same name as this InfoPrint Manager actual destination.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Create an SNA Server/6000 side information profile with the same name as this InfoPrint Manager actual destination. Specify the partner logical unit name, mode name, and remote transaction program (TP) name in the side information profile.

0423-652

The remote transaction program (TP) ended abnormally.

Explanation:: This InfoPrint Manager instance was communicating with a remote transaction program (TP). The remote TP ended abnormally.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Check diagnostic logs on the remote system to determine why the remote TP ended abnormally. Often, this failure occurs because the remote TP has insufficient access authority for resources on the remote server. This may occur, for example, if InfoPrint Manager is not configured to use a user id and password for the remote server.

0423-653

A session with the remote logical unit could not be established or was established but ended abnormally.

Explanation:

Several conditions can cause this message:

SNA Server/6000 could not establish a session with the remote logical unit:
- There is no SNA Server/6000 Partner LU 6.2 Location profile that indicates the node on which the remote LU resides.
- No link connection exists with the remote node.
- If the remote node runs the MVS operating system, the APPC and ASCH APPC/MVS subsystems are not active.
- The remote logical unit is not active.
SNA Server/6000 established a session with the remote logical unit but the session ended abnormally:
- SNA Server/6000 was stopped by the root login.
- If the remote node runs the MVS operating system, the APPC and ASCH APPC/MVS subsystems were stopped by the operator.
- Communication equipment between the local and remote nodes was powered off or malfunctioned.

System action:

InfoPrint Manager ends this InfoPrint Manager instance.

User response:

Ask your network administrator for assistance in identifying the type of failure that occurred and the reason for the failure. If the failure was not caused by a temporary outage, correct the configuration values, equipment, or operational procedures that caused the failure.

0423-654

The Internet Protocol (IP) address, ____, is not a valid IPv4/IPv6 address or hostname.

Explanation:: An IP address has form of IPv4 or IPv6 address. IP also allows hostnames, which are alphanumeric names that map to IP addresses. For example, 'biker' or 'biker.InfoPrint Manager.com'. Your AIX system can be configured to use either an IP name server or the /etc/hosts file to resolve hostnames into IP addresses.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: If you used a numeric address, it must have format of either IPv4 or IPv6 address. If you used a hostname, use SMIT to determine whether your AIX system is configured to use an IP name server. If your AIX system is configured to use an IP name server, ask your network administrator whether the name server IP address configured in your AIX system is correct and whether the hostname is known to the IP name server. If so, use the ping command to ensure that there is a network route between your AIX system and the IP name server. The ping command sends data to an IP host and waits for the IP host to return the data. If ping indicates that data can be successfully sent and echoed, there is a network route between the local IP host and the specified IP host. If your AIX system is not configured to use an IP name server, it uses the /etc/hosts file to resolve hostnames into IP addresses. Ensure that the hostname is included in the file and that it is mapped to the correct IP address.

0423-655

InfoPrint Manager cannot communicate with the server program at TCP port number ____ at Internet Protocol (IP) address ____.

Explanation:

Several conditions can cause this message:

The server program's IP address or port number is incorrect.
The server program is not running.
There is not a network route between the local IP host and the server program's IP host.

System action:

InfoPrint Manager ends this InfoPrint Manager instance.

User response:

Ensure that the server program is installed at the specified TCP port number at the specified IP address. Ensure that the server program is running. Attempt to 'ping' the server program's IP host. The ping command sends data to an IP host and waits for the IP host to return the data. If ping indicates that data can be successfully sent and echoed, there is a network route between the local IP host and the specified IP host. If data cannot be sent and echoed, ask your network administrator for assistance.

0423-656

InfoPrint Manager can no longer communicate with the program at TCP port number ____ at Internet Protocol (IP) address ____.

Explanation:

InfoPrint Manager successfully established a communication connection with the partner program. Later, a communication error occurred. Several conditions can cause this message:

The partner program ended abnormally.
Communication equipment between the local and remote nodes was powered off or malfunctioned.

System action:

InfoPrint Manager ends this InfoPrint Manager instance.

User response:

Check diagnostic logs on the remote system to determine whether the partner program ended intentionally. If it did not, ask your network administrator for assistance in identifying the type of failure that occurred and the reason for the failure.

0423-657

InfoPrint Manager could not open the "iconv" character code-set converter. FromCode = ____, ToCode = ____, error = ____.

Explanation:: The converter could not be initialized for the specified character code-sets.
System action:: The InfoPrint Manager instance continues but cannot convert some strings. Although print data is transmitted, some of the data's spool attributes may not be recorded on the actual destination spool.
User response:: Ensure that the specified character code-sets are valid and are installed on your AIX system. The ASCII and EBCDIC character code-sets used by this InfoPrint Manager instance are defined in the configuration for this InfoPrint Manager actual destination.

0423-658

The "iconv" character code-set converter could not convert a string from EBCDIC to ASCII or from ASCII to EBCDIC. The partially converted string is ____.

Explanation:: The string contains a character that is not valid in the source or target character code-set.
System action:: The InfoPrint Manager instance continues and uses the partially converted string.
User response:: Ensure that the ASCII and EBCDIC character code-sets specified in the configuration for this InfoPrint Manager actual destination are appropriate.

0423-659

File ____ contains data of a type that cannot be processed by this InfoPrint Manager instance. For example, the InfoPrint Manager instance cannot process ASCII datatype files.

Explanation:: This InfoPrint Manager instance only accepts AFPDS files and files that it can transform into AFPDS.
System action:: InfoPrint Manager removes the print job from the queue and continues with the next print job in the queue.
User response:: Refer to the Using InfoPrint Manager for Production Printing publication for information about the datatypes InfoPrint Manager can accept and can transform into AFPDS.

0423-660

The remote server detected an unrecoverable error. ____

Explanation:: The remote server detected an error, which it records in its diagnostic logs and reports to this InfoPrint Manager instance.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: Contact the server administrator on the remote system.

0423-661

The PostScript output command ____ was not successful.

Explanation:: The InfoPrint Manager SMIT Add a Printer panels for PostScript actual destination contains a Command to Execute for the actual destination output entry field. This field specifies the command that InfoPrint Manager runs when directing output to a PostScript actual destination. InfoPrint Manager cannot run the command contained in this field, either because the command does not exist or because it is not specified correctly.
System action:: InfoPrint Manager cannot run the output command.
User response:: Use the InfoPrint Manager SMIT panels to correct the entry in the Command to Execute for actual destination output entry field.

0423-662

A communication error occurred. The SNA Server/6000 error code is ____.

Explanation:: This InfoPrint Manager instance experienced an unrecoverable SNA Server/6000 error.
System action:: InfoPrint Manager ends this InfoPrint Manager instance.
User response:: The SNA Server/6000 error codes are described in the SNA Server/6000 Transaction Program Reference. If the error cannot be corrected, use local problem-reporting procedures to report this message.

0423-663

The remote server detected a recoverable error. ____.

Explanation:: The remote server detected an error, which it records in its diagnostic logs and reports to this InfoPrint Manager instance.
System action:: InfoPrint Manager continues processing the print job.
User response:: Contact the server administrator on the remote system.

0423-664

File ____, created by the InfoPrint Manager Input Manager from tape input, cannot be processed by this InfoPrint Manager instance.

Explanation:: This InfoPrint Manager instance cannot process files created from tape input by Input Manager.
System action:: InfoPrint Manager removes the print job from the queue and continues with the next print job in the queue.
User response:: This is an informational message; no response is required.

0423-917

ERROR: The actual destination reported an included page not previously saved with the specified text suppressions.

Explanation:: An Include Saved Page command attempted to include a page that was not previously saved with the appropriate text suppressions. The current Load Copy Control command specified a combination of text suppressions for which a copy of the page was not previously saved.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0423-918

The actual destination reported that an attempt was made to include a saved page that extends outside of the valid printable area.

Explanation:: The reported problem is: (1) a portion of a saved page included with an Include Saved Page command extends outside of the physical printable area, or (2) a portion of an overlay saved with a page and included with an Include Saved Page command, extends outside of the physical printable area, or (3) a user printable area has been specified and a portion of a saved page or an overlay saved with the page extends outside of the user printable area. One or more characters, rules, or images fall at least partially outside of the printable area. When the print job containing this error was sent, either the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel was set to All or Positioning, or the DATACK keyword value entered with the enq -o command was set to UNBLOCK or BLKCHAR.
System action:: InfoPrint Manager stops processing the page containing the error. Printing continues with the next page in the print job. The actual destination trims the saved page or page overlay to fit within the appropriate printable area.
User response:: Check that the correct form was loaded in the actual destination. To suppress these types of errors, either set the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel to None or Invalid character, or specify DATACK=BLOCK or DATACK=BLKPOS at the command line with the enq -o command.
Note: To correct the source of the problem, check for other error messages, and see their system actions and responses.

0423-919

The actual destination reported that an attempt was made to save a page that extends beyond the current logical page.

Explanation:: The reported problem is: (1) a portion of the page to be saved extends outside the current logical page, or (2) a portion of an overlay to be saved with a page extends outside of the overlay's current logical page. One or more characters, rules, or images fall at least partially outside of the current logical page. When the print job containing this error was sent, either the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel was set to All or Positioning, or the DATACK keyword value entered with the enq -o command was set to UNBLOCK or BLKCHAR.
System action:: InfoPrint Manager stops processing the page containing the error. Processing continues with the next page in the print job. The actual destination trims the page or page overlay to fit within the appropriate current logical page.
User response:: To suppress these types of errors, either set the Type of PRINT DATA ERRORS to report option on the InfoPrint Manager SMIT Start an InfoPrint Manager Print Job panel to None or Invalid character, or specify DATACK=BLOCK or DATACK=BLKPOS at the command line with the enq -o command.
Note: To correct the source of the problem, check for other error messages, and see their system actions and responses.

0423-920

The error occurred while printing page ____ of this print job.

Explanation:: This message identifies the page on which an error described in an accompanying message occurred. If this print job specified multiple copies, the message will only be issued for the first copy.
System action:: See the system actions for other error messages in this message group.
User response:: This is an informational message; no response is required.

0423-921

The error occurred while saving saved page group ____ with sequence number ____ and page name ____.

Explanation:: This message identifies the specific saved page on which an error described in an accompanying message occurred.
System action:: See the system actions for other error messages in this message group.
User response:: This is an informational message; no response is required.

0423-922

afpsplit cannot open the input file: ____.

Explanation:: The input file named in the message was supplied to the afpsplit command. The input file either does not exist or you do not have read permission.
System action:: The afpsplit program terminates.
User response:: Check that the input file exists and file permissions are specified such that you have read permission.

0423-923

Input Manager processing failed on file ____.

Explanation:: The Input Manager psfin program, an InfoPrint Manager transform, a user exit program, or the Input Manager seg program failed.
System action:: The psfin program stops processing the file on which the error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If the process that terminated is an InfoPrint Manager transform program or the Input Manager psfin or seg programs, consult the messages issued by those programs to determine the cause of the error. If the process that terminated is a user exit program, contact the author of the user exit program to report the error. If the error cannot be corrected or the error occurs again, use local problem- reporting procedures to report this message.

0423-924

Incorrect syntax, the correct syntax is: cfu [-d | -b] <cf file> [<build file>]

Explanation:: The coded font utility was invoked with incorrect syntax.
System action:: The cfu command terminates without producing any output.
User response:: Enter the cfu command again with the correct syntax.

0423-925

Input file ____ was not found.

Explanation:: The coded font utility could not open the input file.
System action:: The cfu command terminates without producing any output.
User response:: Enter the cfu command again, specifying a valid input file.

0423-926

cfu could not read input file ____.

Explanation:: The coded font utility could not read the input file into internal memory.
System action:: The cfu command terminates without producing any output.
User response:: Use local problem-reporting procedures to report this message.

0423-927

The size of input file ____ could not be determined.

Explanation:: The coded font utility could not determine the size of the input file.
System action:: The cfu command terminates without producing any output.
User response:: Use local problem-reporting procedures to report this message.

0423-928

Output file ____ exists and will not be overwritten.

Explanation:: The coded font utility discovered that the output coded font file already exists. cfu will not overwrite it.
System action:: The cfu command terminates without producing any output.
User response:: Enter the cfu command again, specifying a name for the coded font file that is not already used.

0423-929

Structured field ____ could not be located in the coded font.

Explanation:: The coded font utility could not locate the structured field named in the message, which is required in a coded font.
System action:: The cfu command terminates without producing any output.
User response:: Correct the error in the coded font and enter the cfu command again.

0423-930

Additional memory could not be allocated.

Explanation:: The coded font utility could not allocate additional memory for processing.
System action:: The cfu command terminates without producing any output.
User response:: Use local problem-reporting procedures to report this message.

0423-931

Characters ____ in the section identifier field in the cfu build file cannot be converted to hex.

Explanation:: The coded font utility encountered a section identifier in the build file which could not be converted to hexadecimal.
System action:: The cfu command terminates without producing any output.
User response:: Correct the build file and enter the cfu command again.

0423-932

Section identifier ____ is missing or invalid on on line number ____ in the cfu build file.

Explanation:: The coded font utility discovered a section identifier in the build file which was either missing or had an invalid format. The valid format is X'ab', where a and b are valid hexadecimal characters 0-9 and A-F.
System action:: The cfu command terminates without producing any output.
User response:: Correct the build file and enter the cfu command again.

0423-933

The character set name is missing from line number ____ in the cfu build file.

Explanation:: The coded font utility discovered a missing character set name on line ____ of the build file.
System action:: The cfu command terminates without producing any output.
User response:: Correct the build file and enter the cfu command again.

0423-934

The code page name is missing from line number ____ in the cfu build file.

Explanation:: The coded font utility discovered a missing code page name on line ____ of the build file.
System action:: The cfu command terminates without producing any output.
User response:: Correct the build file and enter the cfu command again.

0423-935

The resident indicator is missing from line number ____ in the cfu build file.

Explanation:: The coded font utility discovered a missing resident indicator on line number ____ of the build file. Valid download indicators are 0 and 1.
System action:: The cfu command terminates without producing any output.
User response:: Correct the build file and enter the cfu command again.

0423-936

cfu is unable to create new coded font file ___.

Explanation:: The coded font utility cannot open the new coded font file.
System action:: The cfu command terminates without producing any output.
User response:: Use local problem-reporting procedures to report this message.

0423-938

The value ____ for the Object Type in the Include Object Container (IOB) structured field is not valid.

Explanation:: InfoPrint Manager has detected an invalid value in the Object Type field of the Include Object Container (IOB) structured field.
System action:: Correct the print file, and submit the print job again.
User response:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

0423-939

Object rotation ____ is not supported by the actual destination.

Explanation:: InfoPrint Manager actual destination supports only the following values for object rotations: X'0000' (0 degrees), X'2D00' (90 degrees), X'5A00' (180 degrees), and X'8700' (270 degrees). Either the Include Object Container (IOB), Include Page Overlay (IPO), or Page Modification Control (PMC) structured field contains an object rotation other than one of these four values or the Preprocess Presentation Object (PPO) structured field contains an out-of-range value in the object orientation field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the print file, and submit the print job again.

0423-940

The object type ____ contained within the Begin Object Container (BOC) and End Object Container (EOC) structured fields is not a supported object type or is not supported in this context.

Explanation:: An unsupported object was encountered within an object container (BOC/EOC). The object is either not supported by the printer or not supported in this context.
System action:: InfoPrint Manager application stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager application resumes processing starting with the next file in the job; otherwise, InfoPrint Manager application cancels the job.
User response:: Correct the print file, and submit the print job again.

0423-941

The document name ____ contained within the Include Page (IPG) structured field has not been mapped as a saved page resource in a resource group (BR/ER).

Explanation:: A document name has been encountered on an IPG structured field that was not previously encountered as a document resource in a resource group. The document name on the IPG structured field provides mapping information to saved pages in the actual destination.
System action:: Correct the print file, and submit the print job again.
User response:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

0423-942

The page name ____ for document ____ contained within the Include Page (IPG) structured field has not been mapped as a saved page resource in a resource group (BR/ER).

Explanation:: A page name has been encountered on an IPG structured field that was not previously encountered within a document resource in a resource group. The page name on the IPG structured field provides mapping information to saved pages in the actual destination.
System action:: Correct the print file, and submit the print job again.
User response:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

0423-943

The token name on the Begin Document (BDT) structured field is mandatory when explicitly saving pages.

Explanation:: A BDT structured field was encountered within a document resource of a resource group (BR/ER) that did not contain a token name. The document name provides mapping information to saved pages in the actual destination.
System action:: Correct the print file, and submit the print job again.
User response:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

0423-944

ERROR: The font character set ____ is marked as an extension to a base printer-resident font character set with FGID ____ and GCSGID ____. This base font character set is not resident in the actual destination.

Explanation:: The Extension Font Resource flag is set in the font character set (byte 3, bit 1 of the Font Control structured field) indicating that the font character set is an extension to a 'base' printer-resident font character set. However, the font character set identified as the base font is not resident in the actual destination. The Graphic Character Set Global ID (GCSGID) of the base font character set is specified on the Extension Font Triplet (bytes 42-45) of the Font Control structured field, and the Font Global ID (FGID) of the base font character set is specified in bytes 78-79 of the FONT Descriptor structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the font character set and submit the job again.

0423-949

Resident activation failed for code page ____, character set ____, section ____. This coded font section will be downloaded.

Explanation:: InfoPrint Manager can not activate this DBCS section on the actual destination.
System action:: None.
User response:: InfoPrint Manager will attempt to complete the coded font by downloading the section from disk.

0423-966

Grid mapping failed for code page ____, character set ____. All sections in this coded font will be downloaded.

Explanation:: InfoPrint Manager can not map this code page or character set name to an actual destination id.
System action:: None.
User response:: InfoPrint Manager will attempt to complete the coded font by downloading all sections from disk.

0423-971

InfoPrint Manager is processing a forward space request..

Explanation:: InfoPrint Manager has received a forward space request and is processing it. Another message will be issued when the processing of the request is complete.
System action:: This is an informational message, no response is required.

0423-972

InfoPrint Manager is unable to perform the requested forward space operation because of an error.

Explanation:: InfoPrint Manager encountered an error which prevented it from performing the requested forward space operation. The error has been reported in the InfoPrint Manager error log.
System action:: InfoPrint Manager stops processing the forward space request and continues printing the current job.
User response:: Check the InfoPrint Manager error log to determine the specific error which prevented processing of the request.

0423-973

InfoPrint Manager is forward spacing ____ sides in job ____, starting from side ____.

Explanation:: InfoPrint Manager has processed the forward space request and is skipping the specified number of sides before starting to print again.
System action:: InfoPrint Manager continues to print the job after skipping the specified number of sides.
User response:: This is an informational message; no response is required.

0423-976

The actual destination reported an HRI location in a Bar Code Data (BDA) command that is either invalid or not supported.

Explanation:: The Human Readable Interpretation (HRI) location specified in the Flag byte is invalid or is unsupported. The BDA structured field is contained in a bar code object. The bar code object may be contained in an overlay or MO:DCA data.
System action:: The actual destination you were using may attempt to print the page in error. The entire page may not be printed. InfoPrint Manager continues processing the current job with the page following the page in error.
User response:: Correct the error in the bar code object and resubmit the print request.

0423-977

The actual destination reported a GOCA object with an image width that is too large.

Explanation:: The image width value specified in a Begin Image drawing order exceeds the maximum supported image width. The drawing order is contained in a Graphics Data (GAD) structured field. The GAD structured field is contained in a graphics object. The graphic object may be contained in MO:DCA data or an overlay.
System action:: The actual destination you were using may attempt to print the page in error. The entire page may not be printed. InfoPrint Manager continues processing the current job with the page following the page in error.
User response:: Correct the error in the graphics object and resubmit the print request.

0423-978

The actual destination reported a GOCA object with an image height that is too large.

Explanation:: The image height value specified in a Begin Image drawing order exceeds the maximum supported image width. The drawing order is contained in a Graphics Data (GAD) structured field. The GAD structured field is contained in a graphics object. The graphic object may be contained in MO:DCA data or an overlay.
System action:: The actual destination you were using may attempt to print the page in error. The entire page may not be printed. InfoPrint Manager continues processing the current job with the page following the page in error.
User response:: Correct the error in the graphics object and resubmit the print request.

0423-979

The actual destination reported that a print quality level specified in the form definition cannot be provided by the selected font.

Explanation:: The print quality level specified in the Medium Modification Control (MMC) structured field cannot be provided by the font selected to print the data. The MMC structured field is contained in the form definition. If no font was explicitly specified within the MO:DCA data the default actual destination font was being used.
System action:: InfoPrint Manager terminates the processing and printing of the page.
User response:: If the specified print quality level is required, select a font that can be printed at that print quality level and resubmit the print request. If the selected font is required, specify a print quality level in the form definition that is supported by that font and resubmit the print request.

0423-980

The actual destination reported an Absolute Move Baseline (AMB) command that is either not valid or not supported.

Explanation:: An unsupported advancement of the baseline coordinate toward the I-axis was detected. The invalid or unsupported baseline movement occurred within an Absolute Move Baseline (AMB) structured field contained in a text object. The text object may be contained in a MO:DCA data or an overlay.
System action:: The actual destination you were using may attempt to print the page in error. The entire page may not be printed. InfoPrint Manager continues processing the current job with the page following the page in error.
User response:: Correct the error in the text object and resubmit the print request.

0424-034

The job script contains an invalid value for the maximum number of pages to process ahead of an output device. You need to use a value of 500 or greater.

Explanation:: The maximum-transform-pages-ahead attribute contains an invalid value. Valid values are 500 or greater. The field on the InfoPrint Manager SMIT Submit an InfoPrint Manager Job panels that corresponds to the maximum-transform-pages-ahead attribute is MAXIMUM number of pages to process ahead of an output device.
System action:: Input Manager ignores the value you specified and uses a value of 500.
User response:: Edit the attribute file to provide a valid value for the keyword.

0424-035

Input Manager cannot create any more data for printing until an output device stacks some output. If your output device is not running at rated speed or hangs, edit the job script and increase the maximum-transform-pages-ahead attribute. The field on the SMIT Submit an InfoPrint Manager Job panels that corresponds to the maximum-transform-pages-ahead attribute is MAXIMUM number of pages to process ahead of an output device. When you have changed the SMIT panel, cancel this job and resubmit it.

Explanation:: Input Manager has reached the maximum number of pages it can process ahead of an output device.
System action:: Input Manager waits until some pages have been stacked on an output device. When some pages have been stacked, Input Manager creates more pages.vv
User response:: If your output device is not running at rated speed or hangs, edit the job script to provide a larger value for the keyword. Cancel the job and resubmit it.

0424-047

ERROR: The actual destination reported that the logical-page-extent values for the page to be saved are too large.

Explanation:: The current page size is larger then the actual destination's maximum physical page size. You must resubmit the job with a page size that is less than or equal to the actual destination's maximum page size. The logical-page-extent values specified in the most recently received Logical Page Descriptor (LPD) command are too large for a page to be saved. This exception is detected when processing the Begin Page command for a page to be saved.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-048

ERROR: The actual destination reported a color space field had an invalid or unsupported value.

Explanation:: The actual destination reported one of the following conditions occurred: The color space field in a Color Specification (X'4E')triplet contained an invalid or unsupported value. The triplet occurred in either a Logical Page Descriptor (LPD), Write Image Control 2 (WIC2), Write Graphics Control (WGC), Write Bar Code Control (WBCC), Write Object Container Control (WOCC) command, Write Text Control (WTC) command, Rasterize Presentation Object (RPO) command, or an Include Data Object (IDO) command. The color space field in a PTOCA Set Extended Text Color (SEC) control sequence contained an invalid or unsupported value. The control sequence occurred in a Write Text command.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Use local problem-reporting procedures to report this message.

0424-049

ERROR: The actual destination reported a color value field had an invalid or unsupported value.

Explanation:

The printer reported one of the following conditions occurred:

The color value field in a Color Specification (X'4E')triplet contained an invalid or unsupported value. The triplet occurred in either a Logical Page Descriptor (LPD), Write Image Control 2 (WIC2), Write Graphics Control (WGC), Write Bar Code Control (WBCC), Write Object Container Control (WOCC) command, Write Text Control (WTC) command, Rasterize Presentation Object (RPO) command, or Include Data Object (IDO) command.
The color value field in a PTOCA Set Extended Text Color (SEC) control sequence contained an invalid or unsupported value. The control sequence occurred in a Write Text command.
The color value field in a GOCA Set Process Color drawing order in an IPDS Write Graphics command contains an invalid or unsupported value.
A highlight color number is in the range x'0100' - x'FFFF', but a host-invoked Indexed CMR is not found.
An Indexed CMR is selected for use with a highlight color value, but the color value is not found in the Indexed CMR. Note that only the selected Indexed CMR is searched for this color value.

System action:

If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.

User response:

Use local problem-reporting procedures to report this message.

0424-050

ERROR: The actual destination reported a coverage field, shading field or both have an invalid value.

Explanation:: One of the following conditions occurred: Either the coverage field, the shading field, or both in a Color Specification (X'4E') triplet for a highlight color contained an invalid value. The triplet occurred in either a Logical Page Descriptor (LPD), Write Image Control 2 (WIC2), Write Graphics Control (WGC), Write Bar Code Control (WBCC), or Write Object Container Control (WOCC) command, Write Text Control (WTC) command, Rasterize Presentation Object (RPO) command or Include Data Object (IDO) command OR Either the coverage field, the shading field, or both in a PTOCA Set Extended Text Color (SEC) control sequence for a highlight color contained an invalid value. The control sequence occurred in a Write Text command.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Use local problem-reporting procedures to report this message.

0424-052

MMU: Fatal error in checking the cache file status.

Explanation:: The Medium Map Utility uses a temporary cache file to generate multiple copies requested by the -m option. Before writing each set of pages to the cache file, the file system containing the cache file is checked for space availability. The system call to perform this check has failed.
System action:: The Medium Map Utility terminates.
User response:: Check the cache file system /var/psf/mmu and try again. If the problem persists, call your service representative.

0424-053

MMU: No space left on the file system to write to the cache file directory ____.

Explanation:: The Medium Map Utility uses a temporary cache file to generate multiple copies requested by the -m option. The file system containing the cache file is full.
System action:: The Medium Map Utility terminates.
User response:: Make more space available in the file system and try again.

0424-054

MMU: Fatal error in trying to truncate the cache file.

Explanation:: The Medium Map Utility uses a temporary cache file to generate multiple copies requested by the -m option. The cache file is truncated before writing each set of pages. The truncation failed.
System action:: The Medium Map Utility terminates.
User response:: Check the cache file system /var/psf/mmu and try again. If the problem persists, call your service representative.

0424-055

MMU: Illegal value for option -n : ____

Explanation:: The number of pages to be cached must be greater or equal 1.
System action:: The Medium Map Utility terminates.
User response:: Call the MMU with a correct value for the -n option.

0424-056

MMU: Illegal value for option -m : ____

Explanation:: The number of copies must be greater or equal 1.
System action:: The Medium Map Utility terminates.
User response:: Call the MMU with a correct value for the -m option.

0424-057

MMU: Mirror output file ____ could not be opened.

Explanation:: The file specified for mirroring the input data could not be opened.
System action:: The Medium Map Utility terminates.
User response:: Check the path and permissions and try again.

0424-058

MMU: Unrecognized option :____.

Explanation:: An unknown option has been encountered on the command line.
System action:: The Medium Map Utility terminates.
User response:: Call the MMU using only supported options. The call syntax is: mmu [-b] [-e] [-n number to cache] [-m number of copies] [-i filename] {-j js filename | -f js file descriptor}

0424-059

MMU: Both -n and -m options must be specified.

Explanation:: If the multiple copies are desired, both -n and -m options must be specified.
System action:: The Medium Map Utility terminates.
User response:: Call the MMU either using both -n and -m or omitting both -n and -m options.

0424-060

MMU: The cache file ____ could not be opened.

Explanation:: The Medium Map Utility uses a temporary cache file to generate multiple copies requested by the -m option. The cache file could not be opened.
System action:: The Medium Map Utility terminates.
User response:: Check the path and permissions and try again.

0424-061

MMU: Either -f or -j option must be specified.

Explanation:: A job script file must be given to the MMU using either -j or -f option. The job script contains the information needed by the MMU to construct the medium map.
System action:: The Medium Map Utility terminates.
User response:: Call the MMU using -j or -f to specify a job script file.

0424-062

MMU: The job script file could not be opened.

Explanation:: The job script file specified by the -j or -f option could not be opened.
System action:: The Medium Map Utility terminates.
User response:: Check the path and permissions and try again.

0424-063

MMU: Corrupted job script file.

Explanation:: An error has been encountered in parsing the job script file.
System action:: The Medium Map Utility terminates.
User response:: Correct the job script file syntax and try again.

0424-064

MMU: Output bin zero is illegal.

Explanation:: A job script file entry requesting the output bin of zero has been encountered.
System action:: The Medium Map Utility terminates.
User response:: Correct the job script file syntax and try again.

0424-065

MMU: X offset specified in pels. Resolution of 240 pel/inch is assumed.

Explanation:: The offsets can be specified using inches, millimeters or pels. If the offsets are specified in pels, MMU must assume an actual destination resolution to convert the offset into a physical measurement.
System action:: The Medium Map Utility continues processing.
User response:: No response required.

0424-066

MMU: Y offset specified in pels. Resolution of 240 pel/inch is assumed.

Explanation:: The offsets can be specified using inches, millimeters or pels. If the offsets are specified in pels, MMU must assume an actual destination resolution to convert the offset into a physical measurement.
System action:: The Medium Map Utility continues processing.
User response:: No response required.

0424-067

MMU: Encountered a premature end of the input data stream.

Explanation:: The input data stream terminated abruptly, with the current MODCA structured field still incomplete.
System action:: The Medium Map Utility continues processing.
User response:: Correct the error in the data stream and try again.

0424-068

MMU: The input stream is not MODCA.

Explanation:: The data stream submitted to the MMU via standard input is not MODCA.
System action:: The Medium Map Utility terminates.
User response:: Submit only MODCA data stream to the MMU.

0424-069

MMU: encountered objects between pages in cache mode.

Explanation:: Both -n and -m options were specified to the MMU, and the data contained MODCA structured fields between pages. If the value of the -n option was more than 1, the effect of these structured fields can be unpredictable, in some cases affecting later copies of pages logically earlier in the datastream.
System action:: The Medium Map Utility continues processing.
User response:: No response required, but check the output for validity.

0424-070

MMU: Fatal error in checking the mirror file status.

Explanation:: The MMU has been called with the -i option specifying that input data mirroring to a file be performed. Before writing each MODCA structured field to the mirror file, the file system containing the mirror file is checked for space availability. The system call to perform this check has failed.
System action:: The Medium Map Utility terminates.
User response:: Check the file system containing the mirror file and try again. If the problem persists, call your service representative.

0424-071

MMU: No space left on the file system to write to mirror file ____. File ____ will be removed.

Explanation:: There was not enough space left on the file system containing the mirror file to write the next MODCA structured field.
System action:: The Medium Map Utility terminates.
User response:: Make more space available for the mirror file and try again.

0424-077

Syntax: afpReorder

Explanation:

Incorrect input syntax.

afpReorder <input file(s)>[-b2|-c <up size>|-ce <up size>|-b2e]-m <med map list>[-ff <file of file name> |-fm <file of med maps> [-t]

Where:

-ff: file containing input file namest
-b2: booklet 2-up format
-b2e: booklet 2-up format with saved pages
-rb2: reverse booklet 2-up format
-rb2e: reverse booklet 2-up format with saved pages
-b2ic: booklet 2-up format with integrated cover
-b2ice: booklet 2-up format with integrated cover, saved pages
-rb2ic: reverse booklet 2-up format with integrated cover
--b2ice: booklet 2-up format with integrated cover, saved pages
-rb2ic: reverse booklet 2-up format with integrated cover
-rb2ice: reverse booklet 2-up fmt w/ integrated cover, saved pages
-c: side-by-side <up-size> copy format
-ce: side-by-side <up-size> copy format with saved pages
-r: reverse printfile pages, assume <pps> pages per sheet
-cf: side-by-side <up-size> copy format for fanfold
-fltr: filter the data stream (standard in/standard out)
-p2: pages 1 to n/2 and (n/2)+1 to n in parallel columns
-rp2: reversed pages 1 to n/2 and (n/2)+1 to n in parallel columns
-p3: pages 1 to n/3, etc. in parallel columns
-rp3: reversed pages 1 to n/3, etc. in parallel columns
-rb2f: reverse booklet 2-Up format front/back page placement
-rsheet: reverse face down printfile sheets, preserve IMMs if -oldway specified, only preserve IMMs if the name changes.
-rstack: reverse print unit, duplex face up, preserve IMMs if -oldway specified, only preserve IMMs if the name changes.
-revstack: reverse print unit, preserve IMMs. if -oldway specified, only preserve IMMs if the name changes. if <pps> is provided, uses <pps> pages per sheet to calculate number of blank pages to insert at the beginning of the reversed data.
-oldway: for rsheet, rstack and revstack, preserve IMMs only if the name changes.
keeptle: for revstack, preserve Named Group and TLE structured fields.
-sides: number of sides to be printed on. 1 or 2 must be specified. If sides is not specified, defaults will be assumed. Not used if the formdef is inline. Used only with rsheet, rstack and revstack and overrides any MM names starting with 'S' to indicate simplex.
-merge: take same page from each file versus sequential pages
-mc: list of buildMm cfg file names
-fmc: file containing buildMm cfg file names
-fd: a buildMm cfg file for a formdef
-ksf: list of kodak setup files
-o: output file
-i: mirror the input stream to this output file
-sf: file containing a setup info object container
-sfrn: name to be put on BR for the setup container
-nostrp: do not strip any BDT or EDT (default is to strip)
-bdt: insert a BDT at the start of the print file
-edt: insert an EDT at the end of the print file
-imm: insert an IMM immediately following BDT
-t: turn on detailed trace

System action:

None.

User response:

Reissue the command with the correct syntax.

0424-078

________: No input MOD:CA file was specified on the command line.

Explanation:: The program requires an input MOD:CA file
System action:: The transform terminates.
User response:: Reissue the command with an input MOD:CA file.

0424-079

An incorrect copy count ____ was specified.

Explanation:: afpReorder requires a positive integer copy count for the side-by-side copy formats.
System action:: The transform terminates.
User response:: Enter the command again with the correct copy count.

0424-080

Initialization of afpReorder trace function failed.

Explanation:: The initialization of afpReorder trace function failed.
System action:: The program terminates.
User response:: Contact service personnel.

0424-081

cannot open file ____.

Explanation:: The program cannot open the file specified in the message.
System action:: The program terminates.
User response:: Verify the file exists at the proper path and enter the command again.

0424-082

No MOD:CA pages were found.

Explanation:: No MO:DCA pages were found in the input file(s).
System action:: The program terminates.
User response:: Verify the input file is correct and enter the command again.

0424-083

Unknown output format.

Explanation:: The output format specified on the command line is unknown.
System action:: The program terminates.
User response:: Enter the command again with the correct syntax.

0424-085

________: Unknown input parameter ________.

Explanation:: An unknown input parameter was entered on the command line.
System action:: The program terminates.
User response:: Enter the command again with the correct syntax.

0424-087

Inline object transform failed for object ____. The object will not be processed and sent to the actual destination.

Explanation:: The file references a non-OCA object. Inline transform of this object was attempted and failed.
System action:: Check the non-OCA object using the stand-alone transform, correct the problem, and resubmit the print job.
User response:: InfoPrint Manager may continue processing this file depending on the value of Image Checks.

0424-088

The print file contains a document resource and must be printed on an actual destination with Include Saved Page support.

Explanation:: A resource object of type, document, was encountered within the resource group in the print file but the actual destination does not have Include Saved Page support.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Print the file on an actual destination having Include Saved Page support. Otherwise the MO:DCA document resource object and any Include Page (IPG) references to the document resource must be removed from the print file before it can be printed.

0424-089

Invalid MO:DCA datastream. An inline resource group was found in a MO:DCA document.

Explanation:: Input Manager found a BRG structured field after a BDT structured field.
System action:: The psfin program stops processing the file on which the error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: Determine what is generating invalid MO:DCA and correct it. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0424-090

ERROR: The actual destination reported that more then one Include Saved Page command was specified in a page to be printed.

Explanation:: Input Manager found a BRG structured field after a BDT structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-091

ERROR: The actual destination reported that an Include Saved Page command was encountered in a page to be saved.

Explanation:: An Included Saved Page command was encountered in a page to be saved. The page to be saved was found in a group to which the Save Pages group operation applied.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-093

The number of copies given in the Medium Copy Count (MCC) structured field cannot exceed 1 for this type of actual destination. The number of copies is set to 1.

Explanation:: The actual destination does not allow the number of copies (copy count) to be greater than 1. The copy count is derived by the Medium Copy Count (MCC) structured field that is given in the supplied form definition. The copy count is defined by (Stopnum - Startnum) + 1 within the MCC copy subgroup(s).
System action:: InfoPrint Manager automatically sets the copy count to 1 and continues processing the print job.
User response:: This is an informational message; no response is required.

0424-094

MVS Download Object: ____ - MVS download System error; cannot create the MVS job service/daemon process (errno = ____)

Explanation:: mvsprsd detected a system error while trying to create and start the exit routine to print the AFP job.
System action:: InfoPrint Manager does not complete printing of the AFP print job
User response:: Check that your system has not exhausted its paging space or process ids. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-095

MVS Download Object: ____ - MVS download System error on file system ____. (errno = ____)

Explanation:: mvsprsd detected a system error concerning file status
System action:: InfoPrint Manager does not complete printing of the AFP print job
User response:: Check that the file system has not been exhausted of free space. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-096

MVS Download Object: ____ - MVS download System error changing directory to ____. (errno = ____)

Explanation:: mvsprsd detected a system error while changing directories.
System action:: InfoPrint Manager does not complete printing of the AFP print job
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-098

MVS Download Object: ____ - MVS download System error; error while closing a file ____. (errno = ____)

Explanation:: mvsprsd detected a system error when closing the file.
System action:: InfoPrint Manager does not complete printing of the AFP print job
User response:: Check that there is enough free space to write out the file. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-106

MMU: Medium map name is empty or too long : ____.

Explanation:: The medium map name provided with the -mm option must be between 1 and 8 characters long.
System action:: The Medium Map Utility terminates.
User response:: Invoke the Medium Map Utility with a valid medium map name.

0424-107

An invalid server address (____) and port (____) was extracted from the actual destination profile.

Explanation:: The actual destination profile contains a server address and port. This server is used by the inline transform process to PCL and Postscript data. The values in the actual destination profile are not valid.
System action:: Check the values of the transform server address and port in the actual destination profile.
User response:: InfoPrint Manager may continue processing this file depending on the value of Image Checks.

0424-108

PCL/Postscript inline transform failed. PCL/Postscript error message is ____

Explanation:: The PCL/Postscript inline transform failed and returned the preceding error information
System action:: Check the error with the appropriate transform documentation. Check the non-OCA object using the stand-alone transform, correct the problem, and resubmit the print job.
User response:: InfoPrint Manager may continue processing this file depending on the value of Image Checks.

0424-109

TIFF/JPEG inline transform failed. TIFF/JPEG error number is ____

Explanation:: The TIFF/JPEG inline transform failed and returned the preceding error number.
System action:: Check the error with the appropriate transform documentation. Check the non-OCA object using the stand-alone transform, correct the problem, and resubmit the print job.
User response:: InfoPrint Manager may continue processing this file depending on the value of Image Checks.

0424-110

________: Maximum number of input files/medium maps exceeded.

Explanation:: The maximum number of input files or medium maps was entered on the command line or within a file of names. The maximum number is 1000.
System action:: None.
User response:: Enter the command again with the fewer input files or medium maps.

0424-111

Specifying input files on the command line is not valid with the "-ff " command line option.

Explanation:: Input files were specified on the command line and the -ff option was used. These options are mutually exclusive.
System action:: The program terminates.
User response:: Enter the command again with either the input files on the command line or using the -ff command line option.

0424-112

Specifying the command line option "____" is not valid with the "____" command line option.

Explanation:: The command line options specified are mutually exclusive.
System action:: None.
User response:: Enter the command again with only one of the command line option

0424-115

Too many jobs in /var/psf/seglist.

Explanation:: The segprof internal memory allocation allows at most 25,000 entries on the expanded command line. The expanded command line contains the program name, any options and all the file names. If segprof has been invoked with '.' as the file name, all the filenames in the current directory are treated as arguments. Thus, at most some 24998 jobs can be saved in /var/psf/seglist.
System action:: segprof terminates with the return code of 1.
User response:: Clean up at least some of the seglist entries by hand and try again.

0424-119

Canceling job - waiting for child processes to die.

Explanation:: The Input Manager is attempting to cancel processing on a file for which deblocking has finished. Input Manager is waiting for associated child process(es) to complete.
System action:: The psfin program waits until all associated child process(es) are terminated. Deblocking will continue to the next logical file.
User response:: This is an informational message; no response is required.

0424-120

Input Manager could not spawn ____, errno=____.

Explanation:: The Input Manager psfin program attempted to fork( ) a child process and the effort failed. Input Manager attempts to spawn child processes for any required input exit, transform, output exit, and segmenter. One of these attempts to create a child process failed.
System action:: The psfin program stops processing the file on which the error occurred. The psfin program will then shut itself down, removing any existing child processes.
User response:: The number of processes that can be run are controlled by values in the /etc/security/limits file. Contact the person who administers your system for assistance.

0424-121

Canceling JES2 file (Will deblock to the next file).

Explanation:: The Input Manager is attempting to cancel processing on a JES2 file. We must, because of the format of the JES2 file, continue deblocking to find the next file.
System action:: The psfin program stops processing the file on which the error occurred. Deblocking will continue to the next logical file.
User response:: This is an informational message; no response is required.

0424-122

Record BackSpace failed on device ____, errno = ____.

Explanation:: The Input Manager psfin was processing a JES2 tape and during deblocking, a request was made to reposition the tape to a previous tape location. This tape repositioning is required due to the structure of JES2 files on tape. This file structure may require the psfin program to read ahead to determine what the next required activity may be. The attempt to reposition the tape failed.
System action:: The psfin program stops processing the file on which the error occurred. The psfin program will then shut itself down, removing any existing child processes.
User response:: Enter the man ioctl command to determine what action to take for the errno value shown in the message.

0424-123

Input Manager could not find job script ____.js for JES2 file ____ (named ____) in file ____ (named ____).

Explanation:: A job script to process a JES2 file was not found. The job script that was used to submit the print job specified the name of another job script to be used for one or more input JES2 files. The job script named inside the originally submitted job script could not be found.
System action:: TThe psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If you are using the InfoPrint Manager SMIT panels, ensure that any job scripts named in the Names of files to be submitted in the job field exist. If you are using a job script with the psfin command, ensure that any job scripts named with the i_Filenames keyword exist.

0424-124

Processing JES2 file ____ (named ____) in file ____ (named ____) with job script ____.js.

Explanation:: The Input Manager is attempting to process a specific JES2 file. This message identifies the JES2 file which is currently being processed. The file resides on a labeled tape.
System action:: The psfin program processes the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-125

Skipping JES2 file ____ (named ____) in file ____ (named ____).

Explanation:: The Input Manager is skipping the current JES2 file. This message identifies the JES2 file which is being skipped. The file resides on a labeled tape.
System action:: The psfin program skips the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-126

Processing JES2 file ____ (named ____) in file ____ with job script ____.js.

Explanation:: The Input Manager is skipping the current JES2 file. This message identifies the JES2 file which is being skipped. The file resides on a labeled tape.
System action:: The psfin program processes the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-127

Processing JES2 file ____ (named ____) in file ____ with job script ____.js.

Explanation:: The Input Manager is skipping the current JES2 file. This message identifies the JES2 file which is being skipped. The file resides on a labeled tape.
System action:: The psfin program skips the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-128

Processing of JES2 file ____ (named ____) in tape file ____ (named ____) is complete.

Explanation:: The Input Manager completed processing of a specific JES2 file. This message identifies the JES2 file for which processing has completed. The file resided on a labeled tape.
System action:: The psfin program processed the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-129

Processing of JES2 file ____ (named ____) in tape file ____ is complete.

Explanation:: The Input Manager completed processing of a specific JES2 file. This message identifies the JES2 file for which processing has completed. The file resided on an unlabeled tape.
System action:: The psfin program processed the specified JES2 file as requested by the appropriate job script.
User response:: This is an informational message; no response is required.

0424-130

Input Manager could not find job script ____.js for JES2 file ____ (named ____) in file ____.

Explanation:: A job script to process a JES2 file was not found. The job script that was used to submit the print job specified the name of another job script to be used for one or more input JES2 files. The job script named inside the originally submitted job script could not be found.
System action:: The psfin program stops processing the file on which this error occurred. Any files processed by psfin prior to this file are not affected. psfin does not process any more files in the job script.
User response:: If you are using the InfoPrint Manager SMIT panels, ensure that any job scripts named in the Names of files to be submitted in the job field exist. If you are using a job script with the psfin command, ensure that any job scripts named with the i_Filenames keyword exist.

0424-136

InfoPrint Manager is processing a cancel job request for jobid ____.

Explanation:: InfoPrint Manager has received a cancel job request for the specified job and is processing it. Another message will be issued when the processing of the request is complete.
System action:: InfoPrint Manager processes the cancel job request.
User response:: This is an informational message; no response is required.

0424-137

InfoPrint Manager is ignoring the cancel job request because the job has already printed.

Explanation:: InfoPrint Manager has received a cancel job request, but the job to be cancelled has already finished printing, so the job is not cancelled.
System action:: InfoPrint Manager ignores the cancel job request and continues printing the next job, if any.
User response:: This is an informational message; no response is required.

0424-138

InfoPrint Manager has cancelled jobid ____ at document page ____ of copy ____.

Explanation:: InfoPrint Manager has cancelled printing of the requested job at the specified page number.
System action:: InfoPrint Manager continues printing with the next job in the queue, if any.
User response:: This is an informational message; no response is required.

0424-140

InfoPrint Manager is processing a Pause Printer request.

Explanation:: InfoPrint Manager has received a Pause Printer request and is processing it. Another message will be issued when the processing of the request is complete.
System action:: InfoPrint Manager processes the Pause Printer request.
User response:: This is an informational message; no response is required.

0424-141

InfoPrint Manager has paused actual destination ____.

Explanation:: InfoPrint Manager has paused the specified actual destination, as requested.
System action:: InfoPrint Manager waits for a request to resume the actual destination.
User response:: This is an informational message; no response is required.

0424-142

InfoPrint Manager has resumed actual destination ____.

Explanation:: InfoPrint Manager has resumed the specified actual destination, as requested.
System action:: InfoPrint Manager continues printing from the point at which it was paused.
User response:: This is an informational message; no response is required.

0424-169

MMU: At least one Medium Map configuration file name must be provided.

Explanation:: The Medium Map Utility has been invoked with the -mc option on the command line, and no filenames followed the option. At least one name is required after this option. Each filename should refer to a configuration file that specifies the medium map parameters.
System action:: The Medium Map Utility terminates with a nonzero return code.
User response:: Correct the command line syntax and try again.

0424-170

MMU: Memory allocation failed.

Explanation:: An internal memory allocation system call failed.
System action:: The Medium Map Utility terminates with a nonzero return code.
User response:: Contact your service representative.

0424-171

MMU: Error ____ in parsing medium map config file ____.

Explanation:: The Medium Map Utility calls an API to generate an medium map, based on the data provided in the configuration file. The API has returned an error code, indicating that the configuration file could not be opened or contains syntax errors.
System action:: The Medium Map Utility terminates with a nonzero return code.
User response:: Correct the configuration file problem and try again.

0424-172

Syntax: buildMm buildMm -c <cfg file>[-f | -o <output file>]-c = configuration file name, required-f = create formdef instead of justa medium map, opt.-o = output file name, opt.default = stdout -m = medium map name, overrides name in cfg file, opt -v = verbose, optional

Explanation:: Incorrect input syntax.
System action:: None.
User response:: Enter the command again with the correct syntax.

0424-173

The actual destination model specified, ____, does not match the printer-reported device type, ____.

Explanation:: The actual destination model specified in the InfoPrint Manager configuration does not match the device type reported by the actual destination and is for a different actual destination family.
System action:: InfoPrint Manager logs the error for each job and then prints the job.
User response:: Specify the correct actual destination model in the InfoPrint Manager configuration.

0424-178

Input Manager could not locate the /var/psf/seglist directory.

Explanation:: Input Manager requires that the directory /var/psf/seglist exist. This directory should have been created at installation time.
System action:: The current invocation of Input Manager fails. This is a fatal error.
User response:: Determine if the directory /var/psf/seglist exists. If it does not exist, it may identify other potential problems with the installation. If the directory does not exist, it may be manually created by the root userid. The job upon which this error occurred will not print until the job is resubmitted from the user interface.

0424-179

Input Manager is terminating with an exit code of ____.

Explanation:: Input Manager is terminating with a non-zero return code. This is likely to be caused by a failed transform or a system resource problem.
System action:: The current invocation of Input Manager fails. This is a fatal error.
User response:: Determine the cause of the problem and correct the situation. If the cause of the problem cannot be determined, include the provided exit code when requesting assistance from your service representative. The job upon which this error occurred will not print until the job is resubmitted from the user interface.

0424-180

The character set specifies a MICR font. The actual destination does not support MICR fonts.

Explanation:: InfoPrint Manager has detected the MICR bit set in the character set FNC structured field. This indicates that MICR printing is desired, but the actual destination does not support this capability.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the print file, and submit the print job again.

0424-181

ERROR: A Page Modification Control (PMC) structured field specified a PMC overlay ____, but this overlay was not mapped within the containing medium map ____.

Explanation:: A Page Modification Control (PMC) structured field specified an overlay name that was not mapped by any Map Page Overlay (MPO) structured field within the containing medium map (a Formdef copygroup). To include a PMC overlay on a page for N-up printing, the PMC overlay must be mapped with an MPO structured field in the containing medium map.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in a medium map contained in the input file or in a Formdef resource referenced by the input file. The program or person who created the medium map most likely caused the error. Correct the error and send the job again. See the 'MO:DCA Reference' for further information on this structured field.

0424-182

The font character set ____ with the resolution/type ____ cannot be located.

Explanation:: InfoPrint Manager cannot locate a font character set at this resolution. InfoPrint Manager searches for a font at this resolution/type based on font and system search orders as well as extension naming conventions defined for this product. InfoPrint Manager determines the first target resolution/type based on information from the data stream, command line and default actual destination values. If Font Fidelity is CONTINUE, InfoPrint Manager cycles through other possible resolutions/types.
System action:: InfoPrint Manager may continue processing the print job based on the value of font fidelity.
User response:: None.

0424-183

The font character set ____ with the resolution/type ____ appeared inline within the print file at offset ____.

Explanation:: InfoPrint Manager found a FOCA2 FCS inline within the print file.
System action:: InfoPrint Manager may continue processing the print job based on the value of font fidelity.
User response:: None.

0424-184

The actual destination does not support the ____ resolution/type ____ for the font character set ____.

Explanation:: InfoPrint Manager will not attempt to locate a font character set with the identified resolution/type because it is not supported by the target actual destination. InfoPrint Manager searches for a font at this resolution/type based on font and system search orders as well as extension naming conventions defined for this product. InfoPrint Manager determines the first target resolution/type based on information from the data stream, command line and default actual destination values. If Font Fidelity is CONTINUE, InfoPrint Manager cycles through other possible resolutions/types.
System action:: InfoPrint Manager may continue processing the print job based on the value of font fidelity.
User response:: None.

0424-185

All code pages for the DBCS coded font file ____ were located.

Explanation:: InfoPrint Manager located all of the code pages referenced in the DBCS coded font. This message is informational.
System action:: None.
User response:: None.

0424-186

All font character sets for the DBCS coded font file ____ were located at ____ resolution.

Explanation:: InfoPrint Manager located all of the font character sets referenced in the DBCS coded font. This message is informational.
System action:: None.
User response:: None.

0424-187

The font character sets for the DBCS coded font file ____ cannot be located.

Explanation:: InfoPrint Manager failed to locate the font character sets referenced in the DBCS coded font.
System action:: None.
User response:: None.

0424-188

The actual destination does not support the ____ resolution/type ____ for the coded font ____..

Explanation:: InfoPrint Manager will not attempt to locate a coded font with the identified resolution/type because it is not supported by the target actual destination. InfoPrint Manager searches for a coded font at this resolution/type based on font and system search orders as well as extension naming conventions defined for this product. InfoPrint Manager determines the first target resolution/type based on information from the data stream, command line and default actual destination values. If Font Fidelity in CONTINUE , InfoPrint Manager cycles through other possible resolution/types.
System action:: InfoPrint Manager may continue processing the print job based on the value of Font Fidelity.
User response:: None.

0424-189

The coded font file ____ was located ____, path is ____.

Explanation:: InfoPrint Manager located the coded font file. This message is informational.
System action:: None.
User response:: None.

0424-190

The Font Fidelity code on the PFC structured field is invalid. InfoPrint Manager will continue processing.

Explanation:: InfoPrint Manager encountered an invalid Font Fidelity code on the X'78' Font Fidelity Triplet of the Presentation Fidelity Control (X'D3B288') structured field. Valid codes are X'01' and X'02'.
System action:: InfoPrint Manager ignores the Font Fidelity exception code in the formdef and continues processing.
User response:: None.

0424-191

Could not locate coded font ____ of type ____. Font fidelity is ____.

Explanation:: InfoPrint Manager could not locate the coded font. InfoPrint Manager was looking for a coded font of the specified type, derived from the font resolution. If font fidelity is CONTINUE, InfoPrint Manager may continue looking for the coded font at another type. If font fidelity is STOP, InfoPrint Manager will halt.
System action:: InfoPrint Manager may continue processing depending on the value of font fidelity.
User response:: If InfoPrint Manager can not locate the coded font, correct the problem and resubmit the job.

0424-192

The font resolution value X'____'in the Map Coded Font format 2 structured field (MCF2) repeating group number ____ is not valid.

Explanation:: The font resolution value within the Font Resolution and Metric Technology Triplet (X'84') is not valid. Valid values are X'0960' (240-pel) and X'0BB8' (300-pel). This triplet is on an MCF2 structured field. See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-193

The font technology value X'____'in the Map Coded Font format 2 structured field (MCF2) or Map Data Resource (MDR) repeating group number ____ is not valid.

Explanation:: The font technology value within the Font Resolution and Metric Technology Triplet (X'84') (in the case of an MCF2) or within the Data Object Font Descriptor (X'8B') Triplet of the MDR is not valid. Valid values are X'01' (Fixed-metric technology) and X'02' (Relative-metric technology). Valid for an MDR is X'20' (TrueType/OpenType). See the 'MO:DCA Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-194

The actual destination does not support ____ finishing. Finishing fidelity is ____.

Explanation:: Finishing was specified in the data stream, but the actual destination reports finishing operations at this level or finishing operations for the given technology (AFP or UP3i) are not supported.
System action:: If finishing fidelity is CONTINUE, InfoPrint Manager does not request any finishing operations be done at the actual destination, effectively ignoring the contents of the data stream with regards to finishing. If finishing fidelity is STOP, InfoPrint Manager terminates the job.
User response:: No action required if finishing is not required. If finishing is required, resubmit the job to an actual destination with an activated finisher that supports the desired operations or technology.

0424-195

The ____ finishing operation is not available at the actual destination. Finishing fidelity is ____.

Explanation:: A finishing operation was specified in the data stream, but the actual destination reports that the operation is not currently available (or may not support that operation at all).
System action:: If finishing fidelity is CONTINUE, InfoPrint Manager does not request that the finishing operation be done by the actual destination, effectively ignoring the contents of the data stream with regards to this finishing operation.
User response:: No action required if finishing is not required. If finishing is required, resubmit the job to an actual destination with an activated finisher that supports the desired operation.

0424-196

A Medium Finishing Control structured field contains bad values. Finishing fidelity is ____.

Explanation:: Either a set of finishing operations were specified at an invalid scope, or an invalid scope was specified or an invalid Media Collection value was specified. For further details, please refer to the description of the Medium Finishing Control (MFC) structured field in the Mixed Document Object Content Architecture (MODCA) Reference.
System action:: If Finishing Fidelity is CONTINUE, the job continues. InfoPrint Manager does not request that any finishing operations be done at the actual destination, effectively ignoring the contents of the data stream with regards to finishing. If the Finishing Fidelity is STOP, InfoPrint Manager terminates the job.
User response:: If finishing is required, modify the MODCA data stream, then resubmit the file for printing.

0424-197

The actual destination or finishing device is out of staples; add staples.

Explanation:: The actual destination or finishing device is out of staples and printing cannot continue.
System action:: After staples have been added, InfoPrint Manager recovers and printing continues.
User response:: Add staples to the actual destination or finishing device.

0424-198

The actual destination reported a staple jam; clear the jam.

Explanation:: The stapling mechanism in the actual destination or finishing device has jammed or has caused a paper jam. Printing cannot continue until the jam is cleared.
System action:: After the jam is cleared, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0424-199

The postprocessor detected a condition that caused pages to be discarded.

Explanation:: The postprocessor detected a condition that caused it to discard pages. Printing cannot continue until the condition is cleared.
System action:: After the condition is cleared, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0424-200

The postprocessor is not ready and must be made ready before printing can continue.

Explanation:: The postprocessor is in a not-ready state and printing cannot continue.
System action:: After the postprocessor is made ready, InfoPrint Manager recovers and printing continues.
User response:: Follow the instructions in the documentation for the actual destination to correct this problem.

0424-201

The supported finishing operations on the actual destination have changed.

Explanation:: The actual destination reported that the supported finishing operations have changed. InfoPrint Manager reports this message for the user's information in case finishing operations requested for the print job are not performed.
System action:: InfoPrint Manager recovers and printing continues.
User response:: Examine the printed output to see if it is satisfactory.

0424-202

Incompatible finishing operations were requested.

Explanation:: The actual destination reported that the finishing operations requested are not compatible on this device. For example, some devices do not allow z-folding of sheets to be saddle stitched. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: Select finishing operations that are supported and compatible on this device and resubmit the job.

0424-203

The output contains too many or too few sheets to perform the requested finishing operation.

Explanation:: A finishing operation was requested for a collection of sheets, but the number of sheets was too large or too small for the operation. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-204

An invalid or unsupported finishing operation type was requested.

Explanation:: The actual destination reported that a finishing operation type was requested that is invalid or unsupported on this device. For example, some devices do not support saddle stitching. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-205

An invalid or unsupported finishing operation reference corner or edge was requested.

Explanation:: The actual destination reported that a finishing operation reference corner or edge was requested that is invalid or unsupported on this device. For example, some devices do not allow edge stitching on the top or bottom edge of the sheets. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-206

An unsupported finishing operation count was requested.

Explanation:: The actual destination reported that a finishing operation count was requested that is unsupported on this device. For example, some devices do not support more than 3 staples for edge stitching. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-207

An invalid or unsupported finishing operation axis offset was requested.

Explanation:: The actual destination reported that a finishing operation axis offset was requested that is invalid or unsupported on this device. For example, some devices support only a fixed axis for edge stitching. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-208

An invalid or unsupported number of finishing positions was requested.

Explanation:: The actual destination reported that a finishing operation was requested with a number of positions that is invalid or unsupported on this device. For example, some devices support only one fixed position for saddle stitching. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-209

An invalid or unsupported finishing operation position was requested.

Explanation:: The actual destination reported that a finishing operation position was requested that is invalid or unsupported on this device. For example, some devices allow only fixed positions for edge stitching. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-210

The requested finishing operation is incompatible with the selected media or output bin.

Explanation:: The actual destination reported that the finishing operation requested is not compatible on this device with the selected media or with the selected output bin. Some devices require that documents to be finished be routed to particular output bins. See your actual destination documentation for more information on the finishing operations supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: Select finishing operations, media, and output bins that are compatible and available on this device and resubmit the job.

0424-211

The requested finishing operation is incompatible with a change in output bins.

Explanation:: The actual destination reported that the finishing operation requested is not compatible on this device with the requested change in output bins. For some finishing operations, such as stapling, the sheets to be stapled cannot be split among output bins See your actual destination documentation for more information on the finishing operations supported on this device..
System action:: InfoPrint Manager continues printing the job, but without the requested finishing operations.
User response:: Select finishing operations, media, and output bins that are compatible and available on this device and resubmit the job.

0424-212

The media to be finished cannot be sent to the selected output bin; the media may be the wrong size.

Explanation:: The actual destination reported that the media selected for a finishing operation cannot be sent to the selected output bin. Some finishing operations such as saddle stitching and z-folding may require manual adjustments on the finisher based on the media size. Also, there may be restrictions on the size of paper that can be z-folded or saddle stitched. See your actual destination documentation for more information on the finishing operations supported on this device. Finishing operations for the job are specified in the FORMDEF or in medium maps.
System action:: InfoPrint Manager stops printing the job at the point of the error. Printing continues with the next job.
User response:: Select finishing operations, media, and output bins that are compatible and available on this device and resubmit the job.

0424-213

The actual destination reported an invalid or unsupported triplet length value.

Explanation:

The actual destination reported that a triplet length value specified for an IPDS command is invalid or unsupported on this device. This could be bad data in the print file, an actual destination internal microcode error or an InfoPrint Manager internal logic error.

The triplet is one of the following:

X'00' (Group ID)
X'01' (Coded Graphic Character Set Global ID)
X'02' (Fully Qualified Name)
X'50' (Encoding Scheme)
X'6E' (Group Information)
X'85' (Finishing Operation)
X'8B' (Data Object Font Descriptor)
X'8E' (UP3I Finishing Operation)
X'8D' (Linked Font)
X'91' (CMR Descriptor)
X'92' (Invoke CMR)
X'95' (Rendering Intent)
X'97' (Device Appearance)
X'9A' (Image Resolution)
X'9C' (Object Container Presentation Space Size)
X'A2' (Invoke Tertiary Resource)

System action:

InfoPrint Manager stops printing the job when the error occurs. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use local problem-reporting procedures to report this message.

0424-213

The output contains too many sheets to perform the requested finishing operation.

Explanation:: A finishing operation was requested for a collection of sheets, but the number of sheets was too large for the operation. See your actual destination documentation for more information on the finishing operations supported on this device. Finishing operations for the job are specified in the FORMDEF or in medium maps.
System action:: InfoPrint Manager stops printing the job at the point of the error. Printing continues with the next job.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-214

The output contains too many sheets to perform the requested finishing operation.

Explanation:: A finishing operation was requested for a collection of sheets, but the number of sheets was too large for the operation. See your actual destination documentation for more information on the finishing operations supported on this device. Finishing operations for the job are specified in the FORMDEF or in medium maps.
System action:: InfoPrint Manager stops printing the job at the point of the error. Printing continues with the next job.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-215

FORMDEF ____ specified ____ N-up but the actual destination only supports a maximum of ____ N-up pages per sheet side.

Explanation:: A FORMDEF specified more N-up pages for a sheet side than the actual destination supports.
System action:: InfoPrint Manager stops processing the document at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Choose a FORMDEF that specifies the number of N-up pages that is less than or equal to the maximum number supported by the actual destination.

0424-216

The selected FORMDEF ____ and Medium Map ____ specified an incompatible Invoke option for the media eject control value.

Explanation:: The subject medium map may reside within the document or the selected FORMDEF. The medium map specified one of the following conditions: 1) advance to the NEXT BACK PARTITION but did not specify duplex 2) advance to the NEXT BACK PARTITION but no PGP repeating group specified page placement for the back side of a sheet 3) advance to the NEXT FRONT PARTITION but no PGP repeating group specified page placement for the front side of a sheet.
System action:: InfoPrint Manager stops processing the printfile at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job
User response:: Rerun the job after either 1) specifying duplex as an override option when submitting the job or add duplex to the medium map specifications, or 2) making the PGP page placement and Invoke media eject correspond.

0424-217

The selected FORMDEF ____ and Medium Map ____ specified page rotation of ____ but the actual destination does not support page rotation.

Explanation:: A medium map specified that a page should be rotated. The actual destination does not support page rotation and presents the pages without page rotation The subject medium map may reside within the document or the selected FORMDEF.
System action:: InfoPrint Manager continues processing the file.
User response:: Choose a FORMDEF that does not specify page rotation, or choose an actual destination that will rotate pages.

0424-219

An invalid or unsupported finishing option type was requested.

Explanation:: The actual destination reported that a finishing option type was requested that is invalid or unsupported on this device. For example, some devices do not support crease. See your actual destination documentation for more information on the finishing options supported on this device.
System action:: InfoPrint Manager continues printing the job, but without the requested finishing options.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing option.

0424-220

A mechanism error occurred which may have caused a finishing operation to be suppressed.

Explanation:: The postprocessor detected a mechanism error (for example, a finisher paper jam) which would prevent it from being able to apply a finishing operation. If a finishing operation was requested for the sheets being processed at the time of the error, the finishing operation was suppressed. See your actual destination documentation for more information on the postprocessor error conditions.
System action:: InfoPrint Manager continues printing the job, but requested finishing operations may not be applied.
User response:: If the output is not acceptable, submit the print request to an actual destination that can perform the requested finishing operation.

0424-227

The output contains mixed paper sizes which prevent the requested finishing operation.

Explanation:: A finishing operation was requested for a collection of sheets of mixed sizes, but the device requires all of the sheets to be the same size. See your actual destination documentation for more information on the finishing operations supported on this device. \
System action:: InfoPrint Manager stops printing the job at the point of the error. Printing continues with the next job.
User response:: Select finishing operations and media that are compatible and available on this device and resubmit the job.

0424-228

The actual destination reported that no input trays are available, so no printing can be done.

Explanation:: The actual destination reported that no input trays are currently available on the actual destination, so no printing can take place. The tray(s) may not be properly installed or may have been disabled by the operator. See your actual destination documentation for more information on the actual destination's input trays. \.
System action:: InfoPrint Manager disables the actual destination. \
User response:: Install or enable at least one input tray on the actual destination, then enable the actual destination.

0424-230

ERROR: The connection-timeout attribute expired for the actual destination at address ____.

Explanation:: The actual destination did not respond in the necessary amount of time to an attempt to start a session.
System action:: InfoPrint Manager's attempt to communicate with this actual destination failed. The actual destination becomes disabled unless either the actual destination job- retry-count-limit or the actual destination job-retry-interval is nonzero, in which case InfoPrint Manager will not disable the actual destination until the specified number of retries have been attempted and have all failed.
User response:: If the actual destination had an intervention condition, fix the condition and try again. If the actual destination was warming up, you may need to increase the value of this actual destination's connection-timeout attribute to take into account the amount of time spent warming up. Alternatively, if the actual destination is simply not responding at all, then you may need to check your network or have the actual destination fixed.

0424-231

ERROR: The actual destination reported an invalid color fidelity triplet continue value.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid value in the color fidelity triplet continue field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-232

ERROR: The actual destination reported an invalid color fidelity triplet report value.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid value in the color fidelity triplet report field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-233

ERROR: The actual destination reported an invalid color fidelity triplet substitute value.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid value in the color fidelity triplet substitute field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-234

ERROR: The actual destination reported an invalid bar code scaling fidelity length.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid bar code scaling fidelity triplet length value. Either the triplet-length field in a bar code scaling fidelity triplet contained an invalid value or a bar code scaling fidelity triplet was too long to fit in the containing command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-235

ERROR: The actual destination reported an invalid bar code scaling method value.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid value in the bar code scaling fidelity triplet scaling method field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-236

ERROR: The actual destination reported an invalid trapping control length.

Explanation:: The actual destination received a Print Fidelity Control (PFC) command that contained an invalid trapping control length value. Either the triplet-length field in a trapping control triplet contained an invalid value or a trapping control triplet was too long to fit in the containing command.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the form definition and send the job again.

0424-237

ERROR: The actual destination detected an error in an IOCA image object.

Explanation:

The error occurred in an Image Object Content Architecture (IOCA) image. Using the IPDS exception from preceding message 0420-249, match the exception to a description of the specific error in the following list:

X'058C..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A Begin Tile Parameter was encountered out of sequence.

X'058D..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. An End Tile Parameter is missing after a Begin Tile has been encountered or was encountered out of sequence.

X'058E..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A Begin Transparency Mask Parameter was encountered out of sequence or appeared more than once in an image or tile.

X'058F..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. An End Transparency Mask Parameter is missing after a Begin Transparency Mask has been encountered or was out of sequence.

X'0592..01'

An Image Data self-defining field was specified that should not be present because the Band Image Parameter was specified.

X'0598..01'

A Band Image Parameter was specified in an IO image and a subsequence Image Subsampling Parameter was also found. A Band Image Parameter and am Image Subsampling Parameter cannot coexist in the same image.

X'0598..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A Band Image Parameter was encountered out of sequence or appeared more than once. A Band Image Parameter must appear after a Begin Image Content and before the image data.

X'0598..10'

A value within a Band Image Parameter is invalid or unsupported.

X'0598..14'

The number of BITCNT parameters in a Band Image Parameter is not equal to the BCOUNT value.

X'0598..15'

The IDE size determined by the Band Image Parameter (after subtracting padding bits) does not match the IDE Size Parameter.

X'059B..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. An IDE Structure Parameter was encountered out of sequence or appeared more than once. An IDE Structure Parameter must appear after a Begin Image Content and before the image data.

X'059B..10'

A value within an IDE Structure Parameter is invalid or unsupported.

X'059B..18'

The sum of the SIZE1 through SIZE4 values in an IDE Structure Parameter does not match the IDE size specified in the IDE Size Parameter.

X'059C..01'

A Band Image Data self-defining field was specified that should not be present because the Band Image Parameter was not specified.

X'059C..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A Band Image Data self-defining field was missing or encountered out of sequence. When a Band Image Parameter is specified, one or more Band Image Data self-defining fields must appear after image data parameters and before the End Image Content.

X'059C..17'

The number or sequence of Band Image Data self-defining fields within a series of WI2 commands is invalid. Either some of the bands specified in the Band Image Parameter were missing in the Band Image Data or the Band Image Data self-defining fields were not in the sequential order of the band numbers.

X'059F..01'

One of the following occurred:

An External Algorithm Specification Parameter was specified in an IO image, but a corresponding Image Encoding Parameter was not found.
An Image Encoding Parameter was specified in an IO image that requires an External Algorithm Specification Parameter, but no External Algorithm Specification Parameter was found.

X'059F..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. An External Algorithm Specification Parameter was encountered out of sequence or appeared more than once. An External Algorithm Specification Parameter must appear after a Begin Image Content and before the image data.

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Correct the error in the IOCA image data. The error could be in the program which produces the IOCA image data. Refer to the Image Object Content Architecture documentation for additional information.

0424-238

ERROR: The actual destination detected an error in an IOCA image object.

Explanation:

The error occurred in an Image Object Content Architecture (IOCA) image. Using the IPDS exception from preceding message 0420-249, match the exception to a description of the specific error in the following list:

X'059F..10'

A value within an External Algorithm Specification Parameter is invalid or unsupported.

X'059F..11'

An external Algorithm Specification Parameter was specified in the image, but the Image Encoding Parameter does not require it.

X'05B5..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A required Tile Position Parameter is missing or was encountered out of sequence.

X'05B5..10'

A XOFFSET or YOFFSET value within a Tile Position Parameter is invalid or is outside of the image presentation space.

X'05B5..11'

One of the following conditions has occurred in a Tile Position Parameter:

Tiles are specified out of order. This exception can occur only if the Tile TOC Parameter does not contain any TOC entries. If the Tile TOC Parameter does contain TOC entries, the tiles themselves can be specified in any order.
The Tile TOC Parameter does contain the table of contents, but the XOFFSET or YOFFSET given for this tile in the table of contents does not match the corresponding value specified in the Tile Position Parameter.

X'05B6..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A required Tile Size Parameter is missing or was encountered out of sequence.

X'05B6..10'

A value within a Tile Size Parameter is invalid.

X'05B6..11'

One or more of the following conditions has occurred in a Tile Size Parameter:

The tile overlaps a previously specified tile.
The RELRES value specified in the table of contents does not match the corresponding RELRES value in the Tile Size Parameter.
The THSIZE or TVSIZE specified in the table or contents does not match the corresponding value in the Tile Size Parameter.

X'05B7..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. One of the following occurred:

A Tile Set Color Parameter was encountered out of sequence or appeared more than once.
A Tile Set Color Parameter was specified once in the correct sequence, but the tile was not a bilevel tile. The IDE Size Parameter, if specified, must specify an IDE size of 1 bit per IDE. The IDE Structure Parameter, if specified, must specify a color space of either YCrCb or YCbCr.

X'05B7..10'

One or more of the following conditions has occurred in a Tile Set Color Parameter:

An invalid color space (CSPACE) value was specified.
An invalid size value was specified.
An invalid color value was specified.

X'05B7..11'

A Tile Set Color Parameter was specified once in the correct sequence, but the tile was not a bilevel tile. The IDE Size Parameter, if specified, must specify an IDE size of 1 bit per IDE. The IDE Structure Parameter, if specified must specify a color space of either YCrCb or YCbCr

X'05BB..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. In a tiled image, the Tile TOC Parameter did not appear immediately after Begin Image Content or appeared more than once.

X'05BB..10'

A value within a Tile TOC Parameter is invalid.

X'05BB..11'

One or more of the following conditions has occurred in a Tile TOC Parameter:

Not all tiles are listed in the table of contents, even though the table of contents contains at least one tile.
The table of contents lists a non-existent tile.
Invalid tile order; two or more tiles in the table of contents have sort keys (primary - YOFFSET, secondary - XOFFSET) that are identical or out of sequence.
The specified offset for one or more tiles does not point to a position where a Begin Tile Parameter starts.

X'05CE..01'

An Image Subsampling Parameter was specified in an IO image and a subsequence Band Image Parameter was also found. A Band Image Parameter and an Image Subsampling Parameter cannot coexist in the same image.

X'05CE..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. An Image Subsampling Parameter was encountered out of sequence or appeared more than once. An Image Subsampling Parameter must appear after a Begin Image Content and before the image data.

X'05CE..10'

A value within an Image Subsampling Parameter is invalid or unsupported.

X'05DE..0F'

The sequence of self-defining fields within a series of WI2 commands is invalid. A Color Palette Parameter was encountered out of sequence or appeared more than once. A Color Palette Parameter must appear after a Begin Image Content and before the image data.

X'05DE..10'

A value within a Color Palette Parameter is invalid or unsupported

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Correct the error in the IOCA image data. The error could be in the program which produces the IOCA image data. Refer to the Image Object Content Architecture documentation for additional information.

0424-239

InfoPrint Manager canceled printing of the file because a color error occurred and color fidelity was requested.

Explanation:: InfoPrint Manager stops processing the file as part of InfoPrint Manager error recovery. The actual destination reported an exception which indicates an invalid or unsupported color-value was requested. Because color fidelity was requested, the normal recovery for this exception is not taken. Instead, the file is canceled. Color fidelity is requested in the form definition (FORMDEF). The form definition used with this print file requested that color exceptions be reported and that printing be stopped at the point of the first color exception.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the causes of the other error messages in this message group.

0424-240

InfoPrint Manager located a Color Presentation Fidelity indicator in the Formdef, but the device does not support this capability.

Explanation:: InfoPrint Manager found a Color Fidelity Triplet (X'75') on the Presentation Fidelity Control (PFC) Structured Field. The triplet indicated Stop on errors and the device does not support the triplet.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-241

InfoPrint Manager located a Bar Code Scaling Fidelity indicator in the Formdef, but the device does not support this capability.

Explanation:: InfoPrint Manager found a Bar Code Scaling Fidelity Triplet (X'76') on the PFC Structured Field. The triplet indicated Stop on errors and the device does not support the triplet.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-242

InfoPrint Manager located a Trapping Control Fidelity indicator in the Formdef, but the device does not support this capability.

Explanation:: InfoPrint Manager found a Trapping Control Fidelity Triplet (X'77') on the PFC Structured Field. The triplet indicated Stop on errors and the device does not support the triplet.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use local problem-reporting procedures to report this message.

0424-243

InfoPrint Manager located a Color Presentation Fidelity triplet in the Formdef indicating Continue and Report Exceptions. The device does not support this capability.

Explanation:: InfoPrint Manager found a Color Fidelity Triplet (X'75') on the Presentation Fidelity Control (PFC) Structured Field of the Formdef. The triplet indicated Continue on errors and Report Exceptions, but the device does not support the triplet.
System action:: InfoPrint Manager continues processing the file.
User response:: None.

0424-245

The character-pattern addresses in Font Patterns Map (FNM) of the character set are not in ascending order.

Explanation:: InfoPrint Manager discovered an FNM structured field in the font which did not have ascending character-pattern addresses, as required by FOCA architecture.
System action:: InfoPrint Manager skips the font and continues processing the file.
User response:: Fix the font.

0424-246

The character-pattern addresses in Font Patterns Map (FNM) of the character set are not in ascending order.

Explanation:: InfoPrint Manager discovered an FNM structured field in the font which did not have ascending character-pattern addresses, as required by FOCA architecture.
System action:: InfoPrint Manager skips the font and continues processing the file.
User response:: Fix the font.

0424-248

Host Receiver failed to start when a CreateProcess was issued.

Explanation:: The Host Receiver failed to start when a CreateProcess was issued. This is a basic error of the sort caused by a missing executable, or a fundamental system problem.
System action:: The session request is denied, and an UNBIND is done to the Host.
User response:: Retry the connection, and if the error continues, use local problem-reporting procedures to report this message.

0424-253

MVS Download Object: ____ - Error opening destination control file ____. Error = ____.

Explanation:: The indicated file can not be opened.
System action:: This error causes the MVS Download Receiver to terminate initialization processing
User response:: Change the destination control file for the receiver to a file that exists and is accessible to the MVS Download receiver.

0424-254

MVS Download Object: ____ - Destination control file line ____ is longer than ____ characters.

Explanation:: The indicated line in the destination control file is longer than the maximum allowed line length.
System action:: This error causes the MVS Download Receiver to terminate initialization processing.
User response:: Make sure that the line in the destination control file does not exceed the indicated maximum length. Also ensure that proper line delineation has been used in the text file.

0424-255

MVS Download Object: ____ - Destination control file line ____ contains invalid syntax.

Explanation:: The indicated line in the destination control file does not have valid syntax for a control statement.
System action:: Syntax checking of the destination control file continues. However, the MVS Download Receiver will terminate initialization processing after syntax checking is complete.
User response:: Change the indicated line to a valid syntax. Consult the InfoPrint Manager documentation for information on the rules for proper syntax.

0424-256

MVS Download Object: ____ - Destination control file line ____ contains an unrecognized operator action: ____.

Explanation:: The indicated line in the destination control file does not contain a valid operator.
System action:: Syntax checking of the destination control file continues. However, the MVS Download Receiver will terminate initialization processing after syntax checking is complete.
User response:: Change or remove the operator. Consult the InfoPrint Manager documentation for information on valid operators.

0424-257

MVS Download Object: ____ - DEBUG: Received MVS parameter: ____=____.

Explanation:: This message is a result of the request for control file debug information. The indicated MVS parameter and keyword were received from the host system or were specified in a Default statement in the destination control file.
System action:: The indicated MVS parameter will be used for mapping.
User response:: None.

0424-258

MVS Download Object: ____ - DEBUG: MVS keyword ignored due to null mapping in destination control file at line ____.

Explanation:: This message is a result of the request for control file debug information. No InfoPrint Manager attribute was generated for the received MVS keyword due to a null mapping in the destination control file at the indicated line.
System action:: The indicated MVS keyword will be ignored.
User response:: None.

0424-259

MVS Download Object: ____ - DEBUG: MVS Keyword mapped to ____=____.

Explanation:: This message is a result of the request for control file debug information. The MVS keyword was mapped to the indicated InfoPrint Manager attribute and parameter. The syntax displayed in this message may not exactly match the syntax generated. The syntax in this message does not account for null parameters or positional parameters. The generated parameter string will account for these items.
System action:: The indicated InfoPrint Manager attribute and parameter were added to the parameter string.
User response:: None.

0424-260

MVS Download Object: ____ - DEBUG: The InfoPrint Manager attribute was treated as a pass through option.

Explanation:: This message is a result of the request for control file debug information. The generated InfoPrint Manager attribute was identified as a destination-pass-through option.
System action:: The generated InfoPrint Manager attribute and parameter were added to the destination-pass-through option of the parameter string.
User response:: None.

0424-261

MVS Download Object: ____ - DEBUG: Line ____ in the control file was used.

Explanation:: This message is a result of the request for control file debug information. The indicated line in the control file was used to perform previously indicated actions.
System action:: None.
User response:: None.

0424-262

MVS Download Object: ____ - DEBUG: No line in the control file was used. The default action was performed.

Explanation:: The lack of a matching control statement in the control file caused the default action to be performed.
System action:: None.
User response:: None.

0424-263

MVS Download Object: ____ - DEBUG: Replacing InfoPrint Manager attribute ____=____ with ____=____..

Explanation:: The indicated InfoPrint Manager attribute and parameter were replaced with the indicated InfoPrint Manager attribute and parameter. The syntax conveyed in this message may not exactly match the syntax generated. The syntax in this message does not account for null parameters or positional parameters. The generated parameter string will account for these items.
System action:: The indicated InfoPrint Manager attribute and parameter were added to the parameter string.
User response:: None.

0424-264

MVS Download Object ____ - Unable to locate file system: ____ '____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-265

MVS Download Object: ____ - Unable to allocate security descriptor, errno= '____'.

Explanation:: MVS Download detected a system error concerning memory or security descriptor status.
System action:: MVS Download attempts recovery and issues secondary system command.
User response:: If data output fails, logon as 'administrator' and try again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-266

MVS Download Object: ____ - Unable to initialize security descriptor, errno= '____'.

Explanation:: MVS Download detected a system error concerning security descriptor status.
System action:: MVS Download attempts recovery and issues secondary system command.
User response:: If data output fails, logon as 'administrator' and try again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-267

MVS Download Object: ____ - Unable to set security descriptor, errno='____'.

Explanation:: MVS Download detected a system error concerning security descriptor status.
System action:: MVS Download attempts recovery and issues secondary system command.
User response:: If data output fails, logon as 'administrator' and try again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-268

MVS Download Object: ____ - Unable to invoke script./exit, errno='____'.

Explanation:: MVS Download detected a system error concerning the exit routine.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: If data output fails, logon as 'administrator' and try again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-270

MVS Download Object: ____ - Unable to get MVS Download configuration path for destination: '____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-271

MVS Download Object: ____ - Unable to open file: '____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-272

MVS Download Object: ____ - Unable to remove JCL file: '____', errno='____'.

Explanation:: MVS Download leaves the file and continues processing.
System action:: MVS Download attempts recovery and issues secondary system command.
User response:: When time permits, manually delete the file. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error.

0424-273

MVS Download Object ____ - Processing terminated on mvsprpsm.

Explanation:: MVS Download detected a system configuration error.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check InfoPrint Manager log or MVS Download receiver log for previous error messages. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-274

MVS Download Object: ____ - Unable to open file:'____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from beginning of a file to guarantee data integrity.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-275

MVS Download Object: ____ - Cannot set file pointer or set end of file, errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-276

MVS Download Object: ____ - Unable to write to file:'____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted fro the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-278

MVS Download Object: ____ - Unable to rename file:'____ to '____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory does exist and access is allowed. Refer to the file rename command for a list of the possible error conditions. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-280

MVS Download Object: ____ - Error Generating InfoPrint Manager parameters:____. Logical destination: '____'.

Explanation:: The indicated line in the configuration file is does not have valid syntax for a control statement.
System action:: MVS Download Object: unable to process host data.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-281

MVS Download Object: ____ - Unable to locate script/exit routine: '____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: InfoPrint Manager does not complete printing of the print job.
User response:: Check that the named directory and file does exist and access is allowed. Check the script/exit name specified in the receiver definition (Windows) or on the -x parameter to mvsprsd (UNIX). Restart the daemon/receiver when the problem has been resolved. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-282

MVS Download Object: ____ - Unable to OPEN check point file: '____', errno=' ____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of the file to guarantee data integrity.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-283

MVS Download Object: ____ - Unable to WRITE to check point file: '____', errno='____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: This error causes a retry action to be taken by the client if RETRYNUM is set in the MVS routing control file. If RETRYNUM is not specified or exceeded, the client puts the file on hold in the MVS JES spool. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of the file to guarantee data integrity.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-284

MVS Download Object: ____ - Unable to get MVS Download configuration path for destination:'____'

Explanation:: MVS Download detected a system error concerning file status.
System action:: MVS Download Object: unable to process host data.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-287

MVS Download Object ____ - Error changing directory to:'____'.

Explanation:: MVS Download detected a system error concerning file status.
System action:: MVS Download Receiver unable to process host data.
User response:: Check that the named directory does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the return code it contains.

0424-291

MVS Download Object ____ - Cannot open register value for: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-292

MVS Download Object ____ - Cannot remove register value for: '____'

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-293

MVS Download Object ____ - Cannot open register value for: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-294

MVS Download Object ____ - Cannot obtain register value for: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-295

MVS Download Object ____ - Cannot set name/value for: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-297

MVS Download Object ____ - Cannot add register value for: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-298

MVS Download Object: ____ - Unable to report event in system event log, errno= ____

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Check the event log for system error messages. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-299

MVS Download Object: ____ - Unable to register event for system event log, errno=____

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Check the event log for system error messages. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-300

MVS Download Object ____ - Unable to stop receiver: '____'.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Logon as 'administrator' and stop receiver. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-301

MVS Download Object: ____ - Unable to get registry data for receiver:'____', errno=____.

Explanation:: MVS Download detected a system error concerning registry status.
System action:: MVS Download logs warning and continues processing.
User response:: Using 'regedit', check that the named registry key does exist and access is allowed. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this error. When reporting this message, include the register value it contains.

0424-303

MVS Download Object: ____ - DEBUG: Received parameter string from MVS: ____.

Explanation:: This message is a result of the request for control file debug information. The indicated string is the parameter string received from MVS..
System action:: The indicated MVS keyword string will be processed using the MVS Download destination control file.
User response:: None.

0424-304

MVS Download Object: ____ - DEBUG: Generated parameter string: ____.

Explanation:: This message is a result of the request for control file debug information. The indicated string is the parameter string generated from the received MVS parameters using the destination control file.
System action:: The indicated string will be passed to the MVS Download exit routine.
User response:: None.

0424-305

MVS Download Object: ____ - DEBUG: Line ____ in the control file added Global parameter ____=____.

Explanation:: This message is a result of the request for control file debug information. The indicated Global statement in the destination control file identified this InfoPrint Manager attribute and parameter to be added to the parameter list.
System action:: The indicated InfoPrint Manager attribute and parameter were added to the parameter string.
User response:: None.

0424-306

MVS Download Object: ____ - MVS Download Exit submitted for file: ____ and destination: ____

Explanation:: The message is informational.
System action:: MVS Download invoked the exit routine specified when the MVS Download receiver was created.
User response:: No response is required.

0424-307

A data validation error occurred in the printer while printing this job. Inspect the output to determine if it is acceptable. The error occurred at document page ____ of copy ____.

Explanation:: The printer reported a data validation error, which means that it detected incorrectly printed data. For example, a bar code is unreadable.
System action:: This is an informational message.
User response:: Inspect the printed output and determine if all pages are acceptable. The job may need to be printed again.

0424-308

The printer reported a data validation error.

Explanation:: The printer reported a data validation error, which means that it detected incorrectly printed data. For example, a bar code is unreadable.
System action:: The operator can decide whether or not the job should continue printing after the error. If the job should not continue printing, the operator can determine the appropriate action to take for the disposition of this job.
User response:: Follow the instructions in the documentation for the printer to respond to this problem.

0424-309

A ribbon fault occurred in the printer while printing this job. Inspect the output to determine if it is complete and that all printed pages are acceptable.

Explanation:: The printer reported a ribbon fault.
System action:: This is an informational message.
User response:: Inspect the printed output and determine if all pages are acceptable.

0424-310

The printer reported a ribbon fault.

Explanation:: The printer reported a ribbon fault while printing a job.
System action:: After the ribbon fault is cleared, InfoPrint Manager recovers and printing continues..
User response:: Follow the instructions in the documentation for the printer to respond to this problem

0424-311

Inline resource group cannot exceed 2 Gbyte limit.

Explanation:: The segmenter was asked to generate a resource segment and the size of the segment exceeded the 2 Gbyte limit.
System action:: The current invocation of Input Manager terminates. This is a fatal error.
User response:: The print process cannot accept files greater than 2 Gbytes at this time. The print request may need to be broken into smaller pieces so that it can be processed correctly. The job upon which this error occurred will not print until the print request is modified.

0424-312

ERROR: The destination detected an unsupported object-area-origin-offset value in an IDO command.

Explanation:: An Include Data Object (IDO) command specified an invalid object-area-origin-offset value.
System action:: InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job.
User response:: Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-313

ERROR: The actual destination reported invalid data in a presentation object container.

Explanation:: The data in a presentation object container resource sent in a Write Object Container command is invalid.
System action:: If this error occurs within a page, InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job. Otherwise, InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job..
User response:: If you created the container data in the object container resource, correct the error. Refer to the appropriate documentation for the data stream carried within the object container resource. If you used a program to create the structured fields and object container data, contact the program owner.

0424-314

ERROR: The destination reported that a required data object resource was not found.

Explanation:

One of the following conditions occurred with a secondary resource while printing a data object:

A presentation data object referenced a data object resource by an internal resource ID, but there was no active Data Object Resource Equivalence (DORE) entry containing the referenced internal resource ID.
A presentation data object referenced a data object resource by an internal resource ID, a DORE equivalence entry with that internal resource ID was found, but the resource identified by the corresponding host assigned ID (HAID) was not activated.
The resource identified by a DORE equivalence entry with only a HAID was not activated when the resource was required to present a data object.
An Invoke Tertiary Resource (X'A2') triplet references a data object resource by an internal resource ID, but there is no active DORE equivalence entry containing the referenced internal resource ID.
An Invoke Tertiary Resource (X'A2') triplet references a data object resource by an internal resource ID, a DORE equivalence entry with that internal resource ID is found, but the resource identified by the corresponding HAID is not activated.

v

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-315

ERROR: The destination reported that an inappropriate secondary resource was invoked for a data object.

Explanation:: A data object resource was invoked for a presentation data object, but is not a valid object type for that data object.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-316

ERROR: The destination reported a mismatched color toner saver value for a saved page.

Explanation:: The color toner saver value in effect at the destination when it was including a page with an Include Saved Page command is different than the color toner saver value in effect when the page was saved. This error occurs when the color toner saver value saved with the saved pages in the destination for this job, when it was first printed, do not match the color toner saver value requested in the form definition or with the color-toner-saver document attribute at print time.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Change the form definition color toner saver specification or change the color-toner-saver document attribute for the job to match the color toner saver setting specified when the job was first submitted and saved OR resubmit the job so that a different job id is assigned. When a different job id is assigned, the pages will be newly saved; the previously saved pages will not be used and there will not be a color toner saver mismatch.

0424-317

ERROR: The destination detected an Include Tile Parameter that is out of sequence.

Explanation:: The sequence of self-defining fields within a series of WI2 commands is invalid. An Include Tile Parameter was encountered out of sequence or appeared more than once. An Include Tile Paramaeter must appear immediately after a Tile Position Parameter.
System action:: InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job
User response:: Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-318

ERROR: The destination detected an inconsistent Include Tile Parameter.

Explanation:: An Include Tile parameter was specified within an IOCA tile resource. Nested references are not allowed.
System action:: InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job.
User response:: Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-319

An asynchronous decompression error occurred.

Explanation:: The destination detected a data-related decompression error on a page. Incorrectly compressed JPEG image data within a data object or an IOCA image can cause this error.
System action:: After the asynchronous decompression error is cleared, InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Follow the instructions in the documentation for the destination to respond to this problem..

0424-320

An asynchronous decompression error occurred in the destination while processing this job

Explanation:: The destination has detected a data-related decompression error on a page. Incorrectly compressed JPEG image data within a data object or an IOCA image can cause this error.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error in the input print data. The error could be in the program which produces the input print data.

0424-321

ERROR: The destination detected an error in a GOCA graphics object.

Explanation:

The error occurred in an Graphics Object Content Architecture (GOCA) graphic. Using the IPDS exception from the preceding message (0420-249), match the exception to a description of the specific error in the following list. The exception list shows bytes 0, 1, and 19 of the 24 byte exception (sense) displayed as hexadecimal in the 0420-249 message:

X'03C0..00': In a Box or Box at Current Position drawing order, the HAXIS or VAXIS parameter is too large to fit the indicated corner into the size of the box.
X'03C0..01': In a Box or Box at Current Position drawing order, either the HAXIS or VAXIS parameter is outside the valid range.
X'03E3..00': In a Partial Arc or Partial Arc at Current Position drawing order, the calculated new current position for the endpoint of the arc is outside the limits of the graphics presentation space.
X'03E3..02': In a Partial Arc or Partial Arc at Current Position drawing order, the SWEEP angle is invalid (negative).
X'03E3..03': In a Partial Arc or Partial Arc at Current Position drawing order, the START angle is invalid (negative).

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Correct the error in the GOCA graphics data. The error could be in the program which produces the GOCA graphics data. Refer to the Graphics Object Content Architecture documentation for additional information.

0424-322

ERROR: The actual destination detected an error in an IOCA image object.

Explanation:

The error occurred in an Image Object Content Architecture (IOCA) image. Using the IPDS exception from preceding message 0420-249, match the exception to a description of the specific error in the following list. The list below shows bytes 0, 1 and 19 of the 24 bytes displayed in the 0420-249 message:

X'05F8..10'

One or more of the following occurred in the Image Data Description self-defining field within a Write Image Control 2 command:

The X-size or Y-size field within a Set Presentation Space Size self-defining field is invalid.
A Set Presentation Space Size self-defining field was specified, but both the X-size and Y-size can be specified using two bytes. When both values can be specified using two bytes, these values must be specified in IDD bytes 11-14 and the Set Presentation Space Size self-defining field must not be specified.
One or both of the size parameters in a Set Presentation Space Size self-defining field are greater than X'7FFF', but the corresponding value or values specified in IDD bytes 11-14 has not been set to X'7FFF'.

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Correct the error in the IOCA image data. The error could be in the program which produces the IOCA image data. Refer to the Image Object Content Architecture documentation for additional information.

0424-323

Invalid or unsupported data object error code = X'____'.

Explanation:: The error occurred in a presentation or non-presentation data object resource. Using the error code shown in this message, a specific description can be found in the 'Data Object Error Codes' section of the 'Exception Reporting' chapter in the Intelligent Printer Data Stream Reference.
System action:: See the action described in the accompanying messages. This is an informational message.
User response:: Correct the error in the data object resource. The error could be in the program which produces the data object resource.

0424-324

ERROR: The destination detected an invalid control value in a color toner saver triplet.

Explanation:: The color toner saver control value is invalid.
System action:: SInfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Change the color toner saver specification in the form definition or select a different form definition and resubmit the job.

0424-325

ERROR: The number of bits for a color component is invalid or unsupported.

Explanation:

One or more of the following conditions occurred:

An invalid or unsupported value was specified in Colsize1, Colsize2, Colsize3, or Colsize4 field of a Color Specification (X'4E') triplet. The triplet occurred in either a Logical Page Descriptor (LPD), Write Image Control 2 (WIC2), Write Graphics Control (WGC), Write Bar Code Control (WBCC), Write Text Control (WTC) command or Write Object Container Control (WOCC) command, Rasterize Presentation Object (RPO) command, or Include Data Object (IDO) command.
The Colsize fields in a Color Specification (X'4E') triplet specify length values that are inconsistent with the triplet length value.
An invalid or unsupported value was specified in Colsize1, Colsize2, Colsize3, or Colsize4 field of a PTOCA Set Extended Text Color (SEC) control sequence. The control sequence occurred in a Write Text command.
The Colsize fields in a PTOCA Set Extended Text Color (SEC) control sequence specify length values that are inconsistent with the control sequence length value.
An invalid or unsupported value is specified in the Colsize1, Colsize2, Colsize3, or Colsize4 field of a GOCA Set Process Color (GSPCOL) drawing order. The drawing order occurs in a Write Graphics command.
The Colsize fields in a GOCA Set Process Color(GSPCOL) drawing order specify length values that are inconsistent with the drawing order length value.

System action:

PSF stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Use local problem-reporting procedures to report this message.

0424-327

More than the current limit of ____ setup IDs were found in one medium map.

Explanation:: The InfoPrint Manager limit of 100 setup IDs in one medium map was exceeded.
System action:: Terminate job.
User response:: Contact your InfoPrint Manager representative. The current limit was chosen because it was very large relative to any projected use. The architectural limit is approximately 16K (limited by the number of keywords in an MMC structured field). A lower software limit is used to enhance performance.

0424-328

The requested setup ID ____ is not active at the actual destination console.

Explanation:: A setup ID for postprocessing was specified in the Medium Map but is not currently active at the actual destination hardware console.
System action:: Terminate job.
User response:: Have an operator activate the setup ID at the actual destination hardware console. This may also require changes in postprocessor configuration.

0424-329

Actual destination does not support resource management of presentation-object-containers.

Explanation:: The actual destination does not have the IPDS function required to present the resources required by this print job.
System action:: Terminate job.
User response:: Resubmit this job to an actual destination which supports all functions related to managing presentation-object-containers. Consult your hardware documentation to determine which devices support IPDS 'Data Object Resources'.

0424-330

OID reference ____ does not match unique identifer OID ____ found in resource.

Explanation:: To ensure data integrity, a unique identifier specified in a resource reference must match any unique identifier specified in the resource found when resolving the reference.
System action:: Terminate job.
User response:: Either the application which generated the printfile must be corrected or an updated version of the resource must be made available in the resource context for presentation-object-containers.

0424-331

presentation-object-container ____ not found

Explanation:: The presentation-object-container could not be activated at the printer or found in the resource context to be downloaded to the actual destination. The object may be a CMR (color management resource). This message will be issued if a CMR resource mapping was not found in the Color Management Resource Access Table, a CMR name is not 146 bytes long or a generic CMR in an inline resource group is not type halftone or tone transfer curve. If the object name in the message indicates the problem occurred when processing an object identifier (OID), InfoPrint Manager was unable to convert the OID value to a displayable format for the message.
System action:: Terminate job.
User response:: Make the specified resource available in the resource context for presentation-object-containers. If a CMR, make sure the Color Management Resource Access Table contains a mapping for the CMR. If the word OID was displayed in the message, use the offset in the MOD:CA input file displayed in an associated message to diagnose the problem.

0424-332

Invalid Fully Qualified Name (FQN) triplet type X'____' on a ____ structured field.

Explanation:: This is a MOD:CA datastream error. In a Fully Qualified name triplet there is a type value which is either unsupported or incorrect in the context of the structured field in which it appears, is not in the correct reference format (character string) or is required for this structured field.
System action:: Terminate job.
User response:: The application which generated this datastream must be corrected.

0424-333

Resource ____ used without being mapped on page.

Explanation:: In some scenarios, presentation-object-containers must be mapped ahead of time. An example is a secondary resource required by a resource being included through an Include Object (IOB) structured field.
System action:: Terminate job.
User response:: Try to print the job at an actual destination which is known to fully support resource management for presentation-object- containers. Check hardware documentation for support of IPDS 'Data Object Resources'. If the printer does have the needed function, the application which generated this print file is in error and must be corrected. The resource name specified on the IOB or PPO structured fields must match the name specified on the MDR structured field. Additionally for Color Management Resources (CMRs), the name, scope and processing mode on the MDR must match same on the IOB or PPO structured fields and the CMR reference in the datastream on the IOB or PPO must immediately be followed by a CMR Descriptor triplet to identify the resource as a CMR. Ensure the length of the x91 CMR Descriptor triplet on an MDR, IOB or PPO structured field is correct.

0424-334

A reference to a presentation-object container ____ could not be resolved.

Explanation:: This is the catch all message for any error encountered while attempting to process a reference to a presentation-object-container. It is likely that other messages appear which give more detail on what the exact nature of the error was.
System action:: Terminate job.
User response:: See the response for other errors listed on the message page. Also check the PSF trace file for exceptions raised by the primary print process. If no other errors are listed, an unknown error has occurred, so contact your service representative. If using Color Management Resources (CMRs) or Data Object Resources, an object named in a resource access table may not have been found.The resource access table must reside in the same library as the objects the table refers to.

0424-335

Usage: iconv -f FromCodePage -t ToCodePage [Filename]

Explanation:: The syntax of the iconv command is incorrect. Inspect the syntax and try again.
System action:: This is an informational message.
User response:: Inspect the command syntax.

0424-336

The specified input file cannot be opened for read.

Explanation:: The iconv command cannot open the specified input file. The file does not exists.
System action:: This is an error message.
User response:: Check if the specified input file exists.

0424-337

The registry key for InfoPrint Manager does not exist.

Explanation:: The iconv command cannot find the registry key for InfoPrint Manager.
System action:: This is an error message.
User response:: Check if InfoPrint Manager is correctly installed. Reinstall InfoPrint Manager if necessary.

0424-338

The install path for InfoPrint Manager is not found.

Explanation:: The iconv command cannot find the install path for InfoPrint Manager.
System action:: This is an error message.
User response:: Check if InfoPrint Manager is correctly installed. Reinstall InfoPrint Manager if necessary.

0424-339

The iconv DLL cannot be loaded.

Explanation:: The iconv command cannot load the iconv DLL.
System action:: This is an error message.
User response:: Check if InfoPrint Manager is correctly installed. Reinstall InfoPrint Manager if necessary.

0424-340

The iconv functions in DLL cannot be found.

Explanation:: The iconv command cannot find the iconv functions.
System action:: This is an error message.
User response:: Check if InfoPrint Manager is correctly installed. Reinstall InfoPrint Manager if necessary.

0424-341

The iconv_config call failed.

Explanation:: The iconv_config call cannot set the environment variable (LOCPATH).
System action:: This is an error message.
User response:: Consult your system administrator.

0424-342

The iconv_init call failed.

Explanation:: The iconv_init call returns an error code.
System action:: This is an error message.
User response:: Check if the input code page and the output code page pair is valid.

0424-343

The iconv_convert call failed.

Explanation:: The iconv_convert call returns an error code.
System action:: This is an error message.
User response:: Check if the input date is not corrupt and the output buffer has enough room for the converted characters.

0424-344

The iconv_term call failed.

Explanation:: The iconv_term call returns an error code.
System action:: This is an error message.
User response:: Check if the iconv handle is a valid handle.

0424-345

The punch waste bin is full; empty the punch waste bin.

Explanation:: The actual destination reports that the punch waste bin is full and must be emptied before printing can resume.
System action:: After the punch waste bin is emptied, InfoPrint Manager recovers and printing continues.
User response:: Empty the punch waste bin.

0424-346

The host receiver ____ has stopped.

0424-347

DPF resource database not initialized or application not connected.

Explanation:: An attempt was made to perform an operation on the DPF resource database but the database has not been initialized or the application was not connected to the database.
System action:: The process failed.
User response:: Initialize the database by selecting Debug->Re-create DPF Resource Database in the Management Console and retry the operation. If the problem persists, contact your service representative.

0424-348

DPF resource database has too many active connections.

Explanation:: An attempt was made to connect to the DPF resource database but the database already had the maximum number of active connections.
System action:: The process failed.
User response:: Retry the operation. If the problem persists, the server may have too many DPF receivers and associated destinations on it. Consider moving some of the DPF receivers and associated destinations to another InfoPrint Manager.

0424-349

DPF resource database found duplicate entries with type ____ and name ____.

Explanation:: The DPF resource database found duplicate entries with the same resource type and member name.
System action:: The process failed.
User response:: Contact your service representative.

0424-350

DPF resource database cannot find entry with type ____ and name ____.

Explanation:: The DPF resource database could not find an entry with the specified resource type and member name.
System action:: The process failed.
User response:: Contact your service representative.

0424-351

DPF resource database cannot delete entry with type ____ and name ____.

Explanation:: The DPF resource database could not delete the entry with the specified resource type and member name. The entry may still be marked as being used.
System action:: The process failed.
User response:: If you received this error after you tried to delete a resource in the Management Console, wait and retry the operation again later. Otherwise, contact your service representative.

0424-352

DPF resource database cannot find entry with GRN name ____.

Explanation:: The DPF resource database could not find an entry with the specified GRN member name..
System action:: The process failed.
User response:: Contact your service representative.

0424-353

Cannot open file ____.

Explanation:: This file could not be opened.
System action:: The process failed.
User response:: Check the permissions for this file and try your request again. If your request continues to fail, contact your support personnel and ask them to verify that the file system is not full. If the file is on a mounted file system, ask them to verify that the file system is properly mounted and operational.

0424-354

System function ____ returned error number ____.

Explanation:: A call was made to a system function or command that returned an error code.
System action:: The process failed.
User response:: Refer to your system documentation to look up the error value. If you cannot determine the cause of the failure. Contact your service representative.

0424-355

Deletion of the file ____ failed with return code ____.

Explanation:: InfoPrint Manager encountered an error while trying to delete the temporary file.
System action:: The process failed.
User response:: No response is required to this informational message.

0424-356

The submission of the received job failed with return code ____.

Explanation:: The Distributed Print Function (DPF) host receiver cannot submit the received job to InfoPrint Manager.
System action:: The host receiver stops processing and is disconnected.
User response:: See the accompanying messages to determine the cause of the submission failure. Correct the problem and restart the host receiver. The host receiver will attempt to submit the job when it is started. If the problem cannot be corrected, the host receiver must be deleted.

0424-357

The submission error message is: ____

Explanation:: The error received on submission of the job is provided.
System action:: The host receiver stops processing and is disconnected.
User response:: Correct the problem and restart the host receiver. The host receiver will attempt to submit the job when it is started. If the problem cannot be corrected, the host receiver must be deleted.

0424-381

ERROR: The destination detected an error in a 2D bar code object.

Explanation:

The error occurred in a Bar Code Object Content Architecture (BCOCA) object sent in a Write Bar Code (WBC) command. Using the IPDS exception from the preceding message (0420-249), match the exception to a description of the specific error in the following list. The exception list shows bytes 0, 1, and 19 of the 24 byte exception (sense) displayed as hexadecimal in the 0420-249 message.

X'040F..00'

Either the matrix row size value or the number of rows value specified in the BSA data structure is unsupported. Both of these values must be within the range of supported sizes for the symbology.

X'040F..01'

An invalid structured append sequence indicator was specified in the BSA data structure. For a Data Matrix symbol, the sequence indicator must be between 1 and 16 inclusive. For a MaxiCode symbol, the sequence must be between 1 and 8 inclusive.

X'040F..02'

A structured append sequence indicator specified in the BSA data structure is larger than the total number of structured append symbols.

X'040F..03'

Mismatched structured append information was specified in the BSA data structure. One of the sequence-indicator and total-number-of-symbols parameters was X'00', but the other was not X'00'.

X'040F..04'

An invalid number of structured append symbols was specified in the BSA data structure. For a Data Matrix symbol, the sequence indicator must be between 2 and 16 inclusive. For a MaxiCode symbol, the total number of symbols must be between 2 and 8 inclusive.

X'040F..05'

An invalid symbol mode value was specified in the BSA data structure.

X'040F..06'

For a PDF417 symbol, an invalid data symbol characters per row value was specified in the BSA data structure.

X'040F..07'

For a PDF417 symbol, an invalid desired number of rows value was specified or the number of rows times the number of data symbol characters is greater than 928.

X'040F..08'

For a PDF417 symbol, too much data was specified in the BSA data structure.

X'040F..09'

For a PDF417 symbol, an invalid security level value was specified in the BSA data structure.

X'040F..0A'

An incompatible combination of Data Matrix parameters was specified.

X'040F..0B'

An invalid structured append file identification value was specified.Each byte of the 2-byte file identification value must be in the range X'01'-X'FE'.

X'040F..0C'

An invalid Macro PDF417 Control Block length value was specified in the BSA data structure or the length of the Macro PDF417 Control Block was too large.

X'040F..0D'

For a PDF417 symbol, an error occurred within the data for a Macro PDF417 Control Block specified in the BSA data structure.

X'040F..0E'

The EBCDIC-code-page parameter value specified in the BSA data structure is invalid.

X'040F..0F'

The version parameter value specified in the BSA data structure is invalid.

X'040F..10'

The error-correction-level parameter value specified in the BSA data structure is invalid.

X'040F..11'

An incompatible combination of special-function flags was specified in the BSA data structure. Only one of the FNC1 flags can be B'1'.

X'040F..12'

The application-indicator value specified in the BSA data structure in a Write Bar Code command is invalid.

X'040F..16'

Too much data is specified in the BSA data structure in a Write Bar Code command, and the too-much-data flag in the BSA forbids making the QR Code version bigger to fit the data.

X'040F..30'

One or both of the following conditions exist for the image information length in the BSA data structure in a Write Bar Code command:

The length is invalid.
The length is too large to fit into the repeating groups total length.

X'040F..31'

The image-local-ID parameter value in the BSA data structure in a Write Bar Code command is outside the valid range.

X'040F..32'

The unit-base parameter value for the image-object-area offset, specified in the BSA data structure in a Write Bar Code command, is invalid or unsupported.

X'040F..33'

The units-per-unit-base parameter value for the image-object-area offset, specified in the BSA data structure in a Write Bar Code command, is invalid or unsupported.

X'040F..34'

One or both of the following conditions exist in the BSA data structure in a Write Bar Code command:

The X offset value for the image-object-area origin is invalid or unsupported.
The Y offset value for the image-object-area origin is invalid or unsupported.

X'040F..35'

The image-object-area orientation parameter value specified in the BSA data structure in a Write Bar Code command is invalid or unsupported.

X'040F..36'

The image-object-area reference-coordinate-system parameter value specified in the BSA data structure in a Write Bar Code command is invalid or unsupported.

X'040F..37'

The unit-base parameter value for the image-object-area extent, specified in the BSA data structure in a Write Bar Code command, is invalid or unsupported.

X'040F..38'

The units-per-unit-base parameter value for the image-object-area extent, specified in the BSA data structure in a Write Bar Code command, is invalid or unsupported.

X'040F..39'

One or both of the following conditions exist in the BSA data structure in a Write Bar Code command:

The X extent value for the image object area is invalid or unsupported.
The Y extent value for the image object area is invalid or unsupported.

X'040F..3A'

The mapping-option parameter value specified in the BSA data structure in a Write Bar Code command is invalid or unsupported.

X'040F..3B'

The repeating-groups-total-length parameter value in the BSA data structure in a Write Bar Code command is invalid.

System action:

InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job.

User response:

Correct the error in the BCOCA bar code data. The error could be in the program which produces the BCOCA bar code data. Refer to the 'BCOCA Reference' for additional information.

0424-385

PPO structured field encountered but printer does not support this function.

Explanation:: A PPO (Preprocess Presentation Object) structured field was encountered in the print file but the printer does not support this.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise InfoPrint Manager cancels the job.
User response:: Correct the print file, and submit the print job again.

0424-386

The presentation object named ____ on a PPO structured field was not previously mapped with an MDR structured field.

Explanation:: The object named on the PPO structured field was not previously mapped with an MDR structured field so the object cannot be preprocessed by the printer.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise InfoPrint Manager cancels the job.
User response:: Correct the print file, and submit the print job again.

0424-387

PPO structured field found in print file that uses color mapping table.

Explanation:: A PPO (Preprocess Presentation Object) structured field was encountered in the print file but the print file uses a color mapping table. The printer will preprocess the object in this situation but the preprocessed object will not be used for the color mapping table job but will stay in the printer for subsequent jobs.
System action:: InfoPrint Manager continues processing the print job. Printing of subsequent pages in the job is not affected but printing performance is likely to be adversely affected.
User response:: Correct the print file, and submit the print job again.

0424-389

ERROR: The Finishing Fidelity continue value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid continue value on a Presentation Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-390

ERROR: The Finishing Fidelity report value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid report value on a Print Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-391

InfoPrint Manager canceled printing of the file because a finishing error occurred and finishing fidelity of STOP was requested.

Explanation:: InfoPrint Manager stops processing the file as part of InfoPrint Manager error recovery. The actual destination reported an exception which indicates an invalid or unsupported finishing-value was requested. Because finishing fidelity was requested, the normal recovery for this exception is not taken. Instead, the file is canceled. Finishing fidelity is requested in the form definition (FORMDEF). The form definition used with this print file requested that finishing exceptions be reported and that printing be stopped at the point of the first finishing exception.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the causes of the other error messages in this message group.

0424-392

The UP3I-controlled device ____ required intervention because of an equipment check. The error code is X'____'.

Explanation:: A UP3I-controlled pre-processing or post-processing device attached to the printer has reported an equipment check error that is also an intervention required condition.
System action:: The system action taken varies depending on the classification of the exception.
User response:: Check the UP3I-controlled device manual for more information about this error.

0424-393

The UP3I-controlled device ____ required intervention. The error code is X'____'.

Explanation:: A UP3I-controlled pre-processing or post-processing device attached to the printer has reported an intervention required condition.
System action:: The system action taken varies depending on the classification of the exception..
User response:: Check the UP3I-controlled device manual for more information about this error.

0424-394

The UP3I-controlled device ____ reported an equipment check. The error code is X'____'.

Explanation:: A UP3I-controlled pre-processing or post-processing device attached to the printer has reported an equipment check error that can not be corrected by an operator.
System action:: The system action taken varies depending on the classification of the exception..
User response:: Check the UP3I-controlled device manual for more information about this error.

0424-395

The UP3I-controlled device ____ reported an invalid or unsupported parameter. The error code is X'____'.

Explanation:: A specification error was detected for a UP3I-controlled pre-processing or post-processing device.
System action:: The system action taken varies depending on the action code. Finishing is suppressed for the rest of the job.
User response:: Check the UP3I-controlled device manual for more information about this error.

0424-396

The UP3I-controlled device ____ reported a condition requiring host notification. The error code is X'____'.

Explanation:: A UP3I-controlled pre-processing or post-processing device attached to the printer has reported a condition requiring host notification.
System action:: The system action taken varies depending on the classification of the exception.
User response:: Check the UP3I-controlled device manual for more information about this error.

0424-397

Could not locate media ____, and media fidelity is STOP.

Explanation:: InfoPrint Manager could not locate the requested media. If media fidelity is CONTINUE, InfoPrint Manager may continue by performing input bin substitution. If font fidelity is STOP, InfoPrint Manager will halt.
System action:: InfoPrint Manager may continue processing depending on the value of media fidelity.
User response:: If InfoPrint Manager can not locate the media, correct the problem at the printer or specify media fidelity CONTINUE and resubmit the job.

0424-398

InfoPrint Manager located a ____ Presentation Fidelity triplet in the Formdef indicating processing should continue with exceptions not reported. Processing continues.

Explanation:: The user requested finishing fidelity with a continuation rule of DO NOT STOP (X'02') and an exception reporting rule of DO NOT REPORT (X'02'). The printer does not support finishing fidelity and thus does not control the reporting of unsupported or incorrect finishing values. InfoPrint Manager will not issue messages for finishing exceptions reported by the printer that are controlled by finishing fidelity. However, because the printer is still reporting the exceptions, InfoPrint Manager must perform the necessary recover and performance of the print job might be impacted.
System action:: InfoPrint Manager continues processing the files.
User response:: If you experience performance problems with the job due to InfoPrint Manager managing the exceptions, you may want to send the job to a printer that supports finishing fidelity or change the formdef to set the continuation rule to STOP when you run to a printer that does not support finishing fidelity.

0424-399

Output bin number ____, specified on the output-bin or output-bin-numbers attribute is not supported or not available.

Explanation:: An output bin number was specified on the output-bin or output-bin-numbers attribute. This bin is not available.
System action:: InfoPrint Manager disables the actual destination.
User response:: Specify a different output bin, or do not specify an output bin. If no output bin is specified, InfoPrint Manager will select an output bin.

0424-400

ERROR: Invalid Unicode data.

Explanation:: There is an error in Unicode data specified on the current page.
System action:: InfoPrint Manager stops processing the page at the point of the error. If there are other pages in this print job, InfoPrint Manager resumes processing starting with the next page in the job; otherwise, InfoPrint Manager terminates the job.
User response:: Use the accompanying messages to determine if the Unicode data causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-401

ERROR: Invalid TTC-font-index value in a linked font triplet.

Explanation:: The print job references a TTC-font-index value in a linked font triplet which does not exist for that linked font.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-402

ERROR: Invalid full-font-name value in a linked font triplet.

Explanation:: The print job references full-font-name value in a linked font triplet which does not exist for that linked font.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-403

ERROR: Invalid or unsupported encoding-scheme-ID value in an encoding scheme ID triplet.

Explanation:: The encoding-scheme-ID value specified in an encoding scheme ID triplet is invalid. See the 'MO:DCA Reference' for further information on this triplet.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-404

ERROR: Invalid font-technology value..

Explanation:: Invalid font technology value in Data-Object Font Descriptor Triplet. The value X'20' signifies TrueType/OpenType technology.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-405

ERROR: Invalid vertical-font-size value.

Explanation:: Invalid vertical-font-size value in a Data-Object Font Descriptor Triplet. The only valid values are in the range 1 to 32767.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-406

ERROR: Invalid horizontal-scale-factor value.

Explanation:: Invalid horizontal-scale-factor value in a Data-Object Font Descriptor Triplet. If it is to be explicitly specified, the only valid values are in the range 1 to 32767. When a X'0000' is specified, the horizontal scaling is identical to the vertical scaling.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-407

ERROR: Invalid character-rotation value.

Explanation:

The character-rotation value specified in a Data-Object-Font triplet is invalid. Valid character rotations are:

For 0 degrees (left-to-right writing), specify X'0000'.
For 90 degrees (bottom-to-top writing), specify X'2D00'.
For 180 degrees (right-to-left writing), specify X'5A00'.
For 270 degrees (top-to-bottom writing), specify X'8700'.

System action:

InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-408

ERROR: Invalid encoding environment value.

Explanation:: The encoding environment (in TrueType/OpenType font files this parameter is called the 'Platform ID'.) value specified in a Data-Object-Font triplet is invalid. A value of X'0003' for this parameter signifies a Microsoft encoding environment.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-409

ERROR: Invalid environment-specific encoding identifier value.

Explanation:: The environment-specific encoding identifier value specified in in a Data-Object Font Descriptor Triplet is invalid. The values that are valid for the encoding identifier depend on the specific encoding environment parameter. For the Microsoft encoding environment (EncEnv = X'0003'), the encoding identifier X'0001' (Unicode) is valid.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-410

ERROR: Unknown character ID (GCGID) value.

Explanation:

An unknown Graphic Character Global ID (GCGID) value was found within a code page used with a data-object font

One of the following conditions has occurred:

The GCGID was not mapped to a Unicode value by the printer's GCGID to Unicode Mapping table or by the Unicode Extended Code Page.
The GCGID is defined in a Unicode Extended Code Page, which the printer does not support, so the Unicode mapping is not being used by the printer. To tell if your printer supports Unicode Extended code pages, determine if the Sense Type and Model (STM) Loaded-Font Command-Set Vector contains the X'B005' - Extended (Unicode mapping) code page support property pair.

System action:

InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.

User response:

Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-411

ERROR: InfoPrint Manager located a Presentation Text Fidelity triplet but the printer does not suppport presentation text fidelity processing. Processing continues.

Explanation:: The printer does not support presentation fidelity and thus does not control the reporting of unsupported or incorrect values. InfoPrint Manager will not issue messages for exceptions reported by the printer that are controlled by presentation text fidelity. However, because the printer is still reporting the exceptions, InfoPrint Manager must perform the necessary recover and performance of the print job might be impacted.
System action:: InfoPrint Manager continues processing the files.
User response:: If you experience performance problems with the job due to InfoPrint Manager managing the exceptions, you may want to send the job to a printer that supports presentation text fidelity.

0424-412

ERROR: Actual Destination does not support resource management of Data Object Fonts.

Explanation:: The current job defines a Data Object Font (DOF) and DOFs are not supported by the specified actual destination.
System action:: Terminate job.
User response:: Resubmit this job to an actual destination which supports all functions related to managing data object fonts. Consult your hardware documentation to determine which devices support IPDS 'Data Object Fonts'.

0424-413

The font in error consists of the code page ____ and the data object font component ____.

Explanation:: This message provides more information about the code page and data object font component causing the font problem.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0424-414

The font in error consists of the encoding scheme ____ and the data object font component ____.

Explanation:: This message provides more information about the encoding scheme and data object font component causing the font problem.
System action:: See the system actions for other error messages in this message group.
User response:: See the responses for other error messages in this message group.

0424-447

ERROR: The Text Fidelity continue value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid continue value on a Presentation Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-448

ERROR: The Text Fidelity report value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid report value on a Print Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-449

The uconv codepoint conversion for a name on the ____ structured field repeating group number ____ failed.

Explanation:: The uconv codepage conversion call is enabled to convert a character string. This could be due to an error in the MO:DCA datastream or an error due to the system being out of memory.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the structured field in error and resubmit the job.

0424-450

ERROR: MICR printing was requested, but is not available.

Explanation:: A string of text was encountered that was to be printed with a MICR font, but MICR printing is not available. Some printers can print MICR text on one side of the medium, but not the other side, and generate this message when MICR printing is requested on the unsupported side.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Send the print job to a different MICR actual destination, or correct the problem with this MICR actual destination.

0424-451

ERROR: Invalid form length value ____ specified.

Explanation:: The form length value specified in a MDD (Medium Descriptor) structured field or on a pdpr command line is invalid. The only valid values are in the range 1 to 32767 or equal to 16777215 (X'FFFFFF').
System action:: InfoPrint Manager ignores the specified value and defaults to the form length value set on the printer console.
User response:: Use the accompanying messages to determine if the value causing the error is in the input file or on the pdpr command line. The program or person who created the input file or command line most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-452

ERROR: Unable to create a thread from ____. Return code=____.

Explanation:: The executable program specified in the message attempted to create and start a thread but could not start the thread. The Windows Return Code should explain the reason.
System action:: InfoPrint Manager does not complete the operation.
User response:: Depends on the Return Code. See Windows documentation for information on the meaning of the Return Code.

0424-454

MVS Download Object: ____ - Encountered a codepage conversion problem. A default codepage was used

Explanation:: MVS Download receiver encountered a uconv error while processing JCL parameters.
System action:: MVS Download receiver attempts recovery and continues using a default codepage.
User response:: Check the codepages specified when starting the MVS Download receiver to see if they are correct for the JCL parameters. See the section on the mvsprsd utility in the 'InfoPrint Manager: Reference' manual for more information.

0424-455

MVS Download Object: ____ - Unsupported codepage ____ specified.

Explanation:: An unsupported codepage was specified when starting the MVS Download receiver.
System action:: This error causes the MVS Download Receiver to terminate initialization processing.
User response:: The specified codepage is not available. Try another codepage. See the section on the mvsprsd utility in the 'InfoPrint Manager: Reference' manual for more information.

0424-457

MVS Download Object: ____ - usage: mvsprsd -p<n> -d<f> [-d<f>] [-q<n>] [-x<s>] [-k] [-n 1] [-e] [-w] [-B] [-H<s>] [-L<s>] [-t]

Explanation:

MVS Download service invocation error.

MVS Download Object: ____ - usage: mvsprsd -p<n> -d<f> [-d<f>] [-q<n>] [-x<s>] [-k] [-n 1] [-e] [-w] [-B] [-H<s>] [-L<s>] [-t]

where:

-p<n>: port number (required)
-d<f>: file systems (required)
-q<n>: queue name (required with -x option)
-x<s>: exit program name
-k: If the MVS JCL parameter file is to be kept.
-n 1: The daemon is to process one file to completion before accepting the next file.
-e: Provide error information to the mainframe.
-w: Wait for the exit to complete.
-B: a limited EBCDIC to ASCII conversion
-H<s>: host codepage where JCL is submitted
-L<s>: local codepage where MVS download is running
-t: enable receiver trace

Note: These flags are included with the message text when the message is issued.

System action:

MVS Download Receiver unable to process host data.

User response:

Reference system manual.

0424-458

ERROR: Invalid data in a UCC/EAN 128 or RSS bar code.

Explanation:

Data for a UCC/EAN 128 or RSS bar code in the SBA data structure in a Write Bar Code command is invalid. One or more of the following conditions was encountered:

FNC1 is not the first data character
Invalid application identifier (ai) value encountered
Data for an ai doesn't match the ai definition
Insufficient or no data following an ai
Too much data for an ai
Invalid use of the FNC1 character

System action:

InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job.

User response:

Correct the error in the BCOCA bar code data. The error could be in the program which produces the BCOCA bar code data. Refer to the Bar Code Object Content Architecture documentation for additional information.

0424-459

ERROR: Invalid height values for Reduced Space Symbology (RSS) bar code modifier.

Explanation:: The combination of element height and height multiplier values specified for a Reduced Space Symbology (RSS) bar code in the bar code data-descriptor self-defining field is invalid for the modifier specified.
System action:: InfoPrint Manager stops processing the page containing the error; printing continues with the next page in the print job.
User response:: Correct the error in the BCOCA bar code data. The error could be in the program which produces the BCOCA bar code data. Refer to the Bar Code Object Content Architecture documentation for additional information.

0424-460

The PSF buffer size for printer '____' is too large. PSF has been reconfigured to the buffer size required by the printer ('____').

Explanation:: The default PSF buffer size configured for the specified printer is larger than the printer will accept.
System action:: InfoPrint Manager disables the actual destination and reconfigures PSF to the proper buffer size. PSF will now use the proper buffer size.
User response:: This error will only occur once. Enable the actual destination.

0424-461

The terminate message count value '____' is not valid. InfoPrint Manager will use a value of 0.

Explanation:: Valid terminate message count values are in the range 0 to 9999. A value of 0 specifies that the job should not terminate as a result of the number of messages issued. The terminate message count value specified with the print request was not within this range.
System action:: InfoPrint Manager ignores the value specified for the terminate message count, uses the default value of 0, and continues processing the print job.
User response:: The terminate message count can be specified from the command line with the termmsgcount keyword. Specify a value between 0 and 9999 with the print request.

0424-462

The job has been terminated because the job-terminate-message-count limit has been reached.

Explanation:: InfoPrint Manager stops processing the file because the number of messages issued reached the value specified in job-terminate-message-count.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the causes of the other error messages issued.

0424-463

The actual destination reported the media loaded does not match the FORMID selected at the printer console.

Explanation:

The actual destination reported the media loaded in the printer does not match the form that was selected at the printer console. The actual destination detected and reported an asynchronous intervention-required error with an action code of X'0A' (sense byte 2). Bytes 0, 1, and 19 of the error are X'4035..00'. For more information about this error, refer to the publications for the actual destination that reported the error. Printing cannot continue until the mismatch is resolved.

System action:

After the mismatch is resolved, InfoPrint Manager recovers and printing continues.

User response:

Clear the paper up to the jam recovery page counter. Perform the following tasks in order to continue printing:

Verify the correct form for the job is selected at the printer console. If the correct form is not selected, change it to the correct form.
Load the paper that matches the form selected at the printer console. For a continuous forms printer, be sure to NPRO the correct paper up to the jam recovery page counter.
If the correct paper for the job is not available, do one of the following:
1. Cancel the job at the printer console. The job will need to be resubmitted when the correct paper is available.
2. Disable the verifier and continue printing with the paper that is available. PSF assumes that pages between the jam recovery page counter and the stacked page counter are not damaged and do not need to be reprinted. If any pages between these two counters do need to be reprinted, use the backspace function.

0424-464

A forms mismatch occurred in the actual destination while printing this job. Inspect the output to determine if all printed pages are acceptable.

Explanation:: A forms mismatch can be resolved without the loss of pages in the job or any reduction in print quality. Printed output should be carefully inspected after a forms mismatch has occurred to be sure the job was printed on the correct form.
System action:: This is an informational message. The system action was defined in another error message about the forms mismatch.
User response:: Inspect the printed output, and determine if all pages are acceptable.

0424-465

The error message page for the job could not be printed. Conversion from UTF-8 to codepage '____' failed with return code '____'.

Explanation:: Conversion of message page messages to a printable format failed. The message page will not be printed.
System action:: Processing of the job stops.
User response:: The system could be out of memory or the system does not have the appropriate locales installed. Contact the system administrator to be sure the appropriate codepages are installed. If the problem continues, use local reporting procedures to report the problem.

0424-466

MVS Download Object: '____' - A multi-dataset file sequence error occurred.

Explanation:: A multi-dataset file sequence error occurred. This may occur because the host system is retrying a file that was failed by the script/exit and reported back to the host, an invalid system configuration is in use, the 0000*.JOB files in the Download working directory have been erased, the mvsprsd.mdsid file in the working directory has been erased, or a logic error occurred.
System action:: MVS Download continues processing. If an invalid configuration is in use, print data has been lost. If files have been previously erased from the working directory, the partial data is overwritten. If the script/exit did not clean up properly, print data may be lost depending on the coding of the script/exit.
User response:: If the host system is retrying a file that has been failed by the script/exit, ignore this message. If MVS Download is being used with multi-dataset active, verify that only one FSA is driving the receiver/daemon. If files(s) have been erased from the Download working directory, ignore this message. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error.

0424-467

MVS Download Object: '____' - An invalid multi-dataset ID of '____' s received.

Explanation:: An invalid MVS Download multi-dataset ID was received from the host. Either the ID is not in the proper format or a multi-dataset ID has already been assigned.
System action:: InfoPrint Manager does not complete printing of the AFP print job.
User response:: Use local problem reporting procedures to report this error.

0424-468

MVS Download Object: '____' - The MVS Download server encountered a '____' error when accessing the MDS ID database, errno= '____'

Explanation:: An MVS Download processing error occurred or the same working directory is being used for two daemons that are using the Download Plus multi-dataset function.
System action:: InfoPrint Manager does not complete printing of the AFP print job.
User response:: If the message indicates an fcntl error with an errno of 13, two daemons are using the same working directory and are using the Download multi-dataset function. Start the daemons using different working directories. For all other errors, complete all multi-dataset jobs if possible. Stop the Download daemon/receiver that is reporting the error. Delete the mvsprsd.mdsid file in the download working directory. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0424-469

MVS Download Object: '____' - MVS Download Script/Exit for file: '____' failed with return code of '____'.

Explanation:: The script/exit invoked by the daemon/receiver returned a non-zero return code.
System action:: InfoPrint Manager continues processing files.
User response:: For the InfoPrint Manager provided script/exit, an error message is written to the InfoPrint Manager server log and mvsd.log in the download working directory indicating the cause of the failure. For custom script/exits, consult the writer of the script/exit for information on obtaining additional information.

0424-470

MVS Download Object: '____' - A multi-dataset ID of '____' was received but is not currently active.

Explanation:: The mainframe attempted to use a multi-dataset ID that has not been assigned to any active job. This may occur if the mvsprsd.mdsid file was erased from the Download working directory when a multi-dataset file had not completed or a logic error occurred.
System action:: InfoPrint Manager does not complete printing of the AFP print job.
User response:: If the mvsprsd.mdsid file has been erased from the Download working directory, resubmit the job to the JES spool. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error.

0424-471

MVS Download Object: '____' - No multi-dataset IDs are available.

Explanation:: The daemon/receiver has run out of multi-dataset IDs due to 65535 incomplete multi-dataset jobs.
System action:: InfoPrint Manager does not complete printing of the AFP print job.
User response:: Check the Download working directory and delete old files for jobs that will never complete. Be sure to examine the files matching the format 0000*.JOB and delete the files as appropriate. After deleting the files, submit another job. If the error cannot be corrected or the error occurs again, use local problem reporting procedures to report this error.

0424-472

MVS Download Object: '____' - Is starting.

Explanation:: The daemon/receiver is starting.
System action:: The daemon/receiver begins accepting files from the mainframe.
User response:: None.

0424-473

MVS Download Object: '____' - Is stopping.

Explanation:: The daemon/receiver is starting.
System action:: The daemon/receiver begins accepting files from the mainframe.
User response:: If the daemon/receiver stopped unexpectedly, check for previous messages for the cause of the error.

0424-474

MVS Download Object: '____' - The MVS Download server encountered a '____' error when attempting to read the script/exit error message, errno='____'.

Explanation:: An MVS Download processing error occurred.
System action:: InfoPrint Manager continues processing files.
User response:: Use local problem-reporting procedures to report this message.

0424-475

The metric adjustment triplet in the Coded Font Control (CFC) structured field contains an incorrect, unsupported or out of range value.

Explanation:

One of the following conditions occurred in a metric adjustment triplet contained in a Coded Font Control (CFC) structured field:

The Unit Base field contained an incorrect value
The XUPUB or YUPUB field contained an incorrect or unsupported value
The combination of the baseline offset adjustment value and a character's baseline offset value is outside the range the printer can handle

System action:

InfoPrint Manager stops processing the file.

User response:

If you created the coded font, correct the error and resubmit the print job. See the FOCA Reference for more information about the CFC structured field. If you used a program to create the font, contact the program owner.

0424-476

MVS Download Object: ____ - A file decompression error occurred in function ____, errno = ____.

Explanation:: A decompression error occurred while attempting to decompress a file from the client. This can occur due to data corruption during transmission or an out of disk space condition in the MVS Download working directory on the server.
System action:: This error causes a retry action to be taken by the client. When retry is attempted for the errors related to checkpoint/restart, MVS Download could restart from the beginning of a file to guarantee data integrity.
User response:: If the problem persists, verify that there is sufficient space available on the file system. The required space is two times the size of the file being downloaded

0424-477

MVS Download Object: ____ - A compression protocol state error occurred.

Explanation:: A state error occurred in the communication protocol between the client and the server.
System action:: InfoPrint Manager does not complete printing of the AFP print job.
User response:: Use local problem reporting procedures to report this error.

0424-478

Image Resolution required but not supplied.

Explanation:: The image Resolution for a presentation object such as TIFF, GIFF, or JPEG, is needed to process the object but the resolution was not provided within the presentation object and was not provided by an Image Resolution Triplet.
System action:: InfoPrint Manager and the printer continue processing the file. The printer did not know at which resolution to render the image and used the print head resolution.
User response:: Examine the output to see if the object was printed at the correct size. Recreate the object with the resolution provided with the object or put an image resolution triplet in the MOD:CA datastream indicating the resolution the image was created for and send the job again. Without resolution information, the object might not print correctly if the job is printed on more than one printer or if the printer resolution setting is changed at the printer console. If resolution information is added to the object itself or the image resolution triplet is specified on the Include Object (IOB), Container Data Descriptor (CDD), or Preprocess Presentation Object (PPO) structured field, this message will not be issued.

0424-479

The actual destination reported an invalid or unsupported unit base value.

Explanation:: The printer reported an unsupported or invalid unit base value in an image resolution triplet on either an Include Object (IOB), Container Data Descriptor (CDD), or Preprocess Presentation Object (PPO) structured field. Either the X unit base or Y unit base fields contained an invalid or unsupported value, the X unit base and Y unit base fields does not match, or the unit base value of centimeters (x01) is specified and the device does not support this unit base value.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Change the unit base value to be expressed as inches. See the MO:DCA reference for more information.

0424-480

ERROR: The X or Y Resolution value X'____' in a triplet with identifier ____ in a ____ structured field is not valid.

Explanation:: The Resolution field on an image resolution triplet must be in the range of 1 - 32767. The triplet was specified on an IOB, PPO or CDD structured field and contained a value outside this range.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-481

ERROR: The X-Base and Y-Base values in a triplet with identifier _____ in a ____ structured field do not match. The X-Base value is X'____' and the Y-Base value is X'____'.

Explanation:: The X-Base and Y-Base values must match. Valid values are x00 or x01. The values in the structured field specified in the message do not match. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again.

0424-482

InfoPrint Manager located a CMR Tag Fidelity triplet in the Formdef. The device does not support this capability.

Explanation:: InfoPrint Manager found a CMR Tag Fidelity Triplet (X'96') on the Presentation Fidelity Control (PFC) Structured Field. The triplet indicated Stop on errors and the device does not support the triplet.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Either print on a device that supports this function or modify the Formdef.

0424-483

InfoPrint Manager located a CMR Tag Fidelity triplet in the Formdef indicating Continue and Report Exceptions. The device does not support this capability.

Explanation:: InfoPrint Manager found a CMR Tag Fidelity Triplet (X'96') on the Presentation Fidelity Control (PFC) Structured Field. The triplet indicated Continue on errors and Report Exceptions, but the device does not support the triplet.
System action:: InfoPrint Manager continues processing the file. All Color Management Resources are ignored.
User response:: Either print on a device that supports this function or modify the Formdef.

0424-484

Invalid or out of range value ____ for scope or processing mode in the X'91' CMR Descriptor triplet on the ____ structured field.

Explanation:: InfoPrint Manager found a CMR Descriptor triplet (X'91) on the Include Object (IOB), Map Data Resource (MDR) or Preprocess Presentation Object (PPO) Structured Field. The value was either out of range or the scope value was incorrect for the context in which the structured field was found.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Use the accompanying messages to determine if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again. See the 'Mixed Object Document Content Architecture Reference' for further information.

0424-485

Actual Destination does not support CMRs (Color Management Resources). This print request contains a request for one or more Color Management Resources.

Explanation:: InfoPrint Manager found a request to process a CMR (Color Management Resource) descriptor triplet, an invoke CMR (ICMR) triplet, a rendering intent triplet or FQN type x41 triplet which the actual destination does not support. The intended device does not support the IPDS function(s) required to completely process this print request.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-486

Printer does not support CMR (Color Management Resource) type ____. CMR name is ____.

Explanation:: The print job requested a CMR (Color Management Resource) but the actual device does not support that CMR type. The actual destination does not have the IPDS function required to present the color management resources required by this print job.
System action:: If the formdef contains a color fidelity triplet, the continuation and reporting rules in the formdef define the system action. If there is no color fidelity triplet in the formdef, the print server action is to continue processing and not report the error.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-487

Printer does not support ____ command.

Explanation:: InfoPrint Manager found a request to process a MO:DCA Presentation Environment Control (PEC) structured field or a CMR (Color Management Resource), but the actual destination does not support the IPDS function(s) required to completely process this print request.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-488

CMR Name ____ is incorrect length.

Explanation:: InfoPrint Manager found a CMR reference and the CMR Name field is not 146 bytes long.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the CMR Name and resubmit the job.; See the CMOCA Reference for more information.

0424-489

Incorrect Object Type ____ in an Object Offset Triplet (X'5A') on a ____ structured field.

Explanation:: InfoPrint Manager found an Object Offset Triplet (X'5A') on the Map Data Resource (MDR) or Presentation Environment Control (PEC) structured field. The object type value was incorrect for the context in which the structured field was found. For a CMR or device appearance that is to be associated with a specific document in the print file, the Object Offset triplet specifies the offset of the document in the print file with which the CMR or device appearance is associated. The correct object type is X'A8' indicating ‘Document' object offset.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the value and resubmit the job.

0424-490

Too many CMRs specified for ____ command.

Explanation:: The number of CMRs specified for the printfile resulted in an overflow in an internal buffer. InfoPrint Manager was preparing the IPDS command specified in the message. The IPDS Invoke CMR (X'92') triplets are written on the IDO, LPD, WBCC, WGC, WIC2, WOCC, and RPO IPDS commands.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Reduce the number of CMRs and resubmit the job.

0424-491

Printer does not support device appearance triplet (X'97') on the ____ structured field.

Explanation:: InfoPrint Manager found a device appearance triplet, and the actual destination does not support this function.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-494

Invalid units per unit base value in an Image Resolution (X'9A') triplet.

Explanation:: The printer reported an X units per unit base or Y units per unit base field in an Image Resolution (X'9A') triplet with an invalid value. The triplet can occur on the Container Data Descriptor (CDD), Include Object (IOB), or Preprocess Presentation Object (PPO) structured fields.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the value and resubmit the job. See the MO:DCA Reference for information on the Image Resolution triplet..

0424-495

Color Management Resource object error.

Explanation:

The printer reported that an error was detected within a Color Management Resource (CMR). The specific error code is specified in the sense bytes returned by the printer.

The error code can be one of the following:

X'03': Invalid Length value in a CMR header
X'04': Unsupported TagID value in a CMR tag
X'05': Invalid Count value in a CMR tag
X'06': Invalid FieldType value in a CMR tag
X'0E': Missing required CMR tag
X'0F': Invalid sequence of CMR tags
X'10': Invalid or unsupported field value in a CMR header or CMR tag
X'11': Inconsistent CMR tag contents

System action:

For error codes other than X'04', if the formdef being used to process this print request contains a color fidelity triplet (x75), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request. For error code X'04', the CMR Tag fidelity triplet in the formdef controls the system action. For audit and instruction CMRs, the printer uses the device-default CMR in place of the CMR in error.

User response:

The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability..

0424-496

Color Management Resource not available.

Explanation:: The printer report a CMR is needed to process specific print data, but the printer reported the CMR is unavailable because the printer does not have a default CMR for the type of color data and a host-invoked CMR was not supplied. The device default CMRs defined in the CMOCA Reference must be supported by the printer, but defaults for other color spaces are optional and a host-invoked CMR must be specified.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-497

Invoke media-specific instruction Color Management Resource (CMR) does not match selected media.

Explanation:: The printer reported an invoked media-specific instruction CMR is selected, but the printer reported the CMR does not match the currently selected media. Refer to the CMOCA Reference for the rules used to match CMRs with the media type loaded in the printer
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Either change the print job to select the appropriate CMR to match the media loaded in the printer or change the media and resubmit the job.

0424-498

Generic Color Management Resource (CMR) not supported.

Explanation:: The printer reported a generic CMR was selected, but the printer does not have an appropriate device-specific CMR to use in place of the generic CMR.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request using an appropriate printer default CMR.
User response:: Change the print job to select the appropriate CMR and resubmit the job.

0424-499

Invoked and selected Color Management Resource (CMR) was not used.

Explanation:: The printer reported a CMR was invoked and selected for use, but it cannot be used. The CMR is valid, but it is not appropriate for one of the following reasons: a printer-operator control has been invoked to achieve a specific look that overrides a user-specified Tone Transfer Curve (TTC) CMR; or a selected Halftone (HT) CMR is not appropriate for the printer. For example, a threshold-array halftone is invoked and selected for use with an ink-jet printer or an error-diffusion halftone is invoked and selected for use with a laser printer.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request using an appropriate printer default CMR.
User response:: Change the print job to select the appropriate CMR and resubmit the job.

0424-500

IPDS Trace Full.

Explanation:: The printer reported all of the available storage for an IPDS trace has been used, and a Trace Full entry has been added as the last trace entry.
System action:: InfoPrint Manager continues processing the file.
User response:: Turn off tracing or contact the support center.

0424-501

Asynchronous color-related error.

Explanation:: The printer detected a color-related error on a page that is between he received page station and the committed page station. The error is not detected when the IPDS commands for a presentation object were parsed, but it is detected by the object processor before the page is committed. For example, a color value might have been requested within the object data that is not available to the printer. The printer must finish committing prior sheets if any, discard the pages of the error sheet, and discard all upstream data before reporting this error.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request using an appropriate printer default CMR.
User response:: See the IPDS Reference Chapter on Exception Report to understand how to decode the information returned in the sense bytes for this exception.

0424-502

Colorant information changed.

Explanation:: The printer reported one or more colorants has become available, has become unavailable, or has changed a colorant-availability flag.
System action:: InfoPrint Manager recovers and continues processing the job.
User response:: Examine the printed output to see if it is satisfactory.

0424-503

Invalid or unsupported CMR (Color Management Resource) type ____ found. CMR name is ____.

Explanation:: Either an invalid CMR type was found when processing the MO:DCA job or an invalid CMR type was found when processing a CMR reference in the Data Object Resource Access Table or Color Management Resource Access Table.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the error and resubmit the job. See the MO:DCA Reference for more information.

0424-504

InfoPrint Manager canceled printing of the file because a CMR Tag error occurred and CMR Tag fidelity of STOP was requested.

Explanation:: InfoPrint Manager stops processing the file as part of InfoPrint Manager error recovery. The actual destination reported an exception which indicates an invalid or unsupported CMR Tag value was found. Because CMR Tag fidelity was requested, the normal recovery for this exception is not taken. Instead, the file is canceled. CMR Tag fidelity is requested in the form definition (FORMDEF). The form definition used with this print file requested that CMR Tag exceptions be reported and that printing be stopped at the point of the first CMR Tag exception.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the causes of the other error messages in this message group.

0424-505

Baseline adjustment value too large or too small.

Explanation:: The actual destination reported while processing a metric adjustment triplet (x'79') in an Activate Resource command, the combination of the baseline offset adjustment value and a character's baseline offset value created another internal value that is beyond the range the printer can handle.
System action:: InfoPrint Manager stops processing the file.
User response:: Reduce the baseline offset values and resubmit the print job. See the Mixed Object Document Content Architecture Reference for more information about the triplet. If you used a program to create the printjob, contact the program owner.

0424-506

Color Management Resource object error code = X'____'.

Explanation:

The printer reported an error in a color management resource.

The specific error code shown in this message and can be one of the following:

x03: Invalid length value in a CMR header
x05: Invalid Count value in a CMR tag
x06: Invalid FieldType value in a CMR tag
x0E: Missing required CMR tag
x0F: Invalid sequence of CMR tags
x10: Invalid or unsupported field value in a CMR header or CMR tag
x11: Inconsistent CMR tag contents

More information can be found in the Color Management Object Content Architecture Reference.

System action:

See the action described in the accompanying messages. This is an informational message.

User response:

Correct the error in the color management object resource. The error could be in the program which produces the resource.

0424-507

Printer does not support rendering intent triplet (X'95') on the ____ structured field.

Explanation:: InfoPrint Manager found a rendering intent triplet, and the actual destination does not support this function.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-508

Printer does not support rendering intent triplet (X'95') on the ____ structured field.

Explanation:: InfoPrint Manager found a rendering intent triplet, and the actual destination does not support this function. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-509

Printer does not support device appearance triplet (X'97') on the ____ structured field.

Explanation:: InfoPrint Manager found a device appearance triplet, and the actual destination does not support this function. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-510

Actual Destination does not support CMRs (Color Management Resources). This print request contains a request for one or more Color Management Resources.

Explanation:: InfoPrint Manager found a request to process a CMR (Color Management Resource) descriptor triplet, an invoke CMR (ICMR) triplet, a rendering intent triplet or FQN type x41 triplet which the actual destination does not support. The intended device does not support the IPDS function(s) required to completely process this print request. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an atual destination that supports the Color Management Resource capability.

0424-511

Printer does not support ____ command.

Explanation:: InfoPrint Manager found a request to process a MO:DCA Presentation Environment Control (PEC) structured field or a CMR (Color Management Resource), but the actual destination does not support the IPDS function(s) required to completely process this print request. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef controls the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-512

Printer does not support CMR (Color Management Resource) type ____. CMR name is ____.

Explanation:: The print job requested a CMR (Color Management Resource) but the actual device does not support that CMR type. The actual destination does not have the IPDS function required to present the color management resources required by this print job. Processing continues.
System action:: If the formdef contains a color fidelity triplet, the continuation and reporting rules in the formdef define the system action. If there is no color fidelity triplet in the formdef, the print server action is to continue processing and not report the error.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an atual destination that supports the Color Management Resource capability.

0424-513

Printer does not support color specification triplet (X'4E') on the ____ structured field.

Explanation:: InfoPrint Manager found a request to process a Color Specification x4E triplet which the actual destination does not support. The intended device does not support the IPDS function(s) required to completely process this print request.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-514

Printer does not support color specification triplet (X'4E') on the ____ structured field.

Explanation:: InfoPrint Manager found a Color Specification x4E triplet, and the actual destination does not support this function. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-515

Printer does not support extended bar code color specification triplet (X'4E') on the ____ structured field.

Explanation:: InfoPrint Manager found a request to process a Color Specification x4E triplet on a BCOCA BDD structured field which the actual destination does not support. The intended device does not support the IPDS function(s) required to completely process this print request. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-516

Printer does not support extended bar code color specification triplet (X'4E') on the ____ structured field.

Explanation:: InfoPrint Manager found a Color Specification x4E triplet on a BCOCA BDD structured field, and the actual destination does not support this function. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: The print request requires function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-517

Printer color setup may have changed from when pages were saved.

Explanation:: When printing the first page of a print file, PSF detected the color setup at the printer may have changed. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Ensure the actual device color setup does not change between the time the printer saves the pages and the time the job is actually printed.

0424-518

Printer color setup may have changed from when pages were saved.

Explanation:: When printing the first page of a print file, PSF detected the color setup at the printer may have changed. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Ensure the actual device color setup does not change between the time the printer saves the pages and the time the job is actually printed.

0424-519

Printer did not report device type and model needed for CMR matching.

Explanation:: The print file referenced Color Management Resources (CMRs). The printer did not report the device type and model in the Product Identifier Self-Defining Field in the IPDS XOH-OPC response. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Report the problem to your local system administrator who may need to contact your service representative.

0424-520

Printer did not report device type and model needed for CMR matching.

Explanation:: The print file referenced Color Management Resources (CMRs). The printer did not report the device type and model in the Product Identifier Self-Defining Field in the IPDS XOH-OPC response. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Report the problem to your local system administrator who may need to contact your service representative.

0424-521

Printer does not support extended IOCA bilevel color on the ____ structured field.

Explanation:: The print file referenced an IOCA extended bilevel color self-defining field. The printer did not report support for this function. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-522

Printer does not support extended IOCA bilevel color on the ____ structured field..

Explanation:: The print file referenced an IOCA extended bilevel color self-defining field. The printer did not report support for this function.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-523

ERROR: The CMR Tag Fidelity continue value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid continue value on a Presentation Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-524

ERROR: The CMR Tag Fidelity report value on the Presentation Fidelity Control (PFC) structured field is invalid.

Explanation:: InfoPrint Manager encountered an invalid report value on a Print Fidelity Control (PFC) structured field. Valid values are X'01' and X'02'.
System action:: InfoPrint Manager stops processing the file at the point of the error.
User response:: Correct the error in the form definition and send the job again.

0424-525

Printer does not support resident color profiles.

Explanation:: The print file referenced a resident color profile. The printer did not report support for this function. Processing continues.
System action:: InfoPrint Manager continues processing the file from the point of the error.
User response:: Correct the error and resubmit the job. See the 'MO:DCA Reference' for more information.

0424-526

Invalid value ____ in a Rendering Intent Triplet (X'95') on a ____ structured field.

Explanation:: InfoPrint Manager found an invalid rendering intent value. This value came from either the Include Object (IOB), Presentation Environment Control (PEC), or Preprocess Presentation Object (PPO) structured field.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the rendering intent value and resubmit the job. See the 'MO:DCA Reference' for more information.

0424-527

Invalid or unsupported value ____ in a Device Appearance Triplet (X'95') on a ____ structured field.

Explanation:: InfoPrint Manager found an invalid or unsupported appearance value is specified in a Device Appearance (x'97') triplet. The triplet is specified on a Presentation Environment Control (PEC) structured field. The structured field can be in the Document Environment Group or Medium Map in the formdef, the Active Environment of a page or overlay or Object Environment group of a GOCA object, IOCA object or Object Container.
System action:: InfoPrint Manager stops processing the file at the point of the error. If there are other files in this print job, InfoPrint Manager resumes processing starting with the next file in the job; otherwise, InfoPrint Manager cancels the job.
User response:: Correct the device appearance value and resubmit the job. See the 'MO:DCA Reference' for more information.

0424-528

Invalid or unsupported value ____ in a Device Appearance Triplet (X'95') on a ____ structured field. Processing continues.

Explanation:: InfoPrint Manager found an invalid or unsupported appearance value is specified in a Device Appearance (x'97') triplet. The triplet is specified on a Presentation Environment Control (PEC) structured field. The structured field can be in the Document Environment Group or Medium Map in the formdef, the Active Environment of a page or overlay or Object Environment group of a GOCA object, IOCA object or Object Container.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef controls the system action for an unsupported value.
User response:: Correct the device appearance value and resubmit the job. See the 'MO:DCA Reference' for more information.

0424-529

WARNING: SNMP temporarily disabled for duration of back or forward space request.

Explanation:: InfoPrint Manager is processing a back or forward space request and must temporarily disable SNMP until the back or forward space command completes..
System action:: InfoPrint Manager processes the back or forward space request and will re-enable SNMP when the space command completes.
User response:: None.

0424-530

IPDS Dialog with printer ____ was suspended because of a release request from the device.

Explanation:: InfoPrint Manager has suspended the current IPDS session due to a request from the print device. The printer has requested that the flow of data be suspended for the device to print a non-IPDS print request.
System action:: InfoPrint Manager sends the device an IPDS End Dialog command, and the device will switch internally to process the alternate data stream. If another print request is provided to InfoPrint Manager, the host InfoPrint Manager will resume sending IPDS data to the device.
User response:: This is an informational message; no response is required.

0424-531

The print device has requested the temporary suspension of the flow of IPDS data from the InfoPrint Manager host.

Explanation:: The print device has received a print request from a non-IPDS source, and has requested that InfoPrint Manager suspend the sending of data to process the alternate print request. InfoPrint Manager can decide to suspend the data flow, or it can ignore the request, depending on the current host processing environment.
System action:: InfoPrint Manager continues processing print requests until print requests stop for a prescribed amount of time.
User response:: This is an informational message; no response is required.

0424-532

IPDS Dialog with printer ____ was restarted.

Explanation:: The IPDS print process to the device was suspended based on inactivity but has now been resumed with the receipt of a subsequent print request. InfoPrint Manager will resume sending IPDS data to the device and printing should resume.
System action:: InfoPrint Manager will resume sending IPDS data to the device, preceded by the IPDS Start Dialog command. The printer will switch back to printing IPDS data from the InfoPrint Manager host when the print mechanism is available.
User response:: This is an informational message; no response is required.

0424-533

Connection to printer ____ has been ended normally while in a suspended state.

Explanation:: The IPDS print process to the device had been suspended, but has now been terminated due to inactivity. The InfoPrint Manager host received no print requests in the time specified for release of the IPDS connection so the connection to the device has been terminated.
System action:: InfoPrint Manager will terminate the TCP/IP connection with the device, allowing other hosts to access the print device through the TCP/IP port. If the InfoPrint Manager host receives a subsequent print request, PSF will attempt to acquire the TCP/IP port again.
User response:: This is an informational message; no response is required.

0424-534

Printer ____ has requested the release of the communication channel but the printer is defined to not support that capability.

Explanation:: The printer has requested the release of the print mechanism in order to process a non-IPDS data stream. The InfoPrint Manager printer is not configured to support that capability so the request will be ignored.
System action:: InfoPrint Manager will ignore the request and issue this informational message.
User response:: This is an informational message; no response is required.

0424-535

Printer ____ does not support the Manage IPDS Dialog capability but the print destination is defined to support this capability

Explanation:: The destination is defined to utilize the Manage IPDS Dialog capability but the actual printer does not report support of this feature. The capability will not be activated for this device.
System action:: InfoPrint Manager will ignore the destination configuration attribute and will issue this informational message. This message will be produced only once per session.
User response:: This is an informational message; no response is required.

0424-536

Printer does not support set default instruction in ____ for Normal Line Width attributes.

Explanation:: The actual destination does not support default value for Normal Line Width and the set-byte value for this attribute should not be specified for this printer. Processing continues.
System action:: InfoPrint Manager just report the error and continue processing the file.
User response:: Correct the error and send the job again.

0424-537

Printer does not support set default instruction in ____ for Process Color attributes.

Explanation:: The actual destination does not support default value for Process Color and the set-byte value for this attribute should not be specified for this printer. Processing stops.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-538

Printer does not support set default instruction in ____ for Process Color attributes.

Explanation:: The actual destination does not support default value for Process Color and the set-byte value for this attribute should not be specified for this printer. Processing continues.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (x'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error(s) and continue processing the print request.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-539

____ transform failed loading the icu library ____.

Explanation:: A call to load the icu libraries failed.
System action:: InfoPrint Manager does not complete the requested transform operation.
User response:: Make sure to have the icu libraries in the right location in InfoPrint Manager. If the files are present, try the operation again. If the error cannot be corrected, use the local problem-reporting procedures to report this message.

0424-540

The desired-symbol-width value specified in the bar code data-descriptor self-defining field is invalid.

Explanation:: The value specified in the bar code data descriptor self defining field for the desired-symbol-width is invalid.
System action:: The printing continue using the default value X'0000' for the desired-symbol-width in the bar code data descriptor self defining field.
User response:: Check if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again. See the 'Mixed Object Document Content Architecture Reference' for further information.

0424-541

The value for the bar code desired-symbol-width is valid, but the bar code cannot fit using this.

Explanation:: A desired-symbol-width value was specified in the bar code data-descriptor self-defining field, but a bar code symbol cannot be generated that fits within the specified width.
System action:: The printing continue using the default value X'0000' for the desired-symbol-width in the bar code data descriptor self defining field. The resulting symbol is larger than the desired symbol width.
User response:: Check if the structured field causing the error is in the input file or in a resource referenced by the input file. The program or person who created the input file or resource most likely caused the error. Correct the error in the input file or resource and send the job again. See the 'Mixed Object Document Content Architecture Reference' for further information.

0424-550

Invalid MO:DCA syntax was detected.

Explanation:: An invalid length or structured field code was detected. The file probably is in a different format than MO:DCA.
System action:: Tool exits with error code.
User response:: Verify that datastream is MO:DCA. If so, investigate data generator.

0424-551

Cannot write to file or stream.

Explanation:: Either the user does not have permission to write to file, the file no longer exists, or the filesystem is full.
System action:: Tool exits with an error code. Temporary files and output files are deleted by the tool.
User response:: Make sure that the directory containing the file still exists, that the directory has proper permissions, and that the filesystem containing the directory has sufficient free space available.

0424-554

Invalid IS/3 Page Segment object type.

Explanation:: IS/3 document types does not permit IM1 or Presentation Text objects on a Page Segment.
System action:: The event is recorded on the destination error log and continues processing the print job.
User response:: Remove illegal objects from Page segment or use a previous document type.

0424-555

The selected paginated object is not contained in the file.

Explanation:: An Object Offset (X'5A') triplet specified an object offset, but there is no paginated object in the multi-page file at that offset.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Correct the object offset from the Object Offset (X'5A') triplet to specify a valid object from the multi-page file.

0424-556

Invalid Fully Qualified Name (FQN) triplet format X'________' on a ________ structured field.

Explanation:: This is a MOD:CA data stream error. In a Fully Qualified name triplet there is a format value which is either unsupported or incorrect in the context of the structured field in which it appears.
System action:: Terminate job.
User response:: The application which generated this data stream must be corrected.

0424-558

Printer does not support replicate-and-trim mapping option for an IOCA object.

Explanation:: The print file referenced an IOCA object with the mapping option specified as replicate-and-trim. The printer did not report support for this option. Processing stops.
System action:: InfoPrint Manager application stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager application resumes processing starting with the next file in the job. InfoPrint Manager application cancels the job if there are no other files in the print job.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-559

Replicate-and-trim mapping option for a GOCA object has been retired.

Explanation:: The print file referenced a GOCA object with the mapping option specified as replicate-and-trim. This option has been retired from the GOCA architecture. Processing stops.
System action:: InfoPrint Manager application stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager application resumes processing starting with the next file in the job. InfoPrint Manager application cancels the job if there are no other files in the print job.
User response:: Specify another mapping option for the GOCA object according to the MODCA and GOCA architecture.

0424-560

A character string carried in Fully Qualified Name (FQN) triplet exceeds the maximum length allowed.

Explanation:: The print file contained character strings carried in a Fully Qualified Name (FQN) triplet. The triplet limits the length of the data to 250 bytes. When such a character string is converted from one character encoding, such as single-byte EBCDIC, to another character encoding, such as double-byte UTF-16, the string may increase in length. Therefore, the object names that are specified using a single-byte encoding is limited to 125 characters or fewer.
System action:: InfoPrint Manager application stops processing the file when the error occurs. If there are other files in this print job, InfoPrint Manager application resumes processing starting with the next file in the job. InfoPrint Manager application cancels the job if there are no other files in the print job.
User response:: Limit the length of the character string carried in a Fully Qualified Name (FQN) triplet to 125 characters.

0424-561

ERROR: The actual destination reported that a PTOCA with OEG has data that appears outside of the text presentation space.

Explanation:: The error occurred in a PTOCA with OEG. See the 'Mixed Object Document Content Architecture Reference' for further information about text presentation space.
System action:: InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Correct the presentation text with OEG data problem.

0424-562

The actual destination reported that the presentation text data extends outside the defined text object area.

Explanation:: A portion of the presentation text data extends beyond the intersection of the mapped presentation space and text object area. See the 'Mixed Object Document Content Architecture Reference' for further information about text object area.
System action:: InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Correct the presentation text with OEG data problem.

0424-563

A PTOCA with OEG object is not supported in an AFP page segment.

Explanation:: A PTOCA with OEG object is present in an AFP page segment. 'Mixed Object Document Content Architecture Reference' specifies that this inclusion of a PTOCA with OEG in an AFP page segment is not supported.
System action:: InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Remove PTOCA with OEG from the AFP page segment.

0424-564

ERROR: Printer does not support text extended color on the ________ structured field.

Explanation:: The print file reference an extend text color for a PTOCA object with OEG. The printer did not report support for this function.
System action:: If the formdef being used to process this print request contains a color fidelity triplet (X'75'), the continuation and reporting settings from the formdef control the system action. If there is no color fidelity triplet in the formdef, the default action is to not report the error (s) and continue processing the print request.
User response:: Resubmit this print request to an actual destination that supports this function.

0424-565

ERROR: Invalid Unicode Complex Text (UCT) parameter value.

Explanation:: An invalid parameter value was specified in a PTOCA Unicode Complex Text (UCT) control sequence within a Write Text command. The text control is contained in a Presentation Text (PTX) structured field.; See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the syntax of the PTOCA UCT control sequence specified and make sure it complies with the PTOCA architecture.

0424-566

ERROR: Wrong font used with a Glyph Layout Control (GLC) text control sequence.

Explanation:

One of the following conditions exists:

1. The object OID specified in the Glyph Layout Control (GLC) text control sequence does not match the object OID of the current font or any font linked to the current font that was specified as an internal resource within the print file resource group.
2. The OIDs match a font collection. However the full font name from the GLC that specified the OID does not match any font within the collection.
3. The printer does not have a font OID at the time a glyph run is processed.

The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.

System action:

InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.

User response:

Check the OID specified in Glyph Layout Control (GLC) text control and the OID specified in the Fully Qualified Name (X'02') triplet (with FQN Type X'DE' and format X'10') from the Begin Object Container – BOC (X'D3 A8 92') structured field of an inline resource group. The OIDs values should match.

0424-567

ERROR: The font used with a Glyph Layout Control (GLC) chain is not a TrueType / OpenType font

Explanation:: The current font specified in the PTOCA Glyph Layout Control (GLC) control sequence is not a TrueType / OpenType font. The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check Object class (X'10') triplet from the Begin Object Container – BOC (X'D3 A8 92') structured field of an inline resource group. If the ObjClass specifies value X'41' - Data-object font, then the value specified for the MO:DCA-registered ASN.1 object identifier (OID) should be TrueType / OpenType Font Resource Object.

0424-568

ERROR: Glyph ID specified in a Glyph ID Run (GIR) text control sequence, but not found in the font.

Explanation:: One of the glyph IDs specified in the Glyph ID Run (GIR) control sequence is not contained in the font used.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the font used to contain the glyph ID required or change the glyph ID specified in the Glyph ID Run (GIR) to match the one from the font.

0424-569

ERROR: Missing or invalid control sequence found in a Glyph Layout Control (GLC) chain.

Explanation:: The Glyph Layout Control (GLC) chain specified an unexpected control sequence. A PTOCA GLC control sequence must be followed by a series of Glyph ID Run (GIR), Glyph Advance Run (GAR), Glyph Offset Run (GOR), and Unicode Complex Text (UCT) control sequences.; These control sequences must be provided within a chain and be specified in the following order (the square brackets indicate an optional control):X'2BD3' GLC GIR GAR [GOR] [GIR GAR [GOR]] ... [GIR GAR [GOR]] [UCT]; Note that the GLC can be preceded with any chained PTOCA control sequence other than GLC, GIR, GAR, or GOR.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the syntax of the Glyph Layout Control (GLC) chain specified and make sure it complies with the PTOCA architecture.

0424-570

ERROR: An unsupported Unicode Complex Text (UCT) control sequence found outside of a Glyph Layout Control (GLC) chain.

Explanation:: A Unicode Complex Text (UCT) control sequence was found outside of a Glyph Layout Control (GLC) chain.; Printers that support glyph layout controls will ignore UCTs that are chained to a GLC chain and will recognize but not support other UCT control sequences.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the syntax of the Glyph Layout Control (GLC) chain specified and make sure it complies with the PTOCA architecture.

0424-571

ERROR: Glyph ID Run (GIR), Glyph Advance Run (GAR) or Glyph Offset Run (GOR) text control sequence found outside of a Glyph Layout Control (GLC) chain.

Explanation:: A Glyph ID Run (GIR), Glyph Advance Run (GAR), or Glyph Offset Run (GOR) control sequence was encountered outside of a Glyph Layout Control (GLC) chain.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: Skip the unexpected GIR, GAR, or GOR control sequence.
User response:: Check the syntax of the GLC chain specified and makes sure it complies with the PTOCA architecture.

0424-572

ERROR: Invalid number of entries in a Glyph Advance Run (GAR) or Glyph Offset Run (GOR).

Explanation:: The number of entries in a Glyph Advance Run (GAR) or Glyph Offset Run (GOR) text control sequence must match the number of entries in the immediately preceding Glyph ID Run (GIR) control sequence.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the number of entries in GAR and GOR to match the numbers of glyph ids specified in the preceding Glyph ID Run (GIR).

0424-573

ERROR: There is no OID provided for a Glyph Layout Control (GLC) chain.

Explanation:: A PTOCA Glyph Layout Control (GLC) control sequence specified an OID length of zero (indicating that the previously specified OID is still in effect), but there was no previously specified OID found within the text object, page, or overlay.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the syntax of the Glyph Layout Control (GLC) chain specified and make sure it complies with the PTOCA architecture.

0424-574

ERROR: Length mismatch within a Glyph Layout Control (GLC) control sequence.

Explanation:

A PTOCA Glyph Layout Control (GLC) control sequence contains an incorrect length field. One or more of the following conditions occurred:

1. The OID-length field or the full-font-name-length field contains a value that is not consistent with the overall control sequence length.
2. The OID-length field contains an invalid value.
3. The full-font-name-length field contains an invalid value.

The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.

System action:

InfoPrint Manager stops processing the page containing the error and printing continues with the next page in the print job

User response:

Check the syntax of the Glyph Layout Control (GLC) chain specified and make sure it complies with the PTOCA architecture.

0424-575

ERROR: Full Font Name specified in a Glyph Layout Control (GLC) control sequence without a font OID.

Explanation:: A PTOCA Glyph Layout Control (GLC) control sequence contains a value in the full-font-name field and a non-zero value in the full-font-name-length field, but no font OID was specified. The PTOCA architecture forbids specification of a full font name without also specifying a font OID.; The text control is contained in a Presentation Text (PTX) structured field. See the 'Presentation Text Object Content Architecture Reference' for further information on this text control.
System action:: InfoPrint Manager application stops processing the page containing the error and printing continues with the next page in the print job.
User response:: Check the syntax of the Glyph Layout Control (GLC) chain specified and make sure it complies with the PTOCA architecture.

0424-576

ERROR: Invalid or insufficient data for a Royal Mail Red Tag bar code.

Explanation:: Invalid or insufficient data was encountered in a Royal Mail Red Tag bar code object. There must be exactly 21 numeric digits in the input data. The printer validity checks each field of the input data using the BCOCA range.; See the 'Bar Code Object Content Architecture Reference' for further information about Royal Mail Red Tag bar code object.
System action:: InfoPrint Manager stops processing the page containing the error, and printing continues with the next page in the print job.
User response:: Check the syntax of the Royal Mail Red Tag bar code object specified and make sure it complies with the BCOCA architecture.

0424-577

Usage: insrtcmr [options] inputfile Options: -d [Directory] :Location of Color Management Resource (CMR) files with the '.cmr' extension. If the directory is not specified, the default location is used instead. -l [List of CMR files] :List of the Color Management Resource (CMR) files to be added instead of the entire list of CMR files from a directory -i :Include the Color Management Resource (CMR) files inline, if printfile -o [Outputfile] :Name and location of output filename :Render Intent Override -m [AUDIT | INSTRUCT] :Add audit or instruction Color Management Resource (CMR) files .-t :Turn on trace. -f [Path/formdef filename] :Location of external FormDef -riall [PERCEPTUAL | SATURATION | RELCM | ABSCM] -riioca [PERCEPTUAL | SATURATION | RELCM | ABSCM] -riobjc [PERCEPTUAL | SATURATION | RELCM | ABSCM] -riptoca [PERCEPTUAL | SATURATION | RELCM | ABSCM] -rigoca [PERCEPTUAL | SATURATION | RELCM | ABSCM] Notes: Only 75 CMR files can be added at a time insrtcmr only finds Color Management Resource (CMR) files with the '.cmr' extension. FormDef must have a 'Document Environment Group' or 'Form Map' defined.

Explanation:: The insrtcmr command must be in the format described in the usage message. The insrtcmr command entered does not comply with the usage message.
System action:: : The insrtcmr program terminates and no output is produced.
User response:: Invoke insrtcmr with the correct syntax.

0424-578

Problem with ____ option, space must occur between option \ and parameter.

Explanation:: The program was invoked with an incorrect syntax.; A space between a flag and the option for that flag was omitted.
System action:: The program terminates and no output is produced.
User response:: Enter the command again with the correct syntax.

0424-579

Expecting INSTRUCT or AUDIT for flag [-m].

Explanation:: The program was invoked with an incorrect option for flag [-m]. The valid options are: INSTRUCT or AUDIT.
System action:: The program terminates and no output is produced.
User response:: Enter the command again with the correct syntax.

0424-580

Expecting PERCEPTUAL, RELCM, SATURATION or ABSCM for flag [-____].

Explanation:: The program was invoked with an incorrect option for one of the followings flags: -riall, -riioca, -riobjc, -riptoca, or -rigoca. The valid options are: PERCEPTUAL, RELCM, SATURATION or ABSCM.
System action:: The insrtcmr program terminates and no output is produced.
User response:: Enter the command again with the correct syntax.

0424-581

'-' missing from parameter setting.

Explanation:: The program was invoked with an incorrect syntax.; '-' missing from parameter setting.
System action:: The program terminates and no output is produced.
User response:: Enter the command again with the correct syntax.

0424-582

____ not added, maximum number for Color Management Resources (CMRs) reached.

Explanation:: Only 75 Color Management Resources (CMR) files can be added at a time.
System action:: The insrtcmr program terminates and no output is produced.
User response:: Make sure that in the specified directory are less than 75 Color Management Resources (CMR) files.

0424-583

____ not added, unable to locate Color Management Resource name.

Explanation:: Unable to locate Color Management Resource (CMR) name in the CMR file.
System action:: The program terminates and no output is produced.
User response:: Check the validity of the Color Management Resource (CMR) file specified and make sure it complies with the CMOCA architecture.

0424-584

Unable to locate End Document Environment Group or Form Map, Map Data Resources (MDRs) not added.

Explanation:: The insrtcmr program was unable to complete adding Map Data Resources. The command was unable to locate End Document Environment Group or Form Map in the input file specified.
System action:: The program terminates and no output is produced.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture..

0424-585

Invalid input file format.

Explanation:: The program encountered an invalid input file format. The print file is built with the document index first, followed by the resource group.
System action:: The program terminates and no output is produced.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture..

0424-586

Cannot use -f option when input file already has Form Definition defined.

Explanation:: Cannot use -f option when input file already has Form Definition defined.
System action:: The program terminates and no output is produced.
User response:: Reissue the command without -f flag.

0424-587

A Begin Print File (BPF) structured field is not supported in a form defintion.

Explanation:: The program encountered an invalid input file format. A Begin Print File (BPF) structured field is not supported in a form definition.
System action:: The program terminates and no output is produced.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture.

0424-588

Invalid input file format. Unable to locate Begin Resource Group.

Explanation:: The program encountered an invalid input file format.; The command was unable to locate Begin Resource Group (BRG) structured field in the input file specified.
System action:: The program terminates and no output is produced.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture.

0424-589

No Color Management Resource (CMR) found in directory ____ or in list of Color Management Resource (CMR) file names.

Explanation:: The program was unable to locate Color Management Resource (CMR) files in the directory or in the list of Color Management Resource (CMR) file names specified.
System action:: The program terminates and no output is produced.
User response:: Check to see if the specified Color Management Resource directory exists or if is not empty. If a list of Color Management Resource (CMR) file names was specified, check to see if those file names exist in the specified Color Management Resource directory.

0424-590

was unable to allocate system memory.

Explanation:: The program cannot allocate system memory.
System action:: The program terminates.
User response:: Close any unnecessary windows and stop any unneeded processes. Then, enter the command again. If the error cannot be corrected or the error occurs again, use local problem-reporting procedures to report this message.

0424-591

There is no ____ structured field to match the ____ structured field with token name ____ at file offset ____

Explanation:: A file contained a Begin structured field to mark the beginning of an object, but did not contain the matching structured field to mark the end of the object. If the Begin structured field is present, the End structured field must also be present with the same token name.
System action:: The program terminates.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture.

0424-592

Received unexpected ____ structured field.

Explanation:: A structured field was read that is not valid at the current point within the data stream.
System action:: The program terminates.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture.

0424-593

________: An error was found when reading or writing file ____.

Explanation:: The program cannot read from or write the file specified in the message. The file might have been deleted after it was opened, or someone might have changed the permission level on the file.
System action:: The program terminates.
User response:: Check that the specified file exists and that you have read permission for the file. You must have x (execute) and w (write) permission for the directory containing the file and w and r (read) permission for the file itself.

0424-594

Invalid Fully Qualified Name (FQN) triplet type X'____' on a ____ structured field.

Explanation:: This is a MOD:CA datastream error. In a Fully Qualified name triplet, there is a type value which is either unsupported or incorrect in the context of the structured field in which it appears, is not in the correct reference format (character string) or is required for this structured field.
System action:: The program terminates.
User response:: Check the validity of input file specified and make sure it complies with the MO:DCA architecture.

0424-595

An unexpected end-of-file was encountered.

Explanation:: The end of an Advanced Function Printing (AFP) data stream file was detected before all the bytes in a structured field were read. The file might have been built incorrectly or might have been truncated at some point.
System action:: The program terminates.
User response:: Correct the error in the file and enter the command again.

0424-596

The appropriate argument is missing for the ____ option specified.

Explanation:: The option specified in the program command requires a specific argument.
System action:: The program terminates.
User response:: See the usage of the program, specify the appropriate option and enter the command again.

0424-597

Only one output format is allowed.

Explanation:: The program specified multiple output formats that are mutually exclusive.
System action:: The program terminates.
User response:: See the usage of the program and enter the command again.

0424-598

Number of sides specified by afpReorder application is invalid

Explanation:: The valid values are 1 or 2. See the usage of the program.
System action:: The program terminates.
User response:: See the usage of the program and enter the command again.

0424-599

The arguments ____ must be specified together.

Explanation:: The application requires these arguments to run together.
System action:: The program terminates.
User response:: See the usage of the program and enter the command again.

0424-600

Could not reset input file pointer.

Explanation:: The application cannot reset a file pointer to a specific file offset.
System action:: The program terminates.
User response:: Contact service personnel.

0424-601

The structured field ____ specify an incorrect length ____.

Explanation:: When parsing the Advanced Function Printing (AFP) data stream, the application encountered a structured field with an incorrect length specified.
System action:: The program terminates.
User response:: Correct the length of the structured field in the file and enter the command again.

0424-602

afpReorder application specified files to be merged with different number of pages.

Explanation:: Files to be merged by afpReorder has different number of pages.
System action:: The program terminates.
User response:: Specify files with the same number of pages and enter the command again.

0424-603

afpReorder application specified explicit output format to be used with explicit input file.

Explanation:: This output format attempts saved pages. When using standard input, the presence of saved pages is not known in time to change the format.
System action:: The program terminates.
User response:: See the usage of the program, correct the problem and enter the command again.

0424-604

afpReorder application specified more than one medium map in filter mode.

Explanation:: In the medium map configuration file, you can specify the medium maps to be used. In filter mode, only one medium map is allowed to be used.
System action:: None.
User response:: None.

0424-605

afpReorder application cannot read the input file.

Explanation:: The file might have been deleted after it was opened, or the file permission level might have changed.
System action:: The program terminates.
User response:: Check that the specified file exists and that you have read access right for that file.

0424-606

afpReorder application specified more than one setup file in filter mode.

Explanation:: User can specify Kodak setup file or files to be used. In filter mode, only one setup file is allowed to be used.
System action:: None.
User response:: None.

0424-607

In the afpReorder application, a negative value resulted to be set for a page.

Explanation:: The application calculated a negative value of bytes to be set for a page in the Advanced Function Printing (AFP) output data stream.; SYSTEM_ACTION: The program terminates.
System action:: The program terminates.
User response:: Contact your service representative.

0424-608

afpReorder application cannot build a medium map using internal API functionality.

Explanation:: The application cannot use internal API functionality to build a medium map.
System action:: The program terminates.
User response:: Contact service personnel.

0424-609

afpReorder application cannot build a formdef using internal API functionality.

Explanation:: The application cannot use internal API functionality to build a formdef
System action:: The program terminates.
User response:: Contact service personnel.

0424-610

A blank line was found in the afpReorder medium map configuration file.

Explanation:: For the input option specifies, afpReorder reads the names of the medium map configuration files from a specified file. The read operation is done line by line. One of the lines is blank.
System action:: The program terminates.
User response:: Remove the blank line from the file containing the medium maps configuration file names.

0424-611

The configuration file name for afpReorder medium map configuration application is missing.

Explanation:: afpReorder application builds a medium map based on a configuration file.; The configuration file name must be specified in the command line.
System action:: The program terminates.
User response:: Specify a configuration file name and enter the command again.

0424-612

Invalid value ____ for ____ from medium map configuration file.

Explanation:: afpReorder (mmConfig) application builds a medium map based on a configuration file.; The configuration file has a specific syntax. The syntax requires a medium control name to be followed by an appropriate value that has to be in the range specified by MO:DCA architecture.; Most likely, the value entered for the control is out of this range or it is not specified.; Also, the value can be valid, but there is another control that is mutually exclusive with this one.
System action:: The program terminates.
User response:: For the control used, specify a value within the range supported by MO:DCA architecture and reissue the command.

0424-613

Invalid or unexpected keyword name ____ in a medium map config file.

Explanation:: afpReorder (mmConfig) application builds a medium map based on a configuration file.; The configuration file has a specific syntax. The syntax requires a specific name for keywords (medium control name); An unknown or an unexpected name for the keyword was specified.
System action:: The program terminates.
User response:: Specify a valid name for the keyword and enter the command again.

0424-614

Last keyword name read from a medium map config file: ____

Explanation:: afpReorder (mmConfig) application builds a medium map based on a configuration file.; The configuration file has a specific syntax. The syntax requires a specific name for keywords (medium control name).
System action:: None.
User response:: None.

0424-615

Incorrect usage of the front back side definition.

Explanation:: afpReorder (mmConfig) application builds a medium map based on a configuration file. The configuration file has a specific syntax.; When setting simplex or duplex, partition numbers also need to be provided.; They are presented in special sections of the configuration file. Number of these section should be double of N-up count when duplex is specified and it should be equal to N-up count for simplex.
System action:: The program terminates.
User response:: Build a valid configuration file and enter the command again.

0424-616

An incorrect pages per sheet value ____ was specified.

Explanation:: afpReorder requires a positive pages per sheet value for the reverse order format.
System action:: The program terminates.
User response:: Reissue the command with the correct value for pages per sheet.

0424-637

The color specification table vector (X'34') from DO RAT is ignored.

Explanation:

InfoPrint Manager found a Color Specification table vector (X'34') in the DO RAT (Data Object Resource Access Table) associated with the job. The device does not support one or more IPDS functions required to completely process this print request. These are the possibilities:

The DO RAT X'34' table vector is for a bi-level IOCA object that is to be preRIPped and the printer did not report bi-level IO-image color support on the RPO command
The DO RAT X'34' table vector contains a non-standard OCA color for a bi-level IOCA object and the printer doesn't support IOCA Set Extended Bi-level Image Color (X'F4')
The DO RAT X'34' table vector is for a bi-level or grayscale non-OCA object and the printer did not report bi-level and grayscale image color support for object-container images

System action:

InfoPrint Manager stops processing the file when the error occurs. The formdef used to process this print request contains a color fidelity triplet (x'75') that specifies to stop the presentation at point of first color exception and report exception.

User response:

The print request requires the function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-638

The color specification table vector (X'34') from DO RAT is ignored

Explanation:

InfoPrint Manager found a Color Specification table vector (X'34') in the DO RAT (Data Object Resource Access Table) associated with the job. The device does not support one or more required IPDS functions. These are the possibilities:

The DO RAT X'34' table vector is for a bi-level IOCA object that is to be preRIPped and the printer did not report bi-level IO-image color support on the RPO command
The DO RAT X'34' table vector contains a non-standard OCA color for a bi-level IOCA object and the printer doesn't support IOCA Set Extended Bi-level Image Color (X'F4')
The DO RAT X'34' table vector is for a bi-level or grayscale non-OCA object and the printer did not report bi-level and grayscale image color support for object-container images

System action:

InfoPrint Manager continues processing the file. The formdef used to process this print request contains a color fidelity triplet (x'75') that specifies not to stop the presentation because of color exceptions, but to report the exception.

User response:

The print request requires the function defined under the Color Management Object Content Architecture as it relates to Color Management Resources. Resubmit this print request to an actual destination that supports the Color Management Resource capability.

0424-653

Printer does not support preprinted form overlay

Explanation:

InfoPrint Manager displays this message when the printer does not support preprinted form overlay and one of the following occurs:

A preprinted form overlay was specified in the print submission command line.
A medium map specified a preprinted form overlay in a Medium Modification Control (MMC) or a Page Modification Control (PMC) structured field.
A preprinted form overlay was specified in the printer profile.

System action:

InfoPrint Manager stops processing the file when the error occurs. InfoPrint Manager cancels the print job.

User response:

If the preprinted form overlay is specified only in the print submission command line and/or printer profile, remove it and resubmit the job. Otherwise, resubmit this print request to a printer that supports preprinted form overlay.

RICOH InfoPrint Manager™ for Linux

0420-001

0420-002

0420-003

0420-004

0420-005

0420-006

0420-007

0420-008

0420-009

0420-010

0420-011

0420-012

0420-013

0420-014

0420-016

0420-017

0420-018

0420-019

0420-020

0420-021

0420-022

0420-023

0420-024

0420-026

0420-027

0420-028

0420-029

0420-030

0420-031

0420-032

0420-033

0420-034

0420-035

0420-036

0420-037

0420-038

0420-039

0420-040

0420-041

0420-042

0420-043

0420-044

0420-045

0420-046

0420-047

0420-048

0420-050

0420-051

0420-052

0420-053

0420-054

0420-055

0420-056

0420-057

0420-058

0420-059

0420-060

0420-061

0420-062

0420-063

0420-064

0420-065

0420-066

0420-089

0420-090

0420-091

0420-092

0420-093

0420-094

0420-095

0420-096

0420-097

0420-098

0420-099

0420-100

0420-101

0420-102

0420-103