Appendix C: Error Messages

This appendix lists error messages that may appear in ReportWriter, along with explanations of the problems that may have caused the error. If you receive messages that are not listed in this appendix, contact your Synergy/DE Developer Support engineer at at 800.366.3472 (in the U.S. and Canada) or 916.635.7300.

Filename is not a version 7 or version 10 repository.

Repository version 10 can only open repository files that are in version 7 format or version 10 format. (Version 7 format was used by Repository versions 7, 8, and 9; it can be converted to version 10 format by the version 10 Repository.) It is likely that the specified repository predates version 7 and therefore can be neither opened nor converted by version 10. If this is the case, you must use the repository conversion program to convert it. Refer to the Repository release notes (REL_RPS.TXT) for instructions.

Partial expression can only be used in a subscript or ranged reference.

The “,” character is only valid when specifying a subscript value for an arrayed field or when ranging a field.

Partial expression cannot be used as a unary operator in an expression.

Only “+” and “” can be used as unary operators (to designate positive and negative). The specified operator requires two operands.

Partial expression must follow a field name.

The “[” character must follow a field name. It designates the subscripting of an arrayed field.

Alpha field not allowed: field name

You cannot specify an alpha field as part of an arithmetic operation in a calculation expression.

Alpha field not allowed: partial expression

Alpha fields can only be used in calculation expressions when doing assignments, such as CALC_FLD = ALPHA_FLD.

Alpha fields cannot be right‑justified.

You cannot right‑justify an alpha field. Alpha fields can only be left‑justified or centered.

Ambiguous field reference: field name

Two or more fields in the current set of report files have the same name. You must qualify the field name by preceding it with the filename. If more than one structure is assigned to that file and the same field name exists in two or more of the structures, you must also add the structure name (using the format filename.structure name.field name).

Ambiguous file/structure reference: partial expression

You have specified a field name in your expression that is not unique enough; another field in another file has the same name. Specify the filename.field name combination or the filename.structure name.field name combination if necessary.

An arrayed field cannot be referenced for subscripting.

You cannot use an arrayed field as a subscript for another arrayed field. You can only use a numeric literal or a nonarrayed numeric field name for the subscript.

Associated structures for file filename not found.

Refer to the message Structure structure name not found..

Cannot abandon changes after field modifications.

When modifying a report or page header or footer, if you add, delete, or edit a field, you can no longer abandon your changes.

Cannot add a sort field immediately before a merged field.

By definition, a merged sort field is merged with the sort field that precedes it. You’ve attempted to insert a new sort field between two sort fields being merged. Insert the new sort field either before the merged sort fields or at the end of the sort fields list.

Cannot change break status on merged field.

You’ve attempted to set a break on a merged field. By definition, a merged field cannot be a break field; however, the field being merged with can be a break field.

Cannot change sort order on merged field.

When sort fields are merged together, their sort order must be the same. To change the sort order for a set of merged sort fields, remove the merged status, change the sort order, and then reset the merge status for all fields in the set.

Cannot generate report: page size x too small for y lines per page.

You have attempted to generate a report, but the page size (specified in the Miscellaneous input window) is less than the combined number of header, footer, and detail lines. You must increase the page size before you can generate the report.

Cannot merge break field.

You’ve attempted to merge a break field with the field that precedes it. A merged field cannot be a break field; however, the field being merged with can be a break field.

Cannot merge first sort field.

By definition, merging a sort field attaches it to the field that precedes it. Therefore, the first sort field in the list cannot be merged.

Cannot move merged field.

Because a merged sort field is closely associated with the field to which it is merged, it cannot be moved.

Cannot open main repository file.

ReportWriter cannot find either the repository main file specified by the RPSMFIL logical or the rpsmain.ism file in either the directory specified by the RPSDAT logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.

Cannot open report definition file filename.

ReportWriter cannot find either the report definition file specified by the RPTRFIL logical or the reports.rpt file in either the directory specified by the RPTDAT logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.

Cannot open ReportWriter window library.

ReportWriter cannot find its window library file in the directory specified by the RPTDAT logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.

Cannot open repository text file.

ReportWriter cannot find either the repository text file specified by the RPSTFIL logical or the rpstext.ism file in either the directory specified by the RPSDAT logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.

Colon out of place in expression: partial expression

A colon is in an invalid location in the expression. Colons are only allowed within a field range specification (to separate the offset from the length) and within a %SUM intrinsic function specification.

Criterion specification is incomplete.

You have not entered all of the required information. When you define a selection criterion or conditional, you must specify the field name and the comparison operator. If other criteria are already defined, you must also specify the connector.

Decimal type expected: partial expression

You have specified the %SUM intrinsic function in a calculation expression, but you have not supplied a decimal field or literal for both the begin and end arguments.

Division by zero attempted.

While the report is being generated, a calculation field’s arithmetic expression is attempting to divide by zero, which is undefined. If your expression contains fields that might have data values of 0, use a calculation conditional to evaluate the expression only when the data field is nonzero.

Error occurred while scanning the repository.

A fatal I/O error occurred while ReportWriter was trying to read from the repository. ReportWriter will terminate.

Field field name cannot be deleted. It is used in a subtotal access field.

The temporary field you are trying to delete is used in a subtotal access field definition. Before you can delete it, you must remove it from all subtotal access fields that reference it.

Field field name is computed after selections and cannot be used here.

The field you are specifying in a selection criterion is a calculation field and has been designated as being computed after the selections are processed. (This means that you have either flagged the calculation field as being forced to occur after selections and sorting, or that the calculation field uses a subtotal access field, which by definition forces it to be computed after selections and sorting.)

Field field name is not defined as a break field.

The field you’re trying to specify as the break level for a subtotal access field is not defined as a break field. Break fields are sort fields that have been assigned a break status. To use the given field as the break level, you must first select it as a sort field and then set the break status. Press the List selections shortcut to display a list of available break fields.

Field field name not defined.

The field name you specified in a calculation expression is invalid. Use the List selections shortcut to display the list of fields that are available from the current report files.

Field field name not found in file filename.

Refer to the message Structure structure name not found..

Field cannot be deleted. It is printed on a detail line.

The temporary field you’re trying to delete was selected as a field to print. Before you can delete it, you must remove it from the list of fields to print.

Field cannot be deleted. It is printed on a page footer line.

The temporary field you’re trying to delete is used in a page footer. Before you can delete it, you must remove it from the page footer.

Field cannot be deleted. It is printed on a page header line.

The temporary field you’re trying to delete is used in a page header. Before you can delete it, you must remove it from the page header.

Field cannot be deleted. It is printed on a post‑break line.

The temporary field you’re trying to delete is used in a post‑break print line. Before you can delete it, you must remove it from all post‑break print lines.

Field cannot be deleted. It is printed on a pre‑break line.

The temporary field you’re trying to delete is used in a pre‑break print line. Before you can delete it, you must remove it from all pre‑break print lines.

Field cannot be deleted. It is printed on a report footer line.

The temporary field you’re trying to delete is used in a report footer. Before you can delete it, you must remove it from the report footer.

Field cannot be deleted. It is printed on a report header line.

The temporary field you’re trying to delete is used in a report header. Before you can delete it, you must remove it from the report header.

Field cannot be deleted. It is used as a range offset or length.

The temporary field you’re trying to delete is used as the range offset or length for another field. This ranged field is either specified as a field to print, used in a calculation expression, used in a selection statement, used as a sort field, and/or used in a field to print, calculation, or break line conditional. Before you can delete the field, you must remove all such range references.

Field cannot be deleted. It is used as a sort field.

The temporary field you’re trying to delete was selected as a field on which to sort. Before you can delete it, you must remove it from the list of sort fields.

Field cannot be deleted. It is used as a subscript.

The temporary field you’re trying to delete is used as a subscript for an arrayed field. This arrayed field is either specified as a field to print, used in a calculation expression, used in a selection statement, used as a sort field, and/or used in a fields to print, calculation, or break line conditional. Before you can delete it, you must remove the subscripted field from all such references.

Field cannot be deleted. It is used in a calculation expression.

The temporary field you’re trying to delete is used in a calculation expression. Before you can delete it, you must remove it from any and all calculations.

Field cannot be deleted. It is used in a criterion definition.

The temporary field you’re trying to delete is used in a selection criterion or conditional. Before you can delete it, you must remove it from any and all selection criteria and conditionals.

Field size cannot be changed. It is selected to print.

You’ve attempted to change the size of a temporary field that is selected to print on a detail line, break line, or header or footer line. You must remove the field from all print lines before changing its size.

Field used as break level in subtotal field field name. Cannot clear break.

You’ve tried to remove the break status from a sort field that is used in the definition of a subtotal access field. You must remove the field from all subtotal access field definitions before you can clear its break status.

Field used with %BRKCNT in calculation field field name. Cannot clear break.

You’ve tried to remove the break status from a sort field that is used in the %BRKCNT intrinsic within a calculation field. You must remove the field from all %BRKCNT intrinsics before you can clear its break status.

Fields for structure structure name not found.

Refer to the message Structure structure name not found..

File filename not found.

Refer to the message Structure structure name not found..

File cannot be deleted. Filename is linked to it.

This error message is displayed if the following scenario occurs. File A is related to File B in the repository. Both files have been selected as files to read. You are currently trying to delete File A. Because File A is required to access File B, you cannot delete it. Similarly, suppose File A is related to File B, and File B is related to File C. Since File A depends on File B to access File C, you cannot delete File B before deleting File C.

File cannot be deleted. Field field name is printed on a detail line.

A field from this file was selected as a field to print. Before you can delete the file, you must remove the field from the list of fields to print.

File cannot be deleted. Field field name is printed on a page footer line.

A field from this file is used in a page footer. Before you can delete the file, you must remove the field from the page footer.

File cannot be deleted. Field field name is printed on a page header line.

A field from this file is used in a page header. Before you can delete the file, you must remove the field from the page header.

File cannot be deleted. Field field name is printed on a post‑break line.

A field from this file was selected as a field to print on a post‑break line. Before you can delete the file, you must remove the field from all post‑break print lines.

File cannot be deleted. Field field name is printed on a pre‑break line.

A field from this file was selected as a field to print on a pre‑break line. Before you can delete the file, you must remove the field from all pre‑break print lines.

File cannot be deleted. Field field name is printed on a report footer line.

A field from this file is used in a report footer. Before you can delete the file, you must remove the field from the report footer.

File cannot be deleted. Field field name is printed on a report header line.

A field from this file is used in a report header. Before you can delete the file, you must remove the field from the report header.

File cannot be deleted. Field field name is used as a range offset or length.

A field from this file is used as the range offset or length for another field. This ranged field is either specified as a field to print, used in a calculation expression, used in a selection statement, used as a sort field, and/or used in a fields to print, calculation, or break line conditional. Before you can delete the file, you must remove all such range references.

File cannot be deleted. Field field name is used as a sort field.

A field from this file was selected as a field on which to sort. Before you can delete the file, you must remove the field from the list of fields to sort.

File cannot be deleted. Field field name is used as a subscript.

A field from this file is used as a subscript for an arrayed field. This arrayed field is either a field to print, used in a calculation expression, used in a selection statement, used as a sort field, and/or used in a fields to print, break line, or calculation conditional. Before you can delete the file, you must remove the field being used as a subscript from all such references.

File cannot be deleted. Field field name is used in a calculation expression.

A field from this file is used in a calculation expression. Before you can delete the file, you must remove the field from any and all calculations.

File cannot be deleted. Field field name is used in a criterion definition.

A field from this file is used in a selection criterion or conditional. Before you can delete the file, you must remove the field from any and all selection criteria and conditionals.

File cannot be deleted. Field field name is used in a subtotal access field.

A field from this file is used in a subtotal access field definition. Before you can delete the file, you must remove the field from all subtotal access fields that reference it.

File cannot be deleted. It is used in a multiple projection.

You’ve attempted to delete a secondary file that is associated with another secondary file (its sister file) in a multiple projection. You must set the multiple projection status of the sister file to “Together” before deleting the current file.

File cannot be deleted. Structure structure name is referenced.

This error message is displayed if the following scenario occurs. File A is related to both File B and File C in the repository. File A’s structure defines a key that contains an external segment from File B’s structure. File A then uses this key for the relation to File C. You are currently trying to delete File B. Because File B is essential for the relation to File C, you cannot delete File B before deleting File C.

File/structure not found: partial expression

You’ve specified an invalid file definition or file/structure definition name as the argument in the %GOTREC intrinsic function. View your list of Files to Read for the valid file/structure definition names.

File/structure specification expected: partial expression

You’ve specified the %GOTREC intrinsic function, but a file/structure specification was not found within the parentheses.

Function argument expected: partial expression

You’ve specified the %SUM or %GOTREC intrinsic function without specifying the proper argument(s).

Key key name not found for structure structure name.

Refer to the message Structure structure name not found..

Key of reference key name not found for structure structure name.

Refer to the message Structure structure name not found..

Invalid comparison field type.

The data type of the field you’ve specified as the compare value in a selection criteria statement does not match that of the field being compared.

Invalid date specification.

You’ve entered an invalid date as a comparison value for a date field.

Invalid field field name referenced.

You’ve specified an invalid field name in a print or calculation conditional, as a subscript for an arrayed field, or as a field range offset or length.

Invalid name link relation.

You’ve skipped a segment definition when modifying the NAME_LINK_KEY in the input window. Segment definitions must be contiguous.

Invalid precision specification.

The precision value you specified is larger than the length of the field. (The number of decimal places must be less than or equal to the field length.)

Invalid report version version cannot be loaded with the current ReportWriter.

You’ve attempted to access a report that has not been converted to the current revision level. Refer to your online release notes for information on converting existing ReportWriter reports.

Invalid selection criteria specification.

Your selection criteria contain an invalid wildcard specification. For example, entering one or more asterisks (*) and nothing else would be considered invalid.

Invalid subscript field type.

You can only use numeric type data fields as subscripts for an arrayed field. (Date and time fields are also decimal fields; however, their use as subscripts is rare.)

Invalid temporary field name.

You’ve specified a field name that is invalid. Valid field names begin with a letter and can contain letters, numbers, underscores, and dollar signs.

Invalid time specified.

You’ve either specified a negative value in a question field while a report is being generated, or your data file contains a negative time value. Time values must be greater than zero.

Invalid value.

In your selection criteria, you’ve attempted to compare a numeric field with an alphanumeric literal.

Linked structure structure name not found.

Refer to the message Structure structure name not found..

Maximum number of break line fields (99) has been selected.

You’ve tried to select more than 99 fields to print on your pre‑break or post‑break print line. You cannot select any more fields to print until you delete one or more fields from your list of fields to print.

Maximum number of conditions (5) has been defined.

You’ve tried to define more than five conditions. You cannot add any more conditions to the conditional until you delete one or more existing conditions.

Maximum number of detail lines (10) has been defined.

You’ve tried to create more than 10 detail lines. You cannot create any more lines until you delete one or more existing lines.

Maximum number of fields to print (990) has been selected.

You’ve tried to select more than 990 fields to print. You cannot select any more fields to print until you delete one or more fields from your list of fields to print.

Maximum number of fields to print per line (99) has been selected.

You’ve tried to select more than 99 fields to print on the current detail line. You cannot select any more fields to print until you delete one or more fields from the current line.

Maximum number of files (50) has been selected.

You’ve tried to select more than 50 files to read. You cannot select any more files until you delete one or more files from your list.

Maximum number of individual temporary fields (99) has been defined.

You’ve tried to create more than 99 calculation, question, text, environment, or subtotal access fields. You cannot create any more fields of that type until you delete one or more existing ones.

Maximum number of page header lines (10) has been defined.

You’ve tried to create a new detail line, but the number of detail lines in combination with the number of split headers has reached the allowed maximum. For example, if you have five detail lines, all of which have a field with a split heading, you have a total of 10 header lines. ReportWriter tries to maintain a one‑to‑one correspondence between header and detail lines. To add additional detail lines, edit the page header in some way. Doing so flags the header as “dirty,” and ReportWriter no longer tries to maintain the one‑to‑one correspondence between header and detail lines.

Maximum number of ranged fields (300) has been defined.

Each time a range is specified for a field, the number of ranged fields is increased by 1. You’ve reached the maximum number of ranged fields. You cannot range any more fields in the report until you delete one or more existing ranged fields.

Maximum number of selections (25) has been defined.

You’ve tried to define more than 25 selections. You cannot define any more selections until you delete one or more existing selections.

Maximum number of sort fields (10) has been selected.

You’ve tried to select more than 10 sort fields. You cannot select any more sort fields until you delete one or more fields from your list of fields to sort.

Maximum number of subscripted fields (300) has been defined.

Each time an arrayed field is used in a calculation, in a selection, in a conditional, or as a field to print, the count of subscripted fields is increased by 1. You’ve reached the maximum number of subscripted fields. You cannot subscript any more arrayed fields in the report until you delete one or more existing usages.

Maximum report width (255 columns) has been reached.

The total length of the fields you’ve selected to print on the current line is longer than 255 columns. You cannot select any more fields to be printed on that line until you delete one or more fields from the line.

Merged sort fields must be the same type and length.

You’ve selected a sort field to be merged with the preceding one. When merging two sort fields, the fields must be the same data type and length.

Merged sort fields must have the same sort order.

You’ve selected a sort field to be merged with the preceding sort field, but they are not sorted in the same order.

Missing “)” or “]” in expression: partial expression

ReportWriter has found an open parenthesis ( ( ) without a matching close parenthesis ( ) ) or a left square bracket ( [ ) without a matching right square bracket ( ] ) in the expression.

Missing operand: partial expression

You’ve specified an operator without the corresponding operand(s).

Missing operator in expression: partial expression

You’ve specified two operands in the expression without specifying an operator. Select the List operators menu entry to display a list of valid operators.

Multiple projections not possible for the relation to this file.

When selecting a file on which to perform multiple projections, the relationship defined by the other file (the “From” file) must be one to many. In other words, the key in this file used in the relation must allow duplicates.

No break fields defined.

You’ve selected the List selections function while on the Break level field of a subtotal access field definition. This option attempts to display a list of sort fields that are defined as break fields for the current report. Currently, no sort fields have their break status set. You must have at least one break field defined before you can access a subtotal for a level other than the entire report.

No enumerated information found. Field will be processed as numeric.

A field has been defined as enumerated (E), but the enumerated information cannot be found in the repository. Rather than the numeric value in the field being used as an index to a text string, the numeric value will be processed explicitly.

No files have been defined in the repository.

ReportWriter obtains its list of available files from Repository. You cannot create a report in ReportWriter unless one or more files is defined in the repository and all files have a structure assigned to them. Currently, either no files are defined or the defined files do not have structures assigned to them.

