This message formats and presents the 24 printer-sense bytes that were reported to PSF by a 3800 printer for a non-position check I/O error. A primary message describing the specific I/O error accompanies this message. The primary message should be sufficient for diagnosing and resolving a user error. This detailed sense byte message is intended for use by the system programmer or the IBM® Support Center in diagnosing hardware or PSF logic errors.

• Error sense bytes 0–5 are the first 6 bytes in the sense data, reported in hexadecimal. These bytes are used to identify the specific I/O error:
  • Byte 0—Error group
  • Byte 1—Check code or status code
  • Byte 2—Recovery Action code for this error condition
  • Byte 3—Dynamic conditions
  • Byte 4—X'00', or same as sense byte 1 or X'DE'
  • Byte 5—Depends on format of sense being issued
• Xp position is the print position on the X-axis at the time of the error, stated in pels. This information was obtained from bytes 6 and 7 of the sense data.
• Yp position is the print position on the Y-axis at the time of the error, stated in pels. This information was obtained from bytes 8 and 9 of the sense data.
• Printer buffer offset is the approximate number (in decimal) of the byte, in the data sent by the current channel command, that the printer was processing when it detected the error. This information was transformed from bytes 10 and 11 of the sense data.
• Printer state is the state of the printer at the time the error was detected. This information was formatted from byte 12 of the sense data.
  • X'00'—Home state
  • X'01'—Font index
  • X'02'—Font state
  • X'03'—Page state
  • X'04'—Page image state
  • X'05'—Reserved
  • X'06'—Reserved
  • X'07'—Overlay state
  • X'08'—Overlay image state
  • X'09'—Reserved
  • X'0A'—Reserved
  • X'0B'—Segment state
  • X'0C'—Segment image state
  • X'0D'—Reserved
  • X'0E'—Reserved
  • X'0F'—Compatibility mode
• Channel command is the channel command that was being processed at the time when the error was detected. This information was formatted from byte 13 of the sense data. If the reference manual for the 3800 printer is not available, these channel commands are also listed in IBM System/370 Extended Architecture Reference Summary (GX20-0157) or in IBM Enterprise Systems Architecture/390 Reference Summary (SA22-7209).
• Error identification type identifies the type of ID entry that is displayed in bytes 15 and 16 (the error identification). This information was formatted from byte 14 of the sense data. The values are:
  • X'80'—Font-related error (bytes 15 and 16 contain font ID)
  • X'40'—Segment-related error (bytes 15 and 16 contain segment ID)
  • X'20'—Overlay-related error (bytes 15 and 16 contain overlay ID)
  • X'10'—Suppression-related error (bytes 15 and 16 contain a suppression ID)
• Error identification is the font ID, segment ID, overlay ID, or suppression ID, as identified by the contents of the error identification type value. This information was formatted from bytes 15 and 16 of the sense data.
• Copy subgroup is the number of the active copy group, in decimal. To determine which copy subgroup was being printed at the time of the error, find the active form definition and medium map named in the accompanying environmental messages. In the medium map is a Medium Modification Control (MMC), which specifies the medium modifications to be applied for the copy subgroup specified in the Medium Copy Count (MCC) structured field. If all the copy subgroups specify simplex printing, the value returned in these sense bytes refers to the nth copy subgroup listed in the MCC. Any copy subgroup that specifies duplex counts as two. This information was transformed from byte 17 of the sense data.
• Error sense bytes 18–23, in hexadecimal:
  • Byte 18: Last font number set from the font equivalence table.
  • Byte 19: Check group code ID used with bytes 0 and 1 to identify the error.
  • Bytes 20–23: Page ID sent with the Begin Page command.
    Note:

    If the printer is not in Page or Page Image state, the page ID is zero.

See the accompanying messages for the system action that was taken.

If the accompanying messages are not sufficient to identify the problem, contact your system programmer.

If the accompanying messages are not sufficient to identify the problem, use the sense data to analyze the problem. For more information about printer sense bytes and the specific error, see the printer publications for the printer that reported this error.

No response is necessary.

Items 2, 17, 27.

The page information and object names that were active at the time of the error are presented in this message. A subset of the pages and names listed in the message is associated with each error.

Printing of the page or data set containing the error ends. Processing continues.

To determine an appropriate response, see the specific error conditions described in the accompanying messages.

To determine an appropriate response, see the specific error conditions described in the accompanying messages.

No response is necessary.

Items 2, 17, 27.

The print position exceeded the boundaries of the logical page to the right, bottom, left, or top. The direction in which the print position was off the page is relative not to the logical page, but to the paper as it moves through the printer. For example, the top of the sheet is the perforated edge that leads through the printer.

This error was reported because DATACK=UNBLOCK or BLKCHAR was specified in the OUTPUT JCL statement or the PRINTDEV JCL statement in the PSF initialization procedure or Print error reporting was specified as All or Character in the Printer Inventory. Print-error markers are printed on the page containing the error to indicate the position and the direction in which this position error occurred.

The error was caused by one or more of these:

• More characters were transmitted than can fit on a line in the logical page.
• More lines were transmitted than can fit on the logical page.
• The font selected from the form definition or defined either in the page definition or in the table reference character (TRC) caused the data to exceed the logical page.
• A positioning text-control sequence (Absolute Move Inline [AMI], Absolute Move Baseline [AMB], Relative Move Inline [RMI], or Relative Move Baseline [RMB]) positioned the print position outside of the physical page. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The message containing the sense data that accompanies this message identifies the Xp and Yp position at the time of the error.

The printer you were using might try to print the page in error. The entire page might not be printed. The page in error is printed with print-error markers to indicate the position and direction of the positioning errors. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If your printed output would be acceptable, you can resubmit the print request, specifying BLOCK or BLKPOS for the DATACK keyword on the JCL OUTPUT statement. For more information on how to code this keyword, see PSF for z/OS: User’s Guide.

If you want to correct the source of the problem, and if you were printing MO:DCA data, check the current print position and either the characters per line, the lines per page, or both. Use a different font, if necessary, so that the print position is inside the printable area. Correct the size of the logical page so that it contains the print position. If you created the structured fields for the MO:DCA data, check the PTX structured field for positioning outside of the page.

If you want to correct the source of the problem, and if you were printing a data set containing line data, you could change the font selected from the page definition or the CHARS keyword in the JCL statements to a smaller font. If you were using a page definition and you created its structured fields, check the print-positioning values in the Line Descriptor (LND) structured field, and correlate them with the number of printable characters per line and the number of lines per page. You could also increase the logical page size by changing the Page Descriptor (PGD) structured field in the page definition.

If you want to correct the source of the problem, and if you were printing a data set containing line data with embedded structured fields, check the PTX structured field for positioning outside of the page.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The coded font section identifiers in the Coded Font Index (CFI) structured field are not in ascending order. The CFI structured field is in the coded font.

The printer you were using might try to print the page that contains the error, or might print only part of the page. If the page contains any positioning errors, print-error markers might be included on the printed page. PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 for more information about the structured fields. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

The image color value specified is not valid or is unsupported by this printer. The image color value is specified on any of these structured fields:

• The IM Image Input Descriptor (IID).
• The Image Data Descriptor (IDD) for IOCA images.

The image or image cell might be contained in an overlay, a page segment, or MO:DCA data. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If you created the structured fields for the IOCA image object, correct the error and resubmit the print request. Contact your operator and ask that your previous print request, which was held, be purged. See Image Object Content Architecture Reference, AFPC-0003 for more information about the contents of the IPD structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the IOCA image object, contact your system programmer.

