APS300 to APS399

APS300I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF SKIPPING PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number IS 0.

Explanation:

The current record contains a control character that indicates a skip to a Line Descriptor (LND) structured field with a specific channel control. However, the LND structured field identified in this message had a value of 0 in its Next Line Descriptor IF SKIPPING parameter. The LND structured field is in the page definition.

System action:

User response:

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

System programmer response:

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

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 2, 17, 27.

APS301I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF SKIPPING PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number IS parameter value. THIS EXCEEDS THE LNC STRUCTURED FIELD COUNT VALUE OF parameter value.

Explanation:

In the Line Descriptor (LND) structured field identified in this message, the value of the next LND IF SKIPPING parameter is greater than the total number of LND structured fields in the page definition.

System action:

PSF stops processing the current data set and issues additional messages identifying the processing environment in which the error occurred.

User response:

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

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS307I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: IN LND STRUCTURED FIELD NUMBER structured field number, THE REUSE RECORD FLAG WAS SET BUT THE NEXT LINE DESCRIPTOR IF REUSING DATA PARAMETER WAS 0.

Explanation:

In the Line Descriptor (LND) structured field identified in this message, the Reuse Record flag had a value of B'1', indicating that the line data being processed in this LND structured field should be reused and processed. The Next Line Descriptor If Reusing Data parameter should point to the LND structured field used to continue processing. However, the value for the Reusing Data parameter was X'0000', indicating the end of the chain. The LND structured field is contained in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS308I

THE PRINTABLE AREA IS TOO SMALL TO PRINT MESSAGES WITH THE FONT SPECIFIED.

Explanation:

A check was made to determine whether the messages would fit in the printable area when printed in the specified font on the paper size currently in the printer. Either fewer than 10 characters would fit on a line, or PSF calculated an incorrect value for the maximum baseline position. The values for the maximum baseline position are obtained from the printer; an incorrect value could indicate a microcode error that would cause PSF not to print messages. A value of fewer than 10 characters per line is too small and would also cause PSF not to print messages.

System action:

The messages were not printed.

User response:

Inform your system programmer that this error occurred.

System programmer response:

If messages are to be printed, select a form, a logical page size, and a font with a character increment that allows messages to fit in the printable area. The form definition or page definition selected to process messages might be incorrect, or the font selected might be too large for the page size specified in the form definition or the page definition.

To determine the number of characters that fit on a line, determine the minimum width of either the logical page or the printable area on the physical page. From it, subtract the maximum inline position of the Line Descriptor (LND) structured field, and the form definition offset, plus twice the horizontal adjustment. Divide the result by the character increment for the font.

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

Items 1, 17, 27.

APS309I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE REPEATING GROUP LENGTH PARAMETER VALUE IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. Either the Length of Repeating Groups parameter is zero, or the length of the repeating group data is not a multiple of the size specified in that parameter. The CCP structured field is in the page definition.

System action:

User response:

Determine whether the structured field is correct. For more information about the structured field, see Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884. If the structured field is incorrect and was not created by an IBM licensed program, correct the error and resubmit the print request. If the structured field is incorrect and was created by an IBM licensed program, notify your system programmer. If the structured field is correct, the error could be a PSF logic error. In this case, notify your system programmer of this error.

System programmer response:

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 error messages. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS310I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE COUNT PARAMETER VALUE IN THE LNC STRUCTURED FIELD WAS 0.

Explanation:

The Count parameter in the Line Descriptor Count (LNC) structured field in the data map of the page definition had a value of zero.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS312I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE SIZE PARAMETER VALUE IN THE FDS STRUCTURED FIELD WAS 0.

Explanation:

The Size parameter in the Fixed Data Size (FDS) structured field has a value of 0. The FDS structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS314I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NUMBER OF REPEATING GROUPS PARAMETER VALUE IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. Either the Number of Repeating Groups parameter in the CCP structured field is zero, or the number of repeating groups does not match the number specified in the parameter. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS315I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF SPACING PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number IS 0.

Explanation:

The logical-record control character indicates that the Next Line Descriptor If Spacing parameter should be followed. However, in the Line Descriptor (LND) structured field identified in this message, the Next Line Descriptor If Spacing parameter value was zero. The LND structured field is contained in the page definition.

System action:

PSF stops processing the current data set and issues additional messages that identify the processing environment when the error was found. Refer Mixed Object Document Content Architecture Reference, AFPC-0004.

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS316I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF SPACING PARAMETER IN LND STRUCTURED FIELD NUMBER structured field number IS parameter value. THIS VALUE IS TOO LARGE.

Explanation:

The logical record control character indicates that the Next Line Descriptor If Spacing parameter in the Line Descriptor (LND) structured field should be followed. However, in the Line Descriptor (LND) structured field identified in this message, the Next Line Descriptor If Spacing parameter value was greater than the total number of line descriptors in the data map. The LND structured field is contained in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS317I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE LENGTH OF COMPARISON STRING PARAMETER VALUE IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. Either the Length of Comparison String parameter is zero, or the length of the comparison string data does not match the length of a repeating group minus the fixed lengths of the remaining fields of the repeating group. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS319I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number HAS A NULL VALUE SPECIFIED IN THE SUPPRESSION TOKEN NAME PARAMETER. A NULL VALUE IS NOT VALID.

Explanation:

The Suppression Token Name parameter in the Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field in the page definition has a null value. A null value is any value that contains X'FFFF' in the first 2 bytes.

System action:

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the page definition with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If 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, 17, 27.

APS320I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE IDENTIFIER identifier1 SPECIFIED IN THE NEXT CCP IDENTIFIER PARAMETER IN CCP STRUCTURED FIELD identifier2 WAS NOT FOUND.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Next Conditional Processing Control Identifier parameter in the CCP structured field specifies the identifier used to find a CCP if the CCP structured fields are chained. The identifier must match a value specified in the CCP Identifier parameter of another CCP in the same page definition. The identifier specified in the Next CCP Identifier parameter did not match the CCP Identifier of any CCPs in the page definition. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS321I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE TIMING OF ACTION PARAMETER VALUE value IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Timing of Action parameter in one of the repeating groups of the CCP structured field contains an incorrect value. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS322I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE MEDIUM MAP ACTION PARAMETER VALUE value IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Medium Map Action parameter in one of the repeating groups of the CCP structured field contains an incorrect value. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS323I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE DATA MAP ACTION PARAMETER VALUE value IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Data Map Action parameter in one of the repeating groups of the CCP structured field contains an incorrect value. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS324I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE COMPARISON PARAMETER VALUE value IN CCP STRUCTURED FIELD CCP identifier IS NOT VALID.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Comparison parameter in one of the repeating groups of the CCP structured field contains an incorrect value. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS326I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE DATA MAP ' data map name' SPECIFIED IN THE DATA MAP NAME PARAMETER OF CCP STRUCTURED FIELD CCP identifier WAS NOT FOUND.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Data Map Name parameter in one of the repeating groups of the CCP structured field specifies the token name of a data map used to find a data map in the page definition. The name must match the value specified in the Token Name parameter in one of the Begin Data Map (BDM) structured fields in the current page definition. No data map with name data map name was found in the page definition. The CCP structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS327I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF REUSING DATA PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number WILL CAUSE AN INFINITE LOOP.

