Explanation of the PPFA messages

AKQ001E: END OF COMMENT (*⁄) IS NOT SPECIFIED.

Explanation: The end mark of a comment (*⁄) is not specified.

System action: The page definition or form definition is not generated. The syntax check may be ended.

Operator response: Specify the end mark of a comment.

AKQ002E: DBCS STRING DOES NOT END WITH SHIFT-IN.

Explanation: DBCS strings in comments must terminate with shift-in.

System action: The form definition or page definition is not generated. The syntax check continues, assuming shift-in.

Operator response: Specify a valid DBCS string enclosed by SO and SI.

AKQ003E: LITERAL DOES NOT END WITH APOSTROPHE.

Explanation: A literal must end with an apostrophe.

System action: The page definition is not generated. The syntax check continues, assuming an apostrophe.

Operator response: Specify a valid literal enclosed by apostrophes. Note that an apostrophe in a literal is specified by consecutive double apostrophes.

AKQ004E: DBCS LITERAL DOES NOT END WITH SHIFT-IN AND APOSTROPHE.

Explanation: A DBCS literal must end with shift-in and apostrophe.

System action: The page definition is not generated. The syntax check continues, assuming the end of the DBCS literal at the end of a record.

Operator response: Specify a valid literal ended by shift-in and apostrophe.

AKQ101E: COMMAND SEQUENCE IS INVALID.

Explanation: The command sequence is invalid.

System action: A page definition or form definition is not generated. The syntax check continues from a valid command.

Operator response: Specify commands in a valid sequence.

AKQ102E: INVALID COMMAND (erroneous entry) IS SPECIFIED.

Explanation: An invalid command is specified in the input data.

System action: A page definition or form definition is not generated. The syntax check continues from a valid command.

Operator response: Specify a valid command.

AKQ103E: INVALID SUBCOMMAND (value) IS SPECIFIED.

Explanation: An invalid subcommand was specified in the input data. This message is often issued when a semicolon (;) is missing.

System action: A page definition or form definition is not generated. The syntax check continues from the next keyword.

Operator response: Specify a valid subcommand.

AKQ104E: (command or parameter name) NAME IS NOT SPECIFIED.

Explanation: The required name is not specified.

System action: A page definition or form definition is not generated. The syntax check continues, assuming blanks or default as the name.

Operator response: Specify the required name.

AKQ105E: REQUIRED PARAMETER IN (subcommand name) IS NOT SPECIFIED.

Explanation: The subcommand indicated in the message requires a correct PPFA format.

System action: A page definition or form definition is not generated. The syntax check continues, assuming the default values.

Operator response: Refer to the command reference section of this publication for help in specifying a valid subcommand parameter.

AKQ106E: command or parameter name) NAME IS SPECIFIED WITH INVALID SYNTAX.

Explanation: The required name is specified with invalid syntax. See Character Length for PPFA Names for the correct length of names.

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Specify a valid name.

AKQ107E: PARAMETER IN (subcommand name) IS INVALID.

Explanation: The parameter in the subcommand is invalid (invalid format or out of range).

System action: A page definition or form definition is not generated. The syntax check continues, assuming the default values as the parameter.

Operator response: Specify a valid parameter value.

AKQ108E: (subcommand name) SUBCOMMAND IS DUPLICATED IN ONE COMMAND.

Explanation: The subcommand indicated in the message was specified more than once in the same command. Only one such subcommand is permitted within this command.

System action: A page definition or form definition is not generated. The syntax check continues, ignoring the duplicate subcommand.

Operator response: Delete one subcommand.

AKQ109E: (subcommand name) SUBCOMMAND CONFLICTS WITH (subcommand name) SUBCOMMAND.

Explanation: One subcommand conflicts with another (FONT, PRINTLINE, FIELD, OPCOUNT, OPPOS).

System action: A page definition or form definition is not generated. The syntax check continues, ignoring the latter subcommand.

User response: Delete one of the subcommands.

AKQ110E: THE VALUE OF THE (command name) SUBCOMMAND IS TOO LARGE OR TOO SMALL.

Explanation: The parameter in the subcommand is out of range.

IN

136.5

MM

3467.1

CM

346.7

POINTS

9828.0

PELS (L-units)

32760

These values are specified in:

• FORMDEF N_UP OVERLAY relative_xpos relative_ypos
• PAGEDEF PRINTLINE OVERLAY / SEGMENT relative_xpos relative_ypos

System action: No form definition or page definition is generated. PPFA continues syntax checking.

Operator response: Specify a valid parameter value.

AKQ111E: SUBCOMMAND SEQUENCE IS INVALID: (subcommand name) OCCURS AFTER (subcommand name)

Explanation: For example, a WHEN subcommand occurs after an OTHERWISE subcommand in a CONDITION command.

System action: A page definition or form definition is not generated. The syntax check continues, ignoring the subcommand.

Operator response: Reorder or rewrite the conditions..

AKQ112E: CONDITION COMMAND DOES NOT ALLOW ‘*’ IN ITS START SUBCOMMAND.

Explanation: A relative position (‘*’, ‘* + n’, or ‘* - n’) was specified in a START subcommand of a CONDITION command.

System action: A page definition or form definition is not generated. The syntax check continues from the valid subcommand.

Operator response: Specify an absolute starting position.

AKQ113E: MORE THAN ONE ‘WHEN’ SUBCOMMAND SPECIFIED THE CHANGE PARAMETER.

Explanation: More than one WHEN subcommand specified CHANGE for its field comparison.

System action: A page definition or form definition is not generated. The syntax check continues from the valid subcommand.

Operator response: Remove the extra parameters.

AKQ114E: NUMBER OF PARAMETERS EXCEED LIMIT FOR (subcommand name) SUBCOMMAND OR KEYWORD.

Explanation: The named subcommand/keyword in the messages limits the number of parameters that may be coded with a single subcommand or keyword. The number of parameters that can be coded with the named subcommand or keyword is defined in the command reference sections of this publication; see Form Definition Command Reference and Page Definition Command Reference .

System action: The form definition is not generated. The syntax check continues from the valid subcommand.

Operator response: Remove the extra parameters.

AKQ115E: REQUIRED PARAMETER(S) (PARM1, PARM2, …) IN (COMMAND OR SUBCOMMAND) IS (ARE) NOT SPECIFIED.

Explanation: This is a generic message which indicates one or more missing parameters on a subcommand or command. For example a DRAWGRAPHIC BOX must have a BOXSIZE subcommand coded.

System action: A page or form definition is not generated.

Operator response: Provide the correct parameter(s) on the command or subcommand.