No input files have been defined for this report.

You must select one or more report files before ReportWriter can perform the requested function. Select the Files to read function.

No name link relations available.

You have selected Add file via name link from the Files to read function and one of the following situations is true: the Repository cross‑reference file rpsxref.ism (or the file pointed to by RPSXFIL) is not found, or the cross‑reference file does exist, but it doesn’t contain any relations based on field name links.

No previous file at the same read level.

When you select a file on which to perform multiple projections, there must already be at least one file to read on the same level. “Same level” refers to the levels of the tree in a hierarchical relationship. For example, if File A relates to File B, File A relates to File C, and File C relates to File D, files B and C are at the same level, while File D is not.

Null value not allowed in expression: partial expression

One of the following error conditions is present in the calculation expression: no expression was entered, no value was specified between parentheses or brackets, or an operator was followed by either nothing or a close parenthesis.

Numeric fields cannot be centered.

You cannot center a numeric field. Numeric fields can only be left‑ or right‑justified.

Operator (operator) not allowed with alpha operand.

You’ve specified a mathematical operator in conjunction with an alpha operand. Alpha operands can only be used in calculation fields to assign their value to a temporary field.

Percent sign out of place: partial expression

You’ve specified the intrinsic function character (“%”) in an unexpected location in the calculation field expression.

Question fields cannot inherit attributes from an integer field.

You have attempted to inherit the characteristics of a question field from a field whose type is integer. This is not allowed.

Quoted string encountered in expression: partial expression

You cannot use quoted strings in calculation expressions that perform numeric operations.

Range offset plus length literal must be within the field size.

The range offset and length values must be equal to or less than the size of the field, and the range offset plus the length must be less than or equal to the size of the field.

Range specification is incomplete.

You have not entered all of the required information. When you range a field, you must specify the range offset and the range length.

Range value literal must be in the range 1 to 99.

The largest field size that can be accessed is 99 characters. Therefore, the value specified for the range length must be between 1 and 99, inclusive.

Relation relation name is not for structure structure name.

Refer to the message Structure structure name not found..

Relation linkage corrupted. Report cannot be loaded.

Refer to the message Structure structure name not found..

Relation records for structure name not found.

Refer to the message Structure structure name not found..

Report cannot be deleted. It is being used by another user.

Only one user can load or delete a report at a time, and someone else is currently using the requested report.

Report cannot be saved into an existing report.

When you modify an existing report, you can save it (copy it) under another name. The name you have specified is the name of an existing report. Enter another name.

Report cannot be saved. It is being used by another user.

Only one user can load or delete a report at a time, and someone else is currently using the requested report.