Explanation:

The Next Line Descriptor If Reusing Data parameter in the Line Descriptor (LND) structured field identified in this message caused an infinite-loop condition. The LND structured field is contained in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS328I

DATA IN A FORMDEF RESOURCE IS NOT VALID: MEDIUM MAP medium map name SPECIFIES A CONDITIONAL EJECT TO A PARTITION, BUT THE PARTITION DOES NOT EXIST.

Explanation:

The Begin Medium Map (BMM) structured field specified a conditional eject to a partition that does not exist in the Page Position (PGP) Format 2 structured field. The BMM structured field specified either a conditional eject to the next front side partition or a conditional eject to the next back side partition, but the PGP structured field does not contain a repeating group specifying a partition on the requested side. The BMM and PGP structured fields are in the form definition.

System action:

The form definition containing the error is not used, and one of these occurs:

If the error is in the default form definition, or a form definition specified for printing messages or separator pages, PSF is not started.
If the error is in a form definition specified on the user's JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

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

System programmer response:

Operator response:

Problem determination:

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

APS329I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF REUSING DATA PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number IS parameter value1. THIS EXCEEDS THE LNC STRUCTURED FIELD COUNT VALUE OF parameter value2.

Explanation:

The Next Line Descriptor If Reusing Data parameter in the Line Descriptor (LND) structured field identified in this message has an incorrect value. The value is greater than the Count parameter in the Line Descriptor Count (LNC) structured field in the current data map. The LNC and LND structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS330I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: WHEN THE DATA START POSITION VALUE IS ADDED TO THE DATA LENGTH VALUE IN LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number, IT EXCEEDS THE FDS STRUCTURED FIELD SIZE VALUE OF parameter value.

Explanation:

The Use Fixed Data flag in byte 0 in the Line Descriptor (LND) structured field, in byte 11 in the Record Descriptor (RCD) structured field, or in byte 1 in the XML Descriptor (XMD) was set to B'1'. This indicates that data from Fixed Data Text (FDX) structured fields is to be added to the data placed within the page by the LND, RCD, or XMD structured field. The FDX, XMD, RCD, and LND structured fields are in the page definition.

The Data Start Position parameter in the LND, RCD, or XMD structured field indicates the offset of the first byte of data. The Data Length parameter specifies how many bytes of FDX are to be placed within the page. This error was caused when these two parameters specified more data than the FDX structured fields contain. The number of bytes of data in the FDX structured fields can be found in the Size parameter of the Fixed Data Size (FDS) structured field.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS331I

A FORMDEF RESOURCE SPECIFIES PAGE ROTATION IN THE PGP STRUCTURED FIELD, BUT PAGE ROTATION IS NOT SUPPORTED BY THE PRINTER. THE PAGE ROTATION IS IGNORED. THIS MESSAGE IS ONLY ISSUED ONCE PER PRINT DATA SET.

Explanation:

A medium map or Document Environment Group in the current form definition contains a Page Position (PGP) Format 2 structured field with a repeating group that requests page rotation in the PGorient parameter, but the printer does not support page rotation.

System action:

The page rotation is ignored, and processing continues. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

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

System programmer response:

Operator response:

Problem determination:

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

APS334I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE AMOUNT OF FIXED DATA RECEIVED DID NOT AGREE WITH THE VALUE SPECIFIED IN THE FDS STRUCTURED FIELD SIZE PARAMETER.

Explanation:

The Fixed Data Text (FDX) structured field more bytes of data than was specified in the Size parameter of the Fixed Data Size (FDS) structured field. The FDS and FDX structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS335I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE MEDIUM MAP 'medium map name' SPECIFIED IN THE MEDIUM MAP NAME PARAMETER OF CCP STRUCTURED FIELD CCP identifier WAS NOT FOUND.

Explanation:

The Conditional Processing Control (CCP) structured field has an incorrect value. The Medium Map Name parameter in one of the repeating groups of the CCP structured field specifies the token name of a medium map used to find a medium map in the form definition. The name must match the value specified in the Token Name parameter in one of the Begin Medium Map (BMM) structured fields in the current form definition. No medium map with name medium map name was found in the form definition. The CCP structured field is in the page definition.

System action:

PSF stops processing the current data set and issues additional messages that identify the processing environment when the error was found. PSF releases the current data set back to JES and requests that it be held by the system. See Mixed Object Document Content Architecture Reference, AFPC-0004.

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS337I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: IN LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number, THE CONDITIONAL PROCESSING FLAG WAS SET BUT THE CONDITIONAL PROCESSING CONTROL IDENTIFIER WAS ZERO.

Explanation:

In the Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field, the Conditional Processing flag had a value of B'1', indicating that the line data to be processed by this LND, RCD, or XMD structured field is to be compared with a value specified in a Conditional Processing Control (CCP) structured field. The CCP Identifier parameter in the LND, RCD, or XMD structured field is used to find one of the CCP structured fields in the current page definition. This parameter was set to 0, which is not a valid value if the Conditional Processing flag is on. The LND, RCD, XMD, and CCP structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS339I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE IDENTIFIER identifier SPECIFIED IN THE CONDITIONAL PROCESSING CONTROL IDENTIFIER PARAMETER IN LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number WAS NOT FOUND.

Explanation:

In the Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field, the Conditional Processing flag had a value of B'1', indicating that the line data to be processed by this LND, RCD, or XMD structured field is to be compared with a value specified in a Conditional Processing Control (CCP) structured field. The CCP Identifier parameter in the LND, RCD, or XMD structured field is used to find one of the CCP structured fields in the current page definition. However, the identifier specified in identifier does not match the value specified in the CCP Identifier parameter in any of the CCP structured fields in the current page definition. The LND, RCD, XMD, and CCP structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS340I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF CONDITIONAL PROCESSING PARAMETER VALUE IN LND, RCD, or XMD STRUCTURED FIELD NUMBER structured field number IS value1. THIS EXCEEDS THE LNC STRUCTURED FIELD COUNT VALUE OF value2.

Explanation:

The Next Line Descriptor If Conditional Processing parameter in the Line Descriptor (LND), Record Format Descriptor (RCD), or XML Descriptor (XMD) structured field has an incorrect value. The value is greater than the Count parameter in the Line Descriptor Count (LNC) structured field in the current data map. The LNC, LND, RCD, and XMD structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS342I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NEXT LINE DESCRIPTOR IF CONDITIONAL PROCESSING PARAMETER VALUE IN LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number WILL CAUSE AN INFINITE LOOP.

Explanation:

The Next Line Descriptor If Conditional Processing parameter in the Line Descriptor (LND), Record Format Descriptor (RCD), or XML Descriptor (XMD) structured field caused an infinite-loop condition. The LND, RCD, and XMD structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS343I