If you submitted the print request to the wrong printer, consult your operator to determine to which printer that data set should be rerouted.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If you are running under Job Entry Subsystem (JES), use the JES data-set release commands to release the data set to a printer that supports this function. For a JES command to release the data set for printing, see z/OS JES2 Commands or z/OS JES3 Commands .

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The X-coordinate or Y-coordinate for a page overlay is not valid or is unsupported.
2. The Overlay Type parameter in an Include Overlay (IO) command is not valid or is unsupported (possible logic error).

If the overlay containing the error is a secure overlay, this condition was caused by a PSF logic error. If the overlay containing the error is not a secure overlay, the coordinates are specified in the Include Page Overlay (IPO) structured field. The IPO structured field might be in the MO:DCA data or a page definition, or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If the error involves a secure overlay, notify your system programmer of this error. If you created the structured fields for the print data set, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the print data set, contact your system programmer.

If the error involves a secure overlay, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center. If the error does not involve a secure overlay, and if an IBM licensed program was used to create the structured fields for the print data set with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The reference corner and edge field (byte 5) in a Finishing Operation triplet (X'85') contains an incorrect or unsupported value for this finisher.

Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map.

Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition.

When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and the data set is marked unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT was specified on the OUTPUT statement.

When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:

• If the printer supports the PFC Finishing Fidelity triplet and if the REPORT field is set to REPORT (X'01'), the printer reports this exception. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer supports the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer does not report this error to PSF but takes its continuation action and continues processing the page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer reports this exception but PSF does not issue the error message. The printer takes its continuation action for the page and PSF continues processing the data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to REPORT (X'01'), the printer reports this exception and PSF issues the error message. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.

If the output is not acceptable:

• Verify that you have requested the appropriate form definition for the finishing operation intended.
• Submit the print request to a printer that can perform the finishing operation.
• If you created the structured fields for the form definition, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the form definition, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 13, 15c, 17, 19.

While a data set was being processed, the printer presented a command reject I/O error indicating that the data transmission came to an abnormal end during a fast-buffer-release operation. For more information about this error, see the printer publications for the printer that reported this error.

PSF stops processing the data set being processed at the time of the error and marks it unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement.

If the data set was held by the system, consult the system operator to release the data set for printing. If PSF stopped processing the data set but it was not held by the system, resubmit the data set for printing. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

If the data set was held by the system, a JES message displays on the console. For a JES command to release the data set for printing, see the publication containing JES commands for your operating system.

Items 1, 8, 18.

One or more of these conditions occurred:

• An undefined character or a character that is not valid has been detected in Write Bar Code (WBC) command bar code data.
• An undefined character has been detected in the font specified for text, bar code human-readable interpretation (HRI), or graphics character-string data.
• An undefined character has been detected in Presentation Text (PTX) command data at the quality level specified.

When a code page is used, the flag byte parameter in either the Code Page Control (CPC) or a repeating group of the Code Page Index (CPI) structured field had the undefined bit set for a code point in the text data that was to be printed. The CPC and CPI structured fields are in the code page. This error occurred because DATACK=UNBLOCK or BLKPOS was specified in the OUTPUT JCL statement or the PRINTDEV JCL statement in the PSF initialization procedure or Print error reporting was specified as All or Character in the Printer Inventory. One of these conditions occurred:

• The code page did not include the code point, and the default character, specified by the CPC, had the not valid flag on.
• The character assigned to this code point did not exist in the character set, and the default character, specified by the CPC, had the not valid flag on.
• The code point, specified by the CPI structured field, had the not valid flag on.

For a Data-Object font used without a code page, a character was not defined for a code point. In this case, a special default character, such as Glyph Index 0 for a TrueType or OpenType font, is substituted for the missing character.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If bytes 12-13 in the formatted sense message (APS830I) are COMMAND= 'D681'x (WBC), the error must be corrected in the application data; not by setting a DATACK value. Contact the data owner to correct this error. Otherwise, to eliminate this error message from your output, you can resubmit the print request specifying BLOCK or BLKCHAR for the DATACK keyword on the JCL OUTPUT statement. For more information about how to code this keyword, see PSF for z/OS: User’s Guide.

If you want to correct the source of the problem, you first need to identify which character in which font contains the error. If the printer returned the information about the incorrect character, check these:

• Immediately following this message (APS708I) is a formatted sense message (APS830I). The Element Identifier field in this message contains the code point in which the error occurs, or zeros if the printer did not return the information.
• To determine which code page and font have this incorrect code point, check the APS701I messages. These are the environmental messages for this page. If the printer returned the information, one of the APS701I messages provides the active code page name and the active character set name.

Ensure that the code point in the print data is correct. If the code point is incorrect and you created the structured fields for the code page, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information on the correct format of the referenced structured field. If you used a program to create the structured fields for the code page, consult your system programmer.

If an IBM licensed program was used to create the structured fields for the code page with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Pattern Data Count parameter value in the Font Control (FNC) structured field is not valid. The FNC structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected this error while processing the font sections of a specified double-byte font. Except for two parameters, font sections are required to have identical data. The control data was not the same for one or more of the sections specified for the font. The font-control parameters must have unique data, except for these:

• Pattern Data Count in the Font Control (FNC) structured field
• Flag Byte in the Font Orientation (FNO) structured field

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The paper in the printer was jammed, or a post processor was resynchronized. The printer detected and reported an asynchronous intervention-required error with an action code of X'08' (sense byte 2). For more information about this error, see the printer publications for the printer that reported the error.

PSF resends pages to the printer, starting from the jam recovery page counter plus 1. PSF might print this message on a separate sheet in the data set to mark the position at which the recovery from this error was started. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 8, 18.

An error occurred with the process power of the printer. The printer detected and reported an asynchronous equipment check with an action code of X'0B' (sense-byte 2). For more information about this error, see the printer publications for the printer that reported this error.

PSF resends pages to the printer, starting from the jam recovery page counter plus 1. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set. PSF also prints this message at the end of the print data set to indicate that this message was printed within the print data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 8, 18.

The printer presented a unit check to PSF with an action code of X'0D' (sense-byte 2) to indicate that an automatic or manual initial microcode load (IML) operation has been successfully completed. For more information about this error, see the printer publications for the printer that reported this error.

Pages in the printer's page buffer and all resources in the printer are lost. If the printer is in the middle of finishing a group of pages, that finishing operation is not performed. The printer resets its page counters to zero. PSF resends pages to the printer, starting from the committed page counter. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. PSF also prints this message at the end of the data set to indicate that this message was printed within the data set. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 8, 18.

The printer detected and reported a data check with an action code of X'10' (sense byte 2). This message indicates one of these:

• The page or paper size is not compatible with accumulator data stored earlier.
• The base page was moved to accumulator storage and needs to be reloaded.
• The raster overlay in the accumulator storage needs to be reloaded.

PSF causes the printer to discard the printer's buffered data and to delete all overlays, page segments, and fonts. On the first occurrence of this error, the message is printed on a separate sheet in the data set to mark the position before recovery starts. PSF recovers by resending pages to the printer, starting from the last known committed page counter plus 1. On the second occurrence of this error, the message is printed at the end of the message data set, and PSF stops processing the data set at the committed page counter plus 1.

If the output is unacceptable, resubmit the print request. The overlay or page segment might need to be modified. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 8, 18.

The printer detected a Begin Suppression (BSU) text control while it was processing the page. The corresponding End Suppression (ESU) text control was not received before the page was completed. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, a presentation text object, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, a presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected an incorrect value for the character-box size specified either in the Character Box X-Extent or in the Character Box Y-Extent parameter in the Font Control (FNC) structured field of the font being processed.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of an error condition that caused the exception to be reported. For error sense X'0226..02' (written as Byte 0 Byte1...Byte 19), one or both of these conditions occurred:

1. The character box X size specified in the Font Control (FNC) structured field of the font is not valid or is unsupported, or is incompatible with the specified font.
2. The character box X size specified in the FNC structured field of the font is greater than the maximum X-box size.

For error sense X'0227..02' (written as Byte 0 Byte1...Byte 19), one or both of these conditions occurred:

1. The character box Y size specified in the Font Control (FNC) structured field of the font is not valid or is unsupported, or is incompatible with the specified font.
2. The character box Y size specified in the FNC structured field of the font is greater than the maximum X-box size.

The FNC structured field is in the font character set.

PSF stops processing and printing the data set that uses the font containing the error.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

This message presents the 24 printer sense bytes that were reported to PSF at the time of an I/O error.

See the accompanying messages for the system action that was taken.

If the accompanying messages are not sufficient to identify the problem, contact your system programmer.

If the accompanying messages are not sufficient to identify the problem, use the sense data to analyze the problem. For more information about printer sense bytes and the specific error, see the printer publications for the printer that reported this error. If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

Inform your system programmer that this error occurred.

Items 1, 8, 18.

The printer detected that the width and length values for the character-box size for a font specified to be non-uniform were not equal (for example, the font has variable character-box sizes). The character box X-Extent and the character box Y-Extent, specified in the Font Control (FNC) structured field, must be equal for non-uniform fonts. The Uniform Character Box Size parameter in the FNC structured field indicates whether the character box size of a font is uniform or non-uniform. The FNC structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

While processing double-byte data, the printer detected a font section identifier that could not be used. Either the coded font specified to print the data did not contain a section with that identifier, or the section identifier was not in the valid range. The font section identifier is the first byte of the 2-byte character code in a double-byte data stream.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

Verify that the appropriate font was selected and that the section identifier coded in the print data for the character is valid. Valid ranges for font section identifiers are described in Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884. If the font section identifier is valid, ensure that a font section with that identifier is included in the double-byte coded font you want to use.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Set Variable Space Increment (SVI) text-control sequence is outside the valid range. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected and reported an equipment check error with an action code of X'0B' (sense-byte 2). The printer identified by the address reported in this message requires the operator to restore power to the printer process. For more information about this error, or to interpret the printer sense bytes, see the printer publications for the printer that reported this error.

After the printer has been readied, PSF resends pages to the printer, starting from the jam recovery page counter plus 1. PSF prints a message on a separate sheet in the data set to mark the position where the recovery from this error was started. PSF also prints the same message at the end of the data set to indicate that the message was printed within the data set. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

Restore power to the printer and press RESET or READY.

Items 1, 8, 18.

The printer detected and reported an asynchronous intervention-required error with an action code of X'08' (sense-byte 2). An unexpected RESET command was received and might have caused the printer's paper path to jam. For more information about this error, see the printer publications for the printer that reported this error.

PSF resends pages to the printer, starting from the jam recovery page counter plus 1. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

See the operator's guide for the printer that reported this error, and clear the paper jam in the printer. PSF assumes that pages between the jam recovery page counter and the stacked page counter are not damaged by the paper jam and do not need to be reprinted. If any pages between these two page counters need to be reprinted, use the JES BACKSPACE command.

Items 1, 8, 18.

The Uniform Character Increment parameter in the Font Orientation (FNO) structured field is not valid. The FNO structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected and reported an out-of-storage print error with an action code of X'0C' (sense-byte 2). The requirement for raster-pattern storage (RPS), writable-control storage (WCS), compressed-pattern storage (CPS), or font storage (FONT) exceeded the available storage resources of the printer.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

PSF recovers from this out-of-storage print error by deleting all resources (for example, overlays, page segments, and fonts) that are not required for the current page being sent to the printer. PSF then resends pages to the printer, starting from the Received Page ID. If the error condition persists, PSF issues message APS725I, skips the page containing the error, and continues processing the current data set with the page after the page containing the error. If repositioning is not supported in the current environment, PSF stops processing the data set.

If the printed output is not acceptable, make the page less complicated by deleting resources (for example, overlays, page segments, and fonts) or print the data set on a printer with more of the type of storage that was exceeded. For more information, see the documentation provided with the printer.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected and reported an out-of-storage error with an action code of X'0C' (sense-byte 2). The requirement for raster-pattern storage (RPS), writable-control storage (WCS), compressed-pattern storage (CPS), or font storage (FONT) exceeded the available storage resources of the printer. PSF detected that this was the second resource-constrained error for the page containing the error. (See message APS724I.) This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

PSF recovers from this out-of-storage printer error by skipping the page containing the error because this is the second attempt to send it to the printer. PSF continues processing the current data set with the page after the page containing the error. If repositioning is not supported in the current environment, PSF stops processing the data set.

If the data stream errors stopped processing of the page just before the page for which APS725I was issued, correct the data stream errors first and resubmit the print request. The condition that caused message APS725I to be issued might be resolved after the other errors have been corrected. If this situation does not apply, make the page less complicated by deleting resources (for example overlays, page segments, and fonts), or print the data set on a printer with more of the type of storage that was exceeded.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Orientation parameter in the Font Orientation (FNO) structured field is not valid. The FNO structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Uniform Baseline Offset parameter in the Font Orientation (FNO) structured field is not valid. The FNO structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Font Index Number, bits 0–2 of the Flag Byte parameter, in the Font Orientation (FNO) structured field is not valid. The FNO structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The pattern data offsets in the repeating group entries in the Font Pattern Map (FNM) structured field are not in ascending order.
2. A pattern data offset in the repeating group entries in the FNM structured field points past the end of the raster data.
3. A pattern data offset in the repeating group entries in the FNM structured field points to a character pattern that extends beyond the end of the raster data.
4. A pattern data offset in the repeating group entries in the FNM structured field points into a previously defined character pattern.

The FNM structured field is in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the number of overlays specified in the Medium Modification Control (MMC) structured field and the number of medium overlays specified on the OUTPUT, PRINTDEV, or both statements, or in the Printer Inventory are added, the total exceeds what this printer can support on a physical page (one side of a sheet). The MMC structured field is contained in the form definition.

The limit for the total number of overlays depends on the printer you use.

PSF stops processing the data set that was being processed at the time of the error and marks it unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement.

Change the output class for the next submission. Consult the system operator to have the print request released to a printer that can print the total number of overlays on that page. If you do not have access to a printer that can support that number of overlays on a page, the number of overlays needs to be decreased. If you created the form definition that contains the MMC structured field, you must remove one or more of the overlays, depending on how many medium overlays were specified. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. Resubmit the print request. If the total number of user overlays and OUTPUT/PRINTDEV statement medium overlays is less than or equal to what this printer should support, the error might be a PSF logic error.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If you are running under Job Entry Subsystem (JES), use the JES data set release commands to release the data set to a printer that can handle a larger number of medium overlays. To find the JES command to release the data set for printing, see the publication containing JES commands for your operating system.

Items 2, 17, 28.

An incorrect text control code was found. The text control came from a Text Data (PTX) structured field or was generated by PSF from a page definition. The Presentation Text Data (PTX) structured field might be contained in a MO:DCA document, an overlay, a presentation text object, or a page segment; or it might be embedded in a data set containing line data.

Reporting of this exception can be controlled by the Text Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition.

When the Text Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and marks the data set unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement.

When the Text Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:

• If the printer supports the PFC Text Fidelity triplet and if the REPORT field is set to REPORT (X'01'), the printer reports this exception. PSF continues processing the current data set with the page following the page in error, unless the printer reports another error that requires a more severe PSF recovery action. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer supports the PFC Text Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer does not report this error to PSF but takes its continuation action and continues processing the page.
• If the printer does not support the PFC Text Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer reports this exception but PSF does not issue the error message. The printer takes its continuation action for the page and PSF continues processing the data set with the page following the page in error, unless the printer reports another error that requires a more severe PSF recovery action. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer does not support the PFC Text Fidelity triplet and the REPORT field is set to REPORT (X'01'), the printer reports this exception and PSF issues the error message. PSF continues processing the current data set with the page following the page in error, unless the printer reports another error that requires a more severe PSF recovery action. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

For a double-byte font, many of the parameters specified in the Code Page Control (CPC), Font Control (FNC), and Font Orientation (FNO) must be identical for all sections with the same character rotation, or must be identical for those sections in the range X'45' through X'FE'. One or more parameters violated these rules:

These parameters must be the same for all sections:

• Default Graphic Character Global ID (CPC)
• Space character Section Number and Code Point (CPC)
• Variable space enable flag (CPC)
• X Unit Base (FNC)
• Y Unit Base (FNC)

This parameter must be the same for all sections with the same character rotation:

Space Character Increment (FNO)

These parameters must be the same for all sections in the range X'45' through X'FE' with the same character rotation:

• Uniform Character Box Font flag must be set to B'1' (FNC)
• Maximum Character Box Size (FNC)
• Maximum Baseline Offset (FNO)
• Maximum Character Increment (FNO)
• Uniform baseline offset flag must be set to B'1' (FNO)
• Uniform character increment flag must be set to B'1' (FNO)
• Minimum A-space (FNO)
• Maximum baseline extent (FNO)
• Uniform A-space flag must be set to B'1' (FNO)

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The X-coordinate value specified in the Image Block Origin parameter of an Image Output Control (IOC) structured field is outside of the valid range. The value is specified in absolute I-units. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

The Y-coordinate value specified in the Image Block Origin parameter of an Image Output Control (IOC) structured field is outside of the valid range. The value is specified in absolute B-units. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

The physical media cannot be sent to the selected media destination. The printer cannot continue processing the data set.

PSF stops processing and printing the data set.

Follow these steps:

1. Ensure that the input media source is valid and that it contains the appropriate media for the finishing operation being performed. The input media source can be selected in the form definition, or PSF uses the default media source for the printer.
2. Ensure that the output media destination is valid for the finishing operation being performed. The media destination can be selected on the JCL OUTPUT statement with the OUTBIN keyword, or PSF uses the default media destination.
3. Verify that you have requested the appropriate form definition for the finishing operation intended.

No response is necessary.

No response is necessary.

Items 1, 2, 13, 15c, 17, 19.

The Medium Finishing Control (MFC) structured field contains Finishing Operation triplets that are incompatible. Compatible combinations of finishing operations are specific to a particular presentation device. When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. An MFC structured field contains two or more Finishing Operation triplets that specify incompatible finishing operations.
2. A pair or more of MFC structured fields create nested Finishing Operation triplets that specify incompatible finishing operations.

The MFC is specified in the Document Environment Group of the form definition or in a Medium Map.

Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition.

When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and the data set is marked unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT was specified on the OUTPUT statement.

When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:

• If the printer supports the PFC Finishing Fidelity triplet and if the REPORT field is set to REPORT (X'01'), the printer reports this exception. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer supports the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer does not report this error to PSF but takes its continuation action and continues processing the page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'021'), the printer reports this exception but PSF does not issue the error message. The printer takes its continuation action for the page and PSF continues processing the data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to REPORT (X'01'), the printer reports this exception and PSF issues the error message. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.

If the output is not acceptable:

• Verify that you have requested the appropriate form definition for the finishing operation intended.
• Submit the print request to a printer that can perform the finishing operation.
• If you created the structured fields for the form definition, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the form definition, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 13, 15c, 17, 19.

The X-coordinate value in the Page Origin parameter in the Page Position (PGP) structured field is outside of the valid range. The PGP structured field is in the form definition.

PSF stops processing and printing the data set.

If you created the structured fields for the form definition, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the form definition, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the form definition with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

The Y-coordinate value in the Page Origin parameter in the Page Position (PGP) structured field is outside of the valid range. The PGP structured field is in the form definition.

PSF stops processing and printing the data set.

If you created the structured fields for the form definition, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the form definition, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the form definition with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. Additional data is required to complete a partial control sequence or double-byte code point. The text-control sequences came from a Presentation Text Data (PTX) structured field or were generated by PSF from a page definition.
2. Additional Image Picture Data (IPD) structured field data is required to complete a partial image. If the original image was an IM1 image and the resolution in the IID structured field does not match the printer resolution, PSF attempts to convert the IM1 image to Image Object Content Architecture (IOCA) (if the printer supports IOCA). During this conversion process, IM1 structured fields are converted to IOCA Intelligent Printer Data Stream (IPDS) commands. This error occurs in either of these conditions:
   • A Set Home State command occurs before the entire image data is sent to the printer.
   • An error is detected in the process of outputting image data that causes PSF to stop processing the page.
3. Additional Graphics Data (GAD) structured field data is required to complete a partial graphics Begin Segment Introducer or drawing order.
4. Additional Object container Data (OCD) structured field data is required to complete a partial object container.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the appropriate structured field. For more information, see Mixed Object Document Content Architecture Reference, AFPC-0004. If you used a program to create the structured fields for the MO:DCA print data set, overlay, or page segment, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the appropriate structured field. If the structured field has no errors, consult your system programmer.

If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error. Consult your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Maximum Baseline Extent parameter in the Font Orientation (FNO) structured field parameter is not valid. The FNO structured field is contained in the font character set.

PSF stops processing and printing the data set.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The sum of the Xm (or Ym) coordinate of the User Printable Area (UPA) origin and the Xm extent of the User Printable Area specified in the security definitions library member exceeds the maximum value that can be represented in the printer. The UPA dimensions are specified in the security definitions library.

PSF stops processing and printing the data set.

Inform your system programmer that this error occurred.

Decrease the size of the UPA dimensions in the security definitions library member. See PSF for z/OS: Security Guide for information about the format of the security definitions library.

If this message displays on the operator's console, it indicates that PSF cannot print a separator page or print error messages. Inform your system programmer that this error occurred.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The X axis extent in a Page Descriptor (PGD) or Presentation Text Data Descriptor (PTD) structured field is not valid or is unsupported.
2. The X axis extent in a Medium Descriptor (MDD) structured field is not valid or is unsupported.

The PGD structured field is in the MO:DCA data, an overlay, or a page definition. The PTD might be specified in either the Object Environment Group (OEG) for the presentation text object or the Active Environment Group (AEG) for the page or overlay. The MDD structured field is in the form definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a form definition, and you created the structured fields in the object containing the error, change the page size in the print data set, overlay, or form definition. If you were printing MO:DCA data, an overlay, or a form definition, and you used a program to create the structured fields in the object containing the error, change your input to that program to change the paper size. If you were printing a data set containing line data, change the page size in the page definition.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The Y axis extent in a Page Descriptor (PGD) or Presentation Text Data Descriptor (PTD) structured field is not valid or is unsupported.
2. The Y axis extent in a Medium Descriptor (MDD) structured field is not valid or is unsupported.