Report control structure overflow.

The report you’re trying to generate is too complex for ReportWriter. Although you haven’t exceeded any individual program maximums, the amount of memory required to store the current report definition is too extensive.

Report is incomplete. Please select fields to print.

You cannot display the current report until you have selected fields to print using the Fields to print function, selected pre‑ or post‑break fields to print, or selected a field to print in a header or footer. (If you have not selected your report files, you must do that first.)

Report not found.

You’ve attempted an operation on a report that cannot be found in the current report definition file. Press the List selections shortcut to display a list of available reports.

Selected field name field name will not fit in the expression.

By adding this field, you will exceed the maximum size of an expression (150 characters). Therefore, you cannot add this field. If any of the field names used in the expression are prefixed with their file and/or structure names, and if these field names are unambiguous, you can remove the prefixes to decrease the size of the expression.

Sort field cannot be deleted. It is merged with the next field.

Merged sort fields must be deleted in a “last in, first out” order. In other words, you must delete them from the bottom up.

Structure structure name not found.

The report definition and the repository are out of sync. This could have happened in one of two ways: the repository was modified after a report definition was saved, or, while a report was being designed, the repository was modified.

Once a repository is defined, it should not be modified! Modifications to a repository that is being used by ReportWriter can invalidate report definitions.

Structure structure name not found. Cannot load fields.