AKQ116E: PARAMETER (PARM1) IN (COMMAND OR SUBCOMMAND) IS INVALID.

Explanation: This is a generic message which indicates that a parameter in a subcommand or command is invalid.

System action: A page or form definition is not generated.

Operator response: Provide the correct parameter on the command or subcommand.

AKQ117E: PARAMETER (PARM1) IN (COMMAND OR SUBCOMMAND) IS DUPLICATED.

Explanation: This is a generic message which indicates that a parameter in a subcommand or command is coded more than once. For example, …LINEWT LIGHT BOLD… shows two different line weights in the same subcommand.

System action: A page or form definition is not generated.

Operator response: Remove one of the parameters.

AKQ118E: MUTUALLY EXCLUSIVE PARAMETERS ON THE (INSERT1) COMMAND OR SUBCOMMAND ARE DUPLICATED.

Explanation: A command or subcommand contains more than one mutually exclusive parameter. For example, the PAGECOUNT subcommand on the PAGEDEF command cannot have both STOP and CONTINUE coded.

System action: A page or form definition is not generated.

Operator response: Remove one of the parameters.

AKQ119E: GRAPHICS-TYPE (BOX, LINE, CIRCLE, ELLIPSE) MUST IMMEDIATELY FOLLOW DRAWGRAPHIC.

Explanation: The DRAWGRAPHIC command must have the graphics type (BOX, LINE, CIRCLE, ELLIPSE) immediately following the command.

System action: A page or form definition is not generated.

Operator response: Code one of the graphics types.

AKQ120I: UNKNOWN COMPONENT ID. PPFA WILL ASSUME IT IS SUPPORTED.

Explanation: PPFA allows the use of numeric component IDs when the object type is OTHER so that new OTHER object types can be supported without a new release of PPFA. This is one of them.

System action: A PAGEDEF will be generated.

Operator response: Insure that the object type component id is supported by your printer and PSF service level.

AKQ121W: COMMAND SEQUENCE IS INVALID. A (insert-1) OCCURS BEFORE A (insert-2).

Explanation: For example, an overlay occurs outside a copygroup.

System action: A dummy copygroup will be created. This will be the first copygroup. The FORMDEF will be generated.

Operator response: Reorder the command statements.

AKQ122W: THE (insert-1) IS TOO LONG. IT IS TRUNCATED TO (insert-2) BYTES.

Explanation: The input length of a parameter is exceeded. For example, the maximum length of a barcode Macro is 4096 bytes.

System action: Only the first (insert-2) bytes of a parameter will be used. Processing continues. A PAGEDEF will be generated.

Operator response: Use a shorter text parameter.

AKQ201E: (subcommand name) SUBCOMMAND IS NOT SPECIFIED.

Explanation: The required subcommand is not specified.

System action: A page definition or form definition is not generated. The syntax check continues, assuming the default.

Operator response: Specify the required subcommand.

AKQ202E: SPECIFIED (command name) NAME IS NOT DEFINED.

Explanation: A resource name (OVERLAY, SUPPRESSION, FONT, OBJECT, QTAG, or COLOR) is not defined.

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Correct the name.

AKQ203W: (command name) NAME IS DUPLICATED.

Explanation: The required name must be unique for OVERLAY, COPYGROUP, FONT, PAGEFORMAT, OBJECT, or SUPPRESSION.

System action: A page definition or form definition is generated.

Operator response: Specify a unique name.

AKQ204E: (object) NAME IS DUPLICATED.

Explanation: The name must be unique (OVERLAY, COPYGROUP, FONT, PAGEFORMAT, SEGMENT).

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Specify a unique name.

AKQ205E: PAGEFORMAT (pageformat name) WAS NOT FOUND IN THIS PAGE DEFINITION.

Explanation: A WHEN or OTHERWISE subcommand of CONDITION specifies a PAGEFORMAT name not found in the page definition being processed.).

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Specify a pageformat name that is in the page definition.

AKQ206E: CONDITION (condition name) HAS ALREADY BEEN DEFINED.

Explanation: A CONDITION command specifies LENGTH, WHEN, or OTHERWISE, and the condition with this condition name has already been defined by an earlier CONDITION command.

System action: A page definition is not generated. The syntax check continues.

Operator response: Define the condition only the first time it occurs.

AKQ210E: THE RELATIVE POSITION VALUE EXCEEDS THE ALLOWED RANGE.

Explanation: The value specified for the relative x position or relative y position on the N_UP subcommand (for an OVERLAY) or PRINTLINE command (for an OVERLAY or SEGMENT) exceeds the range of +32760 to -32760 L-units. For example, assuming the default of 240 pels per inch is being used, the values must be equal to, or less than the following:

IN

136.5

MM

3467.1

CM

346.7

POINTS

9828.0

PELS (L-units)

32760 (+ or -)

CPI

*

LPI

*

System action: The page definition or form definition is not generated. The syntax check continues.

Operator response: Correct the relative x and y position values within the allowed range.

AKQ211E: FRONT/BACK SIDE IS NOT SPECIFIED FOR DUPLEX.

Explanation: The SUBGROUP specified with BACK does not exist after the SUBGROUP specified with FRONT, or the SUBGROUP specified with FRONT does not exist before the SUBGROUP specified with BACK.

System action: A form definition is not generated. The syntax check continues.

Operator response: Specify subgroups for both sides.

AKQ212W: PAPER SIDE IS SPECIFIED FOR SIMPLEX.

Explanation: A subgroup specified with BOTH, FRONT, or BACK is invalid with single-sided printing.

System action: A form definition is generated, ignoring the subcommand specifying the paper side.

User response Either delete the subcommand that specified the paper side or specify DUPLEX.

AKQ213E: LOGICAL PAGE POSITION EXCEEDS THE LIMIT.

Explanation: The logical page position specified by the OFFSET subcommand in the FORMDEF or COPYGROUP command exceeds the limits.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ214E: MORE THAN 127 SUPPRESSIONS ARE SPECIFIED IN ONE FORMDEF.

Explanation: More than 127 suppressions are specified in one FORMDEF.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ215E: MORE THAN 127 OVERLAYS ARE SPECIFIED IN ONE COPYGROUP.

Explanation: More than 127 OVERLAYs are specified in one copy group. PPFA can issue this message for an N_UP subcommand that specifies more than 127 overlays.

System action: No form definition is generated. The syntax check continues.

User response Correct the error.

AKQ216E: MORE THAN ONE RASTER OVERLAY IS SPECIFIED IN ONE COPYGROUP.

Explanation: More than one raster OVERLAY is specified in one copy group.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ217W: LOGICAL PAGE POSITION FOR BACK SIDE OF PAGE SPECIFIED IN SIMPLEX PROCESSING.

Explanation: The logical-page position specified by the OFFSET subcommand in a FORMDEF or COPYGROUP command for the back side of a page was specified, but simplex was specified in a COPYGROUP command.

System action: A form definition is generated, with the back side logical page position included, as if duplex had been specified. The syntax check continues.

Operator response: Correct the error by specifying duplex in the COPYGROUP command or remove the second set of coordinates in the OFFSET subcommand.

AKQ218E: MORE THAN 255 COPIES ARE SPECIFIED IN ONE COPYGROUP.

Explanation: More than 255 copies are specified in a COPYGROUP.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ219E: MORE THAN 127 SUBGROUPS ARE SPECIFIED IN ONE COPYGROUP.

Explanation: More than 127 subgroups are specified in a COPYGROUP

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ220E: MORE THAN 8 OVERLAYS ARE SPECIFIED IN ONE SUBGROUP.

Explanation: More than eight overlays are specified in one SUBGROUP.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ221E: MORE THAN 8 SUPPRESSIONS ARE SPECIFIED IN ONE SUBGROUP.

Explanation: More than eight suppressions are specified in one SUBGROUP.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ222W: DIFFERENT NUMBERS OF COPIES ARE SPECIFIED FOR EACH SIDE OF DUPLEX.

Explanation: The number of copies for BACK side is not equal to those for FRONT side.

System action: A form definition is generated assuming the number of copies specified for front side.

Operator response: Check the number of copies.

AKQ223E: LOGICAL PAGE POSITION FOR (page side) SIDE OF PAGE EXCEEDS THE LIMIT.

Explanation: The logical-page position specified by the OFFSET subcommand in a FORMDEF or COPYGROUP command exceeds the limit for the current side of the page.

System action: A form definition is not generated. The syntax check continues.

Operator response: Correct the positioning OFFSET parameter.

AKQ224E: MORE THAN 254 OVERLAYS ARE SPECIFIED IN A PAGEFORMAT.

Explanation: The maximum number of OVERLAY commands is 254. PPFA can issue this message for the OVERLAY subcommand of the PRINTLINE command.

System action: A page definition is not generated. The syntax check continues.

User response: Specify a valid number of OVERLAY commands.

AKQ225E: CONSTANT SUBCOMMAND PARAMETER (parameter) SPECIFIED IN SIMPLEX PROCESSING.

Explanation: The BACK or BOTH parameter has been specified for the CONSTANT subcommand within simplex processing.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct this CONSTANT subcommand or indicate DUPLEX.

AKQ226E: DIRECTION SUBCOMMAND ONLY ALLOWED WITH PRESENT SUBCOMMAND.

Explanation: The DIRECTION subcommand has been specified, but the PRESENT subcommand has not.

System action: A form definition is not generated. The syntax check continues.

Operator response: Either add the PRESENT subcommand or remove the DIRECTION subcommand.

AKQ227E: THE ORIGIN OF THE RESOURCE (name) NAMED IN THE PRINTLINE COMMAND IS OFF THE LOGICAL PAGE.

Explanation: The relative position of the PRINTLINE overlay or segment named is off the logical page. The origin of the overlay or segment specified for the resource named in the N_UP subcommand is off the medium.

System action: The page definition that has the overlay or segment in question is not generated. PPFA continues the syntax check, ignoring the problem.

Operator response: Correct the x-position and y-position for the OVERLAY or SEGMENT subcommand.

AKQ228E: THE ORIGIN OF THE OVERLAY (overlay name) NAMED IN THE (command) COMMAND IS OFF THE MEDIUM.

Explanation: The resource position values will position the resource such that at least part of the resource will be off the medium (physical page).

System action: The form definition that has the overlay in question is not generated. PPFA continues the syntax check, ignoring the problem.

Operator response: Correct the relative x-position and relative y-position values for the OVERLAY named in the N_UP subcommand.

AKQ229W: SUBGROUPS FOR FRONT AND BACK OF SAME SHEET USED DIFFERENT BINS.

Explanation: In your subgroup command you specified FRONT and BACK parameters. However, your COPYGROUP has different bins specified.

System action: A form definition is generated that specifies the bin used for the front side.

Operator response: Check the number of copies and correct the bin setting.

AKQ231E: PRINTLINE OR LAYOUT IS NOT SPECIFIED.

Explanation: There is no PRINTLINE or LAYOUT command in the page format.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify either a PRINTLINE or LAYOUT command.

AKQ232E: REQUIRED SUBCOMMAND TEXT OR LENGTH IS NOT SPECIFIED.

Explanation: A FIELD subcommand must have a TEXT or LENGTH subcommand.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify either a TEXT subcommand or a LENGTH subcommand.

AKQ233E: THE LOGICAL PAGE SIZE IS TOO LARGE OR TOO SMALL.

Explanation: The specified page size is too large or too small. The page size must be from 1 to 32767 pels. The HEIGHT and WIDTH subcommands must have values between 1 and 32767 PELS, inclusive, or the same measurements expressed in other units.

System action: A page definition is not generated. The syntax check continues, assuming the defaults.

Operator response: Correct the error.

AKQ234E: POSITION OF LINEONE EXCEEDS THE LOGICAL PAGE BOUNDARY.

Explanation: The TOP or MARGIN position specified by the LINEONE subcommand exceeds the logical page boundary. This error message is issued only if TOP or MARGIN is specified.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify a valid position value.

AKQ235E: MORE THAN 127 SEGMENTS ARE SPECIFIED IN ONE PAGEFORMAT.

Explanation: More than 127 segments are specified in a single PAGEFORMAT command. PPFA can issue this message for the SEGMENT subcommand of the PRINTLINE command.

System action: No page definition is generated. The syntax check continues.

User response: Correct the error.

AKQ238E: MORE THAN 127 FONTS ARE SPECIFIED IN ONE PAGEFORMAT.

Explanation: More than 127 fonts are specified in one PAGEFORMAT or the specified TRC number exceeds 126. PPFA counts each use of a font in more than one direction or rotation as a separate font.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ239E: PRINT POSITION EXCEEDS THE LOGICAL PAGE BOUNDARY.

Explanation: The print position specified by POSITION subcommand exceeds the logical page boundary.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ240E: NUMBER OF PRINTLINES, FIELDS, AND CONDITIONS EXCEEDS 65,535 IN ONE PAGE FORMAT.

Explanation: The total number of PRINTLINEs, FIELDs, and CONDITIONs exceeds 65,535 in one page format.

