Text |
The file number must be in the range 1 - 5000. |
Explanation |
The database file number must be in the range from 1 to 5000. |
Action |
Enter correct file number. |
Text |
First character of file name must be alphabetical. |
Explanation |
A valid file name must begin with an alphabetical character, and may be constructed according to the rules for variable names (as described in the section on user-defined variables in the Natural documentation). |
Action |
Enter correct file name. |
Text |
A file name must be specified. |
Explanation |
For the CATALOG function, which requires a file name, no file name was specified. |
Action |
Enter a valid file name. |
Text |
Level must be higher than previous level. |
Action |
Check and correct the level. |
Text |
Invalid characters in file name. |
Explanation |
A file name must be constructed according to the rules for variable names (see the section on user-defined variables in the Natural documentation). |
Action |
Enter a correct file name. |
Text |
Invalid name for the 'default sequence' field. |
Explanation |
An invalid name was specified for the default sequence descriptor. The default descriptor must be specified as the 2-character short name of a field which must exist as a descriptor in the global database file definition. |
Action |
Enter correct name for default sequence descriptor. |
Text |
Invalid database field name for coupling field. |
Explanation |
The field name specified for the coupling relation must be specified as a 2-character short name and must begin with an alphabetical character. The field to be used for the coupling relation must exist in the global database file definition. |
Action |
Enter correct name for coupling field. |
Text |
Invalid field name for coupling field (columns S + D). |
Explanation |
The name for the coupling field must be specified as a 2-character database field name beginning with an alphabetical character and must exist in the global file definition. The value for the coupling field name must be entered in the columns with headings S and D (one character each). |
Action |
Enter correct coupling field name. |
Text |
Coupled file number not numeric. |
Explanation |
The identification of the coupled file must be entered as the file number in the database. The identification must be a valid file number in the range from 1 to 255. It must be entered in the field with heading 'LENG'. |
Action |
Enter correct coupling file number. |
Text |
Occurrence value must be 1-999. |
Explanation |
The specified value for the occurrence is not correct. Only values in the range from 1 to 999 are allowed for a periodic group or multiple-value field. |
Action |
Enter correct value for occurrence. |
Text |
Database short field name must be specified (column DB). |
Explanation |
The specification of a field requires a database short field name. The short field name must be 2 characters long and begin with an alphabetical character. |
Action |
Enter correct field short name. |
Text |
Field long name must be specified (column NAME). |
Explanation |
The specification of a field requires a long name to be specified for a field. The long name must begin with an alphabetical character and must be constructed according to the rules for variable names (see the section on user-defined variables in the Natural documentation). |
Action |
Enter valid long field name. |
Text |
First character of field long name must be alphabetical. |
Explanation |
The first character of a field's long name must be alphabetical. |
Action |
Enter a valid long name for the field. |
Text |
Field format (column F) must be A,B,U,I,N,P,F,D,T or L. |
Explanation |
Only one of the following formats may be specified for a database field: A - alphanumeric B - binary U - unicode I - integer N - numeric unpacked P - packed numeric F - floating point D - date T - time L - logical |
Action |
Enter a valid format. |
Text |
Alpha field length must be 1-253 or LA/LB option must be set. |
Explanation |
Fixed-length alphanumeric fields can only have a length of up to 253 characters. A variable-length field may be defined as DYNAMIC by setting the format option LA or LB. Use the .E line command to enter a format option. |
Action |
Enter a valid field length or set LA/LB format option. |
Text |
The length of a numeric field must be 1 - 29. |
Explanation |
The maximum length for a numeric field is 29 digits. The length for a numeric field is always specified in digits. |
Action |
Enter valid numeric length. |
Text |
VSAM descriptor can only be 'P','S','A','X' or blank. |
Explanation |
A character other than 'P', 'S', 'A', 'X' or blank has been specified to mark a field as a descriptor field. |
Action |
Enter correct character (P, S, A, X or blank). |
Text |
Specification of field length must be numeric. |
Explanation |
The specification for the field length must be numeric in the form 'nn.m', where 'nn' represents the digits before and 'm' the digits after the decimal character. |
Action |
Enter correct length. |
Text |
Field long name must consist of at least 3 characters. |
Explanation |
The long name for a field must consist of 3 or more characters. |
Action |
Enter valid field long name. |
Text |
Invalid characters in long name. |
Explanation |
Long field names must be constructed according to the rules for variable names and must begin with an alphabetical character (see the section on user-defined variables in the Natural documentation). |
Action |
Enter valid field long name. |
Text |
Invalid database short name (column DB). |
Explanation |
The field short name must have 2 characters and must begin with an alphabetical character. The field short name must not be 'E0' to 'E9'. |
Action |
Enter valid database short name. |
Text |
Length of a binary field must be 1 - 126. |
Explanation |
Binary fields can only have a length between 1 and 126. |
Action |
Correct the length value of the field. |
Text |
Field type (column T) must be '*', 'P', 'G', 'M', blank. |
Explanation |
Valid field types to be specified in column T are: * - comment line P - periodic group G - group of fields M - multiple-value field ' ' - elementary field |
Action |
Enter valid field type. |
Text |
Special options or descriptor entered for group. |
Explanation |
For a field group, no special options or 'D' (for descriptor) can be specified. Special options must be specified for the individual fields. |
Action |
Do not enter special options for field groups. |
Text |
Invalid level. Level must be 1 - 7. |
Explanation |
Field levels can only be 1 - 7. |
Action |
Enter valid level number. |
Text |
Periodic group within periodic group is not allowed. |
Explanation |
Periodic groups cannot be nested; i.e., a periodic group must not contain another periodic group. |
Action |
Check program and correct error. |
Text |
Edit mask must not be specified for a group. |
Explanation |
No edit mask specification is allowed for a field (periodic) group. Edit masks can only be specified for individual fields. |
Action |
Check program and correct error. |
Text |
Format must not be specified for a group. |
Explanation |
For a group, no format can be specified. Formats can only be specified for individual fields. |
Action |
Check program and correct error. |
Text |
Length must not be specified for a group. |
Explanation |
For a field group, no length can be specified. Field lengths may only be specified for individual fields. |
Action |
Check program and correct error. |
Text |
Special option (column S) must be 'N', 'F', or blank. |
Explanation |
Valid special options are: N - null-value suppression F - fixed field length ' ' - normal |
Action |
Enter valid special option. |
Text |
Coupled file entries must be specified at start of DDM. |
Explanation |
Coupled file entries must be specified at the start of the DDM. |
Action |
Enter the coupled file entries at the start of the DDM. |
Text |
Alternate index missing for VSAM, ISAM or LEASY. |
Explanation |
If the descriptor is 'A', an alternate index must be specified. |
Action |
Enter the alternate index. |
Text |
Occurrence must be greater than '1'. |
Explanation |
For a periodic group or a multiple-value field, only an occurrence greater than '1' is permitted. |
Action |
Enter correct value for the occurrence. |
Text |
Multiple-value field within periodic group not allowed. |
Explanation |
In VSAM processing, a periodic group must not contain a multiple-value field. |
Action |
Change the field in the DDM. |
Text |
Multiple-value field cannot be a descriptor. |
Explanation |
For VSAM processing, a multiple-value field cannot be a descriptor. |
Action |
Change the field type, or remove the descriptor indication. |
Text |
Occurrence missing for periodic group. |
Explanation |
In VSAM processing, an occurrence greater than '1' must be specified for a periodic group. |
Action |
Enter the correct occurrence. |
Text |
Alternate index not allowed for group or periodic group. |
Explanation |
In VSAM processing, an alternate index is not allowed for a group or a periodic group. |
Action |
Change type of field, or do not specify an alternate index. |
Text |
Coupled file entry not allowed. |
Explanation |
In VSAM processing, coupled file entries in the DDM are not allowed. |
Action |
Remove the coupled file entries. |
Text |
Illegal characters in alternate index file name. |
Explanation |
The correct syntax for the alternate index file name requires that the first character be alphanumeric; the following characters may either be alphanumeric or numeric. |
Action |
Enter correct file name. |
Text |
DBID numbers must exclude one another. |
Explanation |
When copying files, the database identifications (DBIDs) of the files must be different from one another. |
Action |
Enter correct DBID. |
Text |
Primary key has been defined twice. |
Explanation |
In VSAM processing, only one field may be specified as primary key. |
Action |
Define only one primary key. |
Text |
Type must be blank. |
Explanation |
In VSAM processing, the type of the field where the primary key is specified must be specified with a blank character. |
Action |
Change type to a blank character. |
Text |
Primary key has not been specified. |
Explanation |
In VSAM processing, one primary key must be specified in the DDM. |
Action |
Enter one primary key field. |
Text |
Duplicate name in DDM not possible. |
Explanation |
There is a name in the DDM which is specified twice. |
Action |
Change the name which is specified twice. |
Text |
The CICS file name is missing. |
Explanation |
The CICS file name in the definition of the file entry is missing. |
Action |
Enter the CICS file name. |
Text |
Only 'Y' or 'N' may be entered in this field. |
Explanation |
In this field, you may only enter 'Y' (for YES) or 'N' (for NO). |
Action |
Enter 'Y' or 'N'. |
Text |
Periodic group is not in FDT. |
Explanation |
There is a periodic group specified in the DDM which does not appear in the corresponding Field Description Table (FDT). |
Action |
Check DDM for the specified periodic group. |
Text |
Use unique key flag/null flag only for VSAM upgrade. |
Explanation |
The unique key flag and the null flag can only be specified if the upgrade flag has been signed. This is only meaningful if the field has an alternate index. |
Action |
Specify correct combination of flags. |
Text |
Invalid format or length. |
Explanation |
Only the following format/length combinations are valid: - INTEGER (I4) - FLOAT (F4/F8) - DATE - TIME - LOGICAL (L1). |
Action |
Check DDM and correct error. |
Text |
Invalid character in descriptor option. |
Explanation |
In column D, only the following values are allowed: D - descriptor S - subdescriptor or superdescriptor P - phonetic descriptor ' ' - not a descriptor and for VSAM files: P - primary index A - alternate index |
Action |
Enter valid descriptor option. |