Refer to the message Structure structure name not found..

Subscript specification is incomplete.

You have not entered all the required information. When you use an arrayed field, you must specify a subscript value for each dimension of the array.

Subscript value literal must be in the range 1 to max array elements.

The literal value used to specify an arrayed field subscript is outside the bounds of the array.

%SUM requires array beg:end: partial expression

You have specified the %SUM intrinsic function but have not included the required arguments. You must specify the name of a one‑dimensional array and two numeric fields or literals indicating the first and last elements to include in the sum.

Tagged field not found.

Refer to the message Structure structure name not found..

Temporary field field name already exists. Please enter another name.

You entered the name of an existing temporary field. Temporary field names must be unique.

Temporary field definition is incomplete.

You have not entered all of the required information. You must specify the following information for each type of temporary field:

Temporary field

Required information

Calculation

Name, type, length, and expression

Environment

Name, type, and length

Question

Name, type, length, and prompt

Subtotal access

Name, field to total, and break level

Text

Name

Too many close parentheses in expression: partial expression

The number of close parentheses ( ) ) exceeds the number of open parentheses ( ( ).

Too many lines to view in the report format. It has been truncated.

The report format that you view is divided into three sections: report header, report page, and report footer. The report page section includes the page header, date and page number line, data lines, pre‑ and post‑break lines, and page footer. The maximum viewable size of each section is 16 lines. Because the size of your report page exceeds 16 lines, this section of the report format that you’re viewing has been truncated.

Too many total fields. Program will terminate.

The number of fields to be totaled requires more memory than is currently available.

Unrecognized character in expression: partial expression

The expression contains an invalid character. An expression can only contain the following characters: all numeric and alphanumeric characters (alphanumeric characters that aren’t in quotation marks are assumed to be field specifications); operators (+, , *, and /); parentheses, brackets, and commas (for array subscripting); and quoted strings for alpha expressions.

Unrecognized intrinsic function reference: partial expression

You’ve specified the intrinsic function character (%) without supplying a valid intrinsic function name.

Wrong number of dimensions specified: partial expression

An arrayed field has either no subscript specifications or the incorrect number of subscript values. The number of array subscript values that you specify must be equal to the number of field dimensions.