System action: A page definition is not generated. The syntax check continues.

Operator response: Reduce the number of PRINTLINEs, FIELDs, or CONDITIONs in the page format.

AKQ241E: TOTAL LENGTH OF TEXT DATA EXCEEDS 65,534 BYTES.

Explanation: The total length of text may be up to 65,534 bytes.

System action: A page definition is not generated. The syntax check continues

Operator response: Correct the error.

AKQ242E: THE VALUE OF THE STARTING POSITION OF A RECORD IS TOO LARGE OR TOO SMALL.

Explanation: The START position of a record exceeds the maximum (65,535) or minimum (1) value.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ243E: DBCS LENGTH IS NOT A MULTIPLE OF 2.

Explanation: The number of bytes of DBCS must be a multiple of two. This means that the value of the LENGTH parameter must be a multiple of two.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify a valid length or a valid DBCS.

AKQ244E: INVALID CODE IS SPECIFIED IN THE TEXT.

Explanation: SBCS text must be within code range X'00' to X'FE'.

Valid double-byte character set (DBCS) codes are between X'41' and X'FE' for each byte. PPFA checks this range. Code X'4040' (blank) is the only exception. For example, the following are valid DBCS codes: X'4040', X'4141', X'41FE', X'FE41', X'FEFE'.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify a valid code.

AKQ245E: HEXADECIMAL TEXT IS INVALID.

Explanation: Hexadecimal text is specified in an invalid format. Hexadecimal text must have an even length parameter and be in hexadecimal notation ('0' to 'F').

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify valid hexadecimal text.

AKQ246E: NULL LITERAL IS SPECIFIED.

Explanation: The literal has no string.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify a valid literal.

AKQ247E: KANJI NUMBER TEXT IS INVALID.

Explanation: A Kanji number is specified in invalid format. Kanji number text must be a string of Kanji numbers delimited by commas. Each Kanji number must be a decimal number equal to a valid DBCS code, minus X'4000'.

System action: A page definition is not generated. The syntax check continues.

Operator response: Specify valid kanji number(s) in a valid format.

AKQ248E: TEXT ATTRIBUTE CONFLICTS WITH FONT.

Explanation: SBCS font is specified for DBCS text (type G, K), or DBCS font is specified for SBCS text (type C).

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ249E: TEXT ATTRIBUTE CONFLICTS WITH TEXT TYPE.

Explanation: The literal type conflicts with text type. SBCS literal is specified as type G or X, and DBCS literal is specified as type C, X, or K.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ250E: TRC NUMBER IS DUPLICATED.

Explanation: The specified TRC number is duplicated in one page format.

System action: A page definition is not generated. The syntax check continues.

Operator response: Correct the error.

AKQ251W: SPECIFIED LENGTH IS SHORTER THAN THE TEXT AND WAS TRUNCATED.

Explanation: The LENGTH parameter of the TEXT subcommand is shorter than the length of the specified literal, which is truncated to a specified length.

System action: The operation continues, truncating the literal.

Operator response: Check the truncation.

AKQ252E: TEXT IS NOT THE LENGTH SPECIFIED BY THE LENGTH SUBCOMMAND.

Explanation: TEXT IS NOT THE LENGTH SPECIFIED BY THE LENGTH SUBCOMMAND.

System action: A page definition is not generated. The syntax check continues.

Operator response: Change the comparison text or the LENGTH parameter so that they match.

AKQ253E: TEXT IN THE ‘WHEN’ SUBCOMMAND IS TOO LONG.

Explanation: Constant text in a WHEN subcommand of a CONDITION command is too long to fit into an 8150-byte CCP structured field.

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Shorten the field to 8000 bytes or fewer, and shorten the comparison text accordingly.

AKQ254E: (text type) LITERAL WAS EXPECTED BUT (text type) WAS FOUND.

Explanation: An SBCS literal occurs where a DBCS one was expected, or vice versa.

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: In a FIELD command, do not use a DBCS literal without specifying a DBCS font. In a CONDITION command, do not mix SBCS and DBCS literals in the comparison text of a single WHEN subcommand.

AKQ255E: INVOKE SPECIFIES A SIDE FOR WHICH NO PLACE SUBCOMMANDS PUT DATA.

Explanation: The N_UP PLACE subcommand contains an error that makes it incompatible with the value specified in the INVOKE subcommand. Either INVOKE BACK was specified, but PLACE n BACK was not specified, or INVOKE FRONT was specified, but PLACE n FRONT was not specified.

System action: No form definition is generated. Processing continues.

User response: Specify the same value (FRONT or BACK) for both the INVOKE and PLACE subcommands.

AKQ256E: INCORRECT NUMBER OF PLACE SUBCOMMANDS.

Explanation: The required number of PLACE subcommands must be specified.

System action: No form definition is generated. Processing continues.

User response: When using N_UP PLACE subcommands with single-sided printing, the number of PLACE subcommands must equal the value specified on N_UP. When using duplex printing, the number of PLACE subcommands must equal two times the value specified on N_UP.

AKQ257W: CONSTANT (parameter) FOUND WITH PLACE SUBCOMMAND.

Explanation: The CONSTANT (parameter) subcommand can not be specified when N_UP PLACE subcommands are specified.

System action: A form definition is generated without constant forms control. The syntax check continues.

User response: Delete the CONSTANT (parameter) from the FORMDEF or COPYGROUP command.

AKQ258W: MORE THAN 122 OPERATION POSITIONS SPECIFIED FOR A FINISH OPERATION.

Explanation: More than 122 operation finishing positions are specified.

System action: A form definition will be generated with 122 finishing positions. All others will be ignored.

User response: Move extraneous operator position values.

AKQ259W: OPCOUNT AND OPPOS VALUES SPECIFIED. OPCOUNT IGNORED.

Explanation: Both OPCOUNT and OPPOS are specified.

System action: A form definition is not generated.

Operator response: If OPCOUNT is specified, OPPOS is ignored. When using OPPOS for controlling the position of each operation on the operation axis, OPCOUNT is ignored.

AKQ260E: (insert-1) not allowed with/on a (insert-2).

Explanation: This is a generic message which indicates a contextually incorrect combination of PPFA commands or subcommands. If this message indicates an action is not allowed with/on a CMR of this type, the processing mode is not valid for that type of CMR. LINK is valid only for device link (DL) CMRs and device link (DL) CMRs can only have processing mode LINK. Any other use of LINK processing mode results in error message AKQ260E. This message may indicate a PPFA command that is not compatible with MO:DCA IS/3.

System action: A page definition or form definition is not generated.

Operator response: Correct the incorrect parameter and rerun the job.

AKQ261E: (insert-1) requires (insert-2).

Explanation: This is a generic message which indicates a missing PPFA command or subcommand.

System action: A page definition is not generated.

Operator response: Add the required parameter and rerun the job.

AKQ262E: (insert-1) specifies a (insert-2) which is not a (insert-3).

Explanation: This is a generic message which indicates a contextually incorrect combination of PPFA commands or subcommands. For example that an ENDGRAPHIC command has specified or defaulted to a GRAPHID that does not match a floating DRAWGRAPHIC BOX or DRAWGRAPHIC LINE.

System action: A page definition is not generated.

Operator response: Correct the indicated problem.

AKQ263E: (insert-1) exceeds (insert-2).

Explanation: This is a generic message which indicates an out of bound condition for some parameters. For example that a DRAWGRAPHIC CIRCLE is positioned off the logical page.

System action: A page definition is not generated.

Operator response: Correct the indicated problem.

AKQ264W: (insert-1) is ignored (insert-2).

Explanation: This is a generic message which indicates that a contextually incorrect combination of PPFA commands or subcommands is clearly incorrect and is just ignored. For example, if a LINEONE subcommand was coded on a Record Format PAGEDEF (for example, one using LAYOUT), the LINEONE subcommand would just be ignored.

System action: A page definition is generated.

Operator response: No action necessary unless the result is not what you wanted.

AKQ265W: (insert-1) exceeds (insert-2).

Explanation: This is a generic message which indicates an out of bound condition for some parameters which is not necessarily critical. For example, when a DRAWGRAPHIC CIRCLE is positioned outside the margin boundary but still on the logical page.

System action: A page definition is generated.

Operator response: No action necessary unless the result is not what you wanted.

AKQ266E: PAGEDEF CONTAINS BOTH LAYOUT AND PRINTLINE COMMANDS.

Explanation: Lines are placed in a record format page definition using LAYOUT commands or in an XML page definition using XLAYOUT command, otherwise lines are placed with PRINTLINE commands. They cannot be mixed in the same page definition.

System action: A page definition is not generated.

Operator response: Remove either the LAYOUT, XLAYOUT, or PRINTLINE commands.

AKQ267E: MORE THAN ONE DEFAULT PAGEHEADER OR PAGETRAILER IN A PAGEFORMAT.

Explanation: Only one LAYOUT DEFAULT PAGEHEADER or PAGETRAILER can be coded in a PAGEFORMAT.

System action: A page definition is not generated.

Operator response: Remove one of the duplicates.

AKQ268E: SPECIFIED MARGINS FOR THIS PAGEFORMAT OVERLAP.

Explanation: Either the left margin is defined on or right of the right margin or the top margin is defined on or below the bottom margin.

System action: A page definition is not generated.

Operator response: Redefine the margins so that they do not overlap.

AKQ269E: A RECORD FORMAT PAGEDEF REQUIRES AT LEAST ONE FONT DEFINITION.

Explanation: At least one font must be defined whether or not one is referenced.

System action: A page definition is not generated.

Operator response: Define a font.

AKQ270E: PDF417 MACRO DATA BYTE (insert-1), CODEPOINT (insert-2) CANNOT BE TRANSLATED TO GLI 0 ENCODATION.

Explanation: This is an ASCII barcode and all code points must ultimately end up as ASCII. The printer will translate EBCDIC code points if you tell it, but it will translate the Macro data as well as the regular data.

When EBCDIC TO ASCII translation is requested for a PDF417 barcode, and the PAGEDEF is being compiled on an ASCII platform, and there is macro data it will be in ASCII. You now have mixed data which cannot be translated. So PPFA must translate the ASCII macro data to EBCDIC so that both will be the same. The printer can now translate the data and print the barcode. Now, not all EBCDIC code points will translate to GLI0 and we have just found one.

System action: The PAGEDEF will not be generated.

Operator response: Make sure that all the PDF417 macro text will translate to good EBCDIC code points.

AKQ271E: THE FONT TYPE AND USER DATA TYPE (UDTYPE) SPECIFIED CAUSES A DATA TRANSFORMATION THAT IS NOT SUPPORTED.

Explanation: When the User's Data Type (UDType) and font encoding are different, the printer must translate your data to the encoding type of the font. For example, if the UDType is UTF8 and the font is an ASCII font, then the printer would have to translate your data from UTF8 to ASCII. For this reason combinations are restricted to the following:

UDType of UTF8

Fonts can only be ASCII or UNICODE.

UDType of UTF16

Fonts can only be UNICODE.

System action: PAGEDEF is not generated.

User response: Chooses an appropriately encoded font.

AKQ275I: (insert-1)

Explanation: This is a generic informational message. Variable text inserts are printed. Two examples are:

1. EXTERNAL OBJECT NAME IS DUPLICATED.
2. KEYWORD USED AS A NAME. CHECK NAME NOT OMITTED. PROCESSING CONTINUES.

System action: Compilation continues. This definition is generated and stored or replaced.

Operator response: Make sure that the situation warned against is desired. For example, that the keyword used as a name is not actually a missing name, or that the duplicated object name is intended.

AKQ2MMS: NUMBER OF MESSAGES EXCEEDS THE 270 ALLOWED LIMIT. PROGRAM TERMINATES.

Explanation: PPFA allows only 269 messages, plus this one. When this limit is reached, the messages are printed and the program terminates.

System action: The program terminates.

Operator response: Correct the PPFA code for the messages issued and redo.

AKQ301I: PAGE PRINTER FORMATTING AID ENDED, MAX RETURN CODE = (max return code).

Explanation: This message accompanies the output listings of all form definitions and page definitions with the maximum return code for that particular object. Only when the return code is less than 8 is the object generated.

System action: None.

Operator response: None.

AKQ302I: NO ERRORS FOUND IN (resource name) DEFINITION.

Explanation: One definition is processed. No statements were flagged in this definition.

System action: This definition is generated, and stored or replaced.

Operator response: None.

AKQ303S: NO CONTROL STATEMENT(S) ARE SPECIFIED IN INPUT DATA.

Explanation: There are no control statements in the input data.

System action: The operation terminates.

Operator response: Specify a valid PPFA command.

AKQ304S: DEFINITION STATEMENT IS NOT SPECIFIED.

Explanation: There is no FORMDEF or PAGEDEF command in the system input command stream.

System action: The operation terminates.

Operator response: Specify valid definition commands.

AKQ305S: THIS DEFINITION IS NOT STORED BECAUSE MEMBER ALREADY EXISTS.

Explanation: This form definition or page definition is not saved because a file with the same name already exists in the directory (REPLACE option is NO).

System action: A page definition or form definition is not generated. The syntax check continues to next definition.

Operator response: Check the specified form definition or page definition name, and specify REPLACE subcommand YES. Specify another form definition or page definition name.

AKQ311I: FORMDEF (form definition name) IS GENERATED AND STORED. MAX RETURN CODE = (max return code).

Explanation: The form definition is generated and stored.

System action: A form definition is generated.

Operator response: None.

AKQ312I: FORMDEF (command name) IS GENERATED AND REPLACED. MAX RETURN CODE = (max return code).

Explanation: The form definition is generated and is replaced. The maximum return code is listed.

System action: A form definition is generated.

Operator response: None.

AKQ313E: FORMDEF (form definition name) IS NOT GENERATED. MAX RETURN CODE = (max return code).

Explanation: The form definition is not generated because of an error. The error is indicated by another message.

System action: A form definition is not generated.

Operator response: Correct the error.

AKQ321I: PAGEDEF (page definition name) IS GENERATED AND FILED. MAX RETURN CODE = (max return code).

Explanation: The page definition is generated and stored.

System action: A page definition is generated.

Operator response: None.

AKQ322I: PAGEDEF (page definition name) IS GENERATED AND REPLACED. MAX RETURN CODE = (max return code).

Explanation: The page definition is generated and is replaced.

System action: A page definition is generated.

Operator response: None.

AKQ323E: PAGEDEF (page-definition name) IS NOT GENERATED. MAX RETURN CODE = (max return code).

Explanation: The page definition is not generated because of an error. The error is indicated by another message.

System action: A page definition is not generated.

Operator response: Correct the error.

AKQ350T: AN UNRECOVERABLE PROGRAM ERROR OCCURRED.

Explanation: There was an error in PPFA logic.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ360E: FONT COMMAND DOES NOT CONTAIN SUFFICIENT INFORMATION.

Explanation: The FONT command referred to does not contain enough information to generate a valid MCF. This is caused by having a CS parameter without a CP parameter, or vice versa.

System action: A page definition is not generated.

Operator response: Correct the referenced FONT command.

AKQ361E: FONT COMMAND SPECIFIES CONFLICTING PARAMETERS.

Explanation: A FONT is specified in more than one way, only one of the following is allowed:

• Coded Font
• Character Set, Code Page pair (CS and CP parameters)
• GRID

System action: A page definition is not generated.

Operator response: Correct the referenced FONT command.

AKQ362E: FONT RATIO SPECIFIED WITHOUT FONT HEIGHT.

Explanation: To scale a font, both the HEIGHT and RATIO must be specified. If a RATIO subcommand is found without a HEIGHT subcommand, the scaling information can not be calculated by PPFA.

System action: A page definition is not generated.

Operator response: Correct the referenced FONT command.

AKQ363W: HEIGHT SPECIFIED, WIDTH IN GRID IGNORED.

Explanation: You have specified both a HEIGHT and GRID in the FONT command.

System action: None.

Operator response: Correct the referenced FONT command.

AKQ364E: INVALID DIRECTION WITH RELATIVE PRINTLINE.

Explanation: You specified an incorrect direction with the relative printline in your page definition source. The field direction must match the direction of the printline. The printline direction must be ACROSS.

System action: A page definition is not generated.

Operator response: Correct the referenced DIRECTION subcommand.

AKQ365W: COLOR AND EXTENDED COLOR SPECIFIED.

Explanation: Both COLOR and one of the extended color keywords (RGB, CMYK, HIGHLIGHT, CIELAB) was specified.

System action: Both requests are placed into the output resource. Output depends on printer function.

Operator response: If output does not print as expected, remove one of the specifications.

AKQ370E: BARCODE NAME WAS NOT PREVIOUSLY DEFINED.

Explanation: You attempted to reference a barcode name that had not been previously defined.

System action: A page definition is not generated.

Operator response: Correct the referenced BARCODE subcommand of the FIELD command.

AKQ371E: BARCODE NAME WAS PREVIOUSLY DEFINED.

Explanation: You attempted to define a barcode name that had been previously defined.

System action: A page definition is not generated.

Operator response: Correct the referenced BARCODE subcommand of the FIELD command.

AKQ372W: BARCODE MODIFICATION UNDEFINED FOR TYPE GIVEN.

Explanation: You specified a modification for a bar code that is not defined for the type specified.

See More About Bar Code Parameters for more information.

System action: A page definition is generated as specified. This is done so that, as new bar code types and modifications are introduced, you can create page definitions for them. However, you will receive this warning, because the specification could also be an error.

Operator response: Correct the referenced BARCODE subcommand of the FIELD command, if appropriate.

AKQ373W: BARCODE TYPE IS UNDEFINED.

Explanation: You specified a bar code type that is not defined.

System action: A page definition is generated as specified. This is done so that, as new bar code types and modifications are introduced, you can create page definitions for them. However, you will receive this warning, because this specification could also be an error.

Operator response: Correct the referenced BARCODE subcommand of the FIELD command, if appropriate.

AKQ374W: INVALID DATA LENGTH FOR SELECTED BARCODE TYPE AND MODIFICATION.

Explanation: You specified a data length for a defined barcode type and modification that is invalid for that combination of type and modification. When extra control characters are used as in the case of QRCode SOSI data, the data after translation might not exceed the limit. See More About Bar Code Parameters for more information.

System action: A page definition is generated as specified. This is done so that, as new bar code types and modifications are introduced, you can create page definitions for them. However, you will receive this warning, because this specification could also be an error.

Operator response: Correct the referenced BARCODE subcommand of the FIELD command, if appropriate.

AKQ401E: EXEC PARAMETER IS INVALID.

Explanation: The program parameter specification is invalid.

System action: A page definition or form definition is not generated. The syntax check continues.

Operator response: Specify a valid program parameter.

AKQ402T: ERROR OCCURRED DURING ATTEMPT TO OBTAIN STORAGE.

Explanation: conditions generate this message:

1. Exceeds the available size to hold the compiled data for the page definition and form definition.
2. Insufficient available disk space on the file system to write the output of the compiler.
3. Exceeds the limit of 269 user errors generated within a PPFA source file.

System action: The operation terminated.

Operator response:

1. Increase the region or VM program size.
2. Increase the size of the file system or specify a directory on another file system that has more disk space.
3. Fix the errors reported to this point and re-run PPFA.

AKQ403T: ERROR OCCURRED DURING ATTEMPT TO FREE STORAGE.

Explanation: A system error occurred while PPFA attempted to free disk space at the end of an execution.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ404T: SYSIPT OPEN FAILURE.

Explanation: SYSIPT cannot be opened.

System action: The operation terminates.

Operator response: Assign a valid input data file.

AKQ405T: INSUFFICIENT STORAGE TO EXECUTE PPFA.

Explanation: The region size is too small to execute PPFA.

System action: The operation terminates.

Operator response: Increase the region size available to the job.

AKQ410T: (Librarian error message).

Explanation: The message describes a librarian error.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ411T: FORMDEF LIBRARY OPEN FAILURE.

Explanation: The FORMDEF library cannot be opened.

System action: The operation terminates.

Operator response: Assign a valid FORMDEF library.

AKQ412T: FORMDEF LIBRARY I/O ERROR.

Explanation: An I/O error occurred during an attempted access of a form definition directory.

System action: The operation terminates.

Operator response: Check the permissions of the directory. If you do not have access, contact the owner of the directory. If this does not resolve the problem, contact a system programmer.

AKQ413T: FORMDEF DIRECTORY CANNOT BE UPDATED.

Explanation: The FORMDEF member cannot be registered on the directory.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ414T: FORMDEF LIBRARY CLOSE FAILURE.

Explanation: A form definition directory cannot be closed.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ415T: PAGEDEF LIBRARY OPEN FAILURE.

Explanation: The PAGEDEF library cannot be opened.

System action: The operation terminates.

Operator response: Assign a valid PAGEDEF library.

AKQ416T: PAGEDEF LIBRARY I/O ERROR.

Explanation: I/O error occurs during an attempted access of a page definition directory.

System action: The operation terminates.

Operator response: Check the permissions of the directory. If you do not have access, contact the owner of the directory. If this does not resolve the problem, contact a system programmer.

AKQ417T: PAGEDEF DIRECTORY CANNOT BE UPDATED.

Explanation: A page definition file cannot be registered on the directory.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ418T: PAGEDEF LIBRARY CLOSE FAILURE.

Explanation: A page definition directory cannot be closed.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ420T: SYSTEM ERROR. ABEND CODE = (ABEND code).

Explanation: System forces PPFA to terminate abnormally.

System action: The operation terminates.

Operator response: Contact a system programmer. Refer to the documentation for your operating system.

AKQ421T: FORMDEF LIBRARY IS FULL.

Explanation: The file system into which PPFA attempted to save the form definition is full.

System action: The operation terminates.

Operator response: Increase the size of the file system or specify a directory on a file system that has more disk space.

AKQ422T: PAGEDEF LIBRARY IS FULL.

Explanation: The file system into which PPFA attempted to save the page definition is full.

System action: The operation terminates.

Operator response: Increase the size of the file system or specify a directory on a file system that has more disk space.

AKQ501T: SYSIN OPEN FAILURE.

Explanation: The PPFA input source file cannot be opened.

System action: The operation terminates.

Operator response: Specify a valid input source file.

AKQ502T: SPANNED RECORD OF SYSIN IS NOT SUPPORTED.

Explanation: The spanned record of the PPFA input source file is not supported.

System action: The operation terminates.

Operator response: Specify a valid input record format.

AKQ503T: UNDEFINED LENGTH RECORD OF SYSIN IS NOT SUPPORTED.

Explanation: An undefined length record of PPFA input source file is not supported.

System action: The operation terminates.

Operator response: Specify a valid input record format.

AKQ504T: LOGICAL RECORD LENGTH OF SYSIN EXCEEDS LIMIT.

Explanation: The logical record length of the PPFA input source file exceeds limit which is 100 bytes except for the OS/390 variable length which is 104 and AIX which is 254.

System action: The operation terminates.

Operator response: Correct the logical record length of the file.

AKQ510T: FORMDEF/PAGEDEF LIBRARY OPEN FAILURE.

Explanation: The FORMDEF or PAGEDEF directory cannot be opened.

System action: The operation terminates.

Operator response: Specify a valid FORMDEF or PAGEDEF or check to make sure that the directory is correct.

AKQ511T: I/O ERROR OCCURRED DURING (FORMDEF/PAGEDEF) DIRECTORY SEARCH. RETURN CODE = (return code) REASON CODE = (reason code)

Explanation: I/O error occurred while performing FIND function.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ512T: LOGICAL RECORD LENGTH OF FORMDEF/PAGEDEF EXCEEDS LIMIT.

Explanation: The logical record length exceeds maximum or minimum value.

System action: The operation terminates.

Operator response: Specify a filename that has a valid record length.

AKQ513T: BLOCK SIZE OF FORMDEF/PAGEDEF EXCEEDS LIMIT.

Explanation: The block size exceeds m aximum or minimum value.

System action: The operation terminates.

Operator response: Assign a filename that has a valid block size.

AKQ514T: UNDEFINED LENGTH RECORD IS NOT SUPPORTED IN FORMDEF/PAGEDEF LIBRARY.

Explanation: An undefined length record is not supported in FORMDEF/PAGEDEF directory.

System action: The operation terminates.

Operator response: Assign a valid record format.

AKQ515T: FIXED LENGTH RECORD IS NOT SUPPORTED IN FORMDEF/PAGEDEF LIBRARY.

Explanation: The fixed length record is not supported in the FORMDEF or PAGEDEF library.

System action: The operation terminates.

Operator response: Assign a valid record format.

AKQ516T: NO CONTROL CHARACTER RECORD IS SUPPORTED IN FORMDEF/PAGEDEF LIBRARY..

Explanation: No control character record is supported in FORMDEF/PAGEDEF directory.

System action: The operation terminates.

Operator response: Assign a valid record format.

AKQ517T: NO SPACE IN FORMDEF/PAGEDEF DIRECTORY.

Explanation: No space was available in the FORMDEF directory or the PAGEDEF directory to add or replace the resource.

System action: The operation terminates.

Operator response: Increase the directory space or specify a directory on another file system that has more disk space.

AKQ518T: I/O ERROR OCCURRED WHILE UPDATING FORMDEF/PAGEDEF DIRECTORY. RETURN CODE = (return code). REASON CODE = (reason code).

Explanation: A permanent I/O error was detected, or the specified data control block is not opened, or insufficient disk space exists to perform the write function.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ519T: I/O ERROR OCCURRED DURING WRITE.

Explanation: The error message is displayed.

System action: The operation terminates.

Operator response: Contact a system programmer.

AKQ520T: SPANNED RECORD IS NOT SUPPORTED IN FORMDEF/PAGEDEF LIBRARY.

