APS2600 to APS5999

APS2600I

THE ERROR SENSE BYTES 0-5 = error sense bytes 0-5, IPDS COMMAND IN PROCESS = ipds command, UP3I-SPECIFIC ERROR CODE = error code, UP3I PAPER SEQUENCE ID OF THE DEVICE = paper sequence id, UP3I-SPECIFIC INFORMATION = up3i-specific information, BYTE 19 = error sense byte 19, PAGE IDENTIFIER = page id.

Explanation:

This message formats and presents the 24 printer sense bytes that were reported to PSF at the time of an I/O error from a Universal Printer Pre- and Postprocessing Interface (UP3I)-controlled device attached to the printer. A message that describes the specific I/O error accompanies this message. The message contains this information:

Error sense bytes 0-5 are the first 6 bytes in the sense data, reported in hexadecimal.
IPDS command is the 2-byte hexadecimal code for the IPDS command that was in process at the time the error occurred. This information was formatted from bytes 6 and 7 of the sense data. A value of X'0000' indicates that the error was not associated with any particular IPDS command.
Error code is the UP3I-specific error code. See the UP3I specification at http://www.up3i.org for a description of the error codes. This information was formatted from bytes 8 and 9 of the sense data.
Paper sequence id is the UP3I paper sequence ID of the device that caused the error. This information was formatted from byte 10 of the sense data.
UP3I-specific information: see the UP3I specification at http://www.up3i.org for a description of the content of these bytes. This information was formatted from bytes 11 - 18 of the sense data.
Error sense byte 19 is the third byte of the 3-byte exception ID; together with sense byte 1, it defines the specific exception within an exception class.

Note:

The error sense is written as Byte 0 Byte 1... Byte 19.
Page id is the page ID from the Begin Page command if the error is associated with a particular page. It is reported in hexadecimal.

System action:

See the accompanying messages for the system action taken.

User response:

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

System programmer response:

To determine an appropriate response, see the specific error conditions described in the accompanying messages. For more information about printer sense bytes and the specific error, see the UP3I-controlled device publications for the printer that reported this error.

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized or cannot print a separator page or an error message. Notify your system programmer.

Problem determination:

Items 2, 17, 27.

APS2601I

MICR PRINTING WAS REQUESTED, BUT IS NOT AVAILABLE.

Explanation:

Magnetic ink character recognition (MICR) printing is requested when the Presentation Text Data (PTX) structured field or the Graphics Data (GAD) structured field uses a font that supports MICR. 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:

A string of text is encountered that is to be printed with a MICR font, but MICR printing is not available for this text string.
Some printers can print MICR text on one side of the media, but not on the other side; in this case, text data to be printed with a MICR font that is placed on the non-MICR side of the media causes this exception to occur.
Some printers can print MICR text only in specific colors, usually black or a specific highlight color.
Some printers allow MICR printing to be disabled (even after a MICR font has been activated).

System action:

PSF cannot print the current data set. PSF stops processing and printing the data set. PSF issues additional messages identifying the processing environment in which the error occurred. 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.

User response:

If you do not want MICR printing, change the PTX or GAD structured field to not use MICR fonts. If you do want MICR printing, change the data stream to request MICR printing on the supported side, send the job to a different printer that prints MICR on the requested side, or reconfigure this printer to print MICR on the requested side.

System programmer response:

No response is necessary.

Operator response:

No response is necessary.

Problem determination:

Items 1, 2, 3, 8, 13.

APS2602I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT SUPPORTED: THE IMAGE RESOLUTION FOR A PRESENTATION OBJECT CONTAINER RESOURCE SPECIFIED A UNIT BASE THAT THE PRINTER DOES NOT SUPPORT.

Explanation:

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:

The X unit base value in an Image Resolution (X'9A') triplet is not valid or is unsupported.
The Y unit base value in an Image Resolution (X'9A') triplet is not valid or is unsupported.
The Y unit base value in an Image Resolution (X'9A') triplet is not identical to the X unit base value.

Image resolution is specified with the X'9A' triplet on the Container Data Descriptor (CDD), Include Object (IOB), or Preprocess Presentation Object (PPO) structured fields.

The CDD structured field is specified inside the presentation object container resource. The IOB structured field can be contained in a page definition, an overlay, or a MO:DCA page, or it can be embedded in line data. The PPO structured field is specified in the Resource Environment Group (REG) for the print data set.

System action:

The printer you were using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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 reports another error that requires a more severe PSF recovery action.

User response:

If you created the structured fields for the data object resource, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 or 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 data object resource, contact your system programmer.

System programmer response:

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 the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

Operator response:

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.

Problem determination:

Items 1, 2, 17, 27.

APS2603I

DATA FOR A RESOURCE IS NOT COMPLETE: THE IMAGE RESOLUTION FOR A PRESENTATION OBJECT IS NEEDED BUT IS NOT SPECIFIED. THE IMAGE IS PRINTED USING THE PRINTER'S RESOLUTION.

Explanation:

The image resolution for a presentation object (such as a GIF, JPEG, PNG, or TIFF, image) is needed to process the object, but the resolution was not provided within the presentation object and was not provided by an Image Resolution (X'9A') triplet.

Image resolution is specified with the X'9A' triplet on the Container Data Descriptor (CDD), Include Object (IOB), or Preprocess Presentation Object (PPO) structured fields.

System action:

The printer uses the printer's resolution to print the image. If the page in error contains any positioning errors, 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 reports another error that requires a more severe PSF recovery action.

User response:

System programmer response:

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 the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2604I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE FONT LOCAL IDENTIFIER FOR A MAPPED FONT IS OUTSIDE THE SUPPORTED RANGE FOR THE PRINTER.

Explanation:

A font local identifier is outside the supported range for the printer. The font local identifier is specified in:

The Map Coded Font Format 2 (MCF-2) structured field in the Resource Local Identifier Triplet (X'24').
The Map Data Resource (MDR) structured field in the Fully Qualified Name Triplet (X'02') with FQNType X'BE' for Data Object fonts.

The MCF-2 and MDR structured fields might be contained in a MO:DCA document, an overlay, or a page definition.

System action:

User response:

If you were printing MO:DCA data or an overlay and you created the structured field in error, make sure the font local identifier that you have specified is supported by your printer. If you used a program to create the structured fields in the object containing the error, contact your system programmer.

If you were printing a data set containing line data and you were using a page definition that you created, ensure that the font local identifier specified in the MCF-2 or MDR structured field is within the supported range for your printer. If the font local identifier is within the supported range for the printer, this is a printer logic error. If the font local identifier is outside the supported range for the printer, either change the font local identifier so it is within the supported range or route your job to a printer that supports your font local identifier value.

See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured fields.

System programmer response:

If an IBM licensed program was used to create the structured fields for the print data set or 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.

Operator response:

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

Problem determination:

Items 1, 2, 17, 27.

APS2605I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE SYMBOL WIDTH PARAMETER IN THE BAR CODE IS NOT VALID.

Explanation:

A bar code is specified as a bar code object or in a page definition; however, the value of the symbol width parameter is not valid. The location of the parameter depends on how the bar code is specified:

If the bar code is specified as a bar code object, the Symbol width parameter in a Bar Code Symbol Descriptor (BSD) structured field is not valid. The bar code object might be contained in a MO:DCA document or in an overlay.
If the bar code is specified with the BARCODE subcommand in a page definition, the WIDTH parameter on the BARCODE subcommand is not valid. The bar code object might be associated with a data set that contains line data.

System action:

The printer you are using might try to print the page in error, but the entire page might not be printed. If the page in error contains any positioning errors, 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 reports another error that requires a more severe PSF recovery action.

User response:

If you created the structured fields for the bar code object or the page definition, correct the error and resubmit the print request. See Bar Code Object Content Architecture Reference, AFPC-0005 for more information about bar code objects. See Page Printer Formatting Aid: User’s Guide for more information about creating page definitions. If the structured field or page definition 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 bar code object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

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.

Problem determination:

Items 2, 3, 8, 13, 17.

APS2606I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE SYMBOL WIDTH PARAMETER IN THE BAR CODE IS TOO SMALL.

Explanation:

A bar code is specified as a bar code object or in a page definition; however, the value of the symbol width parameter is too small to generate a bar code symbol. The location of the parameter depends on how the bar code is specified:

If the bar code is specified as a bar code object, the Symbol width parameter in a Bar Code Symbol Descriptor (BSD) structured field is too small. The bar code object might be contained in a MO:DCA document or in an overlay.
If the bar code is specified with the BARCODE subcommand in a page definition, the WIDTH parameter on the BARCODE subcommand is too small. The bar code object might be associated with a data set that contains line data.

System action:

User response:

In the accompanying formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the smallest valid symbol size measured in twips.

Note:

A twip is a unit of measure equal to 1/20 of a point. There are 1440 twips in 1 inch.

If you used a program to create the structured fields for the bar code object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2607A

THE PRINTER HAS RESPONDED WITH AN ACTION CODE X'4D' SENSE CODE. PSF CANNOT COMMUNICATE WITH THIS CHANNEL DEVICE UNTIL OPERATOR RECOVERY IS PERFORMED.

Explanation:

The PSF error recovery procedure (ERP) was unable to recover from a channel error reported from the device. Communication with the device is not possible. See the accompanying APS717I message for the specific sense code reported by the printer.

System action:

PSF processing ends abnormally.

User response:

No response is necessary.

System programmer response:

See the information provided in the Operator Response section.

Operator response:

PSF ended processing because it could not communicate with the device. For more information, check for the presence of an IOS permanent error message, such as IOS000I with Equipment Check (EQC). Try VARYING the device OFFLINE and back ONLINE. It might be necessary to turn the printer power off and then back on. You must restart the printer with regular JES commands after the device is successfully brought back ONLINE. If the device fails to become READY, contact your IBM service representative.

Use the MVS™ K E,nn command to delete this message from the console display. See z/OS MVS System Commands.

Problem determination:

Items 1, 9, 18.

APS2608I

THE FULLY QUALIFIED NAME IN AN FQN (X'02') TRIPLET IS NOT VALID.

Explanation:

The FQN Format value is X'00' and the FQN value is not a valid UTF-16BE-encoded string.
The FQN Format value is X'00' and the FQN value is not a valid character-encoded string. When the FQN is for a TrueType and OpenType font, the string must be encoded with UTF-16BE. When the FQN is for an object name, the string must be encoded with UTF-16BE unless there is a preceding Coded Graphic Character Set Global Identifier (X'01') triplet.

The Fully Qualified Name (FQName) in an FQN (X'02') triplet is specified on a Map Data Resource (MDR) structured field. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

The printer might try to print the page with the error. The entire page might not be printed. If the page with the 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.

User response:

If you created the data for the FQN triplet, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the contents of the FQN triplet. If the data has no error, the error might be a printer logic error or a PSF error. If you used a program to create the data for the FQN triplet, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the data for the FQN triplet 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.

Operator response:

Problem determination:

Items 2, 3, 17, 18.

APS2611I

THE TRUETYPE OR OPENTYPE COLLECTION FONT INDEX VALUE FOR A LINKED FONT IS NOT VALID.

Explanation:

An index value specified in a TrueType or OpenType Collection Font Index table vector (X'1A') does not correspond to any TrueType or OpenType font in the collection. The TrueType/OpenType Collection Font Index table vector (X'1A') is in the resource access table (RAT), which is installed on a system by a product such as InfoPrint AFP Resource Installer.

System action:

PSF stops processing and printing the data set.

User response:

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

System programmer response:

If an IBM licensed program was used to create the table vectors for the RAT with the error, verify that the input to that program was valid. If the input was valid, see Mixed Object Document Content Architecture Reference for assistance in determining the source of the problem.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2612I

A FULL FONT NAME USED TO IDENTIFY A PARTICULAR LINKED TRUETYPE OR OPENTYPE FONT WITHIN THE COLLECTION IS NOT VALID.

Explanation:

The fully qualified name in the Fully Qualified Name triplet (X'02') with FQNType X'6E' in the Begin Resource (BRS, also called BR) structured field is not valid. There is no TrueType or OpenType font in the collection for this full font name. The BRS structured field is found in a print-file level resource group.

System action:

PSF stops processing and printing the data set.

User response:

If you created the structured fields for the BRS, 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 printer logic error or a PSF error. If you used a program to create the structured fields for the BRS, contact your system programmer.

System programmer response:

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

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2613I

THE FONT TECHNOLOGY VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The font-technology value specified in a Data-Object Font Descriptor (X'8B') triplet is not valid.
The font technology specified in a Data-Object Font Descriptor (X'8B') triplet does not match the actual technology of the font.

The Data-Object Font Descriptor triplet is on a Map Data Resource (MDR) structured field. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

PSF stops processing and printing the data set.

User response:

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

System programmer response:

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

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2614I

THE VERTICAL FONT SIZE VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The vertical font size in a Data Object Font Descriptor triplet (X'8B') on a Map Data Resource (MDR) structured field is not valid. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

PSF stops processing and printing the data set.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2615I

THE HORIZONTAL SCALE FACTOR VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The horizontal scale factor in a Data Object Font Descriptor triplet (X'8B') on a Map Data Resource (MDR) structured field is not valid. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

PSF stops processing and printing the data set.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2616I

THE CHARACTER ROTATION VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The character rotation value in a Data Object Font Descriptor triplet (X'8B') on a Map Data Resource (MDR) structured field is not valid. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

PSF stops processing and printing the data set.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2617I

THE ENCODING ENVIRONMENT VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The encoding environment value specified in a Data-Object Font Descriptor (X'8B') triplet is not valid.
The encoding environment value specified in a Data-Object Font Descriptor (X'8B') triplet cannot be used with the specified font technology.

System action:

PSF stops processing and printing the data set.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2618I

THE ENVIRONMENT-SPECIFIC ENCODING IDENTIFIER VALUE IN A DATA OBJECT FONT DESCRIPTOR TRIPLET (X'8B') IS NOT VALID.

Explanation:

The environment-specific encoding identifier value in a Data Object Font Descriptor triplet (X'8B') on a Map Data Resource (MDR) structured field is not valid. The MDR can be found in a Resource Environment Group (REG) for a document or for a group of pages in a document or in the Active Environment Group (AEG) of the page or overlay.

System action:

PSF stops processing and printing the data set.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2619I

THE UNICODE DATA IN A GRAPHICS OBJECT CHARACTER STRING IS NOT VALID.

Explanation:

One of these errors occurred in the Graphics Data (GAD) structured field:

A high-order surrogate code value was not immediately followed by a low-order surrogate code value. The high-order surrogate range is U+D800 through U+DBFF.
A low-order surrogate code value was not immediately preceded by a high-order surrogate code value. The low-order surrogate range is U+DC00 through U+DFFF.
An incorrect UTF-8 byte sequence, as defined in the Unicode specification, was specified.
The UTF-8 error cases are:
- The value in the first byte of the UTF-8 sequence was not in the valid UTF-8 range (X'00'-X'7F' and X'C2'-X'F4').
- The value in the second byte of the UTF-8 sequence was not in the valid UTF-8 range allowed by the first byte. The valid ranges for the second byte are:
  First Byte Second Byte
  X'C2'-X'DF' X'80'-X'BF'
  X'E0' X'A0'-X'BF'
  X'E1'-X'EC' X'80'-X'BF'
  X'ED' X'80'-X'9F'
  X'EE'-X'EF' X'80'-X'BF'
  X'F0' X'90'-X'BF'
  X'F1'-X'F3' X'80'-X'BF'
  X'F4' X'80'-X'8F'
- The value in the third or fourth byte of the UTF-8 sequence was not in the valid UTF-8 range for that byte (X'80'-X'BF').
For a formal definition of UTF-8, see the Unicode specification on the Unicode web page at http://www.unicode.org.

The GAD structured field is contained in a graphics object. The graphics object might be contained in a MO:DCA document or an overlay, or it might be embedded in a data set that contains line data.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the Unicode code value in error, as follows:

When a high-order surrogate code value was not immediately followed by a low-order surrogate code value, bytes 16-17 contain the high-order surrogate code value.
When a low-order surrogate code value was not immediately preceded by a high-order surrogate code value, bytes 16-17 contain the low-order surrogate code value.
When a UTF-8 code value sequence that is not valid was specified, bytes 16-17 contain the first 2 bytes of the UTF-8 code value sequence.

System action:

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.

User response:

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

System programmer response:

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

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2620I

THE UNICODE DATA IN THE PRINT DATA IS NOT VALID.

Explanation:

One of these errors occurred in the Presentation Text (PTX) command data or line data:

A high-order surrogate code value was not immediately followed by a low-order surrogate code value. The high-order surrogate range is U+D800 through U+DBFF.
A low-order surrogate code value was not immediately preceded by a high-order surrogate code value. The low order surrogate range is U+DC00 through U+DFFF.
An incorrect UTF-8 byte sequence, as defined in the Unicode specification, was specified.
The UTF-8 error cases are:
- The value in the first byte of the UTF-8 sequence was not in the valid UTF-8 range (X'00'-X'7F' and X'C2'-X'F4').
- The value in the second byte of the UTF-8 sequence was not in the valid UTF-8 range allowed by the first byte. The valid ranges for the second byte follow:
  First Byte Second Byte
  X'C2'-X'DF' X'80'-X'BF'
  X'E0' X'A0'-X'BF'
  X'E1'-X'EC' X'80'-X'BF'
  X'ED' X'80'-X'9F'
  X'EE'-X'EF' X'80'-X'BF'
  X'F0' X'90'-X'BF'
  X'F1'-X'F3' X'80'-X'BF'
  X'F4' X'80'-X'8F'
- The value in the third or fourth byte of the UTF-8 sequence was not in the valid UTF-8 range for that byte (X'80'-X'BF').
For a formal definition of UTF-8, see the Unicode specification on the Unicode web page at http://www.unicode.org.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the Unicode code value in error, as follows:

When a high-order surrogate code value was not immediately followed by a low-order surrogate code value, bytes 16-17 contain the high-order surrogate code value.
When a low-order surrogate code value was not immediately preceded by a high-order surrogate code value, bytes 16-17 contain the low-order surrogate code value.
When a UTF-8 code value sequence that is not valid was specified, bytes 16-17 contain the first two bytes of the UTF-8 code value sequence.

System action:

Your printer 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.

User response:

If you created the data for the PTX, correct the error and resubmit the print request. See Presentation Text Object Content Architecture Reference, SC31-6803 for more information about the structured field. If the PTX data has no error, the error might be a printer logic error or a PSF error. If you used a program to create the data for the PTX, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the data for the PTX with the error, verify that the input to that program was valid. If the input was valid, see Presentation Text Object Content Architecture Reference, SC31-6803 and PSF for z/OS: Customization for assistance in determining the source of the problem.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2621I

AN UNKNOWN GRAPHIC CHARACTER GLOBAL ID (GCGID) VALUE WAS FOUND WITHIN A CODE PAGE USED WITH A DATA OBJECT FONT.

Explanation:

The printer does not recognize the GCGID found in the code page used with a data object font. One of these conditions has occurred:

The GCGID was not mapped to a Unicode value by the printer's GCGID to Unicode mapping table or by the Unicode extended code page.
The GCGID is defined in a Unicode extended code page that the printer does not support, so the Unicode mapping is not being used by the printer. To see whether your printer supports Unicode extended code pages, display the printer information report and see whether the Sense Type and Model (STM) Loaded-Font Command-Set Vector contains the X'B005' - Extended (Unicode mapping) code page support property pair.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the unknown character's code point. For double-byte code pages, byte 16 contains the section ID and byte 17 contains the second byte of the code point. For single-byte code pages, byte 17 contains the code point.

System action:

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.

User response:

If the GCGID is not defined and you created the data for the code page, correct the error and resubmit the print request. If the GCGID is defined in a Unicode extended code page, verify which printer supports these code pages and submit the print request to a supporting printer. See the Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 for more information about the code page. If the code page has no error, the error might be a printer logic error or a PSF error. If you used a program to create the data for the code page, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the data for the code page with the error, verify that the input to that program was valid. If the input was valid, see the Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 and PSF for z/OS: Customization for assistance in determining the source of the problem.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2622I

RESOURCE resource name COULD NOT BE RASTERIZED BECAUSE AN X-AXIS ORIGIN OR Y-AXIS ORIGIN WAS SPECIFIED THAT THE PRINTER DOES NOT SUPPORT.

Explanation:

An X-axis origin for object content or Y-axis origin for object content that the printer does not support was specified in the Preprocess Presentation Object (PPO) structured field. 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:

A negative XocaOset or YocaOset value was specified in a PPO structured field, but the printer does not support negative offsets.
A valid XocaOset or YocaOset value was specified in a PPO structured field, but the printer does not support that value with the specified units of measure.

The PPO structured field can be specified in a Resource Environment Group (REG) following Map Data Resources (MDRs) and Map Page Overlays (MPOs).

System action:

PSF stops processing the REG and continues processing the data set.

User response:

If you created the structured fields for the PPO, 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 printer logic error or a PSF error. If you used a program to create the structured fields for the PPO contact your system programmer.

System programmer response:

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

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2623I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: CONVERSION VALUE FOR A QR CODE BAR CODE SYMBOL IS NOT VALID OR IS UNSUPPORTED.

Explanation:

The conversion value specified in the Bar Code Symbol Data (BSA) structure in a Bar Code Data (BDA) structured field is not valid or is unsupported.

The BDA structured field is contained in a bar code object. The bar code object might be contained in a MO:DCA document, an overlay, or might be associated with a data set containing line data.

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.

User response:

If you created the structured fields for the bar code object, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 or 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 bar code object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2624I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE VERSION VALUE FOR A QR CODE BAR CODE SYMBOL IS NOT VALID.

Explanation:

The version parameter value specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field is not valid.

The BDA structured field is contained in a bar code object. The bar code object might be contained in a MO:DCA document, an overlay, or might be associated with a data set containing line data.

System action:

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.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2625I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE ERROR-CORRECTION-LEVEL VALUE FOR A QR CODE BAR CODE SYMBOL IS NOT VALID.

Explanation:

The error-correction-level parameter value specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field is not valid.

The BDA structured field is contained in a bar code object. The bar code object might be contained in a MO:DCA document, an overlay, or might be associated with a data set containing line data.

System action:

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.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2626I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: AN INCOMPATIBLE COMBINATION OF SPECIAL-FUNCTION FLAGS WAS SPECIFIED FOR A QR CODE BAR CODE SYMBOL.

Explanation:

An incompatible combination of special-function flags was specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field. Only one of the FNC1 flags can be B'1'.

The BDA structured field is contained in a bar code object. The bar code object might be contained in a MO:DCA document, an overlay, or might be associated with a data set containing line data.

System action:

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.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2627I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE APPLICATION-INDICATOR VALUE FOR A QR CODE BAR CODE SYMBOL IS NOT VALID.

Explanation:

The application-indicator value specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field is not valid.

The BDA structured field is contained in a bar code object. The bar code object might be contained in a MO:DCA document, an overlay, or might be associated with a data set containing line data.

System action:

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.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2628I

INTERVENTION REQUIRED, DEV=pppp, LUNAME=luname.

Explanation:

A condition that requires intervention, such as a paper jam, has occurred on an SNA-attached printer. The message uses these variables to describe the printer:

pppp: is the printer device type; for example, 3816.
luname: specifies the SNA logical unit name of the SNA-attached printer.

System action:

PSF stops processing. When the intervention condition is cleared, this message is deleted and PSF continues processing.

User response:

No response is necessary.

System programmer response:

If you do not want this message to be issued for this printer, set the Exit 7 XTP7IMSG flag to B'0' or set the Issue intervention messages value in the Printer Inventory to NO.

Operator response:

When this message displays on the console, it indicates that there is a condition that requires intervention at an SNA-attached printer. See the operator's guide for the printer that reported this condition, and clear the condition at the printer. If you do not want this message to be issued for this printer, contact your system programmer.

Problem determination:

Items 1, 8, 18.

APS2629I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: DATA IN A UCC/EAN 128, GS1 DATABAR EXPANDED, OR GS1 DATABAR EXPANDED STACKED BAR CODE IS NOT VALID.

Explanation:

If your bar code is specified as a bar code object, the data specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field is not valid.

If your bar code is specified with the BARCODE subcommand in a page definition, the data selected by the START and LENGTH subcommands on the FIELD command is not valid.

One or more of these conditions exists:

FNC1 is not the first data character.
An application identifier (ai) value is not valid.
Data for an ai does not match the ai definition.
Insufficient data, or no data, follows an ai.
There is too much data for an ai.
The FNC1 character is used incorrectly.

The bar code object might be contained in a MO:DCA document or an overlay, or might be associated with a data set that contains line data.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the application ID (ai) value for the bad data. The ai value is read as four decimal digits, with leading zeros if necessary. For example, ai = 01 is shown as X'0001' and ai = 8005 is shown as X'8005' in bytes 16-17.

System action:

The printer might try to print the page in error. The entire page might not be printed. If the page in error contains any positioning errors, 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 reports another error that requires a more severe PSF recovery action

User response:

If you created the structured fields for the bar code object or the page definition, correct the error and resubmit the print request. See the Bar Code Object Content Architecture Reference, AFPC-0005 for more information. If the data 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 bar code object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object with the error, verify that the input to that program is valid. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2630I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE COMBINATION OF ELEMENT HEIGHT AND HEIGHT MULTIPLIER VALUES FOR A GS1 DATABAR BAR CODE IS NOT VALID FOR THE MODIFIER SELECTED.

Explanation:

If the bar code is specified as a bar code object, the combination of element height and height multiplier values specified in the Bar Code Symbol Data (BSA) data structure in a Bar Code Data (BDA) structured field is not valid for the modifier selected.

If the bar code is specified with the BARCODE subcommand in a page definition, the value specified for the HEIGHT subcommand on the FIELD command is not valid.

The bar code object might be contained in a MO:DCA document or an overlay, or might be associated with a data set that contains line data.

System action:

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

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2633I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE LENGTH VALUE IN THE CMR HEADER FOR A COLOR MANAGEMENT RESOURCE IS NOT VALID.

Explanation:

The length field in the CMR header for a color management resource (CMR) is not valid.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains X'EFFa', where a identifies the specific field within the header.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal 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 as unprintable. PSF releases the current data set back to JES and requests that the system hold the data set unless PRTERROR=QUIT was specified on the OUTPUT statement.

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

If you created the tags for the CMR, correct the error and resubmit the print request. See Color Management Object Content Architecture Reference, AFPC-0006 for more information about the tag. If the tag has no error, the error might be a printer logic error. If you used a program to create the tags for the CMR, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the tags for the CMR with the error, verify that the input to that program was valid. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2634I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: UNSUPPORTED TAGID VALUE IN A CMR TAG.

Explanation:

The CMR Data field for a color management resource (CMR) contains an unsupported TagID value.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error.

System action:

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

When the CMR Tag Fidelity triplet sets the CONTINUE field equal 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 as unprintable. PSF releases the current data set back to JES and requests that the system hold the data set unless PRTERROR=QUIT was specified on the OUTPUT statement.

When the CMR Tag Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC CMR Tag Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 CMR Tag Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2635I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE COUNT VALUE IN A CMR TAG IS NOT VALID.

Explanation:

The CMR Data field for a color management resource (CMR) contains a tag with a Count value that is not valid.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2636I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE FIELDTYPE VALUE IN A CMR TAG IS NOT VALID.

Explanation:

The CMR Data field for a color management resource (CMR) contains a tag with a Fieldtype value that is not valid.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2637I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE CMR DATA FOR A CMR IS MISSING A REQUIRED TAG.

Explanation:

The CMR Data field for a color management resource (CMR) is missing a required tag for its CMR type.

Note:

The Element Identifier bytes 16-17 in the formatted sense message contain the CMR TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2638I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE SEQUENCE OF CMR TAGS SPECIFIED IS NOT VALID.

Explanation:

The CMR Data field for a color management resource (CMR) contains tags out of sequence. Tags in a CMR must be specified in increasing order by their TagIDs.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2639I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: THE FIELD VALUE IN A CMR HEADER OR CMR TAG IS NOT VALID OR IS UNSUPPORTED.

Explanation:

The CMR Data field for a color management resource (CMR) contains a tag with a field value that is not valid or is unsupported.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error. For errors in the CMR header, the Element Identifier (bytes 16-17) contains X'EFFa' where a identifies the specific field within the header.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2640I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: INCONSISTENT CMR TAG CONTENTS.

Explanation:

The CMR Data field for a color management resource (CMR) contains a tag with inconsistent or conflicting values. For example, the count field and the number of components in the tag do not match.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the CMR TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2641I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A COLOR MANAGEMENT RESOURCE IS NOT AVAILABLE.

Explanation:

A color management resource (CMR) is needed to process specific print data. However, a CMR is unavailable because the printer does not have a default CMR for that type of color data and a host-called CMR is not supplied. The device default CMRs defined in the Color Management Object Content Architecture Reference, AFPC-0006 must be supported by the printer, but defaults for other color spaces are optional and a host-called CMR must be supplied.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

See Color Management Object Content Architecture Reference, AFPC-0006 for more information about device default CMRs. If a device default CMR should have been supported by the printer this might be a printer logic error. If the device default CMR is optional for this color space then the required CMR must be specified on the host. The CMR can be mapped directly in the job or indirectly through the resource access table (RAT). If you used a program to create the structured fields for the job or to install the resources in a RAT, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the data set with the error, verify that the input to that program was valid. If the missing CMR has not been installed in the RAT or has not been correctly mapped to a data object resource, use a product such as InfoPrint AFP Resource Installer to update the RAT. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2644I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE INVOKED, MEDIA-SPECIFIC INSTRUCTION CMR DOES NOT MATCH THE SELECTED MEDIA.

Explanation:

An invoked instruction or device link (DL) color management resource (CMR) is requested, but the media-specific fields in the CMR header do not match the current media used by the printer for this sheet.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

If the output is unacceptable, see Color Management Object Content Architecture Reference, AFPC-0006 for more information about the rules for matching media-specific fields with media type on the printer:

If the wrong media was loaded in the printer, correct the error and resubmit the job.
If the loaded media is correct, but the media characteristics selected by the printer operator do not match the loaded media, contact your printer operator to correct the error and resubmit the job.
If the media-specific instruction CMR is not what you intended, change the structured fields in the job that specify the incorrect CMR to specify the correct media-specific instruction CMR.
If the job does not explicitly map the incorrect CMR, the incorrect CMR might have been associated with the job through the resource access table (RAT). If you created the data object RAT or CMR RAT used by this job, make sure the correct media-specific instruction CMR is installed and mapped to the appropriate data object resources. Otherwise, contact your system programmer.
If the media-specific CMR should have matched the media used by the printer, this might be a printer logic error.

System programmer response:

If an IBM licensed program was used to create the structured fields for the job with the error or the CMR in the RAT, verify that the input to that program was valid. If the correct media-specific instruction CMR has not been installed or has not been correctly mapped to a data object resource, use a product such as InfoPrint AFP Resource Installer to update the RAT. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2645I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE REQUESTED GENERIC CMR IS NOT SUPPORTED.

Explanation:

A generic color management resource (CMR) is selected, but the printer does not have the appropriate device-specific CMR to use in place of the generic CMR.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

If you created the CMR resource access table (RAT) being used by this job, then install the required device-specific CMR. Otherwise, contact your system programmer.

System programmer response:

If an IBM licensed program was used to install the CMRs, verify that the input to that program was valid. If the required device-specific CMR has not been installed in the RAT or has not been correctly mapped to a data object resource, use a product such as InfoPrint AFP Resource Installer to update the RAT. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2646I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: AN INVOKED, SELECTED CMR WAS NOT USED. THE PRINTER USED AN APPROPRIATE DEFAULT CMR.

Explanation:

A color management resource (CMR) is invoked, selected for use, and valid, but it cannot be used. 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:

A printer-operator control has been invoked to achieve a specific look that overrides a user-specified tone transfer curve CMR.
A selected halftone CMR is not appropriate for the printer; for example, a threshold-array halftone is invoked and selected for use with an ink jet printer, or an error-diffusion halftone is invoked and selected for use with a laser printer.
A halftone or tone transfer curve CMR has been applied to a portion of a sheet. However, a subsequent halftone or tone transfer curve CMR is not supported because the printer can allow only one halftone or tone transfer curve CMR after a complete sheet is created.
A limited number of halftone or tone transfer curve CMRs are supported on a sheet; for example, when data overlaps, only one halftone can be applied to the overlapping area.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

If the output is unacceptable, do these:

Verify that a print-operator control did not override your CMR.
If you created the structured fields in your job specifying the CMR in error, verify that the appropriate CMR is being specified for the printer being used.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2647I

THE PRINTER DETECTED A COLOR RELATED ERROR WITHIN A PRESENTATION OBJECT CONTAINER. CODE = (code and brief description).

Explanation:

The printer has detected a color-related error in a data object resource. For a complete list of the error codes and descriptions, see Intelligent Printer Data Stream Reference, AFPC-0001.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. PSF stops processing the data set that was being processed at the time of the error and marks the data set as unprintable. PSF releases the current data set back to JES and requests that the system hold it unless PRTERROR=QUIT was specified on the OUTPUT statement. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, the printer takes its continuation action for the page and PSF reports this exception if the REPORT field is set to REPORT. PSF stops processing the data set that was being processed at the time of the error and marks the data set as unprintable. PSF releases the current data set back to JES and requests that the system hold it unless PRTERROR=QUIT was specified on the OUTPUT statement.

User response:

If you created the structured fields for the object container resource, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 or 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 object container resource, contact your system programmer.

System programmer response:

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 is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2648I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE SPECIFIED SET EXTENDED BILEVEL IMAGE COLOR VALUE IS NOT VALID.

Explanation:

A Set Extended Bilevel Image Color value for an image object is not valid. 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:

A specified color space value is not valid.
A specified size value is not valid.
A specified color value is not valid.

The Set Extended Bilevel Image Color self-defining field is in the Image Data Descriptor (IDD) structured field. The IDD structured field is in an image object. The image object might be contained in a MO:DCA document, overlay, or page segment; or embedded in a data set containing line data.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet, the printer reports this exception if the REPORT field is set to REPORT. 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

If you created the structured fields for the image object, 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 image object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the image object with the error, verify that the input to that program was valid. If the input is 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 in the User Response section to correct the error.

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2649I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: INCORRECTLY ORDERED REPEATING GROUPS FOR AN INDEXED COLOR TAG.

Explanation:

The tags used to translate 2-byte indexed color values to a specific color space are specified in repeating groups. These repeating groups must be sorted in ascending order of indexed color value.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the color management resource (CMR) TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet and the REPORT field is set to REPORT, 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2650I

DATA IN A COLOR MANAGEMENT RESOURCE IS NOT VALID: A COLORANT NAME IS SPECIFIED IN MORE THAN ONE REPEATING GROUP IN A COLORANT IDENTIFICATION LIST TAG.

Explanation:

A colorant identification list consists of repeating groups of colorant names. Each of these names must be unique; no duplicates are allowed.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the color management resource (CMR) TagID value for the tag that caused the error.

System action:

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

When the Color Fidelity triplet sets the CONTINUE field equal to DO NOT STOP (X'02'), one of these occurs:

If the printer supports the PFC Color Fidelity triplet and the REPORT field is set to REPORT, 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 printer you are using might attempt to print the page in error, but 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. If the REPORT field was 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 Color Fidelity triplet, this exception might or might not be reported. In either case, 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 printer you are using might attempt to print the page in error, but 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2661I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: INCORRECT OR INSUFFICIENT DATA WAS ENCOUNTERED IN A ROYAL MAIL RED TAG BAR CODE OBJECT.

Explanation:

Within a Royal Mail RED TAG bar code object, data is incorrect or insufficient. There must be exactly 21 numeric digits in the input data. The printer uses the BCOCA range to check that each field of the input data is valid.

System action:

The printer you are 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.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2662I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE OBJECT OFFSET TRIPLET SPECIFIED FOR A PAGINATED DATA OBJECT RESOURCE SELECTED AN OBJECT THAT COULD NOT BE FOUND. THE PAGE IS PRINTED WITHOUT THE OBJECT.

Explanation:

The object offset specified for a data object resource selected an object that does not exist. An object offset is specified with the X'5A' triplet on the Container Data Descriptor (CDD), the Include Object (IOB), or the Preprocess Presentation Object (PPO) structured field for a data object resource.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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 reports another error that requires a more severe PSF recovery action.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 18.

APS2663I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A UNICODE COMPLEX TEXT PARAMETER VALUE IS NOT VALID.

Explanation:

An incorrect PTOCA Unicode Complex Text (UCT) control sequence parameter value was found in a Presentation Text Data (PTX) structured field, which might be contained in a MO:DCA document, a PTOCA object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

For printers that return the IPDS Sense Type and Model (STM) Text Command-Set vector X'4303' property pair, the error is with the UCT data length value (CTLNGTH).

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

If you were printing a MO:DCA document, a PTOCA 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 and Presentation Text Object Content Architecture Reference, SC31-6803 for more information about the structured field and control sequence. 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, PTOCA 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.

To determine whether your printer returns the STM property pair see the printer information report for this printer (specified with the PRTINFO DD statement in the PSF startup procedure). Contact your system programmer for help locating this report.

System programmer response:

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.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2664I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE FONT OBJECT ID SPECIFIED IN A GLYPH LAYOUT CONTROL DOES NOT MATCH THE FONT OBJECT ID OF THE CURRENT FONT BEING USED TO RENDER THE TEXT.

Explanation:

The font object ID (OID), specified in a Presentation Text Data (PTX) Glyph Layout Control (GLC) control sequence FONTOID parameter, does not match the font OID of the font being used to render the text because of one of these:

The font OID does not match the font OID of the current font or any font linked to the current font.
The font OID matched the OID of a font collection, but the full font name (FFONTNME) specified in the GLC does not match any font in the collection.
The printer does not have a font OID for the current font to compare against the GLC font OID.

The element identifier in the formatted sense byte message (APS830I) contains the number identifying the specific cause of the error.

The text-control came from a PTX structured field, which might be contained in a MO:DCA document, a PTOCA object, an overlay, or a page segment; or it might be embedded in a data set containing line data.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

See the accompanying environmental messages for the name of the current font.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2665I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A PTOCA GLYPH LAYOUT CONTROL CHAIN WAS ENCOUNTERED, BUT THE CURRENT FONT IS NOT A TRUETYPE OR OPENTYPE FONT.

Explanation:

The current font used to process the glyph runs in a PTOCA Glyph Layout Control (GLC) chain is not a TrueType or OpenType font. The current font is specified in a previous Presentation Text Data (PTX) Set Coded Font Local control sequence.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

See the accompanying environmental messages for the name of the current font.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2666I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A GLYPH ID SPECIFIED IN A GLYPH ID RUN CONTROL SEQUENCE WAS NOT FOUND IN THE CURRENT FONT.

Explanation:

A glyph ID specified in a PTOCA Glyph ID Run (GIR) was not found in the current font. The current font is specified in the FONTOID parameter of a Presentation Text Data (PTX) Glyph Layout Control (GLC) control sequence for this GLC chain or a previous one if none is specified for this one.

Note:

In the formatted sense message (APS830I), the Element Identifier (bytes 16-17) contains the failing glyph ID.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2667I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A MISSING OR INCORRECT CONTROL SEQUENCE WAS FOUND IN A GLYPH LAYOUT CONTROL CHAIN.

Explanation:

An unexpected PTOCA control sequence was encountered in a Glyph Layout Control (GLC) chain. A GLC chain consists of a GLC control sequence followed by one or more Glyph ID Run (GIR), Glyph Advance Run (GAR), and optional Glyph Offset Run (GOR) control sequences. The GLC chain can end with an optional Unicode Complex Text (UCT) control sequence. A chain must contain these control sequences in this order (brackets surround optional controls):

X'2BD3' GLC GIR GAR [GOR] [GIR GAR [GOR]]...[GIR GAR [GOR]] [UCT]

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

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2668I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: AN UNSUPPORTED UNICODE COMPLEX TEXT CONTROL SEQUENCE WAS FOUND OUTSIDE OF A GLYPH LAYOUT CONTROL CHAIN.

Explanation:

A PTOCA Unicode Complex Text (UCT) control sequence was found outside of a Glyph Layout Control (GLC) chain. If the printer supports glyph layout controls, it ignores UCTs that are chained to a GLC chain and recognizes, but does not support, other UCT control sequences.

System action:

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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2669I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A GLYPH ID RUN, GLYPH ADVANCE RUN, OR GLYPH OFFSET RUN CONTROL SEQUENCE WAS FOUND OUTSIDE A GLYPH LAYOUT CONTROL CHAIN.

Explanation:

A PTOCA Glyph ID Run (GIR), Glyph Advance Run (GAR), or Glyph Offset Run (GOR) control sequence was found outside a Glyph Layout Control (GLC) chain. A GLC chain consists of a GLC control sequence followed by one or more GIR, GAR, and optional GOR control sequences. The GLC chain can end with an optional Unicode Complex Text (UCT) control sequence. A chain must contain these control sequences in this order (brackets surround optional controls):

X'2BD3' GLC GIR GAR [GOR] [GIR GAR [GOR]]...[GIR GAR [GOR]] [UCT]

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2670I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE NUMBER OF ENTRIES IN A GLYPH ADVANCE RUN OR GLYPH OFFSET RUN CONTROL SEQUENCE DOES NOT MATCH THE NUMBER OF ENTRIES IN THE GLYPH ID RUN CONTROL SEQUENCE IN A GLYPH LAYOUT CONTROL CHAIN.

Explanation:

The number of entries in a PTOCA Glyph Advance Run (GAR) or Glyph Offset Run (GOR) control sequence must match the number of entries in the preceding Glyph ID Run (GIR) control sequence in the Glyph Layout Control (GLC) chain.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2671I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A TRUETYPE OR OPENTYPE FONT OBJECT ID WAS NOT PROVIDED FOR A GLYPH LAYOUT CONTROL CHAIN.

Explanation:

A PTOCA Glyph Layout Control (GLC) control sequence specified a font object ID length (OIDLGTH) of zero (indicating that the previously specified font object ID (FONTOID) is still in effect), but there was no previously specified FONTOID found in the text object, page, or overlay.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2672I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A PTOCA GLYPH LAYOUT CONTROL (GLC) CONTROL SEQUENCE CONTAINS AN INCORRECT LENGTH FIELD.

Explanation:

A PTOCA Glyph Layout Control (GLC) control sequence contains an incorrect length field. 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:

The font object ID length (OIDLGTH) field or the full font name length (FFNLGTH) field contains a value that is not consistent with the overall control sequence length.
The font OIDLGTH contains a value that is not valid.
The FFNLGTH field contains a value that is not valid.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2673I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A GLYPH LAYOUT CONTROL (GLC) CONTROL SEQUENCE SPECIFIED A FULL FONT NAME, BUT NO FONT OBJECT ID.

Explanation:

A PTOCA Glyph Layout Control (GLC) control sequence specified a full font name (FFONTNME) and a non-zero value in the full font name length (FFNLGTH) field, but no font object ID (FONTOID) was specified. PTOCA requires an FONTOID when a full font name is specified.

System action:

The printer you are using might try to print the page in error; however, the entire page might not be printed. If the page in error contains any positioning errors, 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.

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2674I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A CHARACTER ENCOUNTERED WITHIN THE BAR CODE DATA IS NOT VALID FOR THE SELECTED ENCODING SCHEME.

Explanation:

Within a Data Matrix bar code object, a C40, Text, X12, or EDIFACT scheme was selected and a character was encountered that is not valid for that encoding scheme. The encoding schemes do not support all 256 possible input characters.

System action:

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS2675I

WHILE THE PRINTER WAS PROCESSING A DATA SET, THIS CONDITION OCCURRED: FUSER OIL SUPPLY IS EMPTY.

Explanation:

The fuser oil supply for the printer is empty. This error condition caused the printer to discard its buffered pages. The printer reports an action code X'1A' to instruct PSF to redrive buffered pages. For more information about this condition, see the printer publications for the printer that reported this error.

System action:

After the printer has been readied, PSF resends pages to the printer, starting from the committed page counter plus 1. If repositioning is not supported in the current environment, PSF stops processing the data set.

User response:

The printed output might be acceptable.

System programmer response:

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

Operator response:

Resolve the error condition at the printer and press RESET or READY.

Problem determination:

Items 1, 18.

APS2676I

WHILE THE PRINTER WAS PROCESSING A DATA SET, THIS CONDITION OCCURRED: DEVELOPER MIX NEEDS CHANGING.

Explanation:

The developer mix for the printer needs changing. This error condition caused the printer to discard its buffered pages. The printer reports an action code X'1A' to instruct PSF to redrive buffered pages. For more information about this condition, see the printer publications for the printer that reported this error.

System action:

User response:

The printed output might be acceptable.

System programmer response:

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

Operator response:

Resolve the error condition at the printer and press RESET or READY.

Problem determination:

Items 1, 18.

APS2677I

WHILE THE PRINTER WAS PROCESSING A DATA SET, THIS CONDITION OCCURRED: OILER FELT NEEDS CHANGING.

Explanation:

The oiler felt for the printer needs changing. This error condition caused the printer to discard its buffered pages. The printer reports an action code X'1A' to instruct PSF to redrive buffered pages. For more information about this condition, see the printer publications for the printer that reported this error.

System action:

User response:

The printed output might be acceptable.

System programmer response:

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

Operator response:

Resolve the error condition at the printer and press RESET or READY.

Problem determination:

Items 1, 18.

APS2678I

WHILE THE PRINTER WAS PROCESSING A DATA SET, THIS CONDITION OCCURRED: TONER COLLECTOR FULL.

Explanation:

The toner collector for the printer is full and needs to be replaced. This error condition caused the printer to discard its buffered pages. The printer reports an action code X'1A' to instruct PSF to redrive buffered pages. For more information about this condition, see the printer publications for the printer that reported this error.

System action:

User response:

The printed output might be acceptable.

System programmer response:

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

Operator response:

Resolve the error condition at the printer and press RESET or READY.

Problem determination:

Items 1, 18.

APS2679I

WHILE THE PRINTER WAS PROCESSING A DATA SET, THIS CONDITION OCCURRED: FINE FILTER NEEDS CHANGING.

Explanation:

The fine filter for the printer needs changing. This error condition caused the printer to discard its buffered pages. The printer reports an action code X'1A' to instruct PSF to redrive buffered pages. For more information about this condition, see the printer publications for the printer that reported this error.

System action:

User response:

The printed output might be acceptable.

System programmer response:

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

Operator response:

Resolve the error condition at the printer and press RESET or READY.

Problem determination:

Items 1, 18.

APS2681I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: TEXT DATA EXTENDS OUTSIDE THE TEXT OBJECT AREA.

Explanation:

A character has been positioned so that a portion of the PTOCA Presentation Text (PTX) data extends beyond the intersection of the mapped presentation text space and the text object area.

The size of the presentation text space is defined in the Presentation Text Descriptor (PTD). The position of the presentation text space is specified in the Map Presentation Text (MPT) structured field or the Object Area Position (OBP) structured field. The text object area is specified in the Object Area Descriptor (OBD) structured field. The position or size of the presentation text object did not fit into the specified object area.

The PTX structured field is contained in a presentation text object. The presentation text object might be contained or referenced in a MO:DCA document, a resource, or it might be embedded in a data set containing line data. The MPT, PTD, OBD, and OBP are specified in the Object Environment Group (OEG) for the presentation text object.

System action:

The printer you are using might try to print the page in error. The entire page might not be printed. If the page in error contains any position errors, exception highlighting might be included on the printed page. PSF continues 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.

User response:

If the structured fields are not valid and you created the structured fields for the resource or print data set, 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.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS2682I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: INCORRECT OR INSUFFICIENT DATA WAS ENCOUNTERED IN AN INTELLIGENT MAIL CONTAINER BAR CODE OBJECT.

Explanation:

Within an Intelligent Mail Container bar code object, data is incorrect or insufficient. 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:

Too many or too few characters were specified; there must be exactly 22 characters in the input data.
A character was encountered in the data that is not valid; specific ranges are defined for each field defined for this symbology.
Data was encountered that would cause subset A to be used; only subsets B and C are allowed for this symbology.

System action:

User response:

If you created the structured fields for the bar code object or the page definition, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about bar code objects. See Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about creating page definitions. If the structured field or page definition 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 bar code object, contact your system programmer.

System programmer response:

If an IBM licensed program was used to create the structured fields for the bar code object 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.

Operator response:

Problem determination:

Items 2, 3, 8, 13, 17.

APS3000I

THE RDJFCB TYPE X'13' SYSTEM FUNCTION IS NOT SUPPORTED BY THIS SYSTEM AND PSF REQUIRES THIS SUPPORT. PLEASE NOTIFY YOUR SYSTEM PROGRAMMER.

Explanation:

The RDJFCB type X'13' system function is not supported by this system. You are running with a down-level DFP or operating system or both. The minimum operating system level is MVS/XA 2.2.0, and the minimum MVS/DFP level is 2.3.0 for this RDJFCB support.

System action:

The PSF initialization is stopped.

User response:

No response is necessary.

System programmer response:

Ensure that PSF is installed on a system that supports the RDJFCB type X'13' system function with the appropriate level of DFP. See Explanation for minimum levels.

If you are on a system at the appropriate level, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

Operator response:

Inform your system programmer that this error has occurred.

Problem determination:

Items 1, 17, 19, 27.

APS3001I

THE RDJFCB TYPE X'13' SYSTEM FUNCTION WAS UNSUCCESSFUL — RETURN CODE return code. PLEASE NOTIFY YOUR SYSTEM PROGRAMMER.

Explanation:

The RDJFCB type X'13' system function was unsuccessful. An RDJFCB macro request was issued to obtain the data set names of a library, and a nonzero code was returned.

System action:

The PSF initialization is stopped.

User response:

No response is necessary.

System programmer response:

Correct the problem in response to the system return code identified in this message. See z/OS DFSMSdfp Advanced Services for information on the hexadecimal return code. See information on the ARLRCODE field.

Operator response:

Inform your system programmer that this error has occurred.

Problem determination:

Items 1, 17, 19, 27.

APS3002I

THE OBTAIN SYSTEM FUNCTION WAS UNSUCCESSFUL FOR DATA SET NAME data set name -- RETURN CODE return code. PLEASE NOTIFY YOUR SYSTEM PROGRAMMER.

Explanation:

The system OBTAIN(reading by Data Set Name) function was unsuccessful and the return code indicates the cause.

System action:

PSF is ended.

User response:

No response is necessary.

System programmer response:

Correct the problem in response to the system return code identified in the message. See z/OS DFSMSdfp Advanced Services for the meaning of the OBTAIN hexadecimal return code.

Operator response:

Notify your system programmer.

Problem determination:

Items 1, 2, 17, 19, 27.

APS3003I

SAVING THE AUXILIARY FILE WAS UNSUCCESSFUL: THERE IS A PROBLEM WITH OUTPUT FILE (filename). RETURN CODE (return code). REASON CODE (reason code).

Explanation:

You specified the parameter for saving auxiliary files in the AFPPARMS control statement or the Printer Inventory; however, AFP Download Plus was unable to save the auxiliary file because it received an error from UNIX System Services when it tried to copy the resource group file and MO:DCA file to the output auxiliary file.

System action:

The AFP Download Plus FSA stops with a system completion code 024 and abend reason code 0D1A.

User response:

No response necessary.

System programmer response:

Use the return code and reason code to determine the problem. See z/OS UNIX System Services Programming: Assembler Callable Services Reference.

Operator response:

Contact your system programmer.

Problem determination:

Items 1, 2, 8, 9, 13, 17.

APS3004I

SAVING THE AUXILIARY FILE WAS UNSUCCESSFUL: THERE IS A PROBLEM WITH INPUT FILE (filename). RETURN CODE (return code). REASON CODE (reason code).

Explanation:

System action:

The AFP Download Plus FSA stops with a system completion code 024 and abend reason code 0D1A.

User response:

No response necessary.

System programmer response:

Use the return code and reason code to determine the problem. See z/OS UNIX System Services Programming: Assembler Callable Services Reference.

Operator response:

Contact your system programmer.

Problem determination:

Items 1, 2, 8, 9, 13, 17.

APS3005I

PSF CANNOT PROCESS THE (resource) LIBRARY FOR DD STATEMENT (ddname) BECAUSE PSF IS NOT UNICODE ENABLED. PROCESSING CONTINUES.

Explanation:

The library specified in the PSF startup procedure cannot be processed because PSF is not Unicode-enabled. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource library request.

System action:

PSF continues processing the data set.

User response:

Inform your system programmer that this error occurred.

System programmer response:

A UNIX System Services error occurred that prevented PSF from processing this resource request. See message APS7001I, which was issued with this message, for help correcting the UNIX System Services error.

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

Item 1.

APS3006I

PSF CANNOT PROCESS THE USERPATH PARAMETER FOR OUTPUT STATEMENT (outputname) BECAUSE PSF IS NOT UNICODE ENABLED. PROCESSING CONTINUES.

Explanation:

The USERPATH parameter specified in the OUTPUT JCL statement cannot be processed because PSF is not Unicode-enabled. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this request.

System action:

PSF continues processing the data set.

User response:

Inform your system programmer that this error occurred.

System programmer response:

Operator response:

None.

Problem determination:

Item 1.

APS3500I

THE FONT MENTIONED IN THE MESSAGE ABOVE HAS A GLOBAL RESOURCE IDENTIFIER (GRID) OF 'grid'. THE COMPONENTS OF THE GRID (SPECIFIED AS DECIMAL VALUES) ARE: GCSGID= gscgid, CPGID= cpgid, FGID= fgid, AND FONT WIDTH= font width.

Explanation:

This message is issued in addition to the message that describes the error. It is intended as additional diagnostic information. The font being processed at the time of the error is listed in this message by its GRID and GRID components (GSCSGID, CPGID, FGID, and font width). The GRID is presented as a hexadecimal value and the GRID components are specified as decimal values.

System action:

The printing disposition depends on the error described in the accompanying messages.

User response:

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

System programmer response:

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

Operator response:

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

Problem determination:

Items 1, 2, 3, 8, 15, 17.

APS3501I

DATA OBJECT RESOURCE TYPE (type string), NAME (member) OR OBJECT ID (object oid), HAS AN UNSUPPORTED REGISTRATION ID (object-type oid).

Explanation:

The registration ID (object-type oid) for the specified data object resource is not supported by either the printer or PSF. The registration ID is specified in the object classification triplet on one of these structured fields:

Include Object (IOB)
Begin Object Container (BOC)
Begin Resource (BRS, also called BR)
Map Data Resource (MDR)

Any message inserts (enclosed in parentheses) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'. If the data object resource type in this message is '(***)', PSF or the printer does not support the resource type. For more information about registration IDs and object types, see Mixed Object Document Content Architecture Reference, AFPC-0004.

System action:

If this error was encountered when processing a Resource Environment Group (REG), PSF skips over this particular data object resource and tries to process any other resources specified in the REG. If this error was encountered while processing a page or overlay object, PSF stops processing the page or overlay object. PSF tries to locate the end of the current page and resume processing on the next page. If the end of the current page cannot be located, PSF stops printing the data set. PSF issues additional messages that identify the processing environment when the error was found.

User response:

If you created the structured fields for the data object resource, ensure that the registration ID is correct. If the registration ID is correct, submit the print job to a printer that supports this object type. For more information about what object types are supported by your printer, see your printer documentation.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3502I

DATA OBJECT RESOURCE TYPE (type string), NAME (member) OR OBJECT ID (object oid), COULD NOT BE PROCESSED. THIS OBJECT IS NOT REQUIRED FOR THIS PRINTER AND IS SKIPPED.

Explanation:

The registration ID (object-type OID) for the specified data object resource is not supported by the printer. The registration ID is specified in the object classification triplet on one of these structured fields:

Include Object (IOB)
Begin Object Container (BOC)
Begin Resource (BRS, also called BR)
Map Data Resource (MDR)

The printer does not support the registration ID; however, this object is not required for printing this document. It is likely that the print file was formatted for a color printer that supports color profiles but is being printed on a printer that does not support these color profile objects. Any message inserts (enclosed in parentheses) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'.

System action:

PSF records this condition and then continues processing.

User response:

If the printed output is not acceptable, choose a printer that supports the color profiles that are specified in this print file, or re-format this print file for the printer on which this print file is being printed.

System programmer response:

Verify that the formatting options at the time the print file was produced are compatible with the printer on which this print file is printing. Correct any mismatches.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3503I

DATA OBJECT RESOURCE TYPE (type string), NAME (member) OR OBJECT ID (object oid), WAS REPLACED BY DATA OBJECT RESOURCE NAME (member) OR OBJECT ID (object oid), (optional user text).

Explanation:

The resource exit requested substitution of this data object resource. The specific type of data object resource is identified in this message. This message also contains the original data object resource name or object ID and the new data object. Any message inserts (enclosed in parenthesis) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'.

System action:

PSF replaces the original data object resource references (name or object ID) with the new data object resource references (name or object ID) specified by the resource exit. PSF then generates this informational message unless directed otherwise by the resource exit.

User response:

If the printed output is not acceptable, contact your system programmer.

System programmer response:

You can use the optional user text field of this message to provide further information to the user about why this data object resource was replaced. For more information about providing optional user text in this message, see PSF for z/OS: Customization.

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS3504I

THIS RESOURCE SUBSTITUTION REQUEST IS NOT ALLOWED. NAME (member) OR OBJECT ID (object OID) WAS NOT REPLACED BY NAME (member) OR OBJECT ID (object OID).

Explanation:

The resource exit requested substitution of this data object resource. This substitution was denied because the identification of the new data object resource (name or object ID) was not of the same identification type (name or object ID) as the original data object resource. The specific type of data object resource is identified in this message. This message also contains the original data object resource name or object ID and the new data object resource name or object ID. Any message inserts (enclosed in parenthesis) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'.

System action:

PSF ignores the new data object resource name or object ID and uses the original data object resource name or object ID. PSF then generates this warning message and continues processing.

User response:

If the printed output is not acceptable, contact your system programmer.

System programmer response:

To specify a new data object resource as a substitute for the original data object resource, the resource identification type must be identical. For example, if the original data object resource was identified with a name, the new data object resource must also be identified with a name and the object ID specifications must remain unchanged. For more information about resource substitution, see PSF for z/OS: Customization.

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS3505I

DATA OBJECT RESOURCE TYPE (type string), OBJECT ID (object id), IS SPECIFIED IN AN IOB STRUCTURED FIELD WITH THE ASN.1 OID FORMAT. PSF DOES NOT SUPPORT THIS FORMAT FOR SOFT DATA OBJECT RESOURCES.

Explanation:

The data object resource referenced by the IOB is soft, meaning that it was not treated as a hard resource managed by PSF. Hard resources are sent to the printer before the page. PSF does not support IOB references with the ASN.1 OID format for soft data object resources.

System action:

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, 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 reports another error that requires a more severe PSF recovery action.

User response:

If you created the structured fields for the IOB, change the IOB to reference the data object resource by name. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the IOB structured field.

System programmer response:

If an IBM licensed program was used to create the structured fields, verify that the input to that program was valid and the correct printer is being used. If the input was valid, change the IOB to reference the data object resource by name.

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS3506I

DATA OBJECT RESOURCE TYPE (type string), OBJECT ID (object oid), COULD NOT BE ACTIVATED IN THE PRINTER.

Explanation:

The printer could not activate the data object resource with object ID object oid. If the data object resource type string (type string) in this message is '(***)' PSF does not support the object type. Any message inserts (enclosed in parenthesis) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'.

System action:

PSF stops printing the current data set and issues additional messages that identify the processing environment when the error was found.

User response:

Choose a printer that can activate the data object resource with the object ID that is specified in the print file, correct the object ID, or reformat this print file for the printer on which it is being printed.

System programmer response:

Verify that the formatting options when the print file is produced are compatible with the printer that is being used. Correct any mismatches.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3507I

DATA OBJECT RESOURCE TYPE (type string), OBJECT ID (object oid), COULD NOT BE ACTIVATED IN THE PRINTER. THIS OBJECT IS NOT REQUIRED FOR PRINTING AND IS SKIPPED.

Explanation:

The data object resource with object ID (object oid) could not be activated by the printer. The printer does not know of this data object resource; however, this object is not required for printing this document. PSF records this condition and continues. It is likely that the print file was formatted for a color printer that supports color profiles but is being printed on a printer that does not support these color profile objects. It is also possible that the object ID (object oid) was specified incorrectly. Any message inserts (enclosed in parenthesis) in this message that are not available or that do not apply to this instance of this message are specified as '(***)'.

System action:

PSF records this condition and then continues processing.

User response:

If the printed output is not acceptable, choose a printer that knows the object IDs that are specified in the print file, correct the object ID, or reformat this print file for the printer on which it is being printed.

System programmer response:

Verify that the formatting options at the time the print file is produced are compatible with the printer on which this print file is printing. Correct any mismatches.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3508I

RESOURCE TYPE (type string), NAME (member) OR OBJECT ID (object oid), SHOULD NOT BE SPECIFIED AS AN OBJECT CONTAINER RESOURCE.

Explanation:

PSF encountered an object in an object container construct that should not be an object container. One example of this is an IOCA object that has been placed in object container structured fields. The object in error was identified by name (member) or object ID (object oid). Any message inserts (enclosed in parenthesis) in this message that are not available or that do not apply to this instance of this message are specified as ''(***)'.

System action:

User response:

If you created the structured fields for the data object resource, ensure that the object type is appropriate for use as an object container or use this object type as intended. For more information about the proper usage of this object type, see Mixed Object Document Content Architecture Reference, AFPC-0004.

System programmer response:

If an IBM licensed program was used to create the structured fields, verify that the input to that program was valid and the correct printer is being used. 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.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3509I

THE ABOVE CONDITION WAS ENCOUNTERED WHILE PROCESSING OBJECTS SPECIFIED IN RESOURCE ENVIRONMENT GROUP (token name). PROCESSING OF THE RESOURCE ENVIRONMENT GROUP CONTINUES.

Explanation:

The previous condition or error was found while processing a Resource Environment Group (REG) for this document. Errors or conditions identified during REG processing are recorded and processing continues. This message is produced to help find the noted condition. The message insert (token name) identifies the REG being processed when the condition was encountered. If the REG does not have a token name, the message insert appears as '(***)'.

System action:

PSF records the environment at the time the primary condition was encountered and continues processing.

User response:

See the User Response for the primary message in this message set.

System programmer response:

See the System Programmer Response for the primary message in this message set.

Operator response:

Problem determination:

Items 1, 2, 17, 27.

APS3510I

THE ABOVE CONDITION OCCURRED IN THE RESOURCE ENVIRONMENT GROUP JUST PRIOR TO PAGE (page number) OF TRANSMISSION (transmission number).

Explanation:

The previous condition or error was found while processing a Resource Environment Group (REG) for this document. Errors or conditions identified during REG processing are recorded and processing continues. This message is produced to help find the noted condition. The condition occurred just before processing the page and transmission identified in this message.

System action:

PSF records the environment at the time the primary condition was encountered and continues processing.

User response:

See the User Response for the primary message in this message set.

System programmer response:

See the System Programmer Response for the primary message in this message set.

Operator response:

Problem determination:

Items 1, 4, 9, 17, 19.

APS3513I

AN ATTEMPT WAS MADE TO ACTIVATE A PRINTER-RESIDENT CODE PAGE USING CPGID cpgid AND GCSGID gcsgid. THE ATTEMPT WAS NOT SUCCESSFUL.

Explanation:

PSF received a request for a TrueType or OpenType font that asked that a code page be used to transform the print data. The code page was identified by a CPGID of cpgid and a GCSGID of gcsgid. However, the code page is not printer resident so PSF could not complete the activation.

A TrueType or OpenType font is introduced in the print data set by using an MDR structured field. The MDR was generated by the print application, PPFA, or some data stream formatter. The MDR for this TrueType or OpenType font specified a code page (by CPGID and GCSGID) to be used by the printer to transform the data encoding to Unicode. The CPGID and GCSGID are identifiers used by PSF and the printer to communicate about a specific code page. In this case, the printer did not know the identified code page.

The CPGID or GCSGID might be incorrect. Since PSF was given only the CPGID and GCSGID for the code page, PSF can attempt to activate only the code page. When the code page activation fails for a code page identified by CPGID and GCSGID, PSF must return this error.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the font was specified. In the associated environment message produced for this error, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

Do one of these to solve this problem:

Verify that the CPGID and GCSGID used to identify this code page are correct.
Specify the code page by name instead of by CPGID and GCSGID. This gives PSF a way to download the code page to the printer.

System programmer response:

If the error involves separator pages or message pages, use the information provided in the User Response section to correct the error. 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 correct. If the input was correct, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

Operator response:

If this message displays on the operator's console, it indicates an error in the specification of a code page to be used with a TrueType or OpenType font for printing the separator pages, message pages, or a default resource specified with the PSF startup procedure. Inform your system programmer.

Problem determination:

Items 2, 8, 17, 18, 19.

APS3514I

PSF CANNOT PROCESS THE TRUETYPE FONT, OPENTYPE FONT, OR COLOR MANAGEMENT RESOURCE (resource name). PSF MUST BE UNICODE-ENABLED TO SUPPORT THIS RESOURCE.

Explanation:

A TrueType or OpenType font or a color management resource was specified in the data stream with a name of resource name. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the resource was specified. In the associated environment message produced for this error, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

None.

APS3515I

THE (structured field name) STRUCTURED FIELD CONTAINS A DATA OBJECT OR OCA OBJECT RESOURCE (resource name) WITH A NAME LONGER THAN 8 CHARACTERS, BUT PSF IS NOT UNICODE-ENABLED. PSF WILL TRUNCATE THE NAME TO 8 CHARACTERS AND ATTEMPT TO PROCESS THIS RESOURCE.

Explanation:

A data object or OCA object resource was specified in the data stream with a resource name that is longer than 8 characters. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process resource names longer than 8 characters.

System action:

PSF truncates the resource name to 8 characters and tries to continue processing the resource.

User response:

If this print data set was not successfully processed by PSF, contact your system programmer.

System programmer response:

If this print data set was not successfully processed by PSF, see message APS7001I, which was issued with this message, for help correcting the UNIX System Services error.

Operator response:

If this print data set was not successfully processed by PSF, inform your system programmer.

Problem determination:

None.

APS3516I

THE (structured field name) STRUCTURED FIELD CONTAINS A DATA OBJECT OR OCA OBJECT RESOURCE (resource name), GCSGID (gcsgid), CPGID (cpgid). PSF MUST BE UNICODE-ENABLED TO SUPPORT THIS RESOURCE.

Explanation:

A data object or OCA object resource with a hexadecimal resource name was specified in the data stream with a name encoding of gcsgid and cpgid. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the resource was specified. In the associated environment messages produced for this error, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

None.

APS3517I

PSF CANNOT PROCESS THE TRUETYPE FONT, OPENTYPE FONT, OR COLOR MANAGEMENT RESOURCE (resource name), GCSGID (gcsgid), CPGID (cpgid). PSF MUST BE UNICODE-ENABLED TO SUPPORT THIS RESOURCE.

Explanation:

A TrueType or OpenType font or a color management resource with a hexadecimal resource name was specified in the data stream with a name encoding of gcsgid and cpgid. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

None.

APS3518I

PSF CANNOT PROCESS THE TRUETYPE FONT, OPENTYPE FONT, OR COLOR MANAGEMENT RESOURCE (resource name), CCSID (ccsid). PSF MUST BE UNICODE-ENABLED TO SUPPORT THIS RESOURCE.

Explanation:

A TrueType or OpenType font or a color management resource with a hexadecimal resource name was specified in the data stream with a name encoding of ccsid. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

None.

APS3519I

THE (structured field name) STRUCTURED FIELD CONTAINS A DATA OBJECT OR OCA OBJECT RESOURCE (resource name), CCSID (ccsid). PSF MUST BE UNICODE-ENABLED TO SUPPORT THIS RESOURCE.

Explanation:

A data object or OCA object resource with a hexadecimal resource name was specified in the data stream with a name encoding of ccsid. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this resource request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

None.

APS3520I

A RESOURCE HAS BEEN FOUND THAT CANNOT BE PLACED INLINE IN THE RESOURCE GROUP: PATH (path), FILENAME (filename).

Explanation:

AFP Download Plus received a request to process a resource that cannot be placed inline. Some resources, for example, TrueType and OpenType Fonts, have a setting that indicates whether embedding is allowed. If this setting forbids embedding, AFP Download Plus cannot place the resource inline.

System action:

AFP Download Plus cannot process the necessary resources to print this page. AFP Download Plus issues this error message and associated environment messages. The action taken depends on where in the data stream the data object resource was specified. The associated environment messages for this error identify the location of the error within the data stream as well as the disposition of the error.

User response:

Use only resources that can be embedded.

System programmer response:

Use only resources that can be embedded in separator pages and message pages and as default resources specified in the AFP Download Plus startup procedure.

Operator response:

If this message displays on the operator's console, it indicates that AFP Download Plus is processing a resource request for separator pages, message pages, or a default resource specified in the AFP Download Plus startup procedure. Inform your system programmer.

Problem determination:

Items 2, 8, 17, 18, 19.

APS3521I

THE (structured field name) STRUCTURED FIELD CONTAINS A PAGE SEGMENT, BCOCA, OR GOCA RESOURCE (resource name) WITH A NAME LONGER THAN 8 CHARACTERS, PSF WILL TRUNCATE THE NAME TO 8 CHARACTERS AND ATTEMPT TO PROCESS THIS RESOURCE.

Explanation:

A page segment, BCOCA, or GOCA resource was specified in the data stream with a resource name longer than 8 characters. PSF supports only these resources with names of 8 characters or less.

System action:

PSF truncates the resource name to 8 characters and tries to continue processing the resource.

User response:

If PSF successfully printed your print data set, no response is necessary. If this print data set was not successfully processed by PSF, ensure that all references in the data stream to this resource are 8 characters or less in length.

System programmer response:

If this print data set was not successfully processed by PSF, ensure that the appropriate resource name is 8 characters or less in length.

Operator response:

No response is necessary.

Problem determination:

None.

APS3522I

THE (structured field) STRUCTURED FIELD CONTAINS A PAGE SEGMENT, BCOCA, OR GOCA RESOURCE (resource name), GCSGID (gcsgid), CPGID (cpgid). PSF ONLY SUPPORTS THIS RESOURCE WITH DEFAULT NAME ENCODING (CCSID=500).

Explanation:

A page segment, BCOCA, or GOCA resource with a hexadecimal resource name was specified in the data stream with a name encoding of gcsgid and cpgid. However, PSF supports only a name encoding of CCSID=500 for page segment, BCOCA, or GOCA resources.

System action:

PSF cannot process the necessary resources to print this page. PSF prints this error message and its associated environment messages, which identify the location of the error within the data stream and the disposition of the page.

User response:

Change the name encoding of the resource to CCSID=500.

System programmer response:

If the error involves separator pages or message pages, do the action in the User Response section to correct the error. 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 correct. If the input was correct, see the PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

Operator response:

If this message displays on the operator's console, it indicates that PSF is processing a resource request for separator pages, message pages, or a default resource specified in the PSF startup procedure. Inform your system programmer.

Problem determination:

None.

APS3523I

THE (structured field) STRUCTURED FIELD CONTAINS A PAGE SEGMENT, BCOCA, OR GOCA RESOURCE (resource name), CCSID (ccsid). PSF ONLY SUPPORTS THIS RESOURCE WITH DEFAULT NAME ENCODING (CCSID=500).

Explanation:

A page segment, BCOCA, or GOCA resource was specified in the data stream with a name encoding of ccsid. However, PSF supports only a name encoding of CCSID=500 for page segment, BCOCA, or GOCA resources.

System action:

User response:

Change the name encoding of the resource to CCSID=500.

System programmer response:

Operator response:

Problem determination:

None.

APS3524I

THE FONT USED IN AN AUXILIARY DATA SET IS NOT IS/3 COMPLIANT. ONLY TRUETYPE AND OPENTYPE FONTS CAN BE USED.

Explanation:

When the Printer Inventory or the AFPPARMS control statement parameter that specifies the MO:DCA level for auxiliary files is set to IS3, auxiliary pages in an output data stream must be MO:DCA IS/3 compliant. To be IS/3 compliant, auxiliary pages, such as separator pages and message files, must use only TrueType and OpenType fonts. An error occurred because the font used for the auxiliary pages is a FOCA font, not a TrueType and OpenType font.

System action:

AFP Download Plus processing ends abnormally with a system completion code 024 and abend reason code 0E60. PSF stops processing the auxiliary data set that caused the error.

User response:

Contact your system programmer.

System programmer response:

Do one of these:

To indicate that the auxiliary files are not IS/3 compliant, specify NONE for the Printer Inventory or the AFPPARMS control statement parameter that specifies the MO:DCA level for auxiliary files.
Update the PRINTDEV statement in the startup procedure to specify separator page and message OUTPUT statements with page definitions that use only TrueType and OpenType fonts, not FOCA fonts.
If you are using AFP separator pages instead of line data, update the AFP separator page files to specify only TrueType and OpenType fonts.

Operator response:

If this message displays on the operator's console, it indicates that an auxiliary page was specified as IS/3, but the auxiliary file did not use only TrueType and OpenType fonts. Inform your system programmer.

Problem determination:

None.

APS4000I

THE AFP STATISTICS REPORT FACILITY IN PSF HAS ENCOUNTERED A MEMORY SHORTAGE AND HAS SHUT DOWN. MEMORY WAS NOT AVAILABLE FOR (memory item). ALL OTHER PSF PROCESSING CONTINUES.

Explanation:

While processing an AFP Statistics (AFPSTATS) report for this print data set, a shortage of virtual memory occurred that caused the AFPSTATS processing to end. The specific error is described by memory item in the message.

memory item can be any of these:

PRINT FILE INFORMATION SECTION, TITLE RECORD
PRINT FILE INFORMATION SECTION, PAGEFOOTER RECORD
PRINT FILE INFORMATION SECTION, HEADING RECORD
PRINT FILE INFORMATION SECTION, PRINTFILE RECORD
PRINT FILE INFORMATION SECTION, COMMENT RECORD
PROCESSING DETAIL SECTION, TITLE RECORD
PROCESSING DETAIL SECTION, PAGEFOOTER RECORD
PROCESSING DETAIL SECTION, HEADING RECORD
PROCESSING DETAIL SECTION, RESOURCE RECORD
PROCESSING DETAIL SECTION, EVENT RECORD
PROCESSING DETAIL SECTION, NOTE RECORD
PROCESSING DETAIL SECTION, COMMENT RECORD
RESOURCE SUMMARY BY NAME SECTION, TITLE RECORD
RESOURCE SUMMARY BY NAME SECTION, PAGEFOOTER RECORD
RESOURCE SUMMARY BY NAME SECTION, HEADING RECORD
RESOURCE SUMMARY BY NAME SECTION, SUMM-NAME RECORD
RESOURCE SUMMARY BY NAME SECTION, COMMENT RECORD
RESOURCE SUMMARY BY NAME SECTION, NOTE RECORD
RESOURCE SUMMARY BY DATA SET SECTION, TITLE RECORD
RESOURCE SUMMARY BY DATA SET SECTION, PAGEFOOTER RECORD
RESOURCE SUMMARY BY DATA SET SECTION, SECTION RECORD
RESOURCE SUMMARY BY DATA SET SECTION, SUMM-DSN RECORD
RESOURCE SUMMARY BY DATA SET SECTION, SUMM-DSN-R RECORD
RESOURCE SUMMARY BY DATA SET SECTION, COMMENT RECORD
RESOURCE SUMMARY BY DATA SET SECTION, NOTE RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, TITLE RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, PAGEFOOTER RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, SECTION RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, HEADING RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, SUMM-REF RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, SUMM-LOC RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, SUMM-DISP RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, COMMENT RECORD
RESOURCE SUMMARY BY RESOURCE TYPE SECTION, NOTE RECORD
PROCESSING SUMMARY SECTION, TITLE RECORD
PROCESSING SUMMARY SECTION, PAGEFOOTER RECORD
PROCESSING SUMMARY SECTION, SECTION RECORD
PROCESSING SUMMARY SECTION, HEADING RECORD
PROCESSING SUMMARY SECTION, SUMM-PAGE RECORD
PROCESSING SUMMARY SECTION, SUMM-EVENT RECORD
PROCESSING SUMMARY SECTION, EVENT-LIST RECORD
PROCESSING SUMMARY SECTION, COMMENT RECORD
PROCESSING SUMMARY SECTION, NOTE RECORD
INTERNAL CONTROL STRUCTURE, DATA SET LIST ITEM
INTERNAL CONTROL STRUCTURE, RESOURCE LIST ITEM
INTERNAL CONTROL STRUCTURE, EVENT LIST ITEM
INTERNAL CONTROL STRUCTURE, RESOURCE NAME LIST ITEM
INTERNAL CONTROL STRUCTURE, PROCESSING SUMMARY ANCHOR
INTERNAL CONTROL STRUCTURE, DATA SET NAME ANCHOR
INTERNAL CONTROL STRUCTURE, RESOURCE TYPE ANCHOR
INTERNAL CONTROL STRUCTURE, RESOURCE NAME ANCHOR

System action:

The processing for the AFP Statistics facility is ended and PSF continues processing the print file.

User response:

Inform your system programmer that this error occurred.

System programmer response:

There is not enough virtual memory for PSF to process the print file and produce an AFP Statistics report at the same time. Increase the amount of virtual memory specified on the REGION parameter of the PSF startup procedure.

Operator response:

If this message displays on the operator's console, inform your system programmer. AFP Statistics are not gathered while processing separator pages or the PSF message data set.

Problem determination:

Items 1, 2, 3, 8,11, 14, 15, 17, 19.

APS4001I

THE AFP STATISTICS REPORT FOR THIS PRINT FILE WAS WRITTEN TO — data set name(member name).

Explanation:

When an AFP Statistics (AFPSTATS) report is requested, this informational message is produced to tell the requester where the report was placed. PSF gives the report a member name and writes it to the PDSE specified in the PSF startup procedure.

data set name: Specifies the name of the PDSE where PSF writes the AFPSTATS report. This data set is defined in the PSF startup procedure by the AFPSTATS DD statement.
member name: The name PSF gave the report when it was placed in the PDSE named data set name. This report can be viewed or printed. For information about printing the AFPSTATS report, see PSF for z/OS: User’s Guide.

System action:

This message is placed in the message data set for the print data set when an AFPSTATS report has been requested. PSF processing continues.

