Appendix E: Precompiler Messages

The following messages may be issued during precompilation under various circumstances. Most are self-explanatory, but an additional explanation is given below for each of them. The severity level of each message is also shown. The meanings of these are as follows:

• Severe (S) Implies a serious violation of the rules of syntax or usage, such that the object program is not reliable - perhaps even incomplete - and should not be run.

• Error (E) Implies a violation of the rules of syntax or usage, but such that the resultant program will be executable, although the results will not necessarily be those expected.

• Warning (W) Implies a less severe violation of the rules, or a situation where a change to the code is preferable, although the program will execute as intended.

• Informational (I) Is used for a confirmatory or informational message and does not imply any violation on behalf of the user. Return codes are issued by the precompiler to indicate the most severe level of error. They are listed in Installation and Operation.

Messages

Ident.-Sev.	Message and Explanation
RW-001-I	No Report Writer data entries were found in this program. The precompiler found no REPORT SECTION. This is not an error, as the program need not contain report writer statements.
RW-002-S	Clause xx not allowed in this context: ignored. The given clause should not be coded in this type of entry.
RW-003-S	Unrecognized item xx: discarded. The given word was found when a new clause keyword was expected.
RW-004-S	Report Writer statements in FILE-CONTROL/FILE SECTION but no REPORT SECTION. The program contains a report writer clause in a SELECT...ASSIGN or FD entry but there is no REPORT SECTION.
RW-007-S	No END DECLARATIVES found. While processing the DECLARATIVES portion, the precompiler encountered the end of the source before END DECLARATIVES.
RW-008-I	FD has record definition but no RECORD CONTAINS: compiler may assume variable-length. If there is an 01-level entry following the FD for a report file, the record description generated by the precompiler may disagree with it in length, causing the compiler to assume that the file is RECORDING MODE V. If the 01-level entry is not used in the program, it should be removed.
RW-009-E	Word xx expected here: assumed. The named word is compulsory for this clause.
RW-010-E	No period after REPORT SECTION: assumed. REPORT SECTION should be followed by a period (".") character.
RW-011-S	RD absent or not in A-margin: assumed. This fault may be the consequence of a fault in the coding of the REPORT SECTION header.
RW-012-S	Clause xx not permitted in RD statement: ignored. The precompiler is still scanning the RD statement but has found a clause that cannot be used there. It is likely that a period has been omitted.
RW-013-S	Clause/phrase xx not allowed in REPORT SECTION: discarded. The named keyword is a recognized COBOL keyword but cannot be used in the REPORT SECTION.
RW-014-S	No report-name follows RD. A period or a keyword follows immediately after RD. Report writer constructs a name in order to continue scanning.
RW-015-S	This report-name has already been defined. Each report-name can follow only one RD.
RW-017-S	REPORT SECTION absent/misspelt: assumed. An RD entry has been found without a correct REPORT SECTION header preceding it.
RW-019-W	Report xx in FD has no REPORT SECTION entry. A report-name has been declared in a REPORT clause of an FD but there is no RD entry for the report-name. This situation is allowed by OS/VS and DOS/VS COBOL. The superfluous report-name should be removed, together with the clause, if it is its only operand.
RW-020-S	Group item has elementary clauses: ignored. This message appears as a result of an illogical sequence of level-numbers. For example, you may have coded: 03 LINE 1 COL 20 ... 05 COL 30 ... The first COLUMN clause is at a group level, but COLUMN must always be at the elementary level. This example should be re-coded: 03 LINE 1 COL 20 ... 05 COL 20 ... 05 COL 30...
RW-021-E	Clause xx empty: ignored. This may be the result of using a reserved word as a data item, for example, CONTROLS ARE PAGE.
RW-022-S	Clause xx cannot be repeated in entry: previous occurrence discarded. This normally happens as the result of a missing period.
RW-023-S	Invalid CODE Clause: ignored. The CODE clause is incorrect.
RW-024-S	CODE too long for record: ignored. The CODE value has too many characters and, taking into account the size of the longest print line (and possible carriage control character), would cause the record length implied by the RECORD CONTAINS clause to be exceeded.
RW-026-S	FINAL/REPORT control not highest: ignored. The keyword FINAL or REPORT, if included in the CONTROLS clause, must be the first (or only) operand.
RW-027-S	Invalid control identifier. This implies that an identifier used as a CONTROL is improperly formed.
RW-028-E	No integer after PAGE LIMIT: assuming 60. The integer was probably mistyped.
RW-029-S	PAGE LIMIT not in range 1 to 9999: assuming 60. The integer of PAGE LIMIT is not feasible.
RW-030-I	PAGE LIMIT will never be reached. This message is issued when there is no PAGE FOOTING and the [LAST CONTROL] FOOTING value is less than the PAGE LIMIT, or when there is a PAGE FOOTING but it does not reach the PAGE LIMIT
RW-031-W	PAGE LIMIT increased to value of LAST DETAIL or FOOTING. The PAGE LIMIT must not be less than the value of LAST DETAIL or [LAST CONTROL] FOOTING. It has been adjusted up to the higher value.
RW-032-I	Length xx assumed for CODE identifier. If the identifier form of the CODE clause is used, the number of characters to be assigned to the CODE is calculated by subtracting the LINE LIMIT (and the size of any carriage control character) from the record size given in the RECORD or BLOCK CONTAINS clause, rather than from the size of the identifier. This message confirms the calculated length.
RW-033-S	Values of PAGE sub-clauses invalid or not in sequence. The integers of the HEADING, FIRST DETAIL, LAST DETAIL, and LAST CONTROL FOOTING sub-clauses and the PAGE LIMIT should be in non-descending order.
RW-034-E	Size of CODE differs from other reports going to same file. This situation is tolerated but, since the CODE literal is placed at the front of each output record, the output may be difficult to interpret.
RW-036-I	Standard OS/VS code literal is normally length 1. However with report writer, CODE values may be of any length.
RW-037-S	Invalid level number: assuming xx. This usually happens as the result of other faults in the code.
RW-038-E	LINAGE not allowed with REPORT(S) clause in FD. The LINAGE and REPORT(S) clauses are mutually exclusive. If you are using report writer, do not code LINAGE or any of its phrases.
RW-039-E	Report has no groups. This is usually the result of the absence of a 01 level-number after the RD entry.
RW-041-S	First level no. after RD not 01. A value of 01 is assumed.
RW-042-S	Group-name not unique: name discarded. Each report group-name should be unique within the RD.
RW-043-S	Invalid TYPE: assuming DETAIL. The keyword after TYPE is not one of the standard names.
RW-044-S	Already had TYPE xx: assuming DETAIL. Two non-body groups of the same TYPE were found in one RD.
RW-045-S	Clause xx allowed only at level 01: discarded. The clauses TYPE, NEXT GROUP, GROUP LIMIT and REPEATED can be coded only at the 01 level.
RW-047-S	TYPE xx not allowed without PAGE: assuming DETAIL. TYPE PH and PF are allowed only if there is a PAGE clause in the RD.
RW-049-S	Control in TYPE clause not declared: assuming DETAIL. TYPE CH or CF should be followed by FINAL/REPORT or the name of one of the identifiers listed in the CONTROL(S) clause of the RD.
RW-050-S	Already had CH/CF for this control: assuming DETAIL. Each control identifier can appear in only one CH and/or one CF group (including multiple CF's).
RW-051-W	Duplicated control: ignored. The same control name cannot be used twice in a CONTROL clause. (There is no restriction, however, on using the same field under a redefined name.)
RW-052-I	No TYPE: assuming DETAIL. The TYPE clause may be omitted, in which case DETAIL is assumed.
RW-054-E	Absolute LINE not allowed in unpaged report: PLUS form assumed. Without a legal PAGE clause, every LINE must be relative (LINE + or PLUS).
RW-055-S	LINE value should be non-negative integer: ignored. The integer of the LINE clause is not numeric or is negative.
RW-056-S	NEXT PAGE option of LINE in unpaged report: discarded. LINE [integer] ON NEXT PAGE is not allowed if there is no PAGE clause in the RD.
RW-058-S	PLUS not allowed with NEXT PAGE: ignored. The form LINE IS PLUS/+ integer ON NEXT PAGE is not allowed.
RW-059-E	NEXT PAGE allowed only in first line of this group. The LINE IS [integer] ON NEXT PAGE clause can only appear as the first LINE clause of a group, except in a TYPE RH or RF, or a MULTIPLE PAGE group.
RW-060-W	Integer in NEXT PAGE below heading value. In the LINE IS integer ON NEXT PAGE clause, the integer must not be less than the HEADING integer (default value 1)
RW-061-E	Absolute line follows relative line. This is not allowed if the first LINE of the group is relative, except in a MULTIPLE PAGE group.
RW-062-W	Line position precedes previous line. All absolute LINE numbers must be in strictly ascending order (taking into account possible ABSENT lines), except in a MULTIPLE PAGE group.
RW-063-S	LINE clause subordinate to another LINE: ignored. This condition arises when the OSVS option is not in effect and the LINE clauses in a report group are at different levels, for example: 01 GROUP-01 TYPE DE LINE NEXT PAGE. 05 COLUMN 20 ... 03 LINE PLUS 1. 05 COLUMN 20 ... It may be rewritten as follows: 01 ... TYPE DE. 03 LINE NEXT PAGE. 05 COLUMN 20 ... 03 LINE PLUS 1. 05 COLUMN 20 ... This structure is accepted as written by OS/VS COBOL, DOS/VS COBOL, and by this implementation, provided the OSVS option is in effect, in which case a Warning RW-064 appears.
RW-064-W	LINE entries nested: previous LINE assumed level xx. See the comments under RW-063 above.
RW-066-S	COLUMN value should be positive integer < 999: ignored. The integer of the COLUMN clause is not feasible.
RW-069-W	COLUMN should be subordinate to LINE: LINE + 0 assumed. This message is issued when a COLUMN clause is found but there is no LINE clause containing it, for example: 01 TYPE IS PH. 03 COLUMN 30 ... The same message appears if the OSVS option is not in effect and the COLUMN clause is coded at the same level as the preceding LINE clause (or higher), for example: 03 LINE 1 COLUMN 20 ... 03 COLUMN 30 ... Here, the second COLUMN clause is not subordinate to any LINE clause. A LINE PLUS ZERO clause is assumed in default. This means that an unnecessary second record will be written so that the item will be printed in the position defined by the preceding LINE. This structure should be re-coded as follows: 03 LINE 1 05 COLUMN 20 ... 05 COLUMN 30 ... If the OSVS option is in effect, Warning message RW-070 appears instead and the additional LINE PLUS ZERO is not generated.
RW-070-W	COLUMN entries following LINE assumed to be subordinate to it. See under RW-069 above. See also Part 6.
RW-071-S	NEXT GROUP value should be positive integer: discarded. The integer following NEXT GROUP is not numeric or is negative or zero.
RW-072-W	This message may be result from the following type of construct when the option OSVS is in effect: 03 LINE 1 COLUMN 10 ... 03 LINE 1 COLUMN 30 ... The two COLUMN entries should be brought together under a single LINE 1 entry, but OS/VS and DOS/VS COBOL allow this construct, as does the precompiler also.
RW-074-S	NEXT GROUP absolute or NEXT PAGE in unpaged report: PLUS assumed. The forms NEXT GROUP IS integer and NEXT GROUP NEXT PAGE are not allowed unless there is a PAGE clause in the RD.
RW-075-S	Invalid PICTURE: PICTURE X substituted. The PICTURE clause has an invalid symbol, or an invalid combination of symbols or lacks a compulsory symbol.
RW-076-S	PICTURE too long: truncated to 32 symbols. There is a limit of 32 characters on a PICTURE string.
RW-081-S	Invalid literal: clause or phrase ignored. A literal is expected here but the item found is not correct.
RW-082-S	Invalid integer: clause or phrase ignored. An integer is expected here but the item found is not correct.
RW-083-W	Hexadecimal value defined as printable text rather than by STYLE clause. Although hexadecimal values are allowed in the REPORT SECTION, their usual purpose is to put control characters in the print data. A more system-independent method is to use the STYLE clause.
RW-084-S	Invalid identifier or expression: clause or phrase ignored. An identifier or expression is expected here but the item found is not correct.
RW-085-I	New reserved word accepted as data-name. Clauses such as SOURCE IS STEP or SUM OF FUNC are recognized as correct even though STEP and FUNC are report writer keywords. This allow older code to continue to function without change.
RW-086-W	CF group refers to identifier that is not a CONTROL: after-break value may be used. You have specified an identifier in a SOURCE clause within a CONTROL FOOTING group and the identifier is not a CONTROL or a SUM total field. This message reminds you that only CONTROL items are restored to their before-the-break values during the processing of CONTROL FOOTING groups. If the data item referred to normally changes at control-break time, you will obtain its after-the-break value (unless the item is a redefinition of, or subordinate to, a CONTROL item) and this may not be what you intended. To obtain the before-the-break value, you could define a Declarative section for the CONTROL HEADING. If the data item does not change at control-break time, this message should be ignored.
RW-087-S	Control in RESET phrase not declared: discarded. Except for FINAL or REPORT, the identifier specified in the RESET phrase must be declared in the CONTROL clause.
RW-088-W	RESET at lower level than associated SUM clause. If SUM and RESET are used in a TYPE CF group, the control used must be at the same level or a higher level than that of this CF group.
RW-089-W	Elementary item must have data-name or SOURCE etc. Every elementary item should have either SOURCE, or VALUE, or SUM/COUNT, or FUNCTION clause, or should carry a data-name.
RW-090-S	LINE...NEXT PAGE not allowed in this type of group. It is not allowed in a TYPE PH or RH group.
RW-094-W	First LINE number will cause group to be positioned higher than top limit. The first LINE number of the group is such that the group will start higher (earlier) than its highest permissible position on the page.
RW-096-W	LINE clauses in group will cause it to extend beyond bottom limit. The last LINE number of the group is such that the group will end lower than its lowest permissible position on the page..
RW-098-W	PRESENT should not precede WHEN/UNLESS if used as qualifier for previous clause. The WHEN phrase of the STYLE clause is not normally preceded by PRESENT. If you have written something like: 05 COL 1 VALUE "Payment overdue" STYLE UNDERLINE PRESENT WHEN W-DATE < W-TODAY. Note that the condition immediately following the STYLE clause is assumed to qualify just the STYLE clause, so this should be re-written as: 05 COL 1 STYLE UNDERLINE VALUE "Payment overdue" PRESENT WHEN W-DATE < W-TODAY.
RW-099-E	ABSENT not allowed before qualifying condition. The STYLE clause cannot be immediately followed by an ABSENT clause and the order of the clauses should therefore be changed.
RW-100-W	WHEN OTHER allowed only with multiple choice. The clause [PRESENT] WHEN OTHER cannot be used in isolation. That is, there must be at least one [PRESENT] WHEN condition clause in the same entry.
RW-106-W	This RH group will have own page: NEXT GROUP NEXT PAGE assumed. If NEXT GROUP NEXT PAGE is not used in an RH group, report writer will try to fit the group on the first page above the PH group. If that cannot be done, this message is issued.
RW-107-W	This RF group will have own page: NEXT PAGE assumed. If LINE...NEXT PAGE is not used in an RF group, report writer will try to fit the RF group on the last page below the PF group. If that cannot be done, this message is issued.
RW-110-I	Elementary item has no size: will not be output. This message occurs when the PICTURE clause is omitted from an elementary item and there is no way of telling its size, such as from a VALUE "literal" as, for example: `05 COLUMN 21 SOURCE IS WS-PAYMENT.` A PICTURE clause is always required at the elementary level except (a) with a simple VALUE "literal". However, OS/VS and DOS/VS COBOL allow the PICTURE to be omitted and treats the field as unprintable, so this technique was often used in the past to enable an item to be used in a SUM when it was not also being used as a SOURCE.
RW-112-W	Absolute NEXT GROUP position not beyond last line position. The integer of a NEXT GROUP integer clause in a TYPE RH or PF group must be greater than the last line position in the group.
RW-113-W	NEXT GROUP position out of range. Either the current group is a REPORT HEADING and the NEXT GROUP is beyond the FIRST DETAIL, or the current group is a PAGE FOOTING and the NEXT GROUP is beyond the PAGE LIMIT.
RW-114-W	Absolute NEXT GROUP not in range FIRST DETAIL to FOOTING. The integer of a NEXT GROUP integer clause in a body group must be in that range.
RW-115-S	NEXT GROUP not allowed in types PH and RF: ignored. To provide spacing following a Page Heading, the FIRST DETAIL clause may be used.
RW-122-S	SUM clause has nonnumeric PICTURE: ignored. The PICTURE clause was probably mistyped.
RW-124-S	Group-name in UPON phrase is unknown or ambiguous. An UPON phrase is followed by a name that is either not a group-name or requires qualification.
RW-125-E	E UPON group not type DETAIL. It is not possible to SUM ... UPON a group that is not TYPE DETAIL. If the field is a SOURCE in the group, you may instead give a data-name to the entry and SUM that data-name.
RW-126-E	Rolling forward of SUM from higher to lower CF group not allowed. An attempt is being made to SUM a field in a higher CONTROL FOOTING and print the total in a lower CONTROL FOOTING.
RW-127-E	Report-name qualifier required: IN xx assumed. The same group-name is in use in more than one report. The name in the first report is arbitrarily chosen.
RW-128-S	Qualifying report-name invalid. The only qualifier accepted following a sum counter, group-name or special register is the report-name itself.
RW-131-S	Name following GENERATE not report or detail group. The name following GENERATE is probably misspelt.
RW-132-S	Name following INITIATE/TERMINATE not report: ignored. The name following INITIATE or TERMINATE is probably misspelt.
RW-133-E	Cannot do summary reporting without CONTROLS clause. This may be issued if GENERATE report-name is coded erroneously instead of GENERATE detail-name.
RW-134-S	SUPPRESS allowed only in DECLARATIVES: ignored. A SUPPRESS keyword has been found outside the DECLARATIVES part of the program.
RW-135-S	Invalid operand after USE BEFORE REPORTING: section discarded. The directive USE BEFORE REPORTING must be followed by the name of a report group.
RW-136-S	"xx".. not allowed in Report Writer DECLARATIVES. This is issued if an INITIATE, GENERATE, or TERMINATE is found in the DECLARATIVES part of the program.
RW-137-E	Report Writer verb has no operands: ignored. The verb INITIATE, GENERATE, or TERMINATE is followed immediately by a period, another verb, or the end of the source.
RW-138-S	Group already has DECLARATIVES section. There can only be one DECLARATIVES section for any given report group.
RW-139-W	USE AFTER EXCEPTION/ERROR DECLARATIVE not used by file-handler. Independent Report File Handlers cannot access the USE AFTER EXCEPTION or USE AFTER ERROR DECLARATIVE section for the file they control. This message warns that the section will have no effect. A FILE STATUS should be created and tested after each operation instead.
RW-142-W	No INITIATE statement found for this report. Check that INITIALIZE was not coded by mistake instead ofINITIATE. This message and the next are issued only if there is a GENERATE statement referring to the report.
RW-143-W	No TERMINATE statement found for this report. See notes under RW-142 above.
RW-144-W	MODE more than 4 characters: excess ignored. Report writer generates the name CRFHxxxx for the name of the Independent Report File Handler, so 4 is the limit.
RW-145-E	MODE not allowed where record descriptions follow FD: discarded. A report file that is written using an Independent Report File Handler cannot process any records other than those implicitly defined in the REPORT SECTION. If the (01-level) record description is not referred to (via a WRITE statement) anywhere in the program, it should be omitted. Otherwise, a way should be found to write the record by means of additional code in the REPORT SECTION. The file handler itself may also be enhanced to write special records to the print file.
RW-146-I	No GENERATE issued for this DETAIL. There is no GENERATE statement in the PROCEDURE DIVISION referring to this DETAIL group-name.
RW-148-S	Invalid UPON file-name. The file-name specified in the INITIATE...UPON is not defined in the FILE SECTION or it is not a report file or its REPORT(S) clause does not include the report-name (or one of the report-names) given in the INITIATE.
RW-149-E	Report assigned to more than one FD: file handler DUPL required. OS/VS and DOS/VS COBOL allowed a report-name to be defined in the REPORT(S) clause of up to two FD's. This property is now emulated using the DUPL file handler. You should code MODE DUPL in the SELECT ... ASSIGN statement for both files, or use the precompiler's FMODE option.
RW-151-W	Superfluous period: ignored. This message will appear if an excess period appears between the level-number and the last clause in the entry, for example: `05 COLUMN 21. PIC Z(5)9. SOURCE IS WS-INCOME.`
RW-152-E	Period missing: assumed. This message will appear if no period appears at the end of an entry before the next level-number or heading. Occasionally, this may be the result of coding a superfluous numeric literal that is wrongly assumed to be a new level-number.
RW-161-I	RW-161-I SUM will be totalled UPON generation of xx due to SOURCE SUM correlation. In an original report writer program that has more than one DETAIL group, this message should be expected for every SUM operand which is not the name of another REPORT SECTION item. This message confirms that SOURCE SUM correlation is in effect (one of the supplied defaults which is essential when an original OS/VS or DOS/VS COBOL source is processed). Report writer has searched the SOURCE clauses in all the DETAIL groups for the same identifier as that specified in the SUM clause and has found it in DETAIL xx . It will perform the adding when, and only when, DETAIL xx. is GENERATEd. This message tells you exactly when adding of the SUM operand takes place.
RW-162-I	SUM will be totalled also UPON generation of xx. This is used in combination with message RW-161. It indicates that the SUM operand was found in more than one DETAIL group. Adding will take place when either the DETAIL named in message RW-161-I or the DETAIL named in this message is GENERATEd.
RW-163-W	Item not in REPORT SECTION is accumulated on every GENERATE. The SUM clause referenced has an identifier from a SECTION other than REPORT SECTION, there are more than one DETAIL groups and either there is no SOURCE SUM correlation or the same identifier does not appear as a SOURCE in any DETAIL of the report. This message reminds you that adding will take place on the execution of a GENERATE for any DETAIL in the same report, in accordance with the ANS-85 standard. This message should not appear for any program written originally for OS/VS or DOS/VS COBOL, as the previous compiler would not have generated any adding for the SUM entry in these circumstances and a zero value should have resulted.
RW-165-W	Sum counter may be accumulated without being cleared. There is a RESET phrase for a total field that is also used for rolling forward to another SUM. Some values will therefore be rolled forward several times into the same total, which is therefore suspect.
RW-166-W	UPON phrase not allowed with SUM of Report Section entry. It is not permissible to use the UPON phrase if the item added is a REPORT SECTION data-name. REPORT SECTION items are added in whenever their group is produced.
RW-167-S	REPORT SECTION entry referred to by SUM must be numeric. Only a numeric entry may be the object of a SUM. However, a COUNT clause may be used to count the occurrences of any entry.
RW-168-S	RESET without SUM or COUNT clause: discarded. The RESET phrase has no meaning except in conjunction with a SUM or COUNT clause.
RW-171-S	Invalid SIGN clause: discarded. The SIGN clause is malformed.
RW-172-S	BLANK WHEN ZERO not applicable: discarded. BLANK WHEN ZERO can only be associated with numeric items.
RW-173-E	Entry contains both DBCS and non-DBCS fields. If the entry has a multiple VALUE clause, either all the literals must be DBCS or all must be non-DBCS.
RW-174-E	DISPLAY-1 group must contain only DBCS fields. If DISPLAY-1 is coded on a group level, every subordinate entry must be DBCS, that is, it must have a DBCS PICTURE ("G" symbol) or a DBCS literal VALUE, or both.
RW-180-E	CODE not allowed in RD where a record description follows FD. The report associated with this file has a CODE clause, but the FD is followed by an 01-level record description. Since all the records written to the file should have the additional "CODE" characters attached, it is not permissible to WRITE records independently of report writer. If the 01-level record description is not referred to, it should be deleted.
RW-181-E	PAGE BUFFER/DUPLICATED not allowed in RD whose FD has a record description. The PAGE BUFFER and DUPLICATED clauses imply a special organization of the report file or its records and it is not permissible to WRITE records independently of report writer. If the 01-level record description is not referred to, it should be deleted.
RW-184-W	Some SELECT clauses will be ignored by file handler and may be invalid. The MODE clause causes the report to be output using an Independent Report File Handler. The phrases RESERVE integer AREA(S), PADDING CHARACTER, RECORD DELIMITER, and PASSWORD of the SELECT...ASSIGN clause are not processed by the file handler and are treated as documentary only.
RW-185-W	Some FD clauses will be ignored by file handler and may be invalid. The MODE clause causes the report to be output using an Independent Report File Handler. The FD phrases CODE-SET, RECORD IS VARYING..., BLOCK CONTAINS integer RECORDS, LABEL RECORD(S) IS/ARE data-name, and VALUE OF... are not processed by the file handler and are treated as documentary only.
RW-190-E	"xx" does not conform to chosen language level. The precompiler has been installed to accept only a subset of the available language and the specified item is not in that subset.
RW-191	"xx": nonconforming nonstandard, yy extension to ANS/ISO 1985 Report Writer module. This message appears as a result of the FIPS option to flag nonstandard IBM and SPC extensions to the current standard.
RW-192	"xx": nonconforming standard, ANS/ISO 1985 Report Writer module. This message appears as a result of the FIPS option to flag standard elements above a specified level.
RW-193	"xx": obsolete element in ANS/ISO 1985 Report Writer module. This message appears as a result of the FIPS option to flag all obsolete elements.
RW-200-I	MODE PRNT has been assumed for file due to CODE clause. If a file has more than one report whose RD's do not all have a CODE of equal length, the file can only be processed by an Independent Report File Handler. The file is therefore treated as though MODE PRNT had been coded.
RW-201-I	Scanning to next recognizable period or keyword. This message is issued after a more serious error to document the precompiler's error-recovery processing.
RW-202-W	No associated FD: MODE PRNT assumed. Each RD's report-name must appear in the REPORT clause of an FD as well as in the RD. The precompiler supplies a file by default and, for simplicity, implements it via the PRNT file handler.
RW-203-E	REPORT SECTION nest level must not exceed 23. This is the limit to the number of different levels of nesting allowed using level-numbers in the REPORT SECTION.
RW-204-I	Data-name accessible in REPORT SECTION only. This message is issued when an entry has a data-name that the precompiler cannot retain when generating the intermediate data description. Possible reasons for this are: (a) the LINE is subject to an OCCURS clause and, as lines are generated only once, the dimensions of the data-name would be insufficient; (b) the item has a PICTURE clause with an "<" symbol and this would be incomprehensible to basic COBOL.
RW-206-S	PLUS integer allowed only with FOOTING: ignored. The HEADING, FIRST DETAIL and LAST DETAIL clauses have no PLUS integer form.
RW-208-S	OCCURS clause not allowed at level 01. Perhaps a REPEATED clause was intended. This is used at level 01 to print several body groups across the page.
RW-210-S	LINE LIMIT invalid: clause ignored. The LINE LIMIT clause is malformed.
RW-211-S	LINE LIMIT too high for record/CODE. The LINE LIMIT exceeds the maximum number of bytes available in the print line, taking into account an existing CODE.
RW-212-E	CODE identifier form not allowed without LINE LIMIT. If the identifier form of the CODE clause is used, a LINE LIMIT clause must be present.
RW-213-I	Value xx assumed for LINE LIMIT. This message is always issued if there is no LINE LIMIT clause in an RD. It gives the rightmost value allowed for any COLUMN and enables report writer to ensure that none of your print lines will be truncated because they are wider than one printer's width. This default value is calculated from the RECORD CONTAINS or BLOCK CONTAINS clause in the corresponding FD (allowing for the carriage control character), or, failing that from the installed default (see Installation and Operation). It should be checked to ensure that the value is as expected. (See LINE LIMIT clause.)
RW-214-I	I SOURCE/SUM will show same value in each repetition. An OCCURS clause or multiple LINES or COLUMNS clause is in effect but the same SOURCE or SUM value will be placed in each occurrence because there are no subscripts to be varied, or there are subscripts but no VARYING clause.
RW-215-S	More than one unconditional SOURCE etc.: previous discarded. More than one SOURCE, VALUE clause, etc. has been found and there are no associated [PRESENT] WHEN condition clauses to indicate a multiple-choice entry.
RW-216-S	Condition has unpaired left parenthesis or reserved word. A major keyword, or a period, or the end of the source was found before the expected closing parenthesis (")") while scanning a condition.
RW-218-S	Item xx found out of context and ignored. The given item was not expected in this context.
RW-220-S	Illegal OCCURS integer: clause discarded. An integer of this OCCURS clause was non-numeric.
RW-221-S	OCCURS...TO maximum must exceed minimum: TO phrase discarded. The second integer in an OCCURS...TO clause must be greater than the first integer.
RW-222-S	Minimum OCCURS integer negative: clause ignored. The first integer in an OCCURS...TO clause must be zero or greater than zero.
RW-223-S	OCCURS integer must be positive: clause discarded. The integer in a basic OCCURS clause or the second integer in an OCCURS...TO clause should be greater than zero.
RW-224-S	S Invalid identifier/expression in DEPENDING ON: phrase discarded. This may be due to the use of a SUM or COUNT term in the expression.
RW-225-S	OCCURS...TO format allowed only with DEPENDING. A DEPENDING ON... phrase was expected following the OCCURS...TO clause. The first integer is discarded.
RW-226-S	Depth of repetition exceeds 4: clause discarded. Only up to four nested levels of OCCURS or multiple LINES or COLUMNS are allowed.
RW-229-S	More than 8 levels of OCCURS or PRESENT etc. Only up to eight levels of PRESENT WHEN, PRESENT AFTER, or GROUP INDICATE clauses, or repetition are allowed, including up to 4 levels of nested OCCURS, multiple LINES, or multiple COLUMNS.
RW-230-S	Invalid FUNCTION: clause ignored. This is issued if the function name is malformed.
RW-231-E	No closing parenthesis in FUNCTION: assumed. A major keyword, or period, or end of source was found before the closing parenthesis following the parameters to a FUNCTION clause.
RW-232-S	Summed REPORT SECTION item must have SOURCE, SUM or VALUE. A SUM was found of a REPORT SECTION item, but the item has no SOURCE, SUM, or VALUE clause.
RW-233-S	Misuse of < symbol in PICTURE: ignored. The "<" symbol may only be used immediately preceding a PICTURE symbol representing "data" as opposed to an insertion character.
RW-235-E	Report has > 1 CONTROL, so control-id must be specified in TYPE CH. TYPE CH must be followed by one of the identifiers (or REPORT / FINAL) listed in the CONTROL(S) clause.
RW-236-S	GROUP INDICATE/PRESENT AFTER not allowed in RH or RF groups. A TYPE REPORT HEADING or REPORT FOOTING group cannot have a GROUP INDICATE clause or a PRESENT AFTER... clause.
RW-237-S	Undeclared control in GROUP INDICATE/PRESENT AFTER: discarded. All control names must first be declared in a CONTROL clause.
RW-238-S	Invalid GROUP INDICATE syntax: default format assumed. The ON/FOR phrase is incomprehensible, so the simple (no-operand) GROUP INDICATE format is assumed.
RW-239-S	PAGE option used in unpaged report: PAGE discarded. There is no (valid) PAGE clause in the RD and hence none of the options using the keyword PAGE can be used.
RW-240-S	REPEATED invalid in dummy or multiple-page group. A group with a REPEATED clause must have at least one LINE and must not have a MULTIPLE PAGE clause.
RW-241-S	Invalid REPEATED syntax: clause ignored. The REPEATED clause is malformed.
RW-242-S	Too many repeats for available LINE LIMIT. The LINE LIMIT cannot accommodate the number of repetitions given in the TIMES phrase. If an EVERY/WIDTH phrase is given, the spacing given is too wide, or, if not, the desired number of repetitions cannot fit, even at the closest possible spacing.
RW-243-S	REPEATED allowed only in body groups: clause ignored. The REPEATED clause can be used only in a TYPE CH, DE, or CF group.
RW-244-S	REPEATED must have EVERY or TIMES: ignored. Either the TIMES phrase or the EVERY/WIDTH phrase or both must be present in the REPEATED clause.
RW-245-E	Repeats of this group will overlap. Running the program will result in encroachment between successive side-by-side groups with unpredictable results.
RW-246-S	Invalid condition: clause ignored. The condition following a PRESENT/ABSENT clause was syntactically invalid.
RW-247-E	Superfluous PRESENT/GROUP INDICATE/ERROR found: discarded. This fault is usually the result of a missing period.
RW-248-E	GROUP IND./PRESENT AFTER cannot be part of multiple choice. The only conditional clauses allowed in a multiple choice entry must be of the form [PRESENT] WHEN condition.
RW-249-E	GROUP IND./PRESENT AFTER in CONTROL group must refer to higher level. If a PRESENT AFTER control [OR PAGE] clause is written in a CH or CF group, the control referred to must be at a higher level than that of the group.
RW-250-W	Item overlaps or is to left of item in same line. This message is issued if two unconditional horizontal items overlap or if their COLUMN numbers are not in ascending sequence. It will also appear in cases where a conditional item could overlap an unconditional one. The item will be accepted as defined. If it does not overlap any of the column positions of a previous field in the line, there will be no problem at run time. Otherwise, the earlier field will be overlaid, in whole or in part, by the new item.
RW-251-I	I Column overlap may occur in this line. This message is issued if some of the items in the report line have PRESENT WHEN clauses without which they would overlap. The precompiler assumes that the programmer has taken action to ensure that the conditions are mutually exclusive.
RW-253-I	Final COLUMN position may exceed line limit. This message is issued if some of the items in the report line have PRESENT WHEN clauses without which they would exceed the size of the line.
RW-254-E	Abs. line follows relative with no unconditional abs. lines. An absolute LINE clause (no +) cannot follow a relative LINE (with +) unless there is an unconditional absolute LINE earlier in the group.
RW-255-E	REPEATED absolute group must have at least 1 unconditional LINE. It is not possible for all the LINE entries in a group with a REPEATED clause to have a PRESENT/ABSENT/GROUP INDICATE clause, unless they are all relative (with PLUS or +).
RW-256-S	Nonnumeric SOURCE or non-REPORT SECTION SUM cannot be ROUNDED. ROUNDED can only be used with (a) a numeric SOURCE or (b) a SUM clause that refers to another REPORT SECTION item.
RW-257-S	Final column position in line exceeds limit. The rightmost column of this line exceeds the value of LINE LIMIT. The line will be truncated.
RW-258-E	Line overlap: LINE PLUS 1 assumed. This message will be issued if two unconditional absolute lines overlap. It will also appear in cases where a conditional absolute line could overlap an unconditional one.
RW-259-I	Line overlap may occur in this group. This message is issued if some of the lines in the group have PRESENT WHEN clauses without which they would overlap. The precompiler assumes that the programmer has taken care to ensure that the conditions are mutually exclusive.
RW-260-I	This group may extend beyond lower limit. This message is issued if some of the lines in the group have PRESENT WHEN clauses, which, if all present, would exceed the maximum size of the group as defined in the PAGE LIMIT sub-clauses or the GROUP LIMIT clause.
RW-261-S	Circular reference of sum totals: no summing. This message is issued if circular combinations of cross-foot SUM's are used, such as: A SUM A or A SUM B --- B SUM A or A SUM B --- B SUM C --- C SUM A etc.
RW-262-E	Number of occurrences of addend and SUM field differ at level xx. This message is issued in the following case: a SUM clause is subject to repetition (OCCURS or multiple LINES / COLUMNS); an item referred to in the SUM clause is a REPORT SECTION item that also has repetition. After matching the axis of each repetition (LINE against LINE, COLUMN against COLUMN, group of LINES against group of LINES and group of COLUMNS against group of COLUMNS), it is found that the numbers of occurrences along the matching axis are not the same.
RW-263-S	Repetition affecting SUM field has no equivalent for summand. This message is issued when a SUM clause has repetition (OCCURS clause or multiple LINES / COLUMNS) and an item referred to in the SUM clause is a REPORT SECTION item but has no repetition along the axis of repetition of the SUM. Briefly: a multiple SUM cannot be manufactured from a single original value.
RW-265-W	UPON phrase required in running total in type DETAIL. This message is issued if a SUM clause is found in a DETAIL group and the item summed is not in the REPORT SECTION. The precompiler cannot ascertain when adding is to take place unless an UPON phrase is included.
RW-266-E	Rolling forward not allowed between these types. It is not permitted to roll forward into a REPORT HEADING group or from a REPORT FOOTING group.
RW-267-S	No subscripts allowed on SUM of REPORT SECTION entry. The SUM identifier must be without subscripts when it refers to an entry in the REPORT SECTION.
RW-270-S	SUM OVERFLOW clause is invalid: discarded. The SUM OVERFLOW clause is malformed.
RW-274-S	Leftmost COLUMN position less than one: COLUMN PLUS 1 assumed. This message is associated with the RIGHT and CENTER forms of the COLUMN clause.
RW-275-S	Invalid MODE clause: discarded. The MODE clause is malformed. (The mode name should not be in quotes or apostrophes.)
RW-276-S	Invalid or duplicated phrase after MODE: discarded. One of the phrases or clauses USING, WITH PAGE BUFFER, or DUPLICATED is either malformed or occurs more than once.
RW-277-S	Invalid DUPLICATED integer: phrase discarded. No valid integer follows the DUPLICATED keyword.
RW-278-I	MODE xx has been assumed for file due to clauses in FILE-CONTROL entry. To implement certain features, such as PAGE BUFFER and DUPLICATED, the independent report file handler protocol is required, rather than direct "WRITEs". If there is not already a MODE clause, report writer handles the file as though a MODE clause had been coded.
RW-281-S	SET statement has invalid syntax: discarded. The SET PAGE/LINE/COLUMN statement is malformed.
RW-282-S	SET statement not allowed with report that has no page buffer. The SET PAGE/LINE/COLUMN statement cannot be used unless the corresponding SELECT...ASSIGN clause has a WITH PAGE BUFFER clause.
RW-283-S	Integer of SET statement is out of range. An attempt is being made to SET the LINE or COLUMN outside the dimensions of the page.
RW-287-E	RESET not allowed in multiple CF group. RESET cannot be used with a SUM or COUNT clause in a multiple CONTROL FOOTING because several levels of totalling are implied.
RW-288-I	TYPE CF with no operands assumed to be multiple CF for all controls. If TYPE CONTROL FOOTING is coded with no control-id operand following, it is taken to mean CONTROL FOOTING FOR ALL.
RW-290-E	Mis-use of CONTROL IS control-id condition. The special condition CONTROL IS control-id can only be used in a multiple TYPE CONTROL FOOTING that has that control-id as one of its operands.
RW-291-W	UPON phrase refers to current group. The operand used in the UPON phrase should refer to the name of a different group.
RW-293-W	SUM of item with GROUP INDICATE/PRESENT AFTER may be incorrect. If the item quoted in the SUM clause is subject to one of these clauses, it cannot be reliably totalled, since report writer will, on principle, not total fields that ordinarily will not be Present.
RW-294-W	Summed REPORT SECTION name xx is ambiguous: first occurrence used. Either (a) the given data-name, the operand of a SUM clause, is either defined in more than one place within the current report (in which case the names should be made different) or (b) the given data-name is not defined in the same report but is defined in more than one different report (in which case report-name qualifiers should be used).
RW-295-I	Maximum number of repetitions will be xx. In the absence of a TIMES phrase, report writer has calculated from the rest of the EVERY/WIDTH phrase of the REPEATED clause and the LINE LIMIT that this many repetitions of the group can be arranged side-by-side.
RW-296-I	Distance between REPEATED groups assumed to be xx COLUMNS. In the absence of an EVERY/WIDTH phrase, report writer has calculated from the TIMES phrase and the LINE LIMIT that the distance between corresponding repetitions will be that many columns.
RW-297-W	Absolute LINEs subject to REPEATED or WRAP cannot all be conditional. For the REPEATED or WRAP clause to work correctly, report writer must know at precompilation time whether the group will be absolute or relative. If all the absolute LINE clauses have a condition attached, this cannot be done.
RW-301-W	Multiple LINE or COLUMN should not be blank. An entry containing a LINE clause with more than one operand should be followed by at least one subordinate COLUMN entry. An entry containing a COLUMN clause with more than one operand should also contain a SOURCE, SUM, VALUE, or FUNCTION clause.
RW-302-S	Number of SOURCE items etc. does not match number of repetitions. With a multiple SOURCE or VALUE, there must be an equal number of repetitions either as an OCCURS or as a multiple LINES or COLUMNS clause.
RW-303-S	OCCURS not allowed in entry with multiple LINE/COLUMN. It is not permissible to combine an OCCURS and a LINE or COLUMN with multiple operands in the same entry.
RW-304-S	STEP/WIDTH/DEPTH allowed only with OCCURS. The STEP/WIDTH/DEPTH clause cannot be coded unless there is a valid OCCURS clause in the same entry.
RW-305-E	STEP/WIDTH/DEPTH not allowed in blank item. The STEP/WIDTH/DEPTH clause is not allowed in an elementary entry that has no COLUMN clause (actual or implied).
RW-306-S	STEP/WIDTH/DEPTH less than size of field: xx assumed. The distance given in the STEP/WIDTH/DEPTH clause must be at least the size (horizontal or vertical) of the item it applies to.
RW-307-W	Wrong axis implied by STEP/WIDTH/DEPTH. The keyword LINES may only be used in the vertical direction and COLUMNS in the horizontal direction.
RW-308-W	Scope of OCCURS includes absolute entry: minimum STEP (xx) assumed. An OCCURS clause includes within its scope an absolute entry (LINE or COLUMN without "+"). The value given is the minimum distance that may be assumed between adjacent entries.
RW-309-S	Mult. SOURCE/VALUE not subject to fixed OCCURS or mult. LINE/ COLUMN. A multiple SOURCE or VALUE clause must be associated with either OCCURS without DEPENDING or a multiple LINES or a multiple COLUMNS.
RW-310-E	SOURCE NONE allowed only in multiple entry. SOURCE NONE can be used only as part of a multiple-operand SOURCE clause.
RW-311-S	Multiple LINE numbers must increase: PLUS 1 assumed as necessary. In a multiple LINES clause, absolute line numbers must be strictly increasing.
RW-313-E	REPORTS ALL already encountered: ignored. REPORTS ARE ALL can only be coded once per program.
RW-314-W	ALL should be only REPORT(S) operand: will be applied to unassigned reports. REPORTS ARE ALL must be coded without any report-names and must be the only REPORT(S) clause in the program.
RW-315-S	Invalid operand for VARYING. An operand following VARYING is not one of the permitted forms.
RW-316-S	VARYING allowed only with OCCURS or multiple LINE/COLUMN. The VARYING clause can be used only if there is an OCCURS clause or a multiple LINES or COLUMNS clause in the same entry.
RW-317-E	VARYING data-name duplicated. This message is issued if the same data-name has been used twice in the same VARYING clause.
RW-318-S	Invalid VARYING data-name. The names DATA-SUB-1/2/3/4 cannot be used as VARYING operands.
RW-319-E	VARYING data-name already in use in an enclosing entry. It is not permissible to use the same data-name for two nested VARYING clauses.
RW-320-S	REPORT SECTION item cannot appear in expression in SUM clause. The use of SUM expression is permitted only if all the items in the expression lie outside the REPORT SECTION.
RW-321-S	Expression summed cannot contain SUM: parentheses required. Expressions of the type SUM A + SUM B are not allowed because the SUM operand binds the entire arithmetical expression. For example, SUM A + B means SUM (A + B) not (SUM A) + B. The expression SUM A + SUM B must therefore be written (SUM A) + (SUM B).
RW-322-S	Only SOURCE expression can contain SUM. The SUM or COUNT term cannot be used in a DEPENDING ON expression, as a parameter to FUNCTION, or as part of a conditional expression.
RW-323-S	SUM not allowed in multiple-choice entry. The SUM clause or SUM term cannot be used in a multiple-choice entry. The code should be rewritten using separate entries.
RW-324-E	SUM in lone DETAIL not allowed except as cross-foot. If the report contains only one DETAIL group, that group cannot contain any SUM clauses except for cross-footing (totalling items within the same group).
RW-325-S	COUNT does not refer to REPORT SECTION entry. Only an entry defined in the REPORT SECTION can be counted.
RW-326-W	Data-name of VARYING referred to in FROM or BY expression. The FROM or BY expression of a VARYING clause refers to its own data-name. This may lead to unpredictable results.
RW-327-S	COUNT cannot be followed by expression or literal. Only simple data-names can be used in the COUNT clause.
RW-328-S	RESET cannot be used with SUM/COUNT expression. RESET is only allowed with the basic SUM or COUNT clause, not when they are a term in an expression.
RW-329-E	E Multiple-choice entry not allowed at LINE level. The LINE clause cannot be written at the same level as COLUMN when the entry is a multiple-choice entry. They should be written at different levels.
RW-330-E	Printer TYPE xx not recognized: default TYPE assumed. The Printer Description File for the given "printer type" in the SELECT clause cannot be found.
RW-331-W	STYLE xx is already in effect. The given style is unnecessary since it is already in effect having been defined at a higher level.
RW-332-E	Unknown STYLE name "xx": changed to NORMAL. The given style cannot be found in the Printer Description File.
RW-333-E	No code defined for this STYLE clause: changed to NORMAL. This particular combination of styles is not permitted (although each style-name is valid).
RW-337-E	STYLE not allowed in unprintable entry. An group entry with a STYLE clause must define at least one line or print column. (However, you can code STYLE in an elementary dummy entry.)
RW-339-S	STYLE within multiple-choice selection cannot have condition. A construct of the form: 05 COL 1 VALUE "ONE" WHEN FLD-A = 1 VALUE "TWO" WHEN FLD-A = 2 STYLE UNDERLINE WHEN FLD-B = 1. should be re-coded as: 05 STYLE UNDERLINE WHEN FLD-B = 1. 07 COL 1 VALUE "ONE" WHEN FLD-A = 1 VALUE "TWO" WHEN FLD-A = 2.
RW-340-S	xx clause has invalid syntax: ignored. The given clause is malformed.
RW-342-S	PRESENT AFTER clause has duplicated phrase: discarded. One of the options following PRESENT AFTER is repeated.
RW-343-S	PAGE and JUST not allowed in PRESENT AFTER in PH or PF group. The clause PRESENT JUST AFTER [NEW] PAGE can appear only in a body group.
RW-344-I	LAST DETAIL assumed to be xx. This informational message is issued if LAST DETAIL is not specified and its assumed value is not the same as PAGE LIMIT.
RW-345-W	LAST BODY GROUP present with FOOTING. LAST BODY GROUP means the same as FOOTING, so one is superfluous.
RW-346-S	PAGE option allowed only with TYPE CH. This refers to the OR PAGE phrase allowed only with a TYPE CH group.
RW-347-I	LAST BODY GROUP assumed to be xx. This message appears when no LAST BODY GROUP (or [LAST CONTROL] FOOTING) clause is specified and its value is inferred from the PAGE LIMIT clause and the size of any PAGE FOOTING group.
RW-348-I	NEXT GROUP syntax inappropriate for this TYPE of group. This is issued if NEXT DE OR CH GROUP is written in a TYPE DE or CH group or if NEXT BODY GROUP is written in a TYPE CF group, both of which imply a misunderstanding of the operation of the NEXT GROUP clause.
RW-349-S	COLUMN RIGHT/CENTER must have absolute value: changed to COLUMN PLUS 1. COLUMN RIGHT and COLUMN CENTER have no relative form.
RW-350-S	MULTIPLE PAGE not allowed in type PH, PF or CH with OR PAGE. These three group types must, by definition, be confined to one page and therefore cannot have a MULTIPLE PAGE clause.
RW-351-S	(NO) MULTIPLE PAGE must have at least 2 subordinate lines. A single line clearly cannot span two pages, so this clause is permitted only for a group of LINE entries, or a multiple LINES or LINE with OCCURS.
RW-352-S	Clause "xx" not allowed in unpaged report. A PAGE clause must be present in the RD if certain clauses, such as GROUP LIMIT are used.
RW-353-S	GROUP LIMIT too low or too high for this group. The GROUP LIMIT cannot be less than (that is, positionally higher than) the normal highest (earliest) position for the group, nor greater than (that is, positionally lower than) the normal latest position.
RW-354-S	GROUP LIMIT allowed only in body group. GROUP LIMIT cannot be used except with a TYPE CH, DE, or CF group.
RW-355-E	NO MULTIPLE PAGE can be nested only within MULTIPLE PAGE. No other nested combinations of these clause are permitted.
RW-358-I	Some styles cannot be output directly and will be DEFERRED. The precompiler may be unable to generate code to resolved certain styles directly, especially when they require "overprinting" of part of a line, or "shadow printing" of characters. In such cases, the precompiler defers the resolution of the codes to execution time and your program will therefore require the Printer Description File and some additional run time routines whenever it executes.
RW-360-E	STYLE not allowed in individual multiple-choice entry. A STYLE clause cannot be coded between the SOURCE or VALUE clause and the WHEN phrase of a multiple-choice entry. It can only apply to the complete entry.
RW-371-E	Condition on STYLE not permitted in FD or RD. Only an unconditional STYLE clause is allowed for FD or RD entries. The required effect must be implemented in the report groups.
RW-372-E	Printer file was absent at precompile time and DEFERRED was assumed. The default Printer Description File could not be found.
RW-375-I	MODE PRNT has been assumed for file because of unresolved STYLE. A file handler interface is required because certain STYLE clauses cannot be resolved at precompilation time but require a run time component.
RW-377-E	STYLE may need to be on each LINE to take effect in page buffer. If the PAGE BUFFER feature is in effect, it is inadvisable to code the STYLE clause at a level between RD and LINE. Take the following construct: 03 STYLE HIGHLIGHT. 05 LINE 1 ... 05 LINE 2 ... The ending control sequence for HIGHLIGHT is not stored until the end of line 2. If any data is placed on the right of line 1 in the page buffer, it may unintentionally also have the HIGHLIGHT property. The sample should therefore be re-coded: 03 LINE 1 STYLE HIGHLIGHT... 03 LINE 2 STYLE HIGHLIGHT...
RW-379-E	TYPE DEFERRED not allowed where record description follows FD. Since a deferred printer requires a file handler, there cannot be any (01-level) record descriptions following the FD for the file (compare error no. RW-145-E).
RW-381-S	WRAP/NO WRAP cannot be duplicated or nested. The only nesting allowed for this clause is a single NO WRAP nested within a single WRAP.
RW-382-S	WRAP cannot be used below LINE level. Only NO WRAP can be used at any level below that of LINE.
RW-383-E	NO WRAP must be subordinate to WRAP. Unlike NO MULTIPLE PAGE, NO WRAP cannot be coded independently.
RW-384-E	NO WRAP must encompass more than one elementary item. Since an elementary item cannot be split by the WRAP feature, NO WRAP is redundant unless it encloses more than one elementary printable item, or a multiple COLUMNS, or a COLUMN with OCCURS.
RW-385-S	WRAP COLUMN integer should be between 1 and LINE LIMIT. The integer following the TO or AFTER phrase clearly must stay within the normal limits for the report.
RW-870-S	Library member not found. The name specified in a COPY statement could not be found in SYSLIB or the indicated library.
RW-871-E	REPLACING phrase has invalid syntax: discarded. The REPLACING phrase will be ignored and the COPY processed with no replacements.
RW-872-E	Word "BY" not found: no replacements done. The end of a token (identifier, literal, pseudo-text, etc.) was reached in a COPY...REPLACING directive and the expected word BY was not found.
RW-873-E	Too many levels of nesting of COPY. This message indicates that a COPY statement has been found within the text of another COPY member and the number of levels to which this is permitted has been exceeded. (See Installation and Operation for details.)
RW-874-E	Pseudotext invalid or too long: no replacements done. Either the pseudotext on the left of BY is empty (that is: == ==) or it is longer than the maximum (normally 512 bytes).
RW-875-W	No items were replaced during COPY. No match was made against the REPLACING phrase of the COPY statement during the COPY.
RW-876-E	Invalid COPY syntax: passed to compiler unchanged. The word COPY is not followed by a word that could be a member-name.
RW-877-W	Pseudotext brackets assumed as required by REPLACE. The format of the REPLACE statement requires that each operand should be within pseudotext brackets (== ==). These were assumed for this REPLACE statement.
RW-880-S	BASIS not allowed: passed to compiler but outcome unpredictable. The BASIS directive is not supported by the precompiler unless it is the first COBOL statement in the source. The results are unpredictable as the precompiler expects a complete source program.
RW-881-W	CBL/PROCESS statement passed to compiler but not actioned. CBL or PROCESS directives are accepted by the precompiler but not actioned by it. Since they may alter the compiler options which the precompiler is unaware of, the results may be unpredictable. See also Part 6.
RW-882-W	nn sequence errors were found in the program. This message may appear if the SEQUENCE option is set.