DATA IN AN INPUT RECORD OR PAGEDEF RESOURCE IS NOT VALID: RELATIVE POSITIONING PLACED DATA OUTSIDE THE LOGICAL PAGE IN THE NEGATIVE Y DIRECTION. THE PRIOR AND CURRENT LND, RCD, OR XMD STRUCTURED FIELD NUMBERS ARE: structured field number1 AND structured field number2.

Explanation:

When relative positioning is being used on a Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field, the relative position specified for the Y direction can be a negative value. The current LND, RCD, or XMD ( structured field number2) is trying to position data outside of the logical page by using a negative value. The prior LND, RCD, or XMD position ( structured field number1) defines the baseline position from which the relative offset of the current LND, RCD, or XMD is measured.

System action:

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

User response:

System programmer response:

Operator response:

Problem determination:

None.

APS344I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE NUMBER OF LND OR RCD STRUCTURED FIELDS DOES NOT MATCH THE VALUE SPECIFIED IN THE LNC STRUCTURED FIELD.

Explanation:

The number of Line Descriptor (LND) or Record Descriptor (RCD) structured fields found in a page definition is either greater than or less than the value specified in the Line Descriptor Count (LNC) structured field. The LND, RCD, and LNC structured fields are in the page definition.

System action:

PSF stops processing the current data set and issues additional messages identifying the processing environment in which the error occurred.

User response:

System programmer response:

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

Operator response:

Problem determination:

Items 2, 17, 27.

APS345I

MESSAGE ID = message identifier EXCEEDS MAXIMUM LENGTH. RECORD SEQUENCE NUMBER = sequence number.

Explanation:

The length of the message text for the message ID is greater than the maximum message length of 1000 bytes.

System action:

The message is printed to the length limit. Processing of the data set continues.

User response:

No response is necessary.

System programmer response:

If you suspect a PSF logic error, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center.

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS346I

DATA IN AN INPUT RECORD OR PAGEDEF RESOURCE IS NOT VALID: A SKIP TO A NONEXISTENT CHANNEL = channel ON RECORD NUMBER = record number WAS DETECTED WITHIN THE LND STRUCTURED FIELDS. OUTPUT WAS FORCED TO SINGLE SPACING, WHICH MAY CAUSE BLANK PAGES.

Explanation:

An attempt was made to skip to a channel not defined in the current data map. The Line Descriptor (LND) structured fields in the page definition are not valid. During scanning, the entire Next Line Descriptor If Skipping parameter could not be followed because the End Page If Skipping flag was set in an LND structured field. This created an infinite loop on the same input record. The LND structured field is in the page definition.

System action:

The record containing the error was forced to single spacing. When forced single spacing occurs, the carriage control character on the record is ignored. The record is treated as if a X'09' machine control character or a X'40' (blank) ANSI control character was specified in the record that caused the error. The record number specified is relative to the input data stream and can be different for multiple transmissions of the data set.

User response:

System programmer response:

If the error involves separator pages, 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 PSF cannot be initialized or cannot print error messages. Notify your system programmer.

Problem determination:

Items 2, 17, 27.

APS347I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: A DXD STRUCTURED FIELD CONTAINS AN INCORRECT PARAMETER VALUE.

Explanation:

The Data Map Transmission Subcase Descriptor (DXD) structured field does not contain a value of X'000100FF'. The DXD structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS350I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: IN LND OR RCD STRUCTURED FIELD NUMBER structured field number, THE SHIFT-OUT CODED FONT LOCAL IDENTIFIER WAS NON-ZERO BUT THE GENERATE FONT CHANGE FLAG WAS NOT SET.

Explanation:

In the Line Descriptor (LND) or Record Descriptor (RCD) structured field identified in this message, the Shift-out Coded Font Identifier was nonzero. The Generate Font Change flag should be set to indicate that the Primary Coded Font Local Identifier should be used whenever a shift-in code is processed. However, the Generate Font Change flag had a value of B'0'. The LND or RCD structured field is in the page definition.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS352I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: BAR CODE GENERATION WAS REQUESTED ON LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number, BUT THE PRINTER DOES NOT SUPPORT BAR CODE OBJECTS. THIS MESSAGE IS ONLY ISSUED ONCE PER PRINT DATA SET.

Explanation:

A Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field in a page definition has requested PSF to generate a bar code object from the line data, but the printer does not support bar code objects.

System action:

PSF ignores the request and continues processing the data set.

User response:

To print the data set and have PSF generate bar code objects, submit the print job to a printer that supports bar code objects. For more information about a printer’s support for bar code objects, see the documentation provided with the printer.

System programmer response:

If the page definition is for a separator page, the message data set, or the default page definition for the user print data sets defined in the PSF startup procedure, delete the option from the page definition that requests that a bar code be generated.

Operator response:

Problem determination:

None.

APS353I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE DATA LENGTH PARAMETER VALUE IN LND STRUCTURED FIELD NUMBER structured field number DOES NOT MATCH THE LENGTH OF COMPARISON STRING PARAMETER VALUE IN CCP STRUCTURED FIELD CCP identifier.

Explanation:

In the Line Descriptor (LND) structured field, the value of the Data Length parameter is used in identifying the field of the current input record for which Conditional Processing is to be performed. This field is to be compared with the Comparison String specified in the Conditional Processing Control (CCP) structured field. In the data set you submitted, however, the length specified in the Data Length parameter in the LND structured field does not match the length specified in the Length of Comparison String parameter of the CCP structured field. The LND and CCP structured fields are in the page definition.

System action:

User response:

System programmer response:

Operator response:

If this message displays on the operator's console, it indicates that PSF cannot be initialized. Inform your system programmer that this error occurred.

Problem determination:

Items 2, 17, 27.

APS355I

DATA IN PAGEDEF RESOURCE IS NOT VALID: A PAGE OVERLAY WAS REQUESTED IN LND OR RCD STRUCTURED FIELD NUMBER structured field number, BUT THE PRINTER DOES NOT SUPPORT PAGE OVERLAYS. THIS MESSAGE IS ONLY ISSUED ONCE PER PRINT DATA SET.

Explanation:

An overlay has been requested by a Line Descriptor (LND) or Record Descriptor (RCD) structured field within the page definition, but the printer does not support page overlays.

System action:

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

User response:

To print the data set containing the page overlay, submit the print job to a printer that supports page overlays. For more information about a printer’s support for page overlays, see the documentation provided with the printer.

System programmer response:

If the page definition is for a separator page, the message data set, or the default page definition for the user print data sets defined in the PSF startup procedure, delete the page overlay from the page definition.

Operator response:

Problem determination:

None.

APS360I

AN OUTPUT BIN WAS REQUESTED FOR THE JOB, BUT EITHER THE PRINTER DOES NOT SUPPORT BIN SPECIFICATION OR THE BIN SPECIFIED WAS NOT AVAILABLE. THE PRINTER DEFAULT BIN WAS USED.