User response:

Use the data set name and member name from this message to locate the requested AFPSTATS report for viewing or printing.

System programmer response:

No response is necessary.

Operator response:

If this message appears on the operator's console, inform your system programmer. AFP Statistics are not gathered or reported while processing separator pages or the PSF message data set.

Problem determination:

Items 1, 8.

APS4002I

THE AFP STATISTICS REPORT WAS REQUESTED BUT COULD NOT BE GENERATED BECAUSE THE AFPSTATS DD STATEMENT WAS NOT SPECIFIED ON THE PSF STARTUP PROCEDURE.

Explanation:

An AFP Statistics (AFPSTATS) report was requested for this print file, but the required AFPSTATS DD statement was not specified in the PSF startup procedure.

System action:

No AFPSTATS report was generated. PSF stops AFPSTATS report-related processing but continues all other processing.

User response:

Inform your system programmer of this condition. The system programmer must specify the AFPSTATS DD statement in the PSF startup procedure for PSF to produce the AFPSTATS report.

System programmer response:

The AFPSTATS DD statement must be specified in the PSF startup procedure for PSF to produce the AFPSTATS report. For information about how to allocate the PDSE for AFP Statistics facility see PSF for z/OS: Customization.

Operator response:

If this message appears on the operator's console, inform your system programmer. AFP Statistics are not gathered during processing of separator pages or the PSF message data set.

Problem determination:

Item 8.

APS4003I

THE AFP STATISTICS REPORT FACILITY IN PSF HAS ENCOUNTERED AN AFPSTATS FILE ACCESS PROBLEM AND HAS SHUT DOWN. THE DETAILS FOR THE FILE ACCESS FAILURE ARE (file access failure). ALL OTHER PSF PROCESSING CONTINUES.

Explanation:

While processing an AFP Statistics (AFPSTATS) report for this print data set, an error occurred accessing the PDSE where PSF is trying to place the AFPSTATS report. This caused AFPSTATS report processing to be ended. The specific error is described by file access failure.

file access failure can be any of these:

OPEN FAILURE, AFPSTATS DD STATEMENT
CREATING MEMBER, member_name
NO UNIQUE MEMBER
WRITE FAILURE, PRINT FILE INFORMATION SECTION
WRITE FAILURE, PROCESSING DETAIL SECTION -- FRONT MATTER
WRITE FAILURE, PROCESSING DETAIL SECTION -- RESOURCE RECORD
WRITE FAILURE, PROCESSING DETAIL SECTION -- EVENT RECORD
WRITE FAILURE, PROCESSING DETAIL SECTION -- BACK MATTER
WRITE FAILURE, RESOURCE SUMMARY BY NAME SECTION
WRITE FAILURE, RESOURCE SUMMARY BY DATA SET SECTION
WRITE FAILURE, RESOURCE SUMMARY BY RESOURCE TYPE SECTION
WRITE FAILURE, PROCESSING SUMMARY SECTION

System action:

The processing for the AFPSTATS report is stopped and PSF continues processing the print file.

User response:

Inform your system programmer that this error occurred.

System programmer response:

There is an error in the way the AFPSTATS DD statement was specified or in the PDSE specified by the AFPSTATS DD statement. This message could be the result of an error in the AFPSTATS repository. The error could be caused by one of these:

The AFPSTATS repository is full.
The volume that contains the AFPSTATS repository is full.
There is an I/O error on the volume containing the AFPSTATS repository.

In order to keep PSF running in the event of an error in the AFPSTATS data set, PSF traps the data set error, produces this message, ends any further AFPSTATS processing, and continues to process the print file.

Correct the AFPSTATS DD statement or the PDSE error and try again. See PSF for z/OS: Customization for information about allocating this PDSE.

Operator response:

If this message displays on the operator's console, inform your system programmer. AFP Statistics are not gathered while processing separator pages or the PSF message data set.

Problem determination:

Items 1, 2, 3, 8,11, 14, 15, 17, 19.

APS4004I

THE AFP STATISTICS REPORT FACILITY IN PSF HAS ENCOUNTERED AN INTERNAL LOGIC ERROR AND HAS SHUT DOWN. THE SPECIFIC ERROR WAS (logic error). ALL OTHER PSF PROCESSING CONTINUES.

Explanation:

While processing an AFP Statistics (AFPSTATS) report for this print data set, an internal logic error occurred that caused the AFPSTATS processing to be ended. The specific error is described by logic error.

logic error can be any of these:

PARAMETERS NOT VALID, APSGARSR
PARAMETERS NOT VALID, APSGAEVR
PARAMETERS NOT VALID, APSGARES
PARAMETERS NOT VALID, APSGATRM
PARAMETERS NOT VALID, APSGARLD
PARAMETERS NOT VALID, APSRAUST
PARAMETERS NOT VALID, APSRASFT
PARAMETERS NOT VALID, APSGAMEX
PARAMETERS NOT VALID, APSGAMLD
PARAMETERS NOT VALID, APSGAINC
PARAMETERS NOT VALID, APSGADEX
PARAMETERS NOT VALID, APSGAJCL
PARAMETERS NOT VALID, APSGAACT
PARAMETERS NOT VALID, APSGAFEX
PARAMETERS NOT VALID, APSGAFRF
INTERFACE ERROR, APSGAPFR
INTERFACE ERROR, APSGARSR
INTERFACE ERROR, APSGAEVR
INTERFACE ERROR, APSGASNM
INTERFACE ERROR, APSGASRT
INTERFACE ERROR, APSGASPR
INTERFACE ERROR, APSGAEND

System action:

The processing for the AFP Statistics facility is stopped and PSF continues processing the print file.

User response:

Inform your system programmer that this error occurred.

System programmer response:

This is most likely an internal PSF error. Contact your service representative in the IBM Support Center or use your electronic link with IBM service for assistance regarding this error code.

Operator response:

If this message displays on the operator's console, inform your system programmer. AFP Statistics are not gathered while processing separator pages or the PSF message data set.

Problem determination:

Items 1, 2, 3, 8,11, 14, 15, 17, 19.

APS4400I

UNICODE CONVERSION FAILURE: FACILITY RETURNED WITH RETURN CODE=return code AND REASON CODE=reason code. CONVERTING STRING FROM INPUT ENCODING=from ccsid TO OUTPUT ENCODING=to ccsid.

Explanation:

PSF encountered an error when using the ZCONV Unicode data transform facility. PSF might have to change the Unicode encoding for resource names. This is necessary because various system facilities might require the name to be in a different Unicode encoding. For example, a TrueType font name might have been specified in Unicode encoding UTF-16 (CCSID=1200) but PSF might be printing a message that wants to give the font name in EBCDIC (CCSID=500). In this case, PSF would have to change the encoding of the font name. For a list of return and reason codes, see z/OS Unicode Services User’s Guide and Reference.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the data object resource was specified. In the associated environment messages produced for this error, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

This problem is generally caused by one of these:

The Unicode encoding of the font name was not correct. Either the to ccsid, the GCSGID and CPGID equivalent of the to ccsid, or the from ccsid were not specified correctly in the Map Data Resource (MDR) structured field.
The font name was not encoded as indicated in the to ccsid or GCSGID and CPGID of the MDR. There was a mismatch between the actual name encoding and the specification of the name encoding.
The z/OS system was not properly prepared to handle this particular name encoding transform. A transform from from ccsid to to ccsid is not currently enabled on the system. Contact your system programmer for assistance in correcting this condition.

System programmer response:

Make sure the z/OS system is properly enabled for Unicode data transforms and that the correct transforms, both to and from, have been initialized. See PSF for z/OS: Customization for more information about setting up the ZCONV facility.

Operator response:

If this message displays on the operator's console, it indicates that PSF is processing a TrueType or OpenType font request for separator pages, message pages, or a default resource specified in the PSF startup procedure. Inform your system programmer.

Problem determination:

Items 2, 8, 17, 18, 19.

APS4401I

CDRA CONVERSION FAILURE: FACILITY RETURNED WITH RETURN CODE = return code.

Explanation:

When using Character Data Representation Architecture (CDRA) services to convert a resource name, PSF must convert a graphic character set global identifier (GCSGID) and code page global identifier (CPGID) encoding pair into a coded character set identifier (CCSID). However, the conversion to a CCSID failed. The possible return codes from the system's conversion services are:

X'00060001'—The CCSID resource repository was not found.
X'00060002'—The CCSID resource repository is currently unavailable.
X'00070001'—The system CCSID resource repository accessed by the function was found not to be valid in structure.
All other return codes—logic error.

System action:

PSF produces this error message and then produces an abend with a system completion code 024 and abend reason code 0E51.

User response:

Inform your system programmer.

System programmer response:

If this is deemed a logic error, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Operator response:

Problem determination:

Items 2, 8, 9, 17, 19.

APS4402I

REQUESTED TRANSFORM OF INPUT DATA FROM GCSGID(gcsgid)-CPGID(cpgid) TO CCSID(ccsid) CANNOT BE PERFORMED.

Explanation:

PSF received a request to process a TrueType or OpenType font, data object resource, or color management resource with a Unicode name encoding GCSGID of gcsgid, and CPGID of cpgid. PSF needs to transform this name to a Unicode encoding of ccsid, and cannot process this request unless PSF is Unicode-enabled. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this request.

System action:

PSF was unable to process the necessary resources to print this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the data object was specified. In the associated environment message produced for this error, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

Contact your system programmer.

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF is processing separator pages, message pages, or a default resource specified in the PSF startup procedure that requires TrueType and OpenType fonts, data object resources, or color management resources, but PSF has not been Unicode-enabled. Inform your system programmer.

Problem determination:

None.

APS4403I

THE REQUESTED TRANSFORM OF INPUT DATA FROM CCSID(ccsid) TO CCSID(ccsid) CANNOT BE PERFORMED.

Explanation:

PSF must convert input data to the specified encoding in order to continue processing, but cannot do so because it is not enabled for Unicode processing. By default, PSF is enabled for Unicode processing; however, because of a UNIX System Services error, PSF cannot use conversion services to process this request.

If the output CCSID is 1200 or 500, the input data is a TrueType or OpenType font, data object resource, or color management resource name. If the output CCSID is anything else, mixed single-byte or double-byte EBCDIC data is being converted to mixed single-byte or double-byte ASCII data for a QR Code bar code.

System action:

PSF is unable to continue processing this page. PSF prints this error message and associated environment messages.

The action taken by PSF depends on where in the data stream the conversion error occurred. In the associated environment message, PSF identifies the location of the error within the data stream as well as the disposition of the error.

User response:

Contact your system programmer.

System programmer response:

Operator response:

Problem determination:

None.

APS4500I

DYNAMIC ALLOCATION FAILED FOR TRACE DATASET dsname, RETURN CODE retcode, REASON CODE reason code.

Explanation:

PSF tried to allocate the requested trace data set, but received the error indicated. One possible cause for this message is that the PSF trace data set did not exist before the PSF FSA was started. Another possible cause is that the data set was not cataloged.

dsname is the PSF trace data set name specified in the Printer Inventory fsa-trace-dsname parameter. retcode and reason code are the values returned to PSF from the system dynamic allocation function and might help diagnose this problem.

System action:

PSF initialization continues with no external tracing.

User response:

No response is necessary.

System programmer response:

Correct the error and restart PSF. For more information on tracing, see PSF for z/OS: Diagnosis.

Operator response:

No response is necessary.

Problem determination:

None.