|
|
|
The following messages are issued by the CA Earl component.
Reason:
An ampersand is only valid when it prefixes a field name in the postsort processing section.
Action:
Check the syntax of the current statement.
Reason:
The compiler expected to encounter an apostrophe (') but did not. Literals must begin and end with an apostrophe, and any embedded apostrophes in the literal must be paired.
Action:
Check specification of apostrophes.
Reason:
The specified bitmask is invalid.
Action:
Ensure that the bitmask is of the form M'mmmmmmmm' where acceptable mask values are 1, 0, or X.
Reason:
An attempt has been made to use a CA Earl reserved word or an ampersand (&) identifier as a user-defined label. CA Earl labels must not be CA Earl reserved words and must start with a letter.
Action:
Change the label definition, and resubmit.
Reason:
The FILE statement does not specify a logical unit number (UNIT=) for a tape file.
Action:
Supply the required parameter on the FILE statement in the form UNIT=SYSnnn.
Reason:
The initial value specified for a number has an invalid decimal place specification. For example, DEF NUMBER (3.3)=999. is invalid; if a decimal point is specified as part of the precision, at least one digit must follow the point.
Action:
Correct the decimal place specification to agree with the precision of the field.
Reason:
An invalid hexadecimal literal or constant has been specified. A hexadecimal literal specifies the contents of one or more bytes; two characters in the range 0 to 9 or A to F must be specified for the contents of each byte.
Action:
Ensure that an even number of characters is in the literal or constant.
Reason:
There are no characters between apostrophes, or a character string is not terminated by a final apostrophe ('). Literals must begin and end with an apostrophe. Any embedded apostrophes must be doubled. For example, to produce a literal containing COMPANY'S, then 'COMPANY''S' must be coded.
Action:
Check for an uneven total number of apostrophes; literals must have an even number of apostrophes.
Reason:
An invalid character was encountered in the CA Earl source program. The invalid character is not a digit, CA Earl special character, arithmetic operator, or relational operator.
Action:
Correct the source program if in error. Respecify the literal as a hexadecimal literal if the character is embedded in a literal.
Reason:
The CA Earl compiler expects a keyword at this point in the program. This is probably the result of a previous error; after the compilation of the previous statement, the compiler expects to find a valid CA Earl keyword at the start of the next statement.
Action:
Check the syntax of the current and previous statements.
Reason:
An invalid PICTURE clause has been specified for a field. A PICTURE clause must specify an alphanumeric literal, enclosed in apostrophes.
Action:
Ensure that the PICTURE clause specifies a valid literal, enclosed in apostrophes.
Reason:
The numeric precision clause is invalid, for example, (0,) or (15.10). Valid numeric precision clauses have the form (i.d) where i+d <= 15.
Action:
Correct the precision clause.
Reason:
The precision clause specifies a data type other than N, P, B, U, X, or Q.
Action:
Correct the precision clause.
Reason:
The syntax of the statement requires a right parenthesis.
Action:
Correct the statement to ensure that all specified right and left parentheses are matched.
Reason:
An arithmetic factor starts with a symbol that is not a numeric variable or signed constant.
Action:
Check for invalid syntax or misplaced parentheses.
Reason:
A field name can only be prefixed with an ampersand in the Report section of a CA Earl program.
Action:
Remove the ampersand or position the statement after the REPORT statement.
Reason:
A nonnumeric symbol was encountered while processing an arithmetic factor.
Action:
Check for invalid syntax or misplaced parentheses.
Reason:
The specification of an array index is invalid. Valid array index specification is of the form (/index value/). There must be no spaces between the characters (/ at the start of the array index value, or between the characters /) at the end.
Action:
Correct the index specification.
Reason:
The syntax of the current statement does not allow this symbol to follow a variable.
Action:
Check the syntax of the current statement.
Reason:
The font name on the indicated statement is not preceded by a period (.).
Action:
Correct that statement so that a period appears before the font name.
Reason:
The specified symbol is not a valid CA Earl identifier.
Action:
Ensure that the identifier is valid. Otherwise, ensure that the indicated symbol is valid at this point in the current statement.
Reason:
The CA Earl compiler expected to find an equal sign (=) but did not.
Action:
Check the syntax of the current statement.
Reason:
An invalid symbol was encountered where a logical factor (a variable name or left parenthesis) was expected.
Action:
Check the syntax of the current statement.
Reason:
The symbol encountered is not an identifier name, literal, number, plus sign, minus sign, left parenthesis, equal sign, bitmask, or relational symbol.
Action:
Check the syntax of the current statement.
Reason:
An invalid symbol follows a logical factor. Valid symbols are AND or a new statement.
Action:
Check the syntax of the current statement.
Reason:
The CA Earl compiler expected to find a minus sign (-) or TO as the delimiter of the elements of an array.
Action:
Check the syntax of the ARRAY definitions.
Reason:
The END statement was not encountered before the physical end of the source program. The last statement of an CA Earl program must be an END statement.
Action:
Add an END statement.
Reason:
The CA Earl compiler expects a simple value (that is, a number, literal, or field name) at this point in the program.
Action:
Check the syntax of the current statement.
Reason:
The symbol encountered is not an identifier name, literal, number, plus sign, minus sign, left parenthesis, equal sign, bitmask, relational symbol, or new statement keyword.
Action:
Check the syntax of the current statement.
Reason:
The indicated item should be an unsigned number.
Action:
Check the syntax of the current statement.
Reason:
The indicated item is not a statement keyword, heading, or picture.
Action:
Check the syntax of the current statement.
Reason:
A label has been assigned incorrectly to a statement where use of a label is not permitted.
Action:
Remove the label, or move it to a statement that permits labels.
Reason:
The OPTION DISK= statement specifies an invalid disk device type. Only values of 2311, 2314, 3330, 3311, 3340, 3350, 3310, 3370, 3375, 3380, 3390, 9332, and 9335 are valid, in the format DISK=nnnn.
Action:
Correct the OPTION statement.
Reason:
The OPTION statement specifies an invalid parameter for the LIST clause. The possible values are LIST ON or LIST OFF.
Action:
Use only ON or OFF.
Reason:
The OPTION statement specifies an invalid parameter for the OMIT clause.
Action:
Correct the syntax of OPTION OMIT.
Reason:
The specified value is not an integer but it should be.
Action:
Ensure that the symbol is a valid integer; it must not contain a decimal point.
Reason:
The OPTION statement specifies invalid parameters for the OMIT clause.
Action:
Correct the syntax of OPTION OMIT.
Reason:
There was an error in the FILE statement—the key length exceeds the stated record length. The key length, either as directly given in the FILE key length specification or as calculated from the total length of the named key fields in the KEY= clause, exceeds the record length as given in the RECORD= parameter.
Action:
Correct the key length or the record length.
Reason:
The OPTION SORT= statement specifies an invalid integer value. Acceptable values are 1 to 9, or NONE to bypass the sort.
Action:
Correct the OPTION SORT= syntax.
Reason:
The WRITE clause of the OPTION statement or the TOTALS clause of the PRINT statement specifies an invalid parameter.
Action:
Specify WRITE ONLY or TOTALS ONLY.
Reason:
The compiler has encountered an unrecognizable parameter on the OPTION statement.
Action:
Check the syntax of the OPTION statement and ensure the correct spelling of specified parameters.
Reason:
The name used is an CA Earl reserved word.
Action:
Remove the reserved word from the DEFINE statement.
Reason:
The precision clause of the SET statements is invalid or an equal sign (=) has been omitted.
Action:
Correct the syntax of SET.
Reason:
Variable length indexed sequential files are not supported under VSE or VM.
Action:
Check the attributes of the file being accessed; it cannot be both indexed sequential (organization INDEXED) and variable length (format VARIABLE).
Reason:
The statement must specify a valid alphanumeric literal.
Action:
Check the literal to ensure that it is enclosed in apostrophes and that any embedded apostrophes are doubled.
Reason:
The END statement has been read prematurely. CA Earl source program is incomplete. The program must either include procedural statements or specify one or more reports.
Action:
Check for missing statements.
Reason:
The indicated statement is not valid at this point in the CA Earl source program. The problem could be caused by a violation of one of the following rules:
Action:
Correct the order of statements in your source program.
Reason:
The END statement has been read, and the CA Earl source program contains no processing or report generation statements. Every CA Earl source program must contain either one or more processing statements (for example, SET, DECODE, PUT), or must specify one or more reports to be produced.
Action:
Check for a misplaced END statement or a missing source file.
Reason:
The FILE keyword does not have a preceding file name. Each CA Earl FILE statement must have a file name.
Action:
Add a file name to the FILE statement.
Reason:
A FILE statement was encountered with no file parameters.
Action:
Correct the FILE statement.
Reason:
A FILE statement for a user module specifies an invalid communication area length. The communications area is used for two-way communication between CA Earl and the user module. The first four bytes have special meaning within CA Earl's input and output routines, and it is necessary to specify a length of at least four bytes for this area.
Action:
Correct the FILE statement.
Reason:
An invalid or unrecognizable parameter was encountered on a FILE statement. Certain parameters are only valid for certain file types.
Action:
Check the syntax of the FILE statement, and ensure the correct spelling of the parameters.
Reason:
An invalid LABEL= parameter was encountered on the FILE statement. The only acceptable values are STANDARD or NONE for this parameter.
Action:
Correct the FILE statement.
Reason:
The data type of the key field is invalid. Only types N, P, U or B (numeric), or type X or Q (alphanumeric) may be specified as key fields for a file.
Action:
Correct the DEFINE statement.
Reason:
The FILE statement specifies an invalid logical unit number for a tape file. The UNIT= parameter must be in the form UNIT=SYSxxx where xxx is in the range 001 to 240.
Action:
Correct the FILE statement.
Reason:
An array has been specified as a key field. Only individual fields of types N, P, U, or B (numeric), or type X or Q (alphanumeric) are allowed as file key fields.
Action:
Specify a non-indexed field as the key.
Reason:
The statement specifies a keyed GET to the named file, but no key fields were specified on the FILE statement. Only values of fields specified in the KEY= clause on the FILE statement may be used in the keyed form of the GET.
Action:
Correct the FILE statement or the GET statement.
Reason:
The indicated GET statement specified more key values than there are key fields specified in the FILE statement for the file.
Action:
Ensure compatibility between the FILE statement KEY= clause and the form of GET statement used.
Reason:
The symbol following the keyword DEFINE is not a valid CA Earl identifier.
Action:
Check the syntax of the DEFINE statement to ensure that the identifier conforms to the CA Earl rules.
Reason:
The current statement is not complete, or an incorrect keyword has been found.
Action:
Correct the statement's syntax.
Reason:
Invalid precision is specified for an alphanumeric field.
Action:
Valid precision for an alphanumeric field is 1 to 32768 bytes. Correct the precision specification.
Reason:
The syntax of the GET statement requires AND here. A GET statement requires that the key argument and any other subsidiary logical expression argument be connected by an AND.
Action:
Correct the GET statement.
Reason:
A second OPTION statement with a SAVE=name parameter has been encountered.
Action:
Remove the unwanted statement.
Reason:
The initial value given in a DEFINE statement is not the correct data type.
Action:
Ensure that the initial values match the field's data type. Use numeric for types N, P, U, or B. Use alphanumeric or hexadecimal literals for type X or Q.
Reason:
The module name for the linkage editor is more than five characters long.
Action:
Reduce the module name to five characters.
Reason:
The symbol following OPTION SAVE= is not a valid name.
Action:
Specify a module name of not more than five characters.
Reason:
The symbol is not valid in the syntax of the ARRAY specification.
Action:
Check the syntax of the ARRAY specification.
Reason:
The bit string field is defined in the General Storage Area (GSA), not in the record area associated with a file. A bit string field may only be specified in a record area associated with a file. If it is necessary to store a bit string field in working storage, it must be defined or predefined as an alphanumeric field (type X), and moved using this definition.
Action:
Correct and resubmit.
Reason:
The data type is not N, P, U, B, X, Q, or S.
Action:
Specify the correct data type.
Reason:
The symbol following the data type on a DEFINE statement is not a 'Heading', literal, PICTURE or another statement command word.
Action:
Correct the syntax of the DEFINE statement.
Reason:
If the GOTO keyword is specified in the form GOTO, the TO must always be specified.
Action:
Specify TO if the GOTO keyword is specified in the form GOTO.
Reason:
Incorrect syntax for the DECODE statement was encountered. CA Earl syntax requires that the name of the primary argument field (the field being DECODEd) is followed by the word INTO.
Action:
Correct the syntax of the DECODE statement.
Reason:
The value for comparison is not an integer, identifier, alphanumeric literal, or bitmask.
Action:
Ensure that only values of the same type are used.
Reason:
The bitmask field was invalidly used. The bitmask field (type S) may only be tested against a bitmask argument. Any other comparison (for example, against numeric or alphanumeric fields) is invalid.
Action:
Correct and resubmit.
Reason:
There was an invalid range test in a logical expression. The two fields or values specified in a range test must be in an equal (=), or not equal (NOT =) relationship with each other. The relational operators (>), (<), (>=), or (<=) are not allowed in a range test. Valid range tests are as follows, where (=) is implicit and not required:
SELECT FLDA (A-B) GOTO LBLA FLDB (99-106) GOTO LBLB FLDC NOT (B-C) SELECT FLDD NOT (400-500)
Action:
Use only = or NOT =.
Reason:
A bit string field was specified with an invalid relational operator. Bit string fields may only be compared in an equal (=) relationship with an argument. The operators (>), (<), (>=), and (<=) are invalid.
Action:
Correct and resubmit.
Reason:
The secondary function specified in a DECODE statement is not an integer, identifier, literal, or arithmetic expression.
Action:
Correct the syntax of the DECODE statement.
Reason:
A DECODE statement specifies no translation to be performed.
Action:
Correct the syntax of the DECODE statement.
Reason:
The logical expression specified in the current statement (for example, DECODE, GOTO, GET, SELECT) is too complex. The current maximum number of terms is 30.
Action:
Reduce the number of terms in the logical expression.
Reason:
A bit string field was specified in a range test and may only be tested against a single bit string argument. A reference to a range of values is not allowed.
Action:
Correct and resubmit.
Reason:
No PRINT statements were specified for this report. Each report must specify one or more PRINT statements. Runs not requiring printed output should not specify a REPORT statement.
Action:
Omit the Report Section if no report is required.
Reason:
Syntax of expression requires a left parenthesis.
Action:
Check syntax of the current statement.
Reason:
This statement requires a (D) or (T) specification when coded as part of postsort processing.
Action:
Correct and resubmit.
Reason:
A taglist on a PRINT statement is not followed by a valid printable item.
Action:
Ensure that only identifiers and alphanumeric literals are tagged.
Reason:
TOTALS ONLY, DOUBLE SPACING, or TREBLE/TRIPLE SPACING specifications apply to the whole report, so they may only appear on the first PRINT statement.
Action:
Specify the print options on the first PRINT statement.
Reason:
The syntax of a PRINT statement expects a valid tag value at this point. A valid tag value consists of one or more tag characters followed by a semicolon (;) with no spaces between the characters.
Action:
Correct and resubmit.
Reason:
The syntax requires the word SPACING following DOUBLE or TREBLE/TRIPLE on the PRINT statement.
Action:
Specify SPACING on the PRINT statement.
Reason:
The syntax of the PRINT statement requires an output item (that is, a field name or literal) to be specified at this point.
Action:
Check the PRINT statement to ensure that:
Reason:
The PRINT statement at sign (@) spacing specification is in error. Valid specifications of @ spacing are:
@ absolute location @ identifier + or - adjustment
Action:
Check the syntax of the PRINT statement.
Reason:
The first symbol of an item on a REPORT or PRINT statement is not an identifier, integer, alphanumeric literal, hash sign, ampersand, or left parenthesis.
Action:
Correct the syntax of the REPORT or PRINT statement.
Reason:
More than one left parenthesis was found within an output item on a PRINT statement.
Action:
Remove extra parentheses.
Reason:
When OPTION WRITE ONLY is specified, the CA Earl program can only write data to an output file and cannot produce a report. The FORMAT statement must be specified to write the data.
Action:
Remove the REPORT statement, or add a FORMAT statement before the END statement.
Reason:
No RELATIONSHIP clause has been specified on a DB statement.
Action:
Specify the hierarchy of the segments of the database.
Reason:
A SELECT statement does not contain ALL or a logical expression as the selection criteria.
Action:
Correct the syntax of the SELECT statement.
Reason:
A precision clause is required for this statement but has not been supplied.
Action:
Specify the precision of the field in the form (n) for an alphanumeric data item, or (i.d) for a numeric data item.
Reason:
The tag character on a SELECT statement is not in the range A to Z, or is not enclosed within apostrophes.
Action:
Correct the syntax of the SELECT statement.
Reason:
The total length of the sort control fields exceeds the limit of 256 bytes.
Action:
Simplify the CONTROL statement by reducing the number of fields to be sorted. If this is not possible, check the length definition of any alphanumeric fields on the CONTROL statement, and reduce the lengths where possible.
Reason:
The length of the specified data item is greater than the logical print line length.
Action:
Check the length of the data item and also the current printer width (that is, the default printer width or OPTION PRINTER= value, if specified).
Reason:
The OPTION statement specifies an invalid parameter for the OPTION OMIT feature.
Action:
Correct the OPTION OMIT statement.
Reason:
The DB statement has no label.
Action:
Check the syntax of the DB statement.
Reason:
The database type is not DL/I, IMS, SQLDS, DB2, or CA Datacom.
Action:
Correct the DB statement.
Reason:
The PCB number or the DBD name is specified incorrectly.
Action:
Specify PCB=number or DBDname.
Reason:
The specified DB statement in the RELATIONSHIP clause refers to a file name that is not a valid segment file definition. This message appears after the last set of definitions for this DB.
Action:
Use the file names from the segment file statements.
Reason:
A GET statement for a database refers to a file that is not a database file.
Action:
Specify the name of a database file.
Reason:
A file name must be followed by either another file name or a search argument.
Action:
Check the syntax of the GET statement for a database.
Reason:
No segment name has been specified on a database FILE statement.
Action:
Specify the DL/I or IMS segment name.
Reason:
The specified segment file name is not defined in the RELATIONSHIP clause for the current DB.
Action:
Specify the correct name entered on the DB statement or FILE DL/I or IMS statement.
Reason:
A RESET statement cannot be issued for a database segment file.
Action:
Remove the RESET statement or correct the file name.
Reason:
A mixture of (D) and (T) statements has been found within the scope of an IF statement.
Action:
Correct the statements.
Reason:
The segment was defined in a previous relationship definition.
Action:
Specify segments in a true hierarchical relationship.
Reason:
The segment relationship must be defined in the correct hierarchical sequence.
Action:
Define the segment relationship in the correct hierarchical sequence.
Reason:
The specified segment was not a child of the parent in the previous relationship definition.
Action:
Specify the correct hierarchical relationship of segments in the database.
Reason:
The specified field is not within a segment file.
Action:
Specify a segment field name.
Reason:
The RELATIONSHIP clause of a DB statement for a DL/1 or IMS database is missing the relational operator '->'.
Action:
Add the relational operator.
Reason:
No comparative field has been specified in a logical expression.
Action:
Specify the name of a field containing the comparative value.
Reason:
A round has been specified on a SET statement for a nonnumeric item.
Action:
Check the item's name and definition.
Reason:
The key field is not a four-byte binary field.
Action:
Specify the correct precision on the key field.
Reason:
The syntax does not allow the specification of both SKP and ADR on a GET statement.
Action:
Check the syntax of the GET statement for VSAM.
Reason:
ADR is not valid on a GET statement for an RRDS file.
Action:
Use the relative record number to retrieve the record.
Reason:
The syntax expects ADR or KEY following DIR or SKP on a VSAM GET statement.
Action:
Correct the syntax of the GET statement for VSAM.
Reason:
A parameter is coded on a VSAM PUT statement that is not applicable to VSAM.
Action:
Check the syntax of the PUT statement for VSAM.
Reason:
A COPY statement has more than 30 USING arguments.
Action:
Limit the COPY member to 30 substitutions.
Reason:
A COPY statement refers to a member that is not in the library identified by the EARLLIB DD, DLBL, or FILEDEF statement.
Action:
Check the spelling of the member name and ensure that the EARLLIB JCL or EXEC statement refers to the correct library. For VSE systems, make sure that the source member is cataloged with sublibrary prefix of 0.
Reason:
The member name is a CA Earl keyword or is not one to eight alphanumeric characters starting with an alphabetic character.
Action:
Check for the missing member name and ensure that the name conforms to the CA Earl rules.
Reason:
A copied statement contains a substitution code that is not numeric or in the range '1' to 'number of USING arguments'.
Action:
Ensure that the substitution code is in the format :nn, where nn is the position of the substitution argument, and that the COPY statement specified all of the required arguments.
Reason:
More than eight nestings of COPY statements were encountered.
Action:
Check for a loop of COPY statements.
Reason:
The library support was excluded from the CA Earl options program.
Action:
Assemble the EARLGEN macro with the parameter LIBRARY=YES specified. Refer to the CA Earl Systems Programmer Guide OS/390 for instructions.
Reason:
An array may not be specified for an SQL column definition.
Action:
Correct the definition.
Reason:
An identifier may only be defined once within a program. Once a field has been defined, its size, field type, headings, picture clause, and so forth, may not be altered.
Action:
If trying to define a unique field, alter the name on the second DEFINE statement so that the names are unique within the first 18 characters.
Reason:
The statement specifies an undeclared identifier. The indicated identifier should have been defined in a previous statement.
Action:
Ensure correct spelling of the identifier, or define it on a previous DEFINE statement.
Reason:
The previous FILE statement specified a key field that has not been defined. All fields specified in the KEY= clause must be defined within the record for that file.
Action:
Check the spelling of the field name.
Reason:
The specified key fields have not been defined as being in contiguous byte locations within the input record. The IBM organization for ISAM files only allows a single physical record key. CA Earl syntax allows you to specify this single key as several logical fields, but they must be contiguous.
Action:
Specify key fields that are contiguous.
Reason:
The indicated file name exceeds the permissible length. The maximum length of the file name, excluding the colon, is seven bytes for VSE or eight bytes for z/OS or VM.
Action:
Shorten the file name.
Reason:
The FILE statement contains duplicate parameters.
Action:
Check the syntax of the FILE statement for duplication of one or more parameters.
Reason:
This message is issued for any of the following reasons:
Action:
Ensure that each value is within acceptable limits.
Reason:
A redefined field is incorrectly specified to end outside the field that it is redefining.
Action:
Ensure the correct definition of the redefined field.
Reason:
The indexed sequential key field length exceeds 255 bytes. IBM logic imposes a limit of 255 bytes on the physical key of an ISAM file; longer keys cannot be written.
Action:
Check the specification of the key field length parameter and the total length of the fields in the KEY= clause.
Reason:
The FILE statement for ISAM file filename contains conflicting information; the specified key length parameter and the calculated total length of the fields in the KEY= clause differ.
Action:
Correct either the key length parameter or the KEY= clause.
Reason:
The FILE statement specifies a logical unit number (UNIT= ) for a disk file.
Action:
Remove the UNIT= parameter. The logical unit information for a disk file is supplied through the JCL.
Reason:
The FILE statement specifies an invalid logical unit number for a tape file. Syntax is: UNIT=SYSnnn, where nnn is in the range 001 to 240.
Action:
Specify a valid logical unit number.
Reason:
The FILE statement does not specify a record length with a RECORD= parameter. A record length is required for all file types except CARD files.
Action:
Specify a RECORD= value.
Reason:
The FILE statement specifies an invalid block length on the BLOCK= parameter.
Action:
Specify one of the following:
Reason:
Maximum length for a user module name is eight bytes; this name is the name of the user module phase on the core image library or load library, and IBM logic imposes an eight-byte length limit.
Action:
Shorten the module name to eight characters.
Reason:
Number contains more decimal digits than is allowed by its precision.
Action:
Ensure that the number of decimal digits agrees with the precision specification of the field.
Reason:
This message may be issued because:
Action:
Reduce the number of digits or alter the numeric value to agree with the given precision.
Reason:
The DEFINE statement specifies an invalid start or finish location for a file field.
Action:
Correct the field's start position, end position, or both in the DEFINE statement.
Reason:
The RECORD= parameter on the FILE statement specifies a record length of zero bytes.
Action:
Specify the record length with a valid, nonzero integer value.
Reason:
There is an invalid FILE statement for an indexed sequential file. A FILE statement must supply information relating to the key of the records.
Action:
Specify the length of the key in the key length parameter or supply a KEY= clause to name the key fields.
Reason:
The DEFINE statement is invalid at this point. The definition of a field in a record must follow a FILE statement.
Action:
Check the sequence of the source deck, and ensure that this DEFINE follows a valid FILE statement.
Reason:
Only one level of array is supported. The indicated definitions attempted to specify two or more levels of arrays.
Action:
Ensure that only a single level of array is specified.
Reason:
The specified data value is too large to fit within the defined precision of the receiving field.
Action:
Check the length of the data value against the implicit or explicit precision of the receiving field.
Reason:
A field specified on the KEY= parameter of a FILE statement is not contained within the record area for that file. Key fields must be defined within the record area for the specified file. They may not be defined in the working-storage area.
Action:
Specify the field within the record that contains the key.
Reason:
A precision clause has been specified for a field that has already been defined or predefined in CA Earl. A precision clause may only be specified on the statement containing the first reference to a field (either on a DEFINE statement, or implicitly as the result of a procedural statement).
Action:
Remove the precision clause from this statement.
Reason:
The assignment specified fields are of conflicting data types. Valid assignments are numeric (type N, P, U, or B) to numeric, or alphanumeric (type X or Q) to alphanumeric.
Action:
Specify only fields that are all numeric or all alphanumeric.
Reason:
The statement uses a field whose data type has not yet been specified. You are probably using a result field before specifying its precision and data type.
Action:
Specify the precision for the result field on the SET statement, or predefine the field using the DEFINE statement.
Reason:
Field headings and PICTUREs have been specified for a field that has already been defined. Field headings and PICTUREs may only be specified the first time a field is referenced (either explicitly through DEFINE or implicitly as the result field in a procedural statement).
Action:
Specify the headings or PICTURE on the first statement that defines this field.
Reason:
A bit string field is defined with a length other than one byte.
Action:
Correct and resubmit.
Reason:
This message indicates an error in the array definition. The start byte must be lower than the finish byte.
Action:
Correct the array specification and resubmit.
Reason:
A label has been defined twice. CA Earl expects label definitions to be unique.
Action:
Alter the label so that it is unique.
Reason:
The GET/PUT/RESET statement is not followed by a valid file name.
Action:
Check the syntax of the GET/PUT/RESET statement and ensure that:
Reason:
The GET statement has been issued to an output file. Only PUT statements can be issued to a file defined as OUTPUT, unless the file has been previously RESET.
Action:
Either remove the GET for your OUTPUT file or specify RESET prior to the GET statement in the program.
Reason:
The PUT statement has been issued to an input file; only GET statements may be issued.
Action:
Specify GET to read the input file or change the file statement to specify OUTPUT.
Reason:
An array index value has been specified for a field that was not defined as an array.
Action:
Check the definition of the indicated field; only array fields may be indexed.
Reason:
The indicated field is an array, but an array index value is not specified.
Action:
Specify an index value or check for a mis-typed field name.
Reason:
This message reflects a syntax difference between CA Earl Release 2 and Release 3.
Action:
Correct the GET statement.
Reason:
Any variable used as a host variable in an SQL SELECT statement must be explicitly defined.
Action:
Add a DEF statement for varname.
Reason:
The FILE statement for an output file specifies a KEY= clause. The KEY= clause applies only to input files; it must not be specified for output files.
Action:
Correct and resubmit.
Reason:
Too many statement labels have been specified. The current maximum number of labels is 256. Statement labels are allocated either directly by an CA Earl source program label or internally by a SELECT statement.
Action:
Reduce the complexity of the program or split the program into two programs.
Reason:
A label has been used in the CA Earl source program but has not been defined. All statement labels must be defined within the source program.
Action:
Correct and resubmit.
Reason:
The generated program is too large. This error message is printed adjacent to the source statement in the compile listing that causes the error condition. The position of the error message will provide a guide to the amount by which the presort program is too large for the operational environment.
Action:
Simplify the CA Earl program to reduce the number of executable statements.
Reason:
The allocated storage for field descriptions has been exceeded. Too many field names have been specified in this CA Earl program. This message is printed against the statement that caused the overflow. The positioning of this error message will provide a guide as to the amount by which the number of field names is too large for the operational environment available to the source program.
Action:
Remove DEFINE statements for fields that are not required during this run of CA Earl.
Reason:
The allocated storage (16 megabytes) for the General Storage Area (GSA) has been exceeded.
Action:
Check source program GSA definitions, especially array specification.
Reason:
An attempt has been made to assign a negative value to a one- or three-byte binary field. One- and three-byte binary fields are considered to contain unsigned positive numbers only. Only two- and four-byte binary fields can hold negative values.
Action:
Use a two- or four-byte field to hold the signed number.
Reason:
Indexed fields are fields that are not allowed in postsort processing.
Note: To allow the specification of indexed fields in postsort statements would require the whole array to be written to the hit file and sorted. This would cause considerable performance degradation; therefore, it is not allowed by the compiler.
Action:
Move the indexed variable to a non-indexed variable before the sort.
Reason:
The statement specifies a string of more than 26 tag characters. Valid tag characters are A to Z and the special character 0 (zero).
Action:
Remove the duplicate tag values.
Reason:
The tag character on a printed field has not been previously defined in a SELECT statement within this report. All tag characters used on PRINT statements, except for the special tag 0 (zero), must have been specified on a SELECT statement within the current report.
Action:
Correct and resubmit.
Reason:
The specified field has been positioned so that part or all of the field is outside the print line.
Action:
Ensure that:
Reason:
The print line field is spaced relative to a field that has not been specified on a previous print line in this report. The PRINT statement allows a field to be specified with @ (at sign) spacing, to indicate that this field is to be spaced relative to a field already printed in a previous print line in this report.
Action:
Refer to a field on a previous line or remove the at sign spacing.
Reason:
The specified field overlaps all or part of a previous field.
Action:
Position the field to the right of all previous fields.
Reason:
OPTION PRINTER specifies an invalid printer line length. Acceptable values are in the range 20 through 216.
Action:
Correct and resubmit.
Reason:
OPTION PAGE or OPTION CPAGE specifies an invalid page depth value. Acceptable values are in the range 1 through 16777215 (2 to the power of 24 - 1).
Action:
Correct and resubmit.
Reason:
OPTION WRITE ONLY specifies an invalid blocking factor.
Action:
Specify a valid blocking factor in the range 1 through 32767.
Reason:
More than 254 reports have been specified. CA Earl allows a maximum of 254 reports to be produced per run. It is recommended, however, that 100 reports per run be considered a practical upper limit.
Action:
Split the source deck so that each run specifies fewer reports.
Reason:
A PICTURE clause has been specified for a field of type X, Q (alphanumeric), or S (bit string). Editing can only be specified for numeric data items.
Action:
Remove the PICTURE clause from this definition.
Reason:
The specified PICTURE does not have the correct number of replaceable characters. The number of source digits in the field must equal the number of replaceable characters in the specified PICTURE.
Action:
Correct the PICTURE clause.
Reason:
The PRINT statement specifies accumulation for an alphanumeric field.
Action:
Remove the parentheses from the field name on the PRINT statement.
Reason:
OPTION OUTLIM specified an invalid output record limit. Acceptable values are in the range 1 to 16777215 (2 to the power of 24 - 1).
Action:
Correct OPTION OUTLIM.
Reason:
The number of heading and footing lines is too great for the page depth. The compiler calculates the number of print lines per page required to print the page headings, plus the specified TITLE and FOOT lines. If this total is more than the total number of lines on the page (either the specified OPTION PAGE= value or the installation default), there is no room available to print detail lines.
Action:
Set the OPTION PAGE= to a larger value or reduce the number of heading and footing lines.
Reason:
More than one USER statement has been specified for this run.
Action:
Remove the second USER statement.
Reason:
A field specified as a result field in a SET(D) or SET(T) statement has also been used as a result field in a presort statement (for example, DECODE or SET). A field used in a presort SET or DECODE statement cannot be specified as a postsort SET(D) or SET(T) result field. Fields to be used as postsort result fields may only be defined with a DEFINE statement presort, or they may be implicitly defined by the SET(D) or SET(T) statement.
Action:
Specify a separate postsort field as a result field.
Reason:
The DECODE statement contains more than 128 translation pairs.
Action:
Split the large DECODE into two or more small DECODEs, each with 128 or fewer pairs. Use IF logic to simplify translation.
Reason:
The field PAGENUMBER has been specified on a statement other than a REPORT statement.
Action:
Confine all references to PAGENUMBER to the REPORT statement.
Reason:
There was an attempt to print a field of data type S bit string. These fields cannot be printed, but can only be compared or used as selection criteria.
Action:
Correct the PRINT statement.
Reason:
The TOTALS ONLY clause of the PRINT statement was specified, but no accumulated fields or SET(T) result fields were printed.
Action:
Correct and resubmit.
Reason:
The literal specified on the REPORT statement is too long.
Action:
Shorten the literal or print on the next line with a TITLE clause.
Reason:
There was an attempt to print a field of data type VARIABLE.
Action:
Specify the correct data type or the component fields if there is a requirement to print.
Reason:
The value being assigned is negative.
Action:
Ensure that all values used with unsigned packed fields are positive.
Reason:
More than 500 PRINT statements have been entered.
Action:
Remove excessive PRINT statements.
Reason:
A user-supplied module has the same name as an identifier.
Action:
Change the name of the module or the identifier.
Reason:
No name was specified on the CALL statement.
Action:
Check the syntax of CALL statements; the module name must appear after the CALL keyword and before the USING keyword.
Reason:
The parameters passed to a user module on the CALL statement must be predefined; in this case, they are not.
Action:
Define the variables before coding the CALL statement.
Reason:
There are more parameters than the maximum number allowed.
Action:
Reduce the number of parameters to 255.
Reason:
The CA Earl compiler expected either NONE or an integer in the specified range. The default value is 30.
Action:
Correct the statement in error to specify a valid integer or NONE.
Reason:
Each IF statement must be paired with an ENDIF statement, and one ENDIF is missing.
Action:
Add the missing ENDIF or remove the extra IF.
Reason:
OUTPUT or UPDATE was specified as a parameter on the FILE statement, but CA Earl is generated to disallow these parameters (OUTPUT = NO or UPDATE = NO).
Action:
Remove these parameters from your FILE statement or regenerate CA Earl to allow them (OUTPUT = YES or UPDATE = YES).
Reason:
The predefined identifier CTRLBREAK has been specified as the result field in a SET or DECODE statement, but it cannot be reset.
Action:
Refer to CTRLBREAK only as a sending field in statements.
Reason:
A GET(D) or GET(T) refers to a CARD file. This is not supported.
Action:
Remove all postsort references to CARD files.
Reason:
A GET(D) or GET(T) refers to a database. This is not supported.
Action:
Remove all postsort references to a database.
Reason:
Your site is licensed only for the CA Common Services for z/OS CA Earl Reporting Service, which is supplied with many products to support CA Earl reports containing product-specific information. I/O for any other types of files is not supported by this component.
Action:
Refer only to the supplied user file modules on the FILE statement, or purchase the entire CA Earl product.
Reason:
The CA Earl Reporting Component only allows I/O through modules supplied with other products.
Action:
Remove the CALL statement.
Reason:
A PROC statement was found with no corresponding ENDPROC statement.
Action:
Code an ENDPROC following the last statement in the PROC.
Reason:
CA Earl requires a GOTO EOJ statement following an explicit GET.
Action:
Pair every explicit GET with a GOTO EOJ statement.
Reason:
You specified a font name that is not currently supported by CA Earl.
Action:
Correct the font name on the flagged statement or replace the hyphen with the required underscore.
Reason:
A font name on a PRINT statement is not suffixed by a (D) or (H).
Action:
If the font specified is for the field's data (detail), specify (D). If the font is for the column heading, specify (H).
Reason:
This is a catastrophic error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This is a catastrophic error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This is a catastrophic error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
You specified an invalid parameter or keyword on an OPTION statement.
Action:
Correct the OPTION statement.
Reason:
This is a catastrophic error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
An initial value was specified for a field that has been defined with a type of VARIABLE. The assignment of an initial value may only be made to a field whose type is X, N, P, U, or B.
Action:
Remove the initial value specification from this definition.
Reason:
This is a catastrophic error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The result field is not large enough to contain the largest theoretical result value. This could cause a runtime overflow in the result field, causing the field to print as asterisks (*).
Action:
Check for incorrect specification.
Reason:
In a logical expression, the value being compared is longer than the field to which it is being compared. The value is logically truncated to the length of the field being compared.
Action:
No action is required.
Reason:
The PRINT statement has spaced a field or literal where it would be overlaid by the GRAND TOTAL legend.
Action:
No action is required.
Reason:
The indicated statement cannot be executed because it is not labeled and therefore cannot be branched to.
Action:
No action is required.
Reason:
Sorting cannot be bypassed in a multiple-report run or when there is any postsort processing. When the CA Earl compiler determines that one of these cases exists, it automatically enables the sort and issues this message.
Action:
No action is required.
Reason:
The field defined has been created as a binary field in the working storage area. The specified precision is 1, 2, 3, or 4 bytes. The precision has been adjusted to allow for the maximum number of digit positions to be printed.
Action:
No action is required.
Reason:
The field defined has been created as a binary field in the working storage area. The specified precision is 1, 2, 3, or 4 bytes. The precision has been adjusted to allow for the maximum number of digit positions to be printed.
Action:
No action is required.
Reason:
The field defined has been created as a binary field in the working storage area. The specified precision is 1, 2, 3, or 4 bytes. The precision has been adjusted to allow for the maximum number of digit positions to be printed.
Action:
No action is required.
Reason:
The field defined has been created as a binary field in the working storage area. The specified precision is 1, 2, 3, or 4 bytes. The precision has been adjusted to allow for the maximum number of digit positions to be printed.
Action:
No action is required.
Reason:
The PRINT statement has spaced a field or literal where it would be overlaid by the control break legend.
Action:
No action is required.
Reason:
The receiving field does not have fewer decimals than the sending field, so no truncation takes place.
Action:
No action is required.
Reason:
PUNCH is not required for object decks that are to be link edited.
Action:
No action is required.
Reason:
You have coded OPTION SAVE=name and the module name has more than five characters. Only the first five characters will be used by CA Earl when generating module names for the SAVED program.
Action:
No action is required.
Reason:
With DLI, the GET statement is used to identify the segments to be retrieved. The program will usually fail if no explicit GET is coded.
Action:
Examine the source code carefully.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |