Category: Report Writer module.
The privilege card does not allow access to the Report Mock-Up Painter. Execution will halt.
Use COBOL or another available report writer. Contact your APS Administrator for Report Writer privileges.
You exceeded the limit (300) of SOURCE, SUM, and VALUE entries in one source program.
Reduce the number of SOURCE, SUM, and VALUE entries in the program. You might compile some report descriptions separately.
You exceeded the limit of 200 lines in the left half of the mock-up.
If the mock-up requires exceeding the line limit to produce the report, do not incorporate blank lines in the mock-up. Use the Line statement to position the report. Verify that you coded the mock-up properly.
The number of reports specified within a Report clause exceeds 15.
Limit the number of reports per FD to 15. Add additional FD'S if necessary. Contact your APS Administrator if you need more assistance.
APS detected a clause beginning with a keyword other than CONTROL, CODE, PAGE, FIRST, LAST, HEADING, FOOTING, or WRITE in the Report Description statement or the required period at the end of the Report description statement is missing.
Verify spelling of keywords and/or insert the required period.
You exceeded the maximum number of control items (28) allowed for the report.
Decrease the number of controls.
You did not follow a Terminate or Initiate statement with a data name.
Enter data name.
You followed an Initiate statement with an improper report name.
Correct report name.
You did not follow a Generate statement with a data name.
Enter data name.
You followed a Generate statement with an improper report name or data name.
Verify report/data name. If the report name is correct, look for an illegal or missing 01 type clause or Mock-up statement.
You followed a Terminate statement with an improper report name.
Enter correct report name.
APS did not find a Declaratives statement before encountering an End statement.
Enter missing Declaratives statement.
APS did not find an End Declaratives statement for the Declaratives section.
Enter missing End Declaratives statement.
The privilege card does not allow access to the report writer module. Execution will halt.
Arrange with the APS Administrator for a new privilege card.
APS encountered a detail item that does not have a Picture clause associated with it.
Code the Picture clause.
A problem occurred during the storage of detail items. Execution will halt.
Contact the APS Administrator.
APS encountered an identifier item that does not have a Picture clause associated with it.
Code the Picture clause.
There is no detail line associated with the Format Extract clause.
Code required detail line.
The Report Description keyword (RED or AUTO) is missing or coded in the wrong column.
Correct the code to include the Report Description keyword.
The Auto (Report Description) statement is not present in the program.
Correct the code to include the Auto statement.
APS encountered an Auto clause that you did not follow with the mandatory report name.
Add the report name to the Auto statement.
A valid data name must follow the CH (Control Heading) or CF (Control Footing) clauses.
Enter valid data name.
You did not give a parameter that tells where to print the specified identifier.
Code a placement parameter.
You must follow the Cover Placement parameter with integer(s). These indicate column placement for centering of the specified literals or identifiers.
Enter correct integer(s) to indicate column placement.
You can use numeric literals only with detail.
Remove non-numeric literals from code.
You did not give a parameter that tells where to print the specified literal.
Code a Placement parameter.
The number of characters where a literal should be is equal to zero. Therefore, it is invalid.
Code legal literal.
You can only use /PAGE/ once for a group, and it must precede all other parameters.
Correct code.
APS encountered a Placement parameter that you did not follow with an identifier or literal.
Enter identifier or literal.
/INTEGER/ indicates a relative number of lines to advance before presenting the first line of the group if used with detail. It is not permitted elsewhere.
Code /INTEGER/ in detail group only.
You can write Placement parameters as keywords only in a non-detail Group Description clause.
Correct code to only use Placement parameters in non-detail Group Description clauses.
You can only use the Group Indicate and Change Indicate clauses with detail lines.
Use proper Indicate with detail line.
Group and Change Indicate both need an identifier following them which APS uses to determine when to print an item.
Enter needed identifier.
APS only allows Picture clauses for detail items.
Correct code.
Identifier is missing before the specified Picture clause.
Enter needed identifier.
APS encountered a subscript or index that you did not prefix with an identifier. APS halts execution.
Place the correct identifier before the subscript/index.
You can only use iterative subscripts for detail lines.
Correct code.
You used more than 3 levels of subscripts or indices where APS only permits 3 levels.
Correct the code to use only 3 levels of subscripts or indices.
In Auto processing, APS found an iterative expression in the format # INTEGER-1/ INTEGER-2 in which INTEGER-2 is less than or equal to INTEGER-1.
Make INTEGER-2 greater than INTEGER-1 or delete INTEGER-2 if INTEGER-1 specifies the top limit of the increment range.
The subscript or index as coded is incorrect.
Correct subscript index.
You can only use the Cover parameter with page headings, heading and footing groups. You may not use it with detail clauses.
Remove Cover parameter from detail clause.
The parameters used during Auto processing of the Detail group were syntactically incorrect.
Correct syntax of Detail group. Refer to manual for correct format of syntax requirements.
There must be at least one identifier in each detail line.
Correct code.
The integer specified for a Page Limit, First Detail, Last Detail, Heading, Footing, Subscript or Cover parameter is greater than the maximum allowable 4 digits.
Change integer to allowable number of digits.
During auto processing of the Page Limit, Heading, Detail or Footing clauses, APS expected an integer and did not find it.
Correct data field to be numeric integer.
APS encountered a negative number where it allows only a positive number.
Code a positive number.
APS encountered a problem in Page Heading storage. Execution will halt.
Contact the APS Administrator.
A Detail group must follow a Detail clause.
Code a Detail group after the Detail clause.
During Auto processing of multiple reports, APS found a duplicate Report group.
Correct Report group names making sure that they are unique in each report.
You must use a control variable with a control heading and control footing in a Control clause. APS did not encounter such a variable.
Enter Control variable.
APS found something other than a mock-up delimiter following the Report Description statement.
Correct the code. Possibly you coded two periods coded in the Report Description statement. APS allows only one.
APS did not find a mock-up for a Report Description entry.
Include mock-up.
APS found a word in AREA-A in the report section which RWT does not recognize.
Correct code.
You did not specify a control identifier (data name) on a Type clause for a Control Heading (CH) or Control Footing (CF) group.
Supply the correct identifier.
You exceeded the buffer limit (25) for consecutive debugger lines. A block of comments with more than 25 lines is probably the cause.
Reduce the number of consecutive comment lines, or set the DEBUG option on GENERATOR OPTIONS to NO.
APS found a mock-up statement when using group mock-ups. You should use mock-up statements only with report mock-ups.
Delete mock-up statement.
APS encountered a mock-up statement out of sequence in a Group Description entry.
A Mock-up statement should occur next after the 01 type statement.
APS encountered a line statement out of sequence in a group description entry.
A Line statement should occur next in sequence after the Mock-up statement; or, if there is not a Mock-up statement (because you used a group mock-up), after the 01 type statement.
Characters following LINE IS or LINE NUMBER IS in a Line statement are not numeric.
Correct the code.
You did not code an item description entry (Source, Sum, or Value statement) correctly.
Correct the code.
You coded ANTIFREEZE in the report section with an APS parameter setting of NOFREEZE (the default).
Change APS parameter to include FREEZE.
APS found an iterative expression, in the format # INTEGER-1 / INTEGER-2, in which INTEGER-1 is not less than INTEGER-2.
Correct code.
You coded a Sum, Source, or Value clause for which there is no matching picture in the mock-up. Possibly you did not delete a Source clause that you no longer reference in the mock-up. Another possibility is that the Mock-up line statements do not accurately match the lines specified for each group in the mock-up.
Correct the present picture. Add a new one for the equivalent Source clause or delete the no longer needed Source clause. Also check mock-up and Mock-up statement.
A Reference statement contains no Picture clause.
Code a PIC clause for the Reference statement.
The right half of the mock-up has more lines than the left.
Correct the code so that right and left halves of the mock-up match. A possible cause is a delimiter (a non-blank character, non-alphabetic and non-numeric) in Column 7, continuing for 4 or more consecutive bytes.
APS did not find the right half of the report mock-up following the left half.
Code mock-up continuation.
You exceeded the limit of 200 lines in the right half of the mock-up.
Code mock-up to not exceed the limit.
A mock-up statement specifies a line number outside the range of the report mock-up as its beginning line or APS found a Mock-up statement when using group mock-ups.
Make the line number greater than 0 or check the Report mock-up for actual number of lines used. You should use mock-up statements with Report mock-ups. Delete Mock-up statement.
A Mock-up statement using the INTEGER-1 through INTEGER-2 format, specifies a line number outside the range of the Report mock-up as its ending line (INTEGER-2).
Make the line number greater than 0 or check the Report mock-up for actual number used.
You specified a data name following a left parenthesis in a Source clause.
Remove the parenthesis.
You specified a data name following a left parenthesis in a Source clause without a closing right parenthesis.
Remove the left parenthesis or verify need for right parenthesis.
You did not follow the keyword designating a Picture (or PIC) in a Sum/Source/Value statement by a COBOL Picture character. If the optional keyword IS has been used, no Picture character follows it.
Remove the Picture clause or supply a correct picture following the Picture keyword. Note that APS does not require a Picture clause but a Picture clause is very helpful in catching incompatibilities between the Mock-up and the Sum/Source/Value statements early in the debugging process (at compile time, rather than execution time).
In a PIC or Picture clause of a Sum/Source/Value or Reference clause, APS encountered an opening parenthesis following a valid Picture character ( X 9 Z $ , 0 . + - C R D * V E ), and APS found a numeric field following the opening parenthesis. APS did not find a closing parenthesis after that.
Correct the code. Note that A is not among the valid Picture characters.
In a PIC or Picture clause of a Sum/Source/Value or Reference clause, APS encountered a character other than X 9 Z $ , 0 . + - C R D * V E ( ).
Correct the code.
APS encountered an Overprint statement that does not include a character string enclosed in quotes.
Correct the statement.
You followed a File Description entry (FD) by blanks or an improper file name.
Correct code.
You improperly coded a Block Contains clause with the optional INTEGER-1 to INTEGER-2 format. INTEGER-2 is not an unsigned integer.
Correct code.
You coded a Block Contains clause in an improper format. You coded the clause with something other than characters or records or you did not specify an unsigned integer.
Correct code.
You improperly coded a Record Contains clause with the optional INTEGER-1 to INTEGER-2 format. INTEGER-2 is not an unsigned integer.
Correct code.
You coded a Record Contains clause in an improper format. You coded the clause with something other than characters or records or you did not specify an unsigned integer.
Correct code.
You coded the Mode clause with an improper mode (i.e., something other than F, V, U, or S).
Enter proper mode.
You coded a Label Records clause in an improper format.
Correct code.
You coded a Value Of clause with an improper file ID.
Enter correct file ID.
You coded a Report clause in an improper format.
Correct format.
You coded a Data Records clause in an improper format.
Correct format.
You followed a Report Description entry (RED or RD) with blanks or an improper name.
Correct code.
You followed a Code clause with an improper mnemonic name or by blanks.
Correct code.
You coded a Control clause in an improper format.
Correct format.
You coded a Page Limit clause in an improper format or the clause specifies 0 as the last line where you can print anything.
Correct code or page limit.
You coded a Heading clause in an improper format or the clause specifies 0 as the first line number of the heading print group.
Correct code or Heading clause.
You coded a First Detail clause in an improper format or the clause specifies 0 as the first line number of the body group.
Correct code or First Detail clause.
You coded a Last Detail clause in an improper format or the clause specifies 0 as the last line number of the last nonfooting body group.
Correct code or Last Detail clause.
You coded a Footing clause in an improper format. The clause specifies 0 as the last line number of the last Control Footing Report group.
Correct Footing clause.
A Type clause specifies an option other than those allowed (i.e.,. RH, PH, CH, CF, PF, RF, DE or the fully spelled out equivalents of each of these).
Enter correct option.
You coded a Line clause in an improper format or INTEGER-1 is not a positive integer for the LINE NUMBER IS INTEGER-1 format; INTEGER-2 is not a positive integer for the LINE NUMBER plus INTEGER-2 format.
Correct format.
You coded a Next Group clause in an improper format or INTEGER-1 is not a positive integer for the NEXT GROUP IS INTEGER-1 format; INTEGER-2 is not a positive integer for the NEXT GROUP IS PLUS INTEGER-2 format.
Correct code.
You coded a Usage clause in an improper format. You specified a usage other than DISPLAY.
Correct format.
You coded the Reset option of the Sum clause in an improper format.
Correct format.
You coded the Justified clause in an improper format. You followed JUSTIFIED (or JUST) with something other than RIGHT or you coded on a clause other than SOURCE or you coded for a data item that is numeric.
Correct format.
You coded the Blank When Zero clause in an improper format.
Correct format.
You coded the Change Indicate clause in an improper format.
Correct format.
You coded the Group Indicate clause in an improper format.
Correct format.
You coded the Column clause in an improper format. You did not specify a positive integer.
Correct format.
You coded the value label for a Source clause in an improper format. You did not specify an integer, keyword or quoted string.
Correct format.
The Sum clause does not specify a valid data name.
Enter correct data name.
The Source clause does not specify a valid data name.
Enter correct data name.
You coded the UPON option of the Sum clause in an improper format.
Correct format.
You coded the Picture phrase with an invalid character string.
Correct Picture phrase.
You coded a Use Before Reporting sentence in an improper format.
Correct format.
You followed an Initiate statement with a report name for which there was no Report Description entry.
Correct Initiate statement.
You followed a Terminate statement with a report name for which there was no Report Description entry.
Correct Terminate statement.
You specified a report name more than once for a Report Description entry.
Make each report name unique.
APS encountered a subscript or index that surpassed the allowable number of subscript or index levels.
Reduce the number of subscripts or indices.
The picture clause is missing for the data name specified.
Code picture clause for data name.
A column clause is not present where one is necessary.
Add the column clause to the code.
A Use Before Reporting sentence specifies a data name which is neither a Heading nor Footing Report group.
Correct Use Before Reporting sentence.
You exceeded the maximum number of detail groups (99).
Reduce the number of detail groups.
The type coded in the Type clause is not consistent with that in the Control clause.
Determine which Type clause is correct and fix the incorrect one. If the Type clause appears correct, the number of control clauses may have exceeded the maximum (28) for the report. Reduce the number of Control clauses.
A Source clause is not present where one is necessary.
Add the Source clause to the code.
A Sum clause is not present where one is necessary.
Add the Sum clause to the code.
APS encountered a hyphen (-) in column 7, or APS encountered an ellipsis (...) as the opening word or symbol of a statement.
Replace the hyphen in column 7 with a properly placed continuation ellipsis. If an ellipsis is present, check for correct alignment with preceding code. Note that there should not be a blank line between original line of code and continuation line containing the ellipsis.
Column 7 contains a character other than an asterisk (*) or a hyphen (-).
Remove the character from column 7. You can reinsert it in column 7 at the COBOL level if you require it for COBOL compilation.
APS encountered a hyphen (-) at the end of the given data name.
Correct the code.
The given data name contains more than 30 characters.
Correct the code.
The given integer contains more than 30 characters.
Correct the code.
The given number contains more than 30 characters.
Correct the code.
The given Picture clause contains more than 30 characters.
Follow the COBOL rule of a maximum of 30 characters for a Picture clause.
APS encountered a Picture clause for a source statement that has edit characters in it.
Correct the Picture clause.
APS encountered Picture statement that contained a character other than X Z , . 9 A B 0 * + - $ E ( or ) (left or right parenthesis).
Correct the Picture clause.
APS encountered a level number (01, 05, etc.) That you did not follow with a space.
Add a space after the level number.
You specified a line number for the printing of the Report Footing.
Specify a line number on the Footing clause.
You exceeded the maximum storage capability of group line items (1625) resulting in table overflow.
Reduce the number of group line items.
You exceeded the maximum storage capability of 30 source items resulting in table overflow.
Reduce the number of source items.
There is not enough room to print the Control Footing where specified.
Check the Report Description entry for the footing and correct.
The Footing line as computed by Auto is less than or equal to zero.
Check syntax for Heading, Detail, and Page clauses.
The integers given on the Heading, Detail, or Footing clause exceed the Page Limit clause. The integers must be in ascending order.
Correct integers used on clauses so they are in ascending order, and not greater than the Page Limit clause.
APS encountered a Page clause before the Auto statement. The Auto statement must come first.
Correct the code so the Auto statement is before the Page clause.
The page limit given was not an integer. APS move the number, 58, to the page limit temporarily for further processing.
Correct the page limit.
The coded Page Limit clause contains a character other than an integer as the page limit.
Correct the Page Limit clause with an integer as the specified limit.
You did not request vertical spacing in the Page Number clause. APS assumes Top.
Correct Page Number clause.
You did not request horizontal spacing in the Page Number clause. APS assumes Right.
Correct Page Number clause.
A word other than NUMBER(S), HEADING or FOOTING follows the Page clause in the program.
Correct code so the Page clause will contain a valid word.
The value following the Heading clause is not an integer so APS calculated the value.
Follow the Heading clause with a valid integer.
The value following the Footing clause is not an integer so APS calculated the value.
Follow the Footing clause with a valid integer.
APS encountered something other than EXTRACT or BOXED after a format statement.
Replace the invalid code with the appropriate correct word.
APS encountered a group type other than Report Heading or Report Footing. Possibly you followed REPORT with something other than HEADING or FOOTING.
You can only follow REPORT with HEADING or FOOTING as proper group type.
In the Control clause, CONTROL IS/ARE is not followed by a data name.
Correct the coded clause.
Something other than a valid line number follows the First Detail clause.
Correct the code so a valid line number follows the clause.
FIRST is a COBOL reserved word and you must use it as one except when you use it in the First Detail clause.
Correct use of FIRST.
Something other than a valid line number follows the Last Detail clause.
Correct the code so a valid line number follows the clause.
LAST is a COBOL reserved word and you must use it as one, except when you use it in the Last Detail clause.
Correct use of LAST.
In the Auto section of the program, APS encountered an invalid word.
Correct code to use only valid words and phrases under the Auto statement.
The /PAGE/ keyword is invalid for Page Heading because it always begins a new page. It is invalid for Page Footing because it cannot begin a new page, and it is invalid for Detail because APS only allows one type of detail in Auto.
Correct code to use the /PAGE/ keyword properly.
APS does not allow SUPPRESS on groups except for PH (Page Heading), CH (Control Heading), or CF (Control Footing).
Correct code to use SUPPRESS properly.
A word other than INDICATE follows a Group or Change clause.
Correct code.
The Picture clause given for a particular source item does not match the source item.
Correct code so that all picture clauses and source items match.
The code that follows the PIC statement in the Picture clause is incorrect.
Correct the Picture clause.
APS encountered an integer without a correct parameter prefixing it (i.e., COVER).
Prefix the integer with a correct parameter.
If APS encounters column 72 after a string (or alphanumeric literal) opens, APS places a quote in column 72.
Correct the code.
You specified a control identifier (data name) on a Type clause for a group other than Control Heading (CH) or Control Footing (CF).
Remove the invalid identifier.
You did not follow a Type clause for a report mock-up by a Mockup statement.
Code Mockup statement.
The syntax used for the DECIMAL-POINT IS COMMA clause is invalid.
Correct the syntax.
The currency symbol in the Currency Sign clause cannot be any of the following characters: 0-9 A B C D L P R S V X Z SPACE * + - / , . ; ( ) = ".
Change the Currency symbol specified in the Currency Sign clause to a valid character.
The syntax used for the Currency Sign clause is invalid.
Correct the syntax.
The optional report description clause, WRITE ROUTINE, is only available when the RWT parameter is ON.
Turn on the RWT parameter or delete the Write Routine clause.
The syntax used for the Write Routine clause is invalid.
Correct the syntax.
APS found more than one control heading or control footing for this control item.
Correct code to have only one control heading or control footing for the control item named.
The third split of the mock-up has more lines than the first and second splits.
Correct the code so the third split matches the first and second.
The fourth split of the mock-up has more lines than the first, second, and third splits.
Correct the code so the fourth split matches the first three.
You exceeded the limit of 200 lines in the third split of the mock-up.
Reduce the number of lines to 200 or less.
You exceeded the limit of 200 lines in the fourth split of the mock-up.
Reduce the number of lines to 200 or less.
You exceed the limit of 3 CONT-MOCKUP statements for one mock-up.
Reduce the number of CONT-MOCKUP statements to 3 or less. A mock-up may have up to four splits and thus up to three CONT-MOCKUP statements to link them.
The Report Description contains RD. COBOL will compile correctly.
Change RD to RED in source code.
APS replaces the 01 level you coded with an APS generated 01 level.
When you specify MOVE 1 TO PRINT-SWITCH, the Heading or Footing Report group you want to suppress should be in a Use Before Reporting sentence.
Check to ensure that you use a Use Before Reporting sentence for the group you want to suppress.
You computed a heading to go in an area that is already occupied by something else.
Check Heading and Cover clause for errors.
The Report Heading line number and the line number given in the Heading clause are not the same.
Correct the Heading clause so that the two agree.
The Report Footing line number and the line number given in the Heading clause are not the same.
Correct the Heading clause so that the two agree.
The report heading and the given Report Heading clause are not the same.
Correct the Heading clause so that the two agree.
The page heading and the given Page Heading clause are not the same.
Correct the Heading clause so that the two agree.
The line number given in the Page Heading clause and the computed line number for the Page Heading line are not the same.
Correct the Page Heading clause.
The line number given in the First Detail clause and the computed line number for the first detail line are not the same.
Correct the First Detail clause.
The line number given in the Report Footing clause and the computed line number for the report footing line are not the same.
Correct the Report Footing clause.
The line number given in the Page Footing clause and the computed line number for the page footing line are not the same.
Correct the Page Footing clause.
The line number given in the Footing clause and the computed line number for the footing line are not the same.
Correct the Footing clause.
The line number given in the Last Detail clause and the computed line number for the Last Detail line are not the same.
Correct the Last Detail clause.
The given Page Number clause is incorrect. APS will place page numbers at the top right of page.
You must code subscripts all on one line. APS attempted a continuation.
Code all subscripts on one line.
APS found a word starting in AREA-A beginning with an M in the Report section. APS assumes a Mock-up.
Correct statement.
You left a period off of the sentence preceding an FD or SD statement.
Add the missing period.
The DECIMAL-POINT IS COMMA clause should not begin in AREA-A.
Indent clause to AREA-B.
The Currency Sign clause should not begin in AREA-A.
Indent clause to AREA-B.
You used a "next group" clause on a page heading, page footing, or report footing. This is not proper syntax for these groups.
No response necessary in most cases, but unexpected results may occur.
In the REPORT clause of an FD, you specified a report-name that you did not define via a RED section header.
Define the named report with a RED Section header, or eliminate it from the report clause of the associated FD.
You cannot match a report defined via a RED section header with any report record description. The report neither uses the WRITE ROUTINE clause nor gets associated with an FD by a REPORT IS clause.
Associate the report to an FD with the REPORT IS clause, or specify developer control of the report via the WRITE ROUTINE clause in the RED section header.
You exceed the space allocated for Structure Block storage.
Contact your APS Administrator.
You exceeded the space allocated for Group Block storage.
Contact your APS Administrator.
The internal table used by APS is full. APS halts execution.
It may be necessary to process the program in two parts and recombine the output for the COBOL compile. Contact your APS Administrator.
The internal data segments used by APS are full. Execution will halt.
Contact your APS Administrator.
The internal buffer used by APS is full. APS halts execution.
It may be necessary to break one long paragraph into two paragraphs.
The internal table used by APS is full. APS halts execution.
Contact your APS Administrator.
Internal processing of the source code expected to find Working Storage information and could not find it.
Rerun. If you receive the same results, contact your APS Administrator.
Internal processing of the source code expected to find Linkage/Communication section and did not find it.
Rerun. If you receive the same results, contact your APS Administrator.
A problem occurred during the storage of identifier items. Execution will halt.
Contact your APS Administrator.
During Auto processing to generate an overline for a total footing line, APS detected an internal problem.
Contact your APS Administrator.
Internal structure block used by APS has overflowed. Execution will halt.
Contact your APS Administrator.
You can only specify 100 reports per program when you use the APS Report Writer Translator.
Contact your APS Administrator if you require more than 100 reports in the program.
Copyright © 2002 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.