Explanation:

The output bin specified by the OUTBIN keyword on the JCL OUTPUT statement or in the form definition is not available, or the device does not support the specification of an output bin.

System action:

PSF continues processing, sending paper to the printer default output bin.

User response:

If the output is not acceptable, submit the print request to a printer that supports the specification of an output bin and has the output bin available, or ensure that the bin is enabled on the original printer before resubmitting the print request.

System programmer response:

Inform your system programmer that this error occurred.

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

Items 1, 2, 8, 19.

APS361I

THE INPUT BIN WITH COMPONENT ID component_id, MEDIA NAME media_name, BIN NUMBER bin_number IS NOT SUPPORTED OR NOT ENABLED ON THE PRINTER. MEDIA FIDELITY REQUESTED THE JOB TO BE TERMINATED WITH NO ALTERNATE BIN SUBSTITUTION.

Explanation:

The Medium Modification Control (MMC) structured field specified a media selection that does not exist on the selected printer or is not enabled. A value of *** for any of the three values means that piece of information was not provided by the MMC structured field. The input bin is selected by a media-source selector keyword with or without media-type local ID keywords in the MMC structured field. The media-type local ID keywords specify the ID of a Map Media Type (MMT) structured field that contains an Object Identifier (OID) with or without a Media Name. The MMC and MMT structured fields are in the form definition.

System action:

Processing of the current data set is ended.

User response:

Submit the print request to a printer that supports the specified media selection. If you want to use the original printer, and if you created the structured fields for the form definition, specify a supported bin in the MMC structured field. For more information about the MMC structured field, see Mixed Object Document Content Architecture Reference, AFPC-0004. If the structured field contains the component ID, media name, or number of a supported bin, the error might be a PSF logic error. If you used a program to create the structured fields for the form definition, ensure that the input to that program specified a supported bin. If it did, consult your system programmer.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 13, 17, 19.

APS362I

SYSTEM ACTION TAKEN: THE ERRORS LISTED OCCURRED DURING THE PROCESSING OF INLINE RESOURCES. PROCESSING OF THE DATA SET WAS TERMINATED.

Explanation:

This message is issued in addition to a message describing an error that occurred during the processing of an inline resource. Other error messages issued by PSF describe the precise error condition.

System action:

PSF stops processing and printing the data set.

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:

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

Problem determination:

Items 2, 17.

APS363I

MULTIPLE COPIES OF THE MESSAGE DATA SET WERE REQUESTED FROM DIFFERENT INPUT BINS BUT THE BIN ATTRIBUTES DID NOT MATCH.

Explanation:

PSF guarantees that at least the first 10 characters of each message are printed on the message page through a special message formatting routine. If multiple copies of message pages are printed from different input bins, and each input bin being used has different attributes such as paper length, paper width, x-extent, y-extent, x-offset, y-offset, or media type (envelope, manual, or normal), PSF cannot guarantee that the first 10 characters of each message are printed on all copies of the message page.

System action:

The messages were not printed.

User response:

Inform your system programmer that this error occurred.

System programmer response:

If messages are to be printed, specify a form definition that specifies only a single copy of the message page, or copies from bins with attributes that are the same.

Operator response:

Inform your system programmer that this error occurred.

Problem determination:

Items 1, 17, 27.

APS364I

THE SET OF MODIFICATIONS SPECIFIED IN THE MCC STRUCTURED FIELD INDICATES DIFFERENT SELECT INPUT SOURCE VALUES FOR THE FRONT AND BACK SIDES OF A DUPLEX SHEET.

Explanation:

The Medium Modification Control (MMC) structured fields referenced by the Medium Copy Count (MCC) structured field repeating groups specify different input-source values or media-type local ID values along with either tumble or normal duplex. This results in an attempt to print the front and back sides of a sheet from different input bins.

System action:

The form definition containing the error is not used, and one of these occurs:

If the error is in the default form definition, or a form definition specified for printing messages or separator pages, PSF is not started.
If the error is in a form definition specified on the user’s JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment when the error was found.

User response:

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

System programmer response:

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, 13, 15c, 17, 19.

APS365I

AN ENVELOPE OR MANUAL FEED INPUT BIN WITH COMPONENT ID componentID, MEDIA NAME media name, BIN NUMBER bin number WAS REQUESTED, BUT IS NOT AVAILABLE ON THE PRINTER.

Explanation:

The Medium Modification Control (MMC) structured field requested an envelope or manual feed bin, but no bins installed on the printer support the requested bin type. A value of *** for any of the three values means that piece of information was not provided by the MMC structured field. The input bin is selected by a media-source selector keyword with or without media-type local ID keywords in the MMC structured field. The media-type local ID keywords specify the ID of a Map Media Type (MMT) structured field that contains an Object Identifier (OID) with or without a Media Name. The MMC and MMT structured fields are in the form definition.

System action:

Processing of the current data set is ended.

User response:

If an envelope or manual feed bin is desired, submit the print request to a printer that supports the requested bin type. If you want to use the original printer without an envelope or manual feed bin, and if you created the structured fields for the form definition, do not specify an envelope or manual feed bin type. For more information about the MMC structured field, see Mixed Object Document Content Architecture Reference, AFPC-0004.

If you used a program to create the structured field for the form definition, ensure that the input to that program specifies that you do not want an envelope or manual bin. If you did not request an envelope or manual bin in your form definition, the error might be a PSF logic error; consult your system programmer.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS366I

DATA IN AN INPUT RECORD OR PAGEDEF RESOURCE IS NOT VALID: THE ORIENTATION USED WITH RELATIVE POSITIONING IS DIFFERENT THAN THE LAST ORIENTATION USED FOR PRINTING. THE PRIOR AND CURRENT LND, RCD, OR XMD STRUCTURED FIELD NUMBERS ARE: structured field number1 AND structured field number2.

Explanation:

When relative positioning is being used on a Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field, the text orientation field of the current LND, RCD, or XMD (structured field number2) must match the text orientation of the LND, RCD, or XMD (structured field number1) that was last used for positioning data. The prior LND, RCD, or XMD position defines the baseline position from which the relative offset of the current LND, RCD, or XMD is measured.

System action:

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

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS367I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE OUTPUT OPTION SPECIFIED IN AN IOB STRUCTURED FIELD WITH RESOURCE LOCAL ID identifier IS NOT VALID OR IS UNSUPPORTED. THE IOB IS INCLUDED WITH LND, RCD, OR XMD STRUCTURED FIELD NUMBER structured field number.

Explanation:

The Include Object (IOB) structured field in error contained an Output Option value that is not valid, or the printer does not support the Output Option value. The IOB is included by using the Line Descriptor (LND), Record Descriptor (RCD), or XML Descriptor (XMD) structured field identified in this message. The IOB, LND, RCD, and XMD structured fields are contained in the page definition.

System action:

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

User response:

If you created the structured fields for the resource, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the 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.

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 for the message data set in the PSF startup procedure. Inform your system programmer.

Problem determination:

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

APS368I

DATA IN A PAGEDEF RESOURCE IS NOT VALID: THE RESOURCE LOCAL ID identifier SPECIFIED IN THE EXTENDED RESOURCE LOCAL ID TRIPLET ON LND OR RCD STRUCTURED FIELD NUMBER structured field number WAS NOT FOUND.

Explanation:

In the Line Descriptor (LND) or Record Descriptor (RCD) structured field, an Extended Resource Local Identifier triplet specifies a local identifier of an Include Object (IOB) structured field. This IOB structured field includes an object when the LND or RCD is used for printing. However, the local identifier specified on the LND or RCD does not match any of the IOB structured fields in the page definition.

System action:

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

User response:

System programmer response:

Operator response:

Problem determination:

Items 2, 17, 27.

APS369I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: STRUCTURED FIELD structured field HAS AN INCORRECT OBJECT CLASS VALUE IN AN OBJECT CLASSIFICATION TRIPLET.

Explanation:

The Object Classification (X'10') triplet in the structured field specified in the message has an incorrect object class value. Possible incorrect class values for each structured field are:

Map Data Resource (MDR)
- Non-presentation object container is included in a repeating group.
- Object container or IOCA embedded in a page or overlay has a data object font mapped in the Object Environment Group.
Include Object (IOB) or Preprocess Presentation Object (PPO)
- Non-presentation object container, data object font (DOF), or non-DOF secondary resource is specified.

System action:

PSF stops processing the current page, attempts to find the end of the current page, and then tries to resume printing on the next page. If PSF cannot find the end of the page, it stops printing the data set.

If this error occurs in a resource or a page definition, PSF stops processing the data set.

If this error occurs in a Resource Environment Group (REG), PSF stops processing the REG and continues processing the data set.

User response:

If you created the structured field, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If you used a program to create the structured field, contact your system programmer. If the object class is valid for the structured field, this release of PSF does not support this function.

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. 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:

No response is necessary.

Problem determination:

Items 2, 13, 17.

APS370I

AN OUTLINE FONT WAS SPECIFIED FOR A PRINTER THAT DOES NOT SUPPORT OUTLINE FONTS.

Explanation:

A request to use an outline font code page or font character set was made to a printer that does not support outline fonts. PSF detected this error while processing a code page or a font character set.

System action:

User response:

Ensure that data sets requiring outline fonts are routed to a printer model or configuration that can process them. Otherwise, do not use outline fonts.

System programmer response:

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, 8, 19.

APS371I

A DOUBLE-BYTE OUTLINE FONT WAS SPECIFIED FOR A PRINTER THAT DOES NOT SUPPORT DOUBLE-BYTE OUTLINE FONTS.

Explanation:

A request to use a double-byte outline font code page or a font character set was made to a printer that does not support double-byte outline fonts. PSF detected this error while processing a code page or a font character set.

System action:

PSF cannot print the current page. PSF attempts to locate the end of the current page and resume printing on the next page. If the end of the current page cannot be located, PSF stops printing the data set. PSF issues a message identifying the position of the structured field in the input data stream or resource. PSF issues additional messages identifying the processing environment when the error was found.

User response:

Ensure that documents requiring double-byte outline fonts are sent to a printer that can process them. Otherwise, do not use double-byte outline fonts.

System programmer response:

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 1, 2, 8, 19.

APS372I

DATA IN A FONT RESOURCE IS NOT VALID: A FONT CHARACTER SET EXTENSION HAS BEEN SPECIFIED FOR A FONT THAT IS NOT A DOUBLE-BYTE OUTLINE FONT.

Explanation:

Bit 1 of byte 3 in the Font Control (FNC) structured field indicates that this font character set is an extension of an existing resident double-byte outline font, but the font technology identifier (byte 1 in the FNC structured field) is not X'1E'. PSF detected this error while processing a font character set.

System action:

User response:

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

System programmer response:

If an IBM licensed program was used to create the structured fields for the font with the error, verify that the input to that program was valid. If the input was valid, see 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, 8, 19.

APS373I

DATA IN A FONT RESOURCE IS NOT VALID: THE FONT RESOLUTION SPECIFIED IN THE FNC STRUCTURED FIELD IS NOT VALID.

Explanation:

The font resolution specified in bytes 22-27 of the Font Control (FNC) structured field was specified incorrectly. For an outline font, these fields must be zeros. PSF detected this error while processing a font character set.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS374I

THE HOST VERSION OF THE REQUESTED OUTLINE FONT CHARACTER SET IS NOT DOWNLOADABLE BECAUSE IT DOES NOT CONTAIN ANY FONT PATTERN DATA. IT MAY BE A METRIC-ONLY OUTLINE FONT CHARACTER SET.

Explanation:

Some printers have optional font features or user-installable fonts on cards or other media. This message might indicate that the referenced font was not installed in the printer when this data set was printed.

To support printing with printer-resident fonts, the host font libraries might contain font resources with formatting information but no downloadable font pattern data. These metric-only font character sets (MOF) are used only to activate printer-resident fonts. Because of missing font data, the character set cannot be downloaded.

The pattern technology specified in byte 1 in the Font Control structured field is X'1E' or X'1F'. Bytes 28-31 in the FNC structured field contain the total number of bytes in the Font Patterns (FNG) structured field.

System action:

User response:

Install the font on the printer, change to a font that is either installed or downloadable, or notify your system programmer of this error.

System programmer response:

If the font character set is a standard IBM-supplied font, it might be a metric-only font. If so, that specific font must be resident in the printer. Verify that the font is resident in the printer being used. For example, double-byte outline (scalable) fonts generally have metric-only fonts on the host system. Double-byte outline resident fonts might be a separate printer feature. See the printer publications for information on resident fonts.

If the font is resident in the printer, ensure that the character set is marked PUBLIC (by APSRMARK). In the Data Definition referenced by the FONTDD parameter in the PSF PRINTDEV statement, ensure that the font libraries containing marked resources are specified first in the library concatenation order. If you use fonts as INLINE or USERLIB resources, verify that they are marked PUBLIC.

If an IBM licensed program was used to create the structured fields for the font containing 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, 8, 19.

APS375I

DATA IN A FONT RESOURCE IS NOT VALID: THE FNN DATA COUNT IN THE FNC STRUCTURED FIELD IS NOT VALID.

Explanation:

The Font Name Map (FNN) Data Count in bytes 36-39 of the Font Control (FNC) structured field is specified incorrectly. PSF detected that this value is less than X'00000002', which is outside of the valid range X'00000002'–X'FFFFFFFF'. PSF detected this error while processing a font character set.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS376I

DATA IN A FONT RESOURCE IS NOT VALID: THE SPECIFIED FONT DOES NOT CONTAIN REQUIRED OUTLINE FONT EXTENSION INFORMATION.

Explanation:

When bit 1 of byte 3 in a Font Control (FNC) structured field indicates that the font character set is an extension of an existing resident double-byte outline font, the font character extension triplet (triplet ID X'6D') must specify the GCSGID of the corresponding resident double-byte outline font. PSF detected this error while processing a font character set.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS377I

DATA IN A FONT RESOURCE IS NOT VALID: THE SPECIFIED OUTLINE FONT CHARACTER SET DOES NOT CONTAIN ANY FNN STRUCTURED FIELDS.

Explanation:

No Font Name Map (FNN) structured fields exist for the specified outline font. PSF requires that at least one FNN structured field exist for an outline font. PSF detected this error while processing a font character set.

System action:

User response:

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS378I

THE ENCODING SCHEME SPECIFIED IN THE CPD STRUCTURED FIELD DOES NOT MATCH THE ENCODING SCHEME SPECIFIED IN THE MCF STRUCTURED FIELD FOR THE FONT.

Explanation:

The font encoding scheme specified in the encoding scheme ID triplet (triplet ID X'27') of the Map Coded Font (MCF) structured field does not match the encoding scheme specified in bytes 42-43 in the Code Page Descriptor (CPD) structured field for the code page. PSF detected this error while processing a code page.

System action:

User response:

The mismatch can be caused by an error in the MCF structured field that referenced the requested font, or by an error in the code page for the requested font. If you created the structured fields for the code page, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 for more information about the structured field. If the structured field has no error, the error might be a PSF or printer logic error. If you used a program to create the structured fields for the code page, contact your system programmer. If you created the MCF structured field for the page definition or the MO:DCA data, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the page definition or the MO:DCA data, consult your system programmer.

System programmer response:

Operator response:

Problem determination:

Items 1, 2, 8, 19.

APS380I

THE REGISTRATION ID (object-type OID) OF AN OBJECT CONTAINER RESOURCE, NAME resource name, DOES NOT MATCH THE CORRESPONDING REGISTRATION ID FOR THE INVOKING JCL KEYWORD OR INCLUDING STRUCTURED FIELD.

Explanation:

An object container resource was requested through a JCL keyword or an IOB or MDR structured field, but the object classification triplet in the Begin Object Container structured field did not match the corresponding registration ID. For a list of registration IDs and their assumed functions, see Mixed Object Document Content Architecture Reference, AFPC-0004.

System action:

If the object container was called out by JCL, PSF stops processing the current data set and issues additional messages that identify the processing environment when the error was found.

If the object container was included by an IOB or MDR structured field, PSF stops processing the page or overlay. PSF attempts 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.

User response:

If you created the structured fields for the object container resource, ensure that the registration ID corresponds to the keyword used to call the resource or to the registration ID specified in the object classification triplet specified on the IOB or MDR structured field.

System programmer response:

If an IBM licensed program was used to create the structured fields for the object container that contains 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, 13, 17.

APS381I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE REGISTERED OBJECT ID IN THE OBJECT CLASSIFICATION TRIPLET ON A structured field name STRUCTURED FIELD IS NOT SPECIFIED.

Explanation:

The registered object ID is 0 in the object classification triplet. Object containers require a registered ID to be specified.

System action:

The system action depends on where the error is located:

If the structured field is included in an object embedded in a page or overlay, or if the structured field is in a resource included by a page or overlay, PSF stops processing the page or overlay. PSF tries to find the end of the current page and resume processing on the next page. If it cannot find the end of the current page, PSF stops printing the data set.
If processing an inline resource, PSF stops processing the data set.
For non-presentation object containers, PSF stops printing the data set.
If the error is contained in a page definition, PSF stops processing the data set and continues processing with the next data set.
If this error occurs in a Resource Environment Group (REG), PSF stops processing the REG and continues processing the data set.

PSF issues a message that identifies the position of the structured field in the input data stream or resource. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

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

System programmer response:

If an IBM licensed program was used to create the structured fields 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, 13, 17.

APS383I

THE PRESENTATION SYSTEM SETUP ID (identifier) SPECIFIED IN THE MMC STRUCTURED FIELD IS NOT CURRENTLY AVAILABLE AT THE DEVICE. THE DATA SET WILL BE HELD BY THE SYSTEM.

Explanation:

The Presentation System Setup ID in the Medium Modification Control (MMC) structured field contains a setup ID that is not currently available at the printer, or the printer does not support setup IDs. The MMC structured field is contained in the form definition.

System action:

PSF stops processing the current data set and issues additional messages that identify the processing environment when the error was found. See Mixed Object Document Content Architecture Reference, AFPC-0004. PSF releases the current data set back to JES and requests that it be held by the system.

User response:

To receive the printed output with the setup ID identified, do one of these:

Specify the FORMS keyword on the OUTPUT statement of the JCL with a parameter as determined by local procedures.
Ask the operator to make available on the printer the identified setup IDs.
Submit the job to a printer containing the identified setup ID.

If the setup ID identified is not what you wanted, do one of these:

Specify a form definition containing a different setup ID or no setup ID.
Modify the form definition to require a different presentation system setup ID or remove the use of the presentation system setup ID.

System programmer response:

If this message appears on the operator's console, use the information provided in the Operator Response section. If the setup ID is not what you wanted, modify the PSF startup procedure as described in the User Response section.

Operator response:

If this message appears on the operator's console, it indicates that the resource containing the setup ID is defined for a separator page or the message data set in the PSF startup procedure. If the setup ID cannot be made available on your printer at all times, then contact your system programmer.

See the operator's manual for your printer or your post-processing device to determine how to make the determined setup ID available for use.

Problem determination:

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

APS384I

DATA IN A FORMDEF RESOURCE IS NOT VALID: THE SET OF MODIFICATIONS SPECIFIED IN THE MCC STRUCTURED FIELD INCLUDES CONFLICTING PRESENTATION SYSTEM SETUP ID VALUES.

Explanation:

Multiple MMC structured fields referenced by the MCC structured field do not use the exact same set of Presentation System Setup ID values.

System action:

The form definition containing the error is not used, and one of these occurs:

PSF is not started if the form definition containing the error is defined in the PSF startup procedure. The form definition resources defined in the PSF startup procedure are for separator pages, for the message data set, and for the default form definition resource for user print data sets.
If the error is in a form definition specified on a user's JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment when the error was found.

User response:

System programmer response:

Operator response:

Problem determination:

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

APS385I

DATA IN A FORMDEF RESOURCE IS NOT VALID: THE MODIFICATIONS SPECIFIED IN THE MMC STRUCTURED FIELD (structured field) INCLUDE UNPAIRED keyword1 AND keyword2 KEYWORDS.

Explanation:

The keywords must be paired in the Medium Modification Control (MMC) structured field. This form definition has one or the other keyword but not both, or the keyword pairs are not adjacent. The MMC structured field is contained in the form definition.

System action:

The form definition containing the error is not used, and one of these occurs:

PSF is not started if the form definition containing the error is defined in the PSF startup procedure. The form definition resources defined in the PSF startup procedure are for separator pages, for the message data set, and for the default form definition resource for user print data sets.
If the error is in a form definition specified on a user's JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment when the error was found.