Explanation: The spanned record is not supported in the FORMDEF or PAGEDEF library.

System action: The operation terminates.

Operator response: Remove the SPAN attribute and assign a valid dataset.

AKQ522T: BLOCK SIZE IS NOT SPECIFIED FOR FORMDEF/PAGEDEF DATA SET.

Explanation: A block size is not specified for FORMDEF/PAGEDEF data set.

System action: The operation terminates.

Operator response: Specify a BLKSIZE in the DD statement.

AKQ540T: SYSTEM ABEND (code) OCCURRED IN PPFA PROCESS.

Explanation: A system ABEND (code) occurred in PPFA/OS/390 process. Termination processing was performed by the ESTAE macro instruction.

System action: The operation terminates.

Operator response: Contact a system programmer. Refer to System Messages for your operating system.

AKQ541T: USER ABEND (code) OCCURRED IN PPFA/OS/390 PROCESS.

Explanation: A user ABEND (code) occurred in PPFA/OS/390 process. Termination processing was performed by the ESTAE macro instruction.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ600T: INPUT FILENAME NOT SPECIFIED.

Explanation: You did not specify an input filename.

System action: The operation terminates.

Operator response: Enter the input filename.

AKQ601T: INPUT FILETYPE NOT SPECIFIED.

Explanation: You did not specify an input filetype.

System action: The operation terminates.

Operator response: Enter the input filetype.

AKQ602T: COMMAND SYNTAX IS NOT VALID.

Explanation: The command syntax you entered was not accepted.

System action: The operation terminates.

Operator response: Enter a valid command.

AKQ603T: FILEMODE FOR (FORMDEF/PAGEDEF/LISTING) IS INVALID.

Explanation: You entered an invalid filemode for FORMDEF, PAGEDEF, or LISTING.

System action: The operation terminates.

Operator response: Enter a valid file extension.

AKQ604T: INVALID PARAMETER IS SPECIFIED IN (FORMDEF/PAGEDEF/LISTING/SIZE) OPTION.

Explanation: You entered an invalid parameter for FORMDEF, PAGEDEF, LISTING, or SIZE.

System action: The operation terminates.

Operator response: Enter a valid option parameter.

AKQ605T: (FORMDEF/PAGEDEF/LISTING/SIZE) KEYWORD IS DUPLICATED.

Explanation: You entered a duplicate keyword for FORMDEF, PAGEDEF, LISTING, or SIZE.

System action: The operation terminates.

Operator response: Enter a unique keyword.

AKQ606T: FILETYPE FOR (FORMDEF/PAGEDEF/LISTING) NOT SPECIFIED.

Explanation: The filetype for FORMDEF, PAGEDEF, or LISTING was not entered.

System action: The operation terminates.

Operator response: Enter an appropriate filetype.

AKQ607T: INVALID KEYWORD SPECIFIED.

Explanation: The keyword you entered was not accepted.

System action: The operation terminates.

Operator response: Enter a valid keyword.

AKQ608T: INVALID SIZE PARAMETER SPECIFIED.

Explanation: The size parameter specified is not valid.

System action: The operation terminates.

Operator response: Enter a valid size parameter.

AKQ610T: SIZE PARAMETER VALUE EXCEEDS THE ALLOWABLE MAXIMUM.

Explanation: The size entered exceeds the maximum allowable.

System action: The operation terminates.

Operator response: Enter a valid size value.

AKQ611T: SIZE PARAMETER VALUE IS TOO SMALL.

Explanation: The size entered is too small for executing in PPFA/VM..

System action: The operation terminates.

Operator response: Enter a valid size value.

AKQ612T: INVALID FILE IDENTIFIER ‘*’ SPECIFIED FOR INPUT FILE.

Explanation: ‘*’ is specified for input filename or filetype.

System action: The operation terminates.

Operator response: Enter a valid filename or filetype.

AKQ613T: SIZE PARAMETER VALUE IS MISSING.

Explanation: You did not specify a size parameter.

System action: The operation terminates.

Operator response: Specify a valid size parameter.

AKQ620T: INPUT FILE WAS NOT FOUND.

Explanation: The input filename entered was not found.

System action: The operation terminates.

Operator response: Correct the input filename.

AKQ621T: NO READ/WRITE (file mode) DISK ACCESSED FOR (INPUT/LISTING/FORMDEF/PAGEDEF /OUTPUT).

Explanation: The disk on which the file is saved cannot be read from or written to because it either was not accessed or was accessed using an invalid access mode.

System action: The operation terminates.

Operator response: Access the file system using a valid access mode.

AKQ622T: INPUT FILE EXCEEDS THE ALLOWABLE LOGICAL RECORD LENGTH MAXIMUM.

Explanation: The logical record length of the input file exceeds the limit which is 100 bytes except the OS/390 variable record length is 104 and AIX is 254.

System action: The operation terminates.

Operator response: Correct the logical record length of the file.

AKQ624T: I/O ERROR OCCURRED IN (AKQINIO/AKQLBIO/AKQPRIO) MODULE. RC = (return code from FWRITE/FGETS macro instruction).

Explanation: An I/O error occurred during either FGETS or FWRITE processing of module AKQINIO, AKQLBIO, or AKQPRIO.

System action: The operation terminates.

Operator response: Contact your system programmer. Refer to the return code in AIX Operating System Messages.

AKQ625T: DISK (file mode) IS FULL.

Explanation: Not enough space is available on the specified file system to write the file.

System action: The operation terminates.

Operator response: Erase some files from the specified file disk and re-execute.

AKQ639T: ABEND EXIT ROUTINE FAILED TO EXECUTE. RC = (return code from ABNEXIT macro).

Explanation: ABEND exit routine cannot be established.

System action: The operation terminates.

Operator response: Contact your system programmer. Refer to the return code in AIX Operating System Messages.

AKQ640T: SYSTEM ABEND (code) OCCURRED IN PPFA/VM PROCESS.

Explanation: A system ABEND occurred during processing. The ABEND exit routine ended processing.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ641T: USER ABEND (code) OCCURRED IN PPFA/VM PROCESS.

Explanation: A user-initiated ABEND occurred during processing. The ABEND exit routine ended the processing.

System action: The operation terminates.

Operator response: Use local problem-reporting procedures to report this message.

AKQ700I: SIZE PARAMETER IS NO LONGER NECESSARY IN PPFA/370.

Explanation: The storage required to contain the messages and control blocks is not automatically set at 32K and 128K respectively. If the control block storage is used up, an additional 128K will be gotten and chained to the previous. All storage necessary to perform the compile will be obtained during processing.

System action: The compile process continues.

Operator response: None.