The PGD structured field is in the MO:DCA data, an overlay, or a page definition. The PTD might be specified in either the Object Environment Group (OEG) for the presentation text object or the Active Environment Group (AEG) for the page or overlay. The MDD structured field is in the form definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a form definition, and you created the structured fields in the object containing the error, change the page size in the print data set, overlay, or form definition. If you were printing MO:DCA data, an overlay, or a form definition, and you used a program to create the structured fields in the object containing the error, change your input to that program to change the paper size. If you were printing a data set containing line data, change the page size in the page definition.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Width parameter in the Draw Inline Rule (DIR) or Draw Baseline Rule (DBR) text-control sequence either is greater than the maximum width or is less than the minimum width. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Width parameter in the Draw Inline Rule (DIR) text-control sequence is less than the minimum width. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Length parameter in the Draw Inline Rule (DIR) text control is outside the valid range. The text-control sequence is in a Presentation Text Data (PTX) structured field. The PTX structured field might be in the MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Width parameter in the Draw Baseline Rule (DBR) text control exceeds the maximum width. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Width parameter in the Draw Baseline Rule (DBR) text control is less than the minimum width. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Length parameter in the Draw Baseline Rule (DBR) text control is outside the acceptable range. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Set Coded Font Local (SCFL) text-control sequence was not specified after the text orientation was changed. When the text orientation changes, the SCFL text-control sequence should be specified after the Set Text Orientation (STO) text control sequence, unless the current font is usable in the new orientation. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, a presentation text object, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the text-control sequence in the PTX structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing MO:DCA data, a presentation text object, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If you were using a page definition to print a data set containing line data, and you created the structured fields for the page definition, specify a valid value for the text orientation parameter in the Line Descriptor (LND) structured field, or specify a font that can be printed in the original text orientation. If you used a program to create the structured fields for the page definition, consult your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. An End Suppression (ESU) text-control sequence that identifies the end of a passage of suppressible text does not specify the print-suppression number used in the Begin Suppression (BSU) text control.
2. An ESU text-control sequence was encountered without a prior BSU text-control sequence.

The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, a presentation text object, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, a presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

A Begin Suppression (BSU) text control was received before the preceding Begin Suppression (BSU) text control was ended by an accompanying End Suppression (ESU) text control. The printer you were using when the error occurred does not allow this. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, a presentation text object, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, a presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

A Begin Suppression (BSU) and an End Suppression (ESU) text-control sequence was specified within an overlay. The printer you were using when the error occurred does not allow this. The text-control sequence is in a Presentation Text Data (PTX) structured field.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the overlay, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the overlay, consult your system programmer.

If an IBM licensed program was used to create the structured fields for the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The orientation of the font selected to print the text does not match the current text orientation. The current text orientation is defined in a Set Text Orientation (STO) text control in a Presentation Text Data (PTX) structured field or, if you were printing a data set containing line data, in a Line Descriptor (LND) structured field in the page definition. The PTX structured field might be in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data. The font is named in a Map Coded Font (MCF) structured field, in the page definition or in the CHARS option of the JCL. The MCF structured field is in the MO:DCA data, an overlay, or a page definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If the orientation was correct but the font was wrong, specify a different font that is compatible with the desired text orientation.

If the orientation was incorrect and if you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, change the text orientation value in the STO text control. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about specifying text orientation. If you were printing MO:DCA data, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If the orientation was incorrect and you were printing a data set containing line data with a page definition that you created, change the Text Orientation value in the LND structured field. If you were printing a data set containing line data, and using a page definition created by a program, consult your system programmer.

If the orientation was incorrect and you were printing a data set containing line data with embedded structured fields, change the text orientation value in the STO text control. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about specifying text orientation.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Coded Font Local Identifier parameter in the Set Coded Font Local (SCFL) text control in a Presentation Text Data (PTX) structured field or in the Line Descriptor (LND) structured field in the page definition is outside the valid range. The Presentation Text Data (PTX) structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the identifier in the SCFL text control. If the SCFL text control has no errors, the error might be a PSF or printer logic error. If you were printing MO:DCA data, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If you were printing a data set containing line data, and you were using a page definition that you created, correct the identifier in the LND structured field. If the LND structured field has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data, and you were using a page definition that you created by use of a program, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the identifier in the SCFL text control. If the SCFL text control has no errors, the error might be a PSF or printer logic error.

For the valid values of the Coded Font Local Identifier in the appropriate structured field, see Mixed Object Document Content Architecture Reference, AFPC-0004.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The inline or baseline orientation value specified in a Set Text Orientation (STO) text control sequence in a Presentation Text Data (PTX) structured field or in a Line Descriptor (LND) structured field in a page definition, is not valid or is unsupported.
2. The combination of the baseline and inline orientations is not valid or is unsupported.

The Presentation Text Data (PTX) structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the value in the STO text control.

If the STO text control has no errors, the error might be a PSF or printer logic error. If you were printing MO:DCA data, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If you were printing a data set containing line data by using a page containing line data and using a page definition that you created, correct the value in the LND structured field. If the LND structured field has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data by using a page definition that you created with a program, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the identifier in the STO text control. If the STO text control has no errors, the error might be a PSF or printer logic error.

See Mixed Object Document Content Architecture Reference, AFPC-0004 for the acceptable values of the Text Orientation parameter in the appropriate structured field.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Inline Coordinate parameter in the Set Inline Margin (SIM) text-control sequence is not valid. The text-control sequence is in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data. If the error occurred while PSF was processing line data, the Inline Position parameter in a Line Descriptor (LND) structured field in the page definition might be incorrect .

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Baseline Increment parameter in the Set Baseline Increment (SBI) text-control sequence is not valid. The text-control sequence is in a Presentation Text Data (PTX) structured field or was generated by the PSF from a page definition. The PTX structured field might be in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Intercharacter Increment parameter or the optional Intercharacter Adjustment Direction parameter in the Set Intercharacter Increment (SII) text control is not valid. The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, a presentation text object, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, a presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Baseline Print Position parameter is not valid. It might have been specified in any of three places:

• The Absolute Move Baseline (AMB) text-control sequence in a Presentation Text Data (PTX) structured field
• The Page Segment Origin in an Include Page Segment (IPS) structured field
• The Baseline Position parameter in a Line Descriptor (LND) structured field

The PTX or IPS structured field might be in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data. The LND structured field is in the page definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the position parameter in the appropriate structured field. If the structured field has no errors, the error might be a PSF or printer logic error. If you were printing MO:DCA data, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If you were printing a data set containing line data by using a page definition that you created, correct the position parameter in the LND structured field. If the LND structured field has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data by using a page definition that you created with a program, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the position parameter in the appropriate structured field. If the structured field has no errors, the error might be a PSF or printer logic error.

For the valid values of the Baseline Position parameter in the appropriate structured field, see Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884. Ensure that the AMB (Absolute Move Baseline) text control fits within the logical page size as defined by the Load Page Descriptor (LPD) command in the page definition.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Inline Position parameter is not valid. It might have been specified in any of three places:

• The Absolute Move Inline (AMI) text-control sequence in a Presentation Text Data (PTX) structured field
• The Page Segment Origin in an Include Page Segment (IPS) structured field
• The Inline Position parameter in a Line Descriptor (LND) structured field

The PTX or IPS structured field might be in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data. The LND structured field is in the page definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the position parameter in the appropriate structured field. If the structured field has no errors, the error might be a PSF or printer logic error. If you were printing MO:DCA data, an overlay, or a page segment, and you used a program to create the structured fields in the object containing the error, consult your system programmer.