User response:

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

System programmer response:

If an IBM licensed program was used to create the structured fields for the form definition with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If 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, 13, 15c, 17, 19.

APS386I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: A REQUIRED TRIPLET WITH ID identifier WAS MISSING FROM AN structured field STRUCTURED FIELD.

Explanation:

When the triplet identifier is X'4B', the x- or y-axis origin for the object content or an object area size is specified on the Include Object (IOB) or Preprocess Presentation Object (PPO) structured field, but no measurement unit (X'4B') triplet is specified. A PPO structured field is contained in a print data set. An IOB structured field is contained in a print data set, overlay, or page definition.

When the triplet identifier is X'22', the Extended Resource Local Identifier (X'22') triplet is required on an IOB structured field in a page definition.

The structured field is contained in a print data set if it is a PPO.

System action:

The system action depends on where the error is located:

If the error is contained in a page definition, PSF stops processing the data set and continues processing with the next data set.
If the error is in a page or overlay and the structured field is an IOB, PSF stops processing the page or overlay containing the structured field in error. PSF tries to find the end of the current page and resume processing on the next page. If PSF cannot find the end of the current page, it stops printing the data set.
If the error is in the print data set and the structured field is a PPO, PSF stops processing the Resource Environment Group and continues processing the data set.

PSF issues a message identifying the position of the structured field in the input data stream or resource. PSF issues additional messages identifying the processing environment when the error was found.

User response:

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

System programmer response:

If an IBM licensed program was used to place the IOB structured field in the print data set or overlay, verify that the input to that program was valid. If it was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem.

Operator response:

No response is necessary.

Problem determination:

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

APS387I

DATA IN AN INPUT RECORD IS NOT VALID: PARAMETER IN AN structured field STRUCTURED FIELD CONTAINS UNACCEPTABLE DATA.

Explanation:

One of the parameters in the structured field is not valid. If structured field is an IOB structured field, one of these caused the problem:

The object type specified is not supported or is not valid.
The x or y offset of the object area or the rotation value are not explicitly specified when the reference coordinate system is set to X'00'.

If structured field is a PPO structured field, one of these caused the problem:

The object type specified is not supported or is not valid.
The x or y offset of the object area is not valid.

If structured field is a PTD structured field, the x or y text presentation extent is not valid.

System action:

PSF stops processing the page or overlay containing the structured field in error. PSF tries to find the end of the current page and resume processing on the next page. If it cannot find the end of the current page, PSF stops printing the data set.

If this error occurs in a Resource Environment Group (REG), PSF stops processing the REG and continues processing the data set.

User response:

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

System programmer response:

Operator response:

Problem determination:

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

APS388I

DATA IN A PAGE SEGMENT IS NOT VALID: structured field STRUCTURED FIELD IS NOT ALLOWED IN A PAGE SEGMENT INCLUDED WITH AN IOB.

Explanation:

Only MO:DCA page segments are allowed to be included with an IOB structured field. MO:DCA page segments cannot contain IM1 images or PTOCA data.

System action:

PSF stops processing the page or overlay containing the structured field in error. PSF attempts 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 a message identifying the position of the structured field in the input data stream or resource. PSF issues additional messages identifying the processing environment when the error was found.

User response:

If you placed the IOB structured field in the print data set or overlay, correct the error and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 for more information about the structured field. If you used a program to place the IOB structured field in the print data set or overlay, contact your system programmer.

System programmer response:

Operator response:

No response is necessary.

Problem determination:

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

APS389I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE METRIC-TECHNOLOGY, THE UNIT BASE OR THE UNITS PER UNIT BASE FIELD IS NOT VALID IN THE X'84' TRIPLET ON THE MCF2.

Explanation:

The metric-technology, the unit base, or the units per unit base value in the X'84' triplet on the MCF2 structured field is not valid.

System action:

User response:

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

System programmer response:

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

Operator response:

Problem determination:

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

APS390I

DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: THE structured field STRUCTURED FIELD CONTAINS A triplet TRIPLET THAT HAS AN INCORRECT VALUE. THE INCORRECT VALUE STARTS IN BYTE offset OF THE TRIPLET.

Explanation:

A value that is not valid was specified for a field that starts in the byte offset of the triplet identified in this message. The triplet is specified on the structured field identified in this message.

System action:

If the error occurred in a form definition, a page definition, or a non-presentation object container resource (for example, COMSETUP), the form definition, page definition, or non-presentation object container resource is not used, and one of these occurs:

PSF is not started for any of these:
- The default form definition
- A form definition specified for printing messages or separator pages
- A page definition specified for printing messages or separator pages
PSF cannot begin printing the data set for a form definition or non-presentation object container resource (or page definition, if printing line data) specified on a user’s JCL OUTPUT statement; PSF tries to print the next data set.

If the error occurred in a structured field in a page or another type of resource, PSF attempts to find the end of the page or resource. If PSF can find the end of the page or resource, it prints any data accumulated for the current page. If PSF cannot find the end of the page or resource, it stops processing the data set.

PSF issues a message identifying the position of the structured field in the data stream or resource. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

System programmer response:

If an IBM licensed program was used to create the structured fields for the 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 1, 2, 13, 15c, 17, 19.

APS391I

THE METRIC-TECHNOLOGY AND RESOLUTION IN THE FONT DO NOT MATCH THE SPECIFIED VALUES.

Explanation:

One of these has occurred:

The metric-technology and resolution values that are specified in the X'84' triplet on the MCF2 structured field do not match the values in the Font Control (FNC) structured field.
The RESFMT keyword on the OUTPUT statement or the Resolution value from the Printer Inventory or the XTP7FMT field from the Resource-Management Exit 7 do not match the values in the Font Control (FNC) structured field.

The FNC structured field is in the font character set. These fields are required to match the specified values when the Presentation Fidelity Control (PFC) has the Font Fidelity triplet continuation rule set to "stop presentation". The PFC structured field is specified in the form definition.

System action:

User response:

Determine whether the font required any preprocessing to match the resolution of the device; if so, ensure that this preprocessing was done. For more information about converting 240-pel fonts to 300-pel fonts, see PSF for z/OS: Customization. If you created the structured fields for the font, correct the error and resubmit the print request. See Data Stream and Object Content Architectures: Font Object Content Architecture Reference, S544-3285 for more information about the structured field. If the structured field has no error, the error might be a PSF logic error. If you used a program to create the structured fields for the font, contact your system programmer.

System programmer response:

If the Printer Inventory or PRINTDEV JCL statement in the PSF startup procedure does not specify the correct font library for the resolution of the printer, correct it.

Operator response:

Problem determination:

Items 1, 2, 3, 8, 13, 17, 19.

APS392I

DATA IN A FORMDEF RESOURCE IS NOT VALID: THE SCOPE VALUE IN THE MFC IS NOT VALID. EITHER DOCUMENT LEVEL OR PRINT FILE LEVEL FINISHING WAS SPECIFIED IN THE MEDIUM MAP OR MEDIUM LEVEL FINISHING WAS SPECIFIED IN THE DEG.

