The parameter parser found a keyword that it did not recognize.

The parameter parser found a value for a keyword that is too long.

The parameter parser found a keyword value that is not valid.

The parameter parser found a keyword value that is not in the range of valid values.

The parameter parser found extraneous data among the keywords.

While converting the data stream, Infoprint XT required more internal data storage than was available and wrote nnnn bytes to the SYSUT1 temporary disk storage file. This might have caused increased execution time.

This is an informational message, and it indicates that utility_program uses parameters passed through the PARM parameter of the JCL EXEC statement for the job.

An internal Infoprint XT error occurred.

An internal Infoprint XT error occurred.

An internal Infoprint XT error occurred.

An internal Infoprint XT error occurred.

Infoprint XT required more internal storage than was available in the primary area, and allocated nnnn additional areas. This might have caused increased execution time.

Infoprint XT calculated that there is not be enough virtual storage to allocate any secondary internal data areas. Either the requested primary xptxsize value is too large, or less than 12 KB is available after allocating the primary area.

An xptxsize request was too small (less than 12 KB).

An xptxsize request was too small (less than 12 KB).

An xptxsize request was too large (greater than the available storage).

An xptxsize request was too large (greater than the available storage).

This is an informational message that identifies the source of the conversion parameters. It requires no user response.

This is an informational message that reports the runtime options. It requires no user response.

Infoprint XT did not recognize the input parameter (parameter) as a valid parameter.

The JDE or JDL name specified in the conversion parameters is either too long or contains non-alphanumeric characters.

Infoprint XT expected a numeric argument in a parameter, but found a nonnumeric argument instead.

Infoprint XT expects the parameter (numeric_argument) for the job to be numeric. It is not numeric, or the numeric value is too large or too small.

Infoprint XT did not recognize the input parameter (parameter) as a valid parameter. Processing cannot continue without producing potentially incorrect output or resource conversions in FILE DJDE jobs.

Infoprint XT did not find a required Xerox resource during job conversion.

A logic error occurred while reading from file file_name.

The conversion process ended abnormally. Previous messages give the reason for abnormal end of the process.

This informational message indicates the return code from data stream processing. It requires no user response.

Infoprint XT examined the job data to determine whether ANSI or IBM3211 control characters were in use. The type of controls found was different from the type expected. cc_type is either:

• ISO/ANSI/FIPS
• IBM3211

IBM3211 is the same as machine code.

This is an informational message that indicates that Infoprint XT has begun to read the reformatted Xerox resource dump parameters. It requires no user response.

Infoprint XT did not find the input file for the job, or it detected incorrect or conflicting attributes for the file.

The named file (file_name) has an incorrect record format (xrecfm=) or record length (xlrecl=) specified by the conversion parameters for the job.

Infoprint XT found an FCB that included the print position indexing (PPI) byte. The PPI byte of an FCB causes a shift in the printed output to the right of the position specified in the message. Infoprint XT ignores the PPI and does not shift the printed output.

Infoprint XT found an FCB that included the print position indexing (PPI) byte. The PPI byte of an FCB causes a shift in the printed output to the left of the position specified in the message. Infoprint XT ignores the PPI and does not shift the printed output.

Infoprint XT cannot dynamically load the resource that the message identifies. A FILE DJDE in the job specified the resource.

The SYSUT2 temporary data set was not defined. The data stream converter might have used SYSUT2 if it had been defined.

A temporary data set was not defined.

Fewer records than expected were found in a temporary data set.

Infoprint XT cannot find overlay overlay_name. Without the overlay, it also cannot track the resources that the overlay invoked and that the reformatted form resource list file resource_list_name listed.

Infoprint XT only supports TWOPASS data stream processing.

You specified the xcsmmname = yes parameter and another parameter which is incompatible with content-sensitive medium map names processing.

The data stream converter found one or more Xerox commands command_names in the job that generated a request for a medium map subcommand. The data stream converter cannot represent the medium map subcommand in a content-sensitive medium map name. Content-sensitive medium map names can only represent:

• Duplex or simplex
• Offset stack change or no offset stack change
• The format of the E1 keyword of the MMC structured field
• The input bin number