If you were printing a data set containing line data using a page definition that you created, correct the position parameter in the LND structured field. If the LND structured field has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data by using a page definition that you created with a program, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the position parameter in the appropriate structured field. If the structured field has no errors, the error might be a PSF or printer logic error.

For the valid values of the Inline Position parameter in the appropriate structured field. see Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884. Ensure that the AMI (Absolute Move Inline) text control fits within the logical page size as defined by the Load Page Descriptor (LPD) command in the page definition.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Inline Print Position Move parameter value is not valid in the Relative Move Inline (RMI) text control. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Baseline Print Position Move parameter in the Relative Move Baseline (RMB) text-control sequence is not valid. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, correct the text-control sequence in the PTX structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA data set, an overlay, or a page segment, consult your system programmer.

If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error.

If you were printing a data set containing line data by using a page definition, and you created the structured fields for the page definition, specify a valid value for the text orientation parameter in the Line Descriptor (LND) structured field, or specify a font that can be printed in the original text orientation. If you used a program to create the structured fields for the page definition, consult your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The length of the Text String parameter in the Repeat String (RPS) text control is outside the valid range. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

While an index for the font was being loaded into the printer, incorrect data was detected. When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The uniform or maximum baseline offset value in a Font Orientation (FNO) structured field is not valid or is unsupported.
2. The uniform or maximum character increment value in an FNO structured field is not valid or is unsupported.
3. The maximum baseline extent value in an FNO structured field is not valid or is unsupported.
4. The uniform or minimum A-space value in an FNO structured field is not valid or is unsupported.
5. The space character increment value in an FNO structured field is not valid or is unsupported.
6. A pattern index value (FNMCnt) in a Font Index (FNI) structured field refers to a nonexistent pattern.
7. A character increment value in an FNI structured field is not valid or is unsupported.
8. An A-space value in an FNI structured field is not valid or is unsupported.
9. A baseline-offset value in an FNI structured field is not valid or is unsupported.
10. A parameter value specified for an individual character is greater than or less than the respective maximum or minimum value specified for that parameter.
11. The combination of baseline offset (FNI) and pattern size for a character is incompatible with the baseline-extent value (FNO) specified.
12. The underscore width value in a Font Position (FNP) structured field is not valid.
13. One or more orientation flags in an FNO structured field for a section from X'45' to X'FE' is not uniform. These sections must have a uniform A-space, uniform baseline offset, and uniform character increment.

The CPC and CPI structured fields are in the code page, but the FNI and FNO structured fields are in the font character set. This message is accompanied by a message that presents the printer sense bytes. These sense bytes are unique to each printer. See the printer publications for the printer that reported this error.

PSF stops processing and printing the data set that uses the font containing the error.

If you created the structured fields for the font or code page, check each of the parameters in each of the structured fields. For more information on the correct format of the referenced structured fields, see Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285. If the structured fields have no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the font or code page, consult your system programmer.

If an IBM licensed program was used to create the structured field for the font or the code page with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The section identifier value in the Coded Font Index (CFI) structured field is nonzero for a single-byte coded font.
2. The section identifier value in a repeating group in the CFI structured field is not in the range X'41' through X'FE' for a double-byte coded font.
3. The section identifier value in a repeating group in the CFI structured field does not match that of any previously loaded section for that font (possible logic error).

The CFI structured field is in the coded font.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a printer logic error or a PSF error. If you used a program to create the structured fields for the font, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Customization for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 2, 3, 8, 13, 17.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The color space field value in a Color Specification (X'4E') triplet is not valid or is unsupported.
2. The color space field value in a Set Extended Text Color (SEC) control sequence is not valid or is unsupported.
3. The color space field value in a Set Process Color (GSPCOL) drawing order is not valid or is unsupported.

The X'4E' triplet might have occurred on these structured fields:

• A Page Descriptor (PGD).
• An Object Area Descriptor (OBD).
• Include Object (IOB)

The PGD is contained in an Active Environment Group (AEG) for a page or an overlay, and the OBD is contained in an Object Environment Group (OEG) for a graphics, image, bar code, or presentation text object, or an object container. The IOB structured field can be contained in a page definition, overlay, or MO:DCA page, or it can be embedded in line data.

The Set Extended Color control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in MO:DCA data, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The Set Process Color drawing order is located in a Graphics Data (GAD) structured field. The structured field might be contained in MO:DCA data, an overlay, or a page segment; or, it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If the object is in a resource, PSF stops processing the data set that uses the resource in error.

If the structured fields are not valid and you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If the color value is unsupported by this printer, resubmit the print request to a printer that does support this color value.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The size of an image cell or image block in the X-dimension is less than the minimum allowed. The size might be specified in the X-dimension subparameter of these:

• The Image Cell Size parameter in the Image Cell Position (ICP) structured field
• The Image Size parameter in the Image Input Descriptor (IID) structured field

The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The size of an image block or image cell in the X-dimension is greater than the maximum allowed. The size might be specified in the X-dimension subparameter of these:

• The Image Cell Size parameter in the Image Cell Position (ICP) structured field
• The Image Size parameter in the Image Input Descriptor (IID) structured field

The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the printer does not support Image Object Content Architecture (IOCA), PSF might have converted your IOCA image to an IM1 image. In this case, the IDD structured field contains an image X-dimension that is larger than the maximum allowed.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The size of an image cell or image block in the Y-dimension is less than the minimum allowed. The size might be specified in the Y-dimension subparameter of these:

• The Image Cell Size parameter in the Image Cell Position (ICP) structured field
• The Image Size parameter in the Image Input Descriptor (IID) structured field
• The Fill Rectangle Size parameter in the Image Cell Position (ICP) structured field

The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the printer does not support Image Object Content Architecture (IOCA), PSF might have converted your IOCA image to an IM1 image. In this case, the IOCA image size is specified in the IDD structured field. This value is less than the minimum allowed.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The size of an image cell or image block in the Y-dimension is greater than the maximum allowed. The size might be specified in the Y-dimension subparameter of these:

• The Image Cell Size parameter in the Image Cell Position (ICP) structured field
• The Image Size parameter in the Image Input Descriptor (IID) structured field

The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the printer does not support Image Object Content Architecture (IOCA), PSF might have converted your IOCA image to an IM1 image. In this case, the IDD structured field contains an image Y-dimension that is larger than the maximum allowed.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

A finishing operation was requested for a collection of sheets, but the number of sheets was too large or too small for the operation.

Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map.

Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition.

When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and marks the data set. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT was specified on the OUTPUT statement.

When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:

• If the printer supports the PFC Finishing Fidelity triplet and if the REPORT field is set to REPORT (X'01'), the printer reports this exception. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer supports the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer does not report this error to PSF but takes its continuation action and continues processing the page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to DO NOT REPORT (X'02'), the printer reports this exception but PSF does not issue the error message. The printer takes its continuation action for the page and PSF continues processing the data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.
• If the printer does not support the PFC Finishing Fidelity triplet and the REPORT field is set to REPORT (X'01'), the printer reports this exception and PSF issues the error message. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. The finishing operation is not applied or is applied incompletely. If the page in error contains any positioning errors, then print-error markers might be included on the printed page.

If the output is not acceptable:

• Verify that you have requested the appropriate form definition for the finishing operation intended.
• Submit the print request to a printer that can perform the finishing operation.
• If errors caused message pages to be added to the output or caused pages to be skipped, fix those errors so the correct number of pages is printed.

If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 13, 15c, 17, 19.

Paper in the post processor was discarded. The printer detected and reported an asynchronous intervention-required error with an action code of X'0A' (sense byte 2). For more information about this error, see the printer publications for the printer than reported this error.