Explanation:

Either a Document Environment Group or a medium map in the current form definition contains a Medium Finishing Control (MFC) structured field with an incorrect value specified for the scope.

System action:

The MFC is ignored and processing continues. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

System programmer response:

Operator response:

Problem determination:

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

APS393I

THE INPUT BIN SPECIFIED IN THE MMC STRUCTURED FIELD OR ON THE OUTPUT STATEMENT IS AN INSERTER BIN AND IS DISABLED. AN ALTERNATIVE BIN WAS SUBSTITUTED.

Explanation:

The Medium Modification Control (MMC) structured field or the output statement requested an input bin that is supported by the printer but is disabled. This bin is an inserter bin. The MMC structured field is contained in a medium map in the form definition. The output statement is in the JCL.

System action:

PSF continues processing, selecting paper from an alternative bin that is not an inserter bin.

User response:

If the output is not acceptable, submit the print request to a printer that has the specified bin available, or ensure that the bin is enabled on the original printer before resubmitting the print request.

System programmer response:

No response is necessary.

Operator response:

No response is necessary.

Problem determination:

None.

APS394I

THE PSF OBJECT STACK IS ABOUT TO OVERFLOW DUE TO MISSING END STRUCTURED FIELDS.

Explanation:

Common conversion machine (CCM) has run out of its object stack area. The cause could be a data stream error. A begin structured field must be followed by a matching end structured field in the data stream. If this requirement is not met, the CCM can run out of its object stack area. A common cause of this problem is missing EDT structured fields.

System action:

PSF stops the processing and printing of this data set.

User response:

If you created the data stream, each begin structured field in the data stream must be followed by a matching end structured field. Check the data stream to ensure that it meets this requirement. If it does not meet the requirement, correct the data stream. If it does meet the requirement, this error code indicates a logic error. If you believe the error is a logic error, consult your service representative in the IBM Support Center for assistance, or use your electronic link with IBM services.

System programmer response:

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

Problem determination:

Items 1, 2, 8, 13, 19.

APS395I

A FORMDEF RESOURCE REQUESTED A MEDIA EJECT CONTROL TO THE NEXT BACK SIDE AND DUPLEX=NO WAS SPECIFIED ON THE OUTPUT STATEMENT.

Explanation:

When a media eject control to the next back side is specified in a FORMDEF, the DUPLEX=NO keyword on the OUTPUT statement cannot be used to change from duplex (specified in the FORMDEF) to simplex. The reason is that an incompatible request is being made—you cannot eject to the next back side when simplexing.

The only valid options for the DUPLEX keyword when a media eject control to the next back side is specified in the FORMDEF are:

If the FORMDEF requests normal or tumble duplex, you can specify either duplex=normal or duplex=tumble on the output statement.

System action:

User response:

Resubmit the job without requesting the DUPLEX keyword on the OUTPUT statement.

System programmer response:

None.

Operator response:

None.

APS396I

DATA IN A FORMDEF RESOURCE IS NOT VALID: THE OUTPUT BIN SELECTION VALUE IN MMC STRUCTURED FIELD, ID identifier, IS NOT ACCEPTABLE.

Explanation:

The Medium Modification Control (MMC) structured field specified an output bin selection value of 0. Values 1 - 65535 are valid. The MMC structured field is in the form definition.

System action:

The form definition containing the error is not used, and one of these occurs:

PSF is not started if the form definition containing the error is defined in the PSF startup procedure. The form definition resources defined in the PSF startup procedure are for separator pages, for the message data set, and for the default form definition resource for user print data sets.
If the error is in a form definition specified on a user's JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

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

System programmer response:

Operator response:

Problem determination:

Items 2, 17.

APS397I

DATA IN A FORMDEF RESOURCE IS NOT VALID: DIFFERENT OUTPUT BIN VALUES ARE SPECIFIED FOR THE FRONT AND BACK SIDES OF A SHEET IN MEDIUM MAP medium map.

Explanation:

The Medium Modification Control (MMC) structured fields referenced by the Medium Copy Count (MCC) structured field repeating groups specify different output bin values along with either tumble or normal duplex. The settings attempt to place the front and back sides of a sheet into different output bins. The MMC structured field is in the form definition.

System action:

The form definition containing the error is not used, and one of these occurs:

PSF is not started if the form definition containing the error is defined in the PSF startup procedure. The form definition resources defined in the PSF startup procedure are for separator pages, for the message data set, and for the default form definition resource for user print data sets.
If the error is in a form definition specified on a user's JCL OUTPUT statement, PSF cannot begin printing the data set; it tries to print the next data set.

PSF issues a message identifying the position of the structured field in the form definition. PSF issues additional messages identifying the processing environment in which the error occurred.

User response:

System programmer response:

Operator response:

Problem determination:

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

APS398I

DATA IN A FORMDEF RESOURCE IS NOT VALID: THE SET OF MODIFICATIONS SPECIFIED IN THE MMC STRUCTURED FIELD, ID identifier, INCLUDES DUPLICATE CONFLICTING VALUES FOR THE identifier KEYWORD.

Explanation:

The Medium Modification Control (MMC) structured field contains duplicate conflicting values for the MMC keyword identified in the message text. The MMC structured field is in the form definition.

System action:

PSF issues this message and continues processing, ignoring the duplicate keyword.

User response:

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

System programmer response:

Operator response:

Problem determination:

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

APS399I

AN OUTPUT BIN bin number WAS REQUESTED FOR THE JOB, BUT IT WAS NOT AVAILABLE OR THE PRINTER DOES NOT SUPPORT OUTPUT BIN SELECTION.

Explanation:

The OUTBIN keyword on the JCL OUTPUT statement or the output bin selection parameter value in the form definition specified an output bin. Either that bin is not available or the printer does not support output bin specification. Since mandatory print labeling is enabled, the data set cannot be processed.

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:

Users have several options to correct or avoid this error:

Resubmit the print request to a printer that supports the requested bin number.
If the bin number was specified on the JCL OUTPUT statement, change the OUTBIN keyword to a bin number that is supported by the printer and resubmit the print request. If the bin number specified by the OUTBIN keyword is supported by the printer, the error might be a PSF logic error.
If you created the structured fields for the form definition, change the MMC structured field, specifying the correct output bin selection parameter value that is supported by the printer and resubmit the print request. See Mixed Object Document Content Architecture Reference, AFPC-0004 and Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884 for more information about the structured field. If the MMC output bin selection parameter is supported by the printer, the error might be a PSF logic error. If you used a program to create the structured fields for the form definition, contact your system programmer.
Disable mandatory print labeling and resubmit the print request.
If you print to a printer that does not support output bin specification, remove the output bin specification.

System programmer response:

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:

Inform your system programmer that this error occurred.

Problem determination:

Items 1, 2, 8, 19.

G550-0432-04

APS300 to APS399

APS300 to APS399