Text |
Field is a counter field. |
Explanation |
A super-, sub-, or phonetic-descriptor may not contain a counter field, e.g., a field which is marked as a counter field (PE-count = "C"). |
Action |
Correct the field name used. |
Text |
Filler may not be used. |
Explanation |
A SUPER-, SUB-, OR PHONETIC-DESCRIPTOR may not be defined out of a field with name "FILLER". |
Action |
Enter a valid field name. |
Text |
Length of superdescriptor > 126. |
Explanation |
The maximum length of a superdescriptor must be less than or equal to 126 characters, i.e., the sum of the length of all fields contained in a superdescriptor must not exceed 126. |
Action |
Correct length. |
Text |
Field is a sub-, super-, or phonetic-descriptor. |
Explanation |
No recursive description can be used for a super-, sub-, or phonetic-descriptor. |
Action |
Change SOURCE-FIELD of descriptor. |
Text |
Field not alphanumeric. |
Explanation |
The field was defined as a phonetic descriptor. The source field of a phonetic descriptor must always be alphanumeric. |
Action |
Enter a field which is alphanumeric. |
Text |
Specify only one field for subdescriptors. |
Explanation |
Only one field can be used to define a subdescriptor. A subdescriptor is a descriptor which contains a subfield of one Adabas field only. |
Action |
Enter only one field name. |
Text |
Specify only one field for phonetic descriptor. |
Explanation |
A phonetic descriptor contains one field only; this field must be alphanumeric. |
Action |
Enter only 1 field. |
Text |
Files found are not Adabas or VSAM files. |
Explanation |
The "related-fields/files-function" can only be executed for an Adabas-file or an Userview (file type "A" or "U"), for a VSAM file or its userview (file type "V" or "W") or for a LOGICAL VSAM file or its userview (file type "L" or "R"). |
Action |
Enter a valid file name. |
Text |
File entered is not a standard file. |
Explanation |
The function "standard file related field" refers to standard files (file type = "Z"). The file entered is not a standard file. |
Action |
Enter a standard file name or leave blank. |
Text |
Member not found. |
Explanation |
The Natural member cannot be found in the specified source library. |
Action |
Restart the punch-job with valid member and library names. |
Text |
Enter "Y", "N", or blank for ciphered. |
Explanation |
Ciphered flag can only be yes (Y) or no (N). Note that a blank means no. |
Action |
Enter a valid ciphered flag. |
Text |
No preprocessor abend data found. |
Explanation |
The preprocessor writes control records to the dictionary. Should the preprocessor abend for any reason, the active reference records must be deleted. This records can be deleted under the control of Predict. No control record was found in the dictionary with the specified search criteria. |
Action |
Enter valid search criteria. |
Text |
Invalid file-number (n001-n255). |
Explanation |
A file must be numbered with a number from 1 to 255. The first digit (n) may be used in Predict as an identifier which identifies the files. |
Action |
Enter a valid file number. |
Text |
Security level must be 0-15. |
Explanation |
The Adabas security level for access or update must be between 0 and 15; "0" means "not protected", and "15" gives the highest protection level. |
Action |
Enter a valid security level. |
Text |
Invalid file type. |
Explanation |
An invalid file type was entered. Valid file types are: A-Adabas file C-conceptual file I-ISAM L-logical VSAM file O-operating system file P-partitioned data set R-userview on VSAM file S-sequential data set U-user view on Adabas file V-user view on VSAM file W-user view on logical VSAM file Z-standard file |
Action |
Enter a valid file type. |
Text |
Member name already used. |
Explanation |
At generation time the user requested to store the generated code in a member which is already used for some other file. To prevent the user from overwriting code Predict issues this message and prompts the user to enter a new member and / or library name where the generated code is to be stored. |
Action |
Enter valid member and library names. |
Text |
Invalid record format. |
Explanation |
An invalid RECFM was specified. Valid RECFM"s are: F---fixed FB--fixed block V---variable VB--variable blocked VBS-variable blocked standard FBS-fixed block standard U---undefined |
Action |
Enter a valid RECFM. |
Text |
File number already exists. New file number assigned. |
Explanation |
During the load process of files Predict checks whether the file number of the file to be loaded is available. If the file number is already assigned to another file Predict seeks for the next free file number and assignes this one to the file to be loaded. |
Text |
Duplicate file number on input data set. |
Explanation |
If two master files were found on the input data set having the same number, this message is issued. To prevent inconsistencies the attribute "file type" of the second master file is changed to "conceptual". |
Text |
Table overflow. |
Explanation |
The function "LIST Adabas FIELDS USED BY PROGRAMS" is restricted
by the following conditions:
no more than 50 user views may be defined to one Adabas file
no more than 100 DDMs generated with prefixes are supported
no more than 100 fields with same Adabas short name are supported.
This message appears if mentioned limits are reached and the process
stops.
|
Text |
Natural specification only if language = "N". |
Explanation |
The specification of
Natural-program
Natural-library
Natural-file number
Natural-database number
is only allowed if the language = "N" is entered.
|
Action |
Enter language = "N". |
Text |
File number already exists. |
Explanation |
An attempt was made to add a file which number already exists in the dictionary. The first digit of the file number may be used to distinguish between files in different DATABASES. (Remember: in Predict the file numbers range from n001 to n255). |
Action |
Change the file number. |
Text |
User views can only be copied from file type A, U, V, R, L or W. |
Explanation |
An User view can only be created cia the COPY function from another User view or an Adabas or VSAM file. Valid file types are "A", "U", "V", "R", "L" or "W". |
Action |
Enter a valid file type. |
Text |
If language = "N" only Natural parameters allowed. |
Explanation |
If you specify language = "N" only
natural program
natural library
natural file number
natural database number
could be entered.
|
Action |
Enter only the natural parameters. |
Text |
File does not exist. |
Explanation |
If you want to display the elements which are used and not defined the entered file must exist. |
Action |
Enter a existing file. |
Text |
Member- and library name must be specified. |
Explanation |
In this function of the subsystem "Maintenance generated code" the Member- and library name must be specified. |
Action |
Enter Member- and/or library name. |
Text |
Unknown programming language. |
Explanation |
An invalid language was entered during program or module
addition or modification. Valid languages are:
B---BAL(assembler)
C---COBOL
P---PL/1
N---Natural (only for a program entry)
" "--(blank) other
|
Action |
Enter a valid language. |
Text |
Only "B", "O" or blank allowed. |
Explanation |
The mode can only be O (online) or B (batch). |
Action |
Enter a valid mode. |
Text |
The related Adabas field does not exist. |
Explanation |
An attempt was made to reference an Adabas field that does not exist in the related Adabas file. |
Action |
Enter a valid Field ID or leave blank. |
Text |
File is not an Adabas file. |
Explanation |
The related Adabas file must be a file of file type "A". |
Action |
Enter a valid File ID or leave blank. |
Text |
A filler may be used in REDEFINEs only. |
Explanation |
Predict recognizes the field type filler, but it may only be specified in a REDEFINE. It is not possible to define fillers for basic fields. |
Action |
Do not use fillers when defining basic (real) fields. |
Text |
Only "C", "I", and blank are valid types. |
Explanation |
For a relationship entry, the type may only be C (coupled in Adabas), I (implicit) or blank (implicit). |
Action |
Enter a valid type. |
Text |
File 1 or 2 missing. |
Explanation |
A relationship can only be established between 2 files: enter a file name. |
Action |
Enter a file name. |
Text |
Purge for automatic rule not allowed. |
Explanation |
Before a automatic rule can be purged, all connections to the fields must be released and the DDM"s of the corresponding files must be regenerated. If no connection between verification and field is active, the status will be changed to conceptual. Then the rule can be purged. |
Action |
Release connection between verification and fields and regenerate DDM"s of corresponding files. |
Text |
Relation field 1 or 2 does not exist. |
Explanation |
A relationship can only be established between 2 fields within 2 different files. If the file exists, the field must exist in the file, too. |
Action |
Enter a valid relationship field. |
Text |
In BATCH needed countersignatures not possible. |
Explanation |
You are authorized to modify this file, but you need a countersignature. This is in Batch not possible. |
Action |
Generate DDM online. |
Text |
Field 1 or 2 missing. |
Explanation |
A relationship can only be established between 2 fields: Enter a field name. |
Action |
Enter a relationship field. |
Text |
File is not a predict file. |
Explanation |
The specified file is not a predict file. |
Action |
Enter the correct filenumber. |
Text |
Formatbuffer for input file is empty. |
Explanation |
At generation ADACMP definitions an input file id was entered. This file should describe the input data for the ADACMP utility, but no formatbuffer was generated. |
Action |
Check input file for corresponding fields to the Adabas file. |
Text |
Usage must be "ACC" or "UPD". |
Explanation |
The usage of a user can only be ACC (access only) or UPD (update). |
Action |
Enter a valid usage code. |
Text |
Invalid verification type. |
Explanation |
The verification type can only be:
R-range
E-equal
L-less
G-greater
U-user routine
T-table
|
Action |
Enter a valid verification type. |
Text |
Type = blank required for REDEFINE group. |
Explanation |
The field-type of a REDEFINE member must be BLANK. |
Action |
Enter a blank. |
Text |
Standard field name is... |
Explanation |
The field referenced is a standard field. i.e. the field name cannot be changed. By using the RENAME function, the name of the standard field can be changed and now all related field names are rippled. |
Action |
Either do not change the field name or use the RENAME function. |
Text |
Formats "I" and "F" require option "FI". |
Explanation |
By Adabas definition, an integer field requires the option "FI". The same is true for a floating point field. |
Action |
Enter option "FI". |
Text |
No Adabas name allowed for REDEFINITIONS. |
Explanation |
A member of a REDEFINE group may not contain an Adabas name. |
Action |
Delete Adabas short name. |
Text |
Length of descriptor is greater than 126. |
Explanation |
By Adabas definition, the maximum length for a descriptor field is 126 bytes. |
Action |
Either make the field length less than or equal to 126, or do not flag it as a descriptor. |
Text |
New user id assigned. |
Explanation |
During the loading of Predict version 1 data this message will be sent because the concept of users has changed in Predict version 2 and a new userid is assigned to the user entry. |
Text |
Binary length > 126 not allowed. |
Explanation |
By Adabas definition, the maximum length of a binary field cannot exceed 126. |
Action |
Enter a length less than or equal to 126. |
Text |
Adabas field is not a descriptor. |
Explanation |
The related field in the Adabas file is not defined as a descriptor. |
Action |
Do not enter the descriptor option. |