The converter used the sequentially numbered name sequential_name instead of the content-sensitive name content_sensitive_name.

The data stream converter could not read the metrics file for form form_name in the reformatted Xerox resource path. The file might not exist, or there might be a problem with the file. Infoprint XT cannot use any fonts that the form specifies and the printed output might not be correct.

Infoprint XT found a reformatted form resource list file resource_list_name in a format that is not at the current level. The file does not include some of the required information.

Infoprint XT found that overlay overlay_name has changed since the last time it was loaded.

The job uses one or more overlays that are missing from the AFP resource library, or one or more reformatted Xerox forms that are missing from the reformatted Xerox resource path.

The conversion parameters for the job specified the CLUSTERLIB parameter (xclb=), or used the default cluster name, which is clustr.lib. However, the cluster database specified in the message does not exist in the reformatted Xerox resource path.

Before the print position was established, Infoprint XT found characters to print or relative moves in a metacode print control record.

Infoprint XT found a character-reshaping metacode print control sequence, but a nongraphic font was in effect. The message indicates that no graphic fonts were active.

Infoprint XT found a character-shaping metacode print control sequence that specified a nongraphic font. The message lists up to three active graphic fonts and shows the position of each graphic font in the active font list.

While processing metacode print controls, Infoprint XT translated ASCII input character X'input_hex' to EBCDIC character X'EBCDIC_hex'. However, because this character is not available in code page code_page, Infoprint XT uses a blank in its place. This might occur because of incorrect characters, such as binary zeros, in the print data stream. It might also occur if you have manually correlated a Xerox font to an AFP font and the AFP font does not have characters that correspond to some of the characters in the Xerox font.

Infoprint XT found an error during repeat command processing at the location identified in the message.

Infoprint XT did not process DBCS information for coded_font_name.

Infoprint XT requires a Xerox image (IMG) to process the job, but no image correlation records exist in the correlation table. Typically, this is because no IMG resources were loaded, or they were loaded as non-shared resources for a different resource group.

Infoprint XT ignored the DJDE record DJDE_record, which it considers to be extraneous.

Infoprint XT ignored the DJDE record DJDE_record, which it considers to be extraneous. The DJDE record is a downloadable PDE (FORMAT=*) and DJDE_record contains a message that indicates that Infoprint XT did not use the fonts listed in the downloadable PDE.

The data stream specified COLLATE=NO, but also specified DUPLEX=YES, which implies COLLATE=YES.

The COLLATE DJDE that Infoprint XT found is not valid after the first data record of the report.

Infoprint XT cannot process the value value correctly. For units such as IN (inches) or CM (centimeters), Infoprint XT expects no more than three decimal places. For DOTS, Infoprint XT expects an integer value.

Infoprint XT cannot process the value value correctly. Infoprint XT does not process the DJDE (DJDE_name). DJDE naming conventions require a numeric entry with specific rounding values.

The option_name option of the DJDE_name DJDE is not valid.

A copy-sensitive MODIFY, FORMS, or BFORM change request was made during the processing of the current report. You can only specify copy-sensitive MODIFY, FORMS, and BFORM commands at the beginning of a report. The program ignores the request. After text has printed on a copy-sensitive report, you can only change a MODIFY, FORMS, or BFORM command to NONE.

The named resource, resource_name, was not found. The resource name might be misspelled. The resource might not be loaded on the Infoprint XT server or it might have been loaded as a resource that belongs to a specific resource group.

The listed command (command) is not a known DJDE command, or its specification or format is not correct. The program might not process the input.

The data stream converter did not find graphic image image_name before it found the ALTER or CANCEL command for the image.

The data stream converter found more than one DJDE packet that contained page-oriented DJDEs on a page. You can only apply one packet of page-oriented DJDEs to each page. The converter ignores all packets after the first packet.

The GRAPHIC DJDE can document-interleave because it has no parameters other than the image name. However, two inconsistencies exist. First, document-interleaved GRAPHIC DJDEs must occur at the beginning of the job, but Infoprint XT found this GRAPHIC DJDE after text data. This is where page-interleaved graphics occur. Second, a preceding IMAGE DJDE must reference a page-interleaved GRAPHIC DJDE. Infoprint XT found no prior matching IMAGE DJDE.

Infoprint XT tracks page segments that correspond to inline graphics by using the naming convention SGnnnnnn. nnnnnn is a number from 0 through 999999. If more inline graphics are found than can be tracked by using this convention (after SG999999 has been used), Infoprint XT begins using previous names, starting with SG000000. Infoprint XT replaces the page segments associated with the reused names.

The data stream converter found one or more FILE DJDEs that specify the card-image format instead of the required LPS format.

The Xerox LPS does not support DBCS font enlargement factors other than 1, 2, 4, 8, or 16.

While processing a Xerox data stream, Infoprint XT determined that the data stream referenced a Xerox IMG, image_name, which is not loaded on the system.

While xclb=none was in effect, the data stream converter found a FEED DJDE that specified tray_name, which is a name other than MAIN, AUX or OPR. The converter interprets the FEED DJDE as FEED=MAIN, and generates AFP that invokes input media source 1.

A cluster name in a FEED DJDE has no corresponding entry in cluster database clb_name. Infoprint XT ignores the FEED DJDE.

A FEED command in a JDE and JDL pair refers to a cluster, cl_name, which has no corresponding entry in cluster database clb_name.

Stock reference STK_reference in a FEED DJDE has no corresponding entry in the STOCKSET identified in the message.

Stock reference STK_reference in a FEED DJDE has no corresponding entry in the STOCKSET identified in the message.

Stock reference STK_reference in a FEED DJDE has no corresponding entry in the STOCKSET identified in the message.

A FEED command in a JDL and JDE pair specifies a stock reference, STK_reference, which has no corresponding entry in an internal STOCKSET.

A FEED command in a JDL and JDE pair specifies a stock reference, STK_reference, which has no corresponding entry in an external STOCKSET.

A FEED DJDE specifies a stock reference, STK_reference, but no STOCKSET is in effect. Infoprint XT ignores the FEED DJDE command.

A FEED command in a JDL and JDE pair specifies a stock reference, STK_reference, but no STOCKSET is in effect.

While processing line data input, Infoprint XT found that EBCDIC character X'EBCDIC_hex' was not available in code page code_page. Infoprint XT uses a blank in its place. This might occur because of incorrect characters, such as binary zeros, in the print data stream. It might also occur if you have manually correlated a Xerox font to an AFP font and the AFP font does not have characters corresponding to some of the characters in the Xerox font. Or, a character translation table was altered so that a character in the Xerox input does not map to the correct character in the AFP font.

Infoprint XT did not find any input data in the Xerox job file.

While processing the input data stream, Infoprint XT found a shift-in function code but did not find a preceding shift-out function code. There are errors in the input data stream.

While processing the input data stream, Infoprint XT did not find a shift-in function code that corresponded to a preceding shift-out function code. There are errors in the input data stream.

While processing the input data stream, Infoprint XT found more than one shift-out function code in succession. There are errors in the input data stream.

While processing the input data stream, Infoprint XT found a shift-out function code but did not find a DBCS font labeled 'K1' in the active font list.

While processing the input data stream, Infoprint XT found a function code that specified font label kanji_label, but did not find a DBCS font with that label in the active font list.

The job contains an inline graphic image that is in the TIFF format, but the data stream converter cannot locate the tiff2afp transform.

Conversion of an inline TIFF graphic failed. nn is the return code from the tiff2afp transform program. graphic_nn uses the naming convention SGnnnnnn. nnnnnn is a number from 0 through 999999. Numbering begins with SG000000 for the first inline graphic found in the data stream, SG000001 for the next, and so on.

The data stream converter found an error during inline graphic processing. The error occurred while opening a TIFF image for input, opening a file for tiff2afp transform output, or while verifying the header record for the graphic.

Conversion of an inline image graphic failed. error_code is the return code from the image transform program. graphic_number uses the naming convention SGnnnnnn. nnnnnn is a number from 0 through 999999. Numbering begins with SG000000 for the first inline graphic found in the data stream, SG000001 for the next, and so on. record_number is the approximate record number of the end of the inline graphic image in the input file.

Conversion on an inline image graphic failed because of insufficient memory. The image graphic uses the naming convention SGnnnnnn. nnnnnn is a number from 0 through 999999. Numbering begins with SG000000 for the first inline graphic found in the data stream, SG000001 for the next, and so on.

The Infoprint XT data stream converter expected to find a valid Xerox resource file name and extension, but found a string that it did not recognize instead.

While processing an inline graphic in an offline job, Infoprint XT did not find the end of the graphic where it was expected. The graphic might have been created incorrectly, it might have data missing, or it might be otherwise corrupted. While searching for the end of the graphic, Infoprint XT might have read through some of the data that immediately follows the graphic, causing incorrect output.

The name of the Xerox font, font_name, is not in the correct format. Xerox font names must not exceed 6 characters and can include only uppercase alphabetic characters, numeric characters, and the dollar sign ($).

The name of the Xerox font, font_name, is not in the correct format. Xerox font names must not exceed 6 characters and can include only uppercase alphabetic characters, numeric characters, and the dollar sign ($).

Infoprint XT found the end of a report before it found a DJDE record that contained the END; command. Infoprint XT does not process DJDEs that it finds after the end of the report.

The data stream converter uses Xerox font p0612c.fnt to print accounting pages. It did not find the font.

Although Xerox LPS printers support an NTO1 value of 1 through 32767 for stapling, data stream conversion might not produce the results that you want if the target printer does not support the value.

The number of report sheets collected for stapling either exceeds the limit that the NTO1 command in the current JDL and JDE pair specifies, or the limit that the xstaplemax conversion parameter specifies.

Although you requested that Infoprint XT process Xerox stapling commands, you did not reload the JDL and JDE pair in effect after stapling support became available in Infoprint XT. Because Infoprint XT cannot determine whether the original JDL and JDE pair specified STAPLE=YES, NTO1=YES or NTO1=n, or FACEUP=YES, it uses STAPLE=NO. Infoprint XT does not include stapling commands in the AFP that it generates for this report.

One page specified more than 128 fonts.

Infoprint XT tried to process AFP text placement items by using the wrong font list.

Infoprint XT did not find entries for the named font in the correlation tables located in the reformatted Xerox resource path. The font correlation tables are tab.aft and tab.sft.

The data stream converter did not find one or more fonts in the font correlation table, so no default text font was available for printing text.

Infoprint XT did not find the metrics file for the named font in the reformatted Xerox resource path. It was looking for font_name.afn.

While loading a form, Infoprint XT did not find the AFP font listed in the message.

The AFP font resource identified in the message has an internal structure that is not valid.

Infoprint XT did not locate the character translation table identified in the message in the reformatted Xerox resource path.

An AFP font resource is incomplete.

Infoprint XT did not locate any font correlation in the reformatted Xerox resource path.

Code page code_page and character set character_set do not match for character ID character_id.

Code page code_page and character set character_set do not match for character ID character_id.

Infoprint XT cannot locate the JDL specified in the message.

The program did not find JDE JDE_name in JDL JDL_name.

The STOCKSET that Infoprint XT was processing refers to a cluster entry, cl_name, which does not exist in cluster database clb_name. cl_type can be INIFEED, SYSPAGE, or ASSIGN.

The STOCKSET that Infoprint XT was processing refers to a cluster entry, cl_name, which does not exist in cluster database clb_name. cl_type can be INIFEED, SYSPAGE, or ASSIGN.

A stock reference in a FEED DJDE or in external STOCKSET STK_name is correlated to a cluster entry, cl_name, which does not exist in cluster database clb_name. cl_type can be FEED for the FEED DJDE, or INIFEED, SYSPAGE, or ASSIGN for the STOCKS DJDE.

Infoprint XT cannot process the job because it uses the unsupported function FORMAT≠BIN or LMULT≠1.

Infoprint XT cannot process the job because it uses the unsupported function FORMAT≠BIN or LMULT≠1.

resource_type can be CME, PDE, STK, or TST. Infoprint XT did not find the named resource resource_name in the reformatted Xerox resource directory.