PSF resends pages to the printer starting from the jam recovery page counter. Pages might be duplicated during recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

See the operator's guide for the printer that reported this error and clear the paper from the printer and post processor. 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 page counters do need to be reprinted, use the JES BACKSPACE command.

Items 1, 8, 18.

The Inline Direction Component of the Orientation parameter in an Input Output Control (IOC) structured field is not valid. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the printer does not support Image Object Content Architecture (IOCA), PSF might have converted your IOCA image to an IM1 image. In this case, the incorrect value is in the OBP structured field.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Baseline Direction Component of the Orientation parameter in an Input Output Control (IOC) structured field is not valid. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field.

If the printer does not support Image Object Content Architecture (IOCA), PSF might have converted your IOCA image to an IM1 image. In this case, the incorrect value is in the OBP structured field.

If the image is in a page, the printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues the processing of the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action. If the image is in a resource, PSF stops processing the data set that uses the resource in error.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

Either the X-Position parameter in the Image Cell Position (ICP) structured field or the Horizontal Coordinate parameter in the Image Output Control (IOC) structured field is within the valid range, but is greater than the Horizontal Page Size parameter in the Page Descriptor (PGD) structured field. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field. The PGD structured field is in the MO:DCA data, the overlay, or a page definition.

For a Begin Image Block (BIM) structured field in a line-data page, the offset is relative to the current print position before the image. For a BIM structured field in the MO:DCA data, the offset is relative to the page origin. For a BIM structured field included in a page segment, the offset is relative to the page segment origin.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data or an overlay, and you created the structured fields in the object containing the error, change the page size in the print data set or an overlay. If you were printing MO:DCA data or an overlay, and you used a program to create the structured fields in the object containing the error, change your input to that program to increase the page size in the print data set or the overlay. If you were printing a data set containing line data, change the page size in the page definition.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

Either the Y-Position parameter in an Image Cell Position (ICP) structured field or the Vertical Coordinate parameter in an Image Output Control (IOC) structured field is within the valid range, but is greater than the Vertical Page Size parameter in the Page Descriptor (PGD) structured field. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field. The PGD structured field is in MO:DCA data, an overlay, or a page definition.

For a Begin Image Block (BIM) structured field in a line-data page, the offset is relative to the current print position before the image. For a BIM structured field in the MO:DCA data, the offset is relative to the page origin. For a BIM structured field included in a page segment, the offset is relative to the page segment origin.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing MO:DCA data or an overlay, and you created the structured fields in the object containing the error, change the page size in the print data set or the overlay. If you were printing MO:DCA data or an overlay, and you used a program to create the structured fields in the object containing the error, change your input to that program to increase the page size in the print data set or an overlay. If you were printing a data set containing line data, change the page size in the page definition.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected and reported that the cancel button on the printer control panel was pressed while the printer was processing a data set.

PSF causes the printer to discard the printer's buffered data. Then, if the stacked page counter is greater than zero, PSF cancels the data set at the stacked page counter plus 1. Otherwise, PSF cancels the data set at the stacked page counter.

If wanted, resubmit the print request that was canceled. If the error condition persists, consult the operator to see why the cancel button is being pressed.

No response is necessary.

No response is necessary.

Items 1, 2, 17, 27.

This error is a result of either too many items (for example, images) being placed on a page, or too many overstrikes being requested. The printer detected and reported an I/O error with an action code of X'09' (sense byte 2). This message is accompanied by a message that presents the printer sense bytes.

When the print error is detected, the printer attempts to print at least part of the page containing the error. PSF causes the printer to discard the printer's buffered data. PSF then stops processing the data set at the stacked page counter plus 1.

Remove one or more resources from the page, and resubmit the print request.

No response is necessary.

No response is necessary.

Items 1, 2, 17, 27.

The magnet settings of the cassette were not the same at the time the page was printed as they were when the page was formatted on the printer. The printer detected and reported an asynchronous error with an action code of X'23' (sense byte 2).

PSF causes the printer to discard the printer's buffered data. PSF resends pages to the printer, starting from the stacked page counter plus 1. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. PSF also prints this message at the end of the data set to indicate that this message was printed within the data set.

Check your output for duplicate pages. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 2, 8, 18.

The serializer card in the printer generated an incorrect parity. The printer detected and reported an asynchronous error with an action code of X'23' (sense byte 2). This is a temporary hardware error.

PSF causes the printer to discard the printer's buffered data. PSF resends pages to the printer, starting from the stacked page counter plus 1. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. PSF also prints this message at the end of the data set to indicate that this message was printed within the data set.

Check your output for duplicate pages. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 2, 8, 18.

Either the X-Position parameter in an Image Cell Position (ICP) structured field or a Horizontal Coordinate parameter in an Image Output Control (IOC) structured field is outside the valid range. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field. If the image is part of a page segment, an overlay, or MO:DCA data, the image block origin is described as a displacement from the origin of the page segment, overlay, or MO:DCA data page. If the image is part of a line-data page, the image block origin is described as a displacement from the current Line Descriptor (LND) structured field. The LND structured field is contained in the page definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

Either the Y-Position parameter in an Image Cell Position (ICP) structured field or a Vertical Coordinate parameter in an Image Output Control (IOC) structured field is outside the valid range. The image block or image cell might be contained in an overlay, a page segment, or a MO:DCA document. It might also be embedded in a data set containing line data by using a Begin Image (BIM) structured field. If the image is part of a page segment, an overlay, or a MO:DCA data page, the image block origin is described as a displacement from the origin of the page segment, overlay, or MO:DCA data page. If the image is part of a line-data page, the image block origin is described as a displacement from the current Line Descriptor (LND) structured field. The LND structured field is contained in the page definition.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you created the structured fields for the resource or print data set containing the image, correct the error in the referenced structured field and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the resource or print data set containing the image, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The printer detected and reported an asynchronous error with an action code of X'23' (sense byte 2). This is a temporary hardware error. For more information about this error, see the printer publications for the printer that reported this error.

PSF causes the printer to discard the printer's buffered data. PSF resends pages to the printer, starting from the stacked page counter plus 1. PSF prints this message on a separate sheet in the data set to mark the position where the recovery from this error was started. PSF also prints this message at the end of the data set to indicate that this message was printed within the data set.

Check your output for duplicate pages. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

No response is necessary.

Items 1, 2, 8, 18.

An attempt was made to print outside the valid printable area. This area is the intersection (common space) of the physical page with the logical page or with an overlay. Characters, rules, or image cells fall at least partially outside of the valid printable area. Note that a data-stream image might consist of a number of image cells, and each cell is sent to the printer as one image.

Characters and images that were not defined completely within the valid printable area are not printed. Rules are printed up to the area boundary. The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

Ensure that the correct form was loaded in the printer. If it was, and if your printed output would be acceptable without the print-error markers, you can resubmit the print request, specifying BLOCK or BLKPOS for the DATACK keyword on the OUTPUT JCL statement.

If you want to correct the source of the problem, you could change the size of the logical page. If you want the logical page size to remain the same and if you were printing MO:DCA data, an overlay, or a page segment, and you created the structured fields in the object containing the error, check the print positioning values in the text-control sequence in the Presentation Text Data (PTX) structured field for positioning outside of the page.

If you were printing an image, coordinate the image dimensions with the logical page size.

If you were printing a data set containing line data, and you were using a page definition that you created, check the print-positioning values in the Line Descriptor (LND) structured field.

If you were printing a data set containing line data with embedded structured fields, check the PTX structured field for positioning outside of the page.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:

1. The suppression ID in a Load Copy Control (LCC) command is not valid or is unsupported (possible logic error).
2. The Begin Suppression (BSU) suppression ID in a text-control sequence is not valid or is unsupported.

The text-control sequence is located in a Presentation Text Data (PTX) structured field or was generated by PSF from a page definition. The PTX structured field might be contained in a MO:DCA document, a presentation text object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, a presentation text object, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, a presentation text object, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The Length parameter in a Repeat String (RPS) text control was nonzero, but the Text String parameter had zero length. The RPS text control is in a Presentation Text Data (PTX) structured field. The Presentation Text Data (PTX) structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document or an overlay, and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a MO:DCA document or an overlay, and you used a program to create its structured fields, contact your system programmer. If you were printing a MO:DCA document containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

In the Code Page Index (CPI) or Code Page Control (CPC) structured fields, an incorrect flag combination was specified for a character of a double-byte font. The CPC and CPI structured fields are in the code page.

PSF stops processing and printing the data set that uses the font containing the error.

If you created the structured fields for the code page, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the code page, contact your system programmer.

If an IBM licensed program was used to create the structured fields for the code page with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference, AFPC-0004 and PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The meaning of this message depends on the printer. For all printers except the 3800 printers, the sum of the Y-Origin parameter in the Page Position (PGP) structured field and the Vertical Page Size parameter in the Page Descriptor (PGD) structured field should not exceed the addressability limit of the printer. Nor should the sum of the X-Origin parameter in the PGP structured field and the Horizontal Page Size parameter in the PGD structured field exceed the addressability limit of the printer. The PGD structured field is in the MO:DCA data, an overlay, or a page definition. The PGP structured field is in the form definition.

For the 3800 printers, the sum of the Y-Origin parameter in the Page Position (PGP) structured field and the Vertical Page Size parameter in the Page Descriptor (PGD) structured field should not exceed the maximum Y values of the following paper sizes. Nor should the sum of the X-Origin parameter in the PGP structured field and the Horizontal Page Size parameter in the PGD structured field exceed the maximum X values of the following paper sizes. The PGD structured field is in the MO:DCA data, an overlay, or a page definition. The PGP structured field is in the form definition.

Common paper sizes:

X-dimension

3330

Y-dimension

2640

ISO paper sizes:

X-dimension

3330

Y-dimension

2880

Additional ISO paper sizes:

X-dimension

3330

Y-dimension

3000

These values represent the maximum common and maximum ISO paper sizes For more information about the maximum X- and Y-dimensions of other paper sizes, see IBM 3800 Printing Subsystem Models 3, 6, and 8 Operator's Guide.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

Ensure that the correct form was loaded in the printer. If it was, and you were printing MO:DCA data or an overlay and you created the structured fields in the object containing the error, change the page size in the print data set or an overlay. You could also change the page origin in the form definition.

If you were printing MO:DCA data or an overlay, and you used a program to create the structured fields in the object containing the error, change your input to that program to reduce the page size in the print data set or overlay. You could also change the page origin in the form definition.

If you were printing a data set containing line data, change the page position in the page definition, or change the page origin in the form definition.

If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

The physical page requires the accumulator. The page size of the form loaded in the printer is too large for the accumulator.

PSF causes the printer to discard the printer's buffered data and to delete all overlays, page segments, and fonts. On the first occurrence of this error, the message is printed on a separate sheet in the data set to mark the position before recovery starts. PSF recovers by resending pages to the printer, starting from the last known committed page counter plus 1. On the second occurrence of this error, the message is printed at the end of the message data set, and PSF stops processing the data set at the committed page counter plus 1.

Request a smaller page size, and ensure that the print request is routed to the appropriate output class. Otherwise, run the print request on a printer with a different size accumulator, if available. If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

Items 1, 2, 17, 27.

The paper in the printer was jammed. The printer detected and reported an asynchronous intervention-required error with an action code of X'08' (sense byte 2). For more information about this error, see the printer publications for the printer that reported this error.

PSF resends pages to the printer starting from the jam recovery page counter plus 1. PSF might print message APS711I on a separate sheet in the data set to mark the position where the recovery from this error was started. Pages might be duplicated during the recovery. If repositioning is not supported in the current environment, PSF stops processing the data set.

The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request If the error condition persists, consult your system programmer.

If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

See the operator's guide for the printer that reported this error and clear the paper jam in the printer. PSF assumes that pages between the jam recovery page counter and the stacked page counter are not damaged by the paper jam and do not need to be reprinted. If any pages between these two page counters do need to be reprinted, use the JES BACKSPACE command.

Items 1, 8, 18.

An equipment check at print time indicated that either a strip-buffer overrun or an insufficient accumulator storage condition (includes the condition of no accumulator installed) occurred. The page at the committed page counter was too complex to print; therefore, the page was skipped. The printer detected and reported an asynchronous error with an action code of X'09' (sense-byte 2).

PSF resends pages to the printer starting from the committed page counter plus 2 in order to skip the page that was too complex to print. PSF prints this message on a separate sheet in the data set to mark the position at which the recovery from this error was started. PSF also prints this message at the end of the data set to indicate that this message was printed within the data set. If repositioning is not supported in the current environment, PSF stops processing the data set.

Remove some of the resources on the page (for example, overlays, images, fonts, or page segments), or remove some of the data from the page, and resubmit the print request.

No response is necessary.

No response is necessary.

Items 1, 2, 17, 27.

The Length parameter in a Repeat String (RPS) text control is not valid. The text-control sequence is located in a Presentation Text Data (PTX) structured field. The structured field might be contained in a MO:DCA document, an overlay, or a page segment; or it might be embedded in a data set containing line data.

The printer you were using might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, then print-error markers might be included on the printed page. PSF continues processing the current data set with the page following the page in error, unless the printer reported another error that required a more severe PSF recovery action.

If you were printing a MO:DCA document, an overlay, or a page segment and you created the structured fields in the object containing the error, correct the text-control sequence in the Presentation Text Data (PTX) structured field. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the MO:DCA document, overlay, or page segment, contact your system programmer. If you were printing a data set containing line data with embedded structured fields, correct the text-control sequence in the PTX structured field. If the PTX has no errors, the error might be a PSF or printer logic error. If you were printing a data set containing line data without embedded structured fields, the error might be a PSF or printer logic error.

If an IBM licensed program was used to create the structured fields for the print data set or the resource with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page or the message data set in the PSF startup procedure. Inform your system programmer.

Items 1, 2, 17, 27.

Not enough writable-control storage (WCS) or raster-pattern storage (RPS) was available to complete the page. This message was issued to indicate that multiple resources in the printer have used all of the WCS or RPS storage, and the data set was printed with the accumulator feature. The complexity of the page or resources from previous pages or data sets might be causing the printer to run slower than usual.

The printer prints the page containing the error by using the accumulator. If the page contains any position errors, the print-error markers are printed on the page containing the error. PSF attempts to free some of the printer storage by deleting all overlays in the printer, all page segments in the printer, or all resources in the printer. The page that caused this error to be reported has already been printed; so PSF continues processing the current data set with the page after the page containing the error.

If repositioning is not supported in the current environment, the channel program is re-driven on the next channel command.

If the printed output is not acceptable, make the page less complicated by deleting resources (for example overlays, page segments, and fonts), or print the data set on a printer with more of the type of storage that was exceeded. If greater throughput is wanted, you could remove some of the resources used for the data set to reduce the page complexity. If the problem persists, notify your system programmer.

If the printer throughput is unacceptable, consider acquiring additional printer storage, if possible.

If the problem persists, notify your system programmer of this error.

Items 1, 2, 17, 27.