Text |
PE-count must be blank or 'C'. |
Explanation |
If 'C' is entered, a PE-count field is specified; a blank means that the field is not a counter field. This field-type is used by COBOL, ASM or PL/1 and it contains the number of occurrences of the respective PE-group or MU-field. |
Action |
Enter blank or 'C'. |
Text |
Too many parameters. Retry. |
Explanation |
More than five commands / parameters have been entered in the editor command line at once. |
Action |
Do not enter more than five commands / parameters at once. |
Text |
The nonstandard flag can only be blank or 'N'. |
Explanation |
The nonstandard flag defines whether the field is a standard field (flag = ' ') or a nonstandard field (flag = 'N'). |
Action |
Enter 'N' or leave blank. |
Text |
Field in standard file may not be marked as nonstandard. |
Explanation |
If you mark a standard field as nostandard this message will be sent. |
Action |
Enter the standard option. |
Text |
Occurrences for multiple value field exceed 191. |
Explanation |
By Adabas definition, the number of occurrences must not exceed 191. |
Action |
Enter a number less than 192. |
Text |
Occurrences for periodic group exceed 99. |
Explanation |
By Adabas definition, the number of occurrences for a periodic group must not exceed 99. |
Action |
Enter a number less than 100. |
Text |
Field not found in the file. |
Explanation |
The field specified does not belong to the file. This message is a warning. The field entered belongs to a group or to a REDEFINE. It is not a real Adabas field. |
Action |
Enter a valid field name. |
Text |
Field not of type 'PE' or 'MU'. |
Explanation |
If the PE-count of a field is flagged with a 'C', a second field must be defined as PE- or MU-field with the same Adabas short name or the field must be of type PE or MU. |
Action |
Correct error. |
Text |
Invalid line command found. |
Explanation |
During the edit session an unknown line command has been entered. The valid line commands of each editor are documented in the help screens. |
Action |
Enter valid line commands. |
Text |
SP/SB/PH Adabas files descriptors must be defined on level 1. |
Explanation |
Super-, sub- or phonetic-descriptors must always be defined on level 1 in an Adabas file. Other levels are invalid. |
Action |
Enter level 1. |
Text |
Adabas name already exists. |
Explanation |
The entered Adabas name is already in use. The Adabas short name within the file must be unique. |
Action |
Enter an unique Adabas short name. |
Text |
Format/length option not allowed for group. |
Explanation |
For groups, the attributes describing format, length, or suppression options are not allowed. |
Action |
Leave these fields blank. |
Text |
Descriptor option not allowed for any group. |
Explanation |
A group cannot be declared as descriptor. |
Action |
Leave the field blank. |
Text |
Adabas Short name cannot be changed. |
Explanation |
After a short name has been defined, it cannot be changed. The short names are used by Adabas and may belong to several files (i.e., master file and Userviews). |
Action |
Do not alter the short name. |
Text |
Related VSAM file already exists. |
Explanation |
The specified new related VSAM file number already exists. |
Action |
Enter another related VSAM file number. |
Text |
Option must not differ from Adabas-option. |
Explanation |
The suppression option entered in the Userview differs from the option entered in the MASTER Adabas FILE. |
Action |
Enter the same option as the Adabas-option. |
Text |
Field type must be equal to the field type in the Adabas file. |
Explanation |
The field type entered for the Userview is not the same as defined in the master Adabas file. |
Action |
Enter the same field type as in the Adabas file. |
Text |
Scan value too long or delimiter missing. |
Explanation |
The 'SCAN' command expects a scan value which is not larger than 32 characters or a scan value which is embedded in special characters. The most probable reason for this error is that the scan value begins or ends with a special character. In this case you should enter a scan value which is embedded in delimiter characters. |
Action |
Enter a valid scan value. |
Text |
Verification not defined. |
Explanation |
The entered verification-id is not defined in Predict. |
Action |
Enter a valid verification. |
Text |
You are not authorized to execute this function. |
Explanation |
If Natural Security is active, it is possible that you are not
authorized to execute one of the following functions.
Add security
Purge file
Use SUPER Natural
Generation of DDM
Incorporation DDM |
Action |
Contact your DDA. |
Text |
DDM of Physical / Logical VSAM file not yet generated. |
Explanation |
Before you may generate DDMs of user views on VSAM files you must generate the DDM of the master VSAM file. |
Action |
Generate the DDM of the master VSAM file. |
Text |
Physical / Logical VSAM file does not exist. |
Explanation |
The specified file of type 'R' (userview of logical VSAM file) has no related Logical VSAM file or the specified file of type 'L' or 'W' (logical VSAM file or userview of a VSAM file) has no related physical VSAM file. |
Action |
Check file name. |
Text |
Physical VSAM DDM must be regenerated. |
Explanation |
If you want to generate a VSAM DDM for a userview or a logical file and the physical VSAM file has been modified, this message will be sent. |
Action |
Generate first the DDM for the physical file. |
Text |
LOGICAL VSAM DDM must be regenerated. |
Explanation |
If you want to generate a DDM of a user view of a LOGICAL VSAM FILE and the LOGICAL VSAM FILE was modified, this message will be send. |
Action |
Generate the DDM of the LOGICAL VSAM FILE again. |
Text |
DDM is not an Adabas DDM. |
Explanation |
If you tried to incorporate a non Adabas DDM with the function incorporate DDM, this message will be sent. If the DDM is of type VSAM, use the function incorporate VSAM DDM . |
Action |
Check type of DDM. |
Text |
Type = application required if lib is specified. |
Explanation |
If the library is specified, the type = application is required. |
Action |
Set type to application |
Text |
For DBID, FNR: only '*', ' ' or number allowed. |
Explanation |
The specified DBID or FNR contains an invalid character. |
Action |
Enter valid value. |
Text |
Improper combination of dbid, fnr, lib and map |
Explanation |
The specified search criteria is not allowed. Please look at the help screens for the allowed combinations. |
Action |
Enter valid combination of dbid, fnr, lib and map. |
Text |
Field without field name found. |
Explanation |
Predict encountered a field definition without a field name. This message is a warning. The record for this field was not unloaded. |
Action |
Please added the elements of the file containing this field and enter a valid field name before unloading this file again. |
Text |
DDMs compared. |
Explanation |
The Predict Adabas FILE or User view are compared with the generated Natural DDM. |
Text |
All DDMs documented in Predict. |
Explanation |
This message tells you that all DDMs on the Natural system file are documented in the dictionary and the generation log coincides with the data. |
Action |
None. |
Text |
Invalid validation character. |
Explanation |
The entered validation character is invalid for this language. Look at the help screen for the valid characters. |
Action |
Enter a valid validation character. |
Text |
File can only be purged. |
Explanation |
After the copy or load of a file this message occurs. Please delete the file and restart the function. |
Action |
Delete the file. |
Text |
Validation characters are.... |
Explanation |
The possible validation characters are
'̲' , '*' , ' ' and 'A' thru '9' for PL/1
'-' , '*' , ' ' and 'A' thru '9' for COBOL |
Action |
Enter one of the validation characters shown before. |
Text |
Error in editor. Response code received. |
Explanation |
While manipulating data in the source area ( the buffer used by the editor ) an error occured. This error is not recoverable and therefore the execution of the currently active program is stopped. |
Action |
Document the response code and contact Software AG Technical Support. |
Text |
Source Area exhausted. |
Explanation |
Some functions of Predict write into the editor buffer in order to store there intermediate results. If this buffer is not large enough to hold all data, this message is issued and the execution of the currently active program is stopped. The size of this buffer is determined by the dynamic parameter ESIZE. |
Action |
Start a new Natural session with a larger ESIZE. |
Text |
All used files or fields defined. |
Explanation |
No file/field is displayed because all used files/fields (active references are existing) are defined. |
Text |
No field used. |
Explanation |
No field displayed because no field is used. |
Text |
Implementation pointer already exists. |
Explanation |
The specified implementation pointer consisting of
- program-name
- library
- fnr
- dbid
already exists. If you want a unique implementation pointer
you must change the specified values. |
Action |
Check the specified implementation pointer and correct it. |
Text |
All SUPER Natural files defined in Predict. |
Explanation |
All existing SUPER Natural files are defined in Predict. |
Text |
Description must be added. |
Explanation |
The extended description must be added, if the general system default parameter (DDA services) of the extended description is set. |
Action |
Add description. |
Text |
Description can not be purged. |
Explanation |
If the general system default parameter of the extended description is set to 'FORCE', no deletion of the description is possible. |
Action |
Change general system default parameter if necessary. |
Text |
At least three lines must be entered. |
Explanation |
If the general system default parameter for the extended description (DDA services) is set, at least 3 lines must be added. |
Action |
Add 3 lines or change system default parameter. |
Text |
At least one owner must be added. |
Explanation |
If the general system parameter 'EDIT OWNER' (via DDA services) is set, at least one owner must be added. |
Action |
Add one owner or change system default parameter. |
Text |
Owner list must be cataloged. |
Explanation |
The added owner list must be confirmed through a CATALOG command. |
Action |
Enter CATALOG or SAVE. |
Text |
Owner has no users. |
Explanation |
The general system parameter 'Edit Owners of an object' is set to 'FORCE'. In this case you must link via the editor at least one owner to the DD object. For every owner linked to the DD object at least one user has to be linked to the owner, too. |
Action |
Enter only owners which have users defined. |
Text |
Owner id / user name not unique, user id missing. |
Explanation |
Predict requires that the userid,which should be maintained, is unique. |
Action |
Enter a user id. You may use the select function to determine the correct user id. |
Text |
No SUPER Natural file. |
Explanation |
The specified file is not a SUPER Natural file. |
Action |
Check the specified file. |
Text |
File is not a Natural file. |
Explanation |
The specified file is not a Natural file. |
Action |
Check the entered file. |
Text |
Object cross-reference displayed. |
Explanation |
The cross-reference of the requested objects has been displayed. |