Although you requested that Infoprint XT process FCBs, you did not reformat the JDL and JDE pair in effect after FCB support became available. Because Infoprint XT cannot determine whether the original Xerox JDL and JDE specified FCB=PROCESS or FCB=IGNORE, it uses FCB=IGNORE and does not process any FCBs in the data stream.

During AFP font processing, Infoprint XT found a correlation between a Xerox DBCS font and an AFP single-byte font. Infoprint XT does not support this type of correlation.

During AFP font processing, Infoprint XT determined that the reformatted Xerox font metrics file for font_name does not contain DBCS information.

During AFP font processing, Infoprint XT found a reference to Xerox DBCS font font_name, but it also found an xresolution value other than 300.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

An unidentifiable or unexpected I/O condition occurred during processing.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred in the resource utility program. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred in the resource utility program. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred in the resource utility program. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

A logic error occurred. Infoprint XT supplies a phase name, diagnostic information, or both, to help identify the problem.

This is an informational message that indicates the correct parameters for the font analyzer.

The font analyzer found a parameter that it did not recognize.

The font analyzer did not find the font_name font. The resource name might be incorrect, or it might not be available on the system.

The font analyzer found an error in the font_name font.

The font analyzer did not recognize the extension value in the font_name font.

The font analyzer did not recognize the orientation value in the font_name font.

The font analyzer did not recognize the font type value in the font_name font.

The font analyzer found an internal error during font processing.

This is an informational message that indicates that Infoprint XT found a Xerox single-byte character set font. It requires no user response.

Infoprint XT does not support this type of font.

Infoprint XT does not support this type of font.

This is an informational message that indicates that Infoprint XT found a Xerox double-byte character set font. It requires no user response.

The font analyzer did not recognize the DBCS font type value in the font_name font.

The font analyzer did not recognize the encoding type value in the font_name font.

This is an informational message that indicates the correct parameters for the resource header utility.

The resource header utility found a parameter that it did not recognize.

This is an informational message that indicates that the resource header utility modified a resource header. It requires no user response.

This is an informational message that indicates that the resource header utility created a resource header. It requires no user response.

The resource header utility did not find the resource_name resource. The resource name might be incorrect, or it might not be available on the system.

The permissions for resource resource_name do not let the resource header utility access the resource.

Header processing for resource_name resource failed because of insufficient memory.

The resource header utility did not open the resource_name resource. The resource name might be incorrect, or it might not be available on the system.

Valid Xerox resources must contain a multiple of 128 bytes.

Valid Xerox resource names contain a 1-to-6 character resource name before the period, and a 3-character extension after the period. The valid Xerox resource name characters are uppercase alphabetic characters, numeric characters, and the dollar sign ($).

The resource header utility did not recognize the extension of the resource_name resource

The resource header utility did not recognize the block size value of the resource_name resource.

The resource header utility did not recognize the extension value of the resource_name resource.

The resource header utility did not recognize the blocking factor value of the resource_name resource.

An unidentifiable or unexpected I/O condition occurred during processing.

The resource header utility found an error during processing.

The specified DJDE exceeded the maximum number of inks in a list, which is 64.

Infoprint XT found incorrect characters in the specified DJDE.

Infoprint XT found incorrect numeric input in the specified DJDE. The syntax for the specified DJDE requires one or more numeric fields, which are incorrect.

Infoprint XT cannot process the LPI DJDE line spacing value correctly. Either the value is nonnumeric, or the value is out of range for the specific units. Permitted units are LPI, DOTS or XDOTS. The maximum value for line spacing is 30 LPI, and the minimum value is 10 dots.

Infoprint XT found an LPI DJDE with multiple overlapping line ranges.

Infoprint XT found a DJDE with more than allowed entries.

This is an informational message that indicates that the resource header utility padded a resource to ensure that it contains one or more complete 512-byte blocks. It requires no user response.

The resource name has an extension for a binary resource, but the file only contains text.

Infoprint XT cannot read the file identified in the message.

This is an informational message that indicates that the resource header utility removed extraneous padding from an existing resource header. It requires no user response.

Infoprint XT could not allocate the required data set. Supervisor Call (SVC) 99 returned the error and information codes.