Text |
Line subcommand is outside of source lines. |
Explanation |
The line subcommand entered is outside of the source lines. |
Action |
Commands may not be entered outside of the source lines. |
Text |
Line command '.M' without 'X' or 'Y' found. |
Explanation |
This command tells you that the editor recognized the line
command '.M' but is missing 'X', 'Y' or 'X-Y'. The line command
'.M' has three valid forms, namely
.MX
.MY
.MX-Y
All other forms are flagged as invalid. |
Action |
Enter one of the three commands mentioned above when you want to move data. |
Text |
No line marked 'X'. |
Explanation |
An edit command referring to a line marked with 'X' was entered without any line being so marked. |
Action |
Mark the desired line with 'X'. |
Text |
No line marked 'Y'. |
Explanation |
An edit command referring to a line marked with 'Y' was entered without any line being so marked. |
Action |
Mark the desired line with 'Y'. |
Text |
Y-position not behind X-position. |
Explanation |
A line command was entered with two marked lines involved. The line marked with 'X' is behind the one marked with 'Y'. |
Action |
Reverse the order of the marks. |
Text |
Copied/moved lines overlap target line. |
Explanation |
An attempt was made to copy source lines into an area between the source lines. |
Action |
Do not enter a line command between the lines marked 'X' and 'Y'. |
Text |
'.J' entered in last line. |
Explanation |
The '.J' line command (JOIN) can not be entered in the last line. |
Text |
An invalid edit command was entered. |
Explanation |
An invalid edit command was entered. Valid commands are explained in the help screen. |
Action |
Enter a valid command or '?' for help. |
Text |
Do not replace to same data. |
Explanation |
Do not scan for data and replace it with same data. |
Action |
Enter different scan and replace strings. |
Text |
All objects from work file 1 loaded. |
Explanation |
All Predict objects,which are on the work file 1, are loaded by the MIGRATE utility. |
Text |
Missing DDNAME for VSAM file. |
Explanation |
To generate a DDM for a VSAM file a DDNAME must be supplied. |
Action |
Add the DDNAME to the file definition in Predict. |
Text |
Rule of mode 'REPORT' may not be generated. |
Explanation |
The mode is set to 'STRUCT' (SM=ON) and it is not permitted to change to 'REPORT' mode. |
Action |
Contact your DDA. |
Text |
Editing terminated. |
Explanation |
The edit session was terminated due to a user-issued edit command. No update was performed. |
Text |
No Adabas short name available. |
Explanation |
The generation of Adabas short names terminated abnormally, because no more Adabas short names available. |
Action |
Reduce fields of file. |
Text |
Standard file updated. |
Explanation |
The standard file has been updated. All elements which are connected to the standard file were updated too (RIPPLING process.) |
Text |
All fields already in standard file. |
Explanation |
You have tried to execute the PUSH BACKWARD function using a file whose fields are already linked to another standard file. No field has been copied to the standard file, because one field can only be linked to one standard file. |
Text |
Invalid program type. |
Explanation |
Allowed program types are:
'F' Fetch program
'M' Map
'N' Call Subroutine
'S' Perform Subroutine |
Action |
Correct program type. |
Text |
Source field for sub-/super-/phon- descriptor missing. |
Explanation |
During DDM generation an error occured. Either a super descriptor with no source field was found or a source field for a super descriptor was not found in the file. Therefore the generation of the DDM has been aborted. |
Action |
Check file and correct error. |
Text |
Do not misuse 'change' command. |
Explanation |
This powerful edit command allows you to change a character string or to replace it with a null value, but not both at the same time. |
Action |
Either replace with a null value or with a new string. |
Text |
No RENAME function for standard fields. |
Explanation |
Standard fields may not be renamed. |
Action |
Do not RENAME a standard field. |
Text |
File is locked by user. |
Explanation |
If the function RENAME or RENUMBER a file terminates abnormally, the file is not released from the locked status. |
Action |
Start the RECOVERY function of Predict. |
Text |
Cursor outside source line. |
Explanation |
When using the '.S' line command a test is made if the cursors position is in the source line. If not, this message is issued. |
Action |
When splitting a line, position the cursor to the split point of the source line. |
Text |
Input-file is locked by user. |
Explanation |
The file, which describes the input data of the ADACMP utility, is lock by the listed user. |
Action |
Use the Predict RECOVERY function to release the file. |
Text |
Do not modify deleted lines. |
Explanation |
In the editor you may delete some fields. These fields remain on the screen, marked as deleted. You may not modify those fields. |
Action |
Do not modify deleted fields. |
Text |
Second 'REDEFINE' on wrong level. |
Explanation |
The additional 'REDEFINE' with the field name 'FILLER' has not the same level as the basic field. |
Action |
Correct error. |
Text |
Maintain AUTOMATIC or FREE RULE with Natural V2 only. |
Explanation |
Rules with status 'AUTOMATIC' or 'FREE' are features of Natural V2 and they can only maintained in a Natural V2 environment. |
Action |
Use Natural V2. |
Text |
No 'SCRATCH' in Natural Security. |
Explanation |
If Natural Security is active, only the function 'PURGE DATABASE' is possible. The connected files of the database must be explicitly deleted. |
Action |
Enter PURGE for function code. |
Text |
Command .J may not be used in first line of screen. |
Explanation |
The command .J joins the current line with the line immediately preceding it. Since no preceding line exists in this case, the command is not executable. |
Action |
Do not enter command .J in the first line. |
Text |
Position the cursor to the split point. |
Explanation |
In order to split a line, the cursor must be positioned to the split point. Hit ENTER to split the line. |
Action |
Position the cursor to the split point and hit ENTER. |
Text |
No shift direction specified (+NN,-NN). |
Explanation |
The edit command shift requires one parameter, the direction. This parameter is a signed number which may be omitted; in this case the default value '+3' is assumed. |
Action |
Enter a shift parameter (+NN, or -NN). |
Text |
Invalid parameter in line command. |
Explanation |
Some line commands may have parameter. For example, the line command '.C(NNN)' will copy a line 'NNN' times; however the line command '.C(0)' means 'copy this line zero times' , which makes no sense. Therefore the message above is issued. |
Action |
Enter a valid parameter for line command. |
Text |
X-line must be on the screen for shift. |
Explanation |
To shift a text, it is required that the X-line be on the screen. After the text has been shifted, part of the text should be seen on the screen. |
Action |
Position to the X-line by entering .X in the command line. |
Text |
DDM does not exist. |
Explanation |
DDM specified does not exist; no incorporation can be performed. Either the DDM does not exist or it is cataloged in another Natural system file. |
Action |
Enter a valid DDM. Ensure that the correct Natural system file has been specified. |
Text |
Objects loaded completely. |
Explanation |
The objects have been loaded into the dictionary. |
Text |
No Object from work file 1 loaded. |
Explanation |
No object on the input file (Natural work file 1) has been loaded. Possibly the search criteria did not match to any object on the input file or the input file is empty. |
Action |
Verify the load criteria. |
Text |
Unkown object-type in group on work file 1. |
Explanation |
Each group of objects on the work file is preceeded by a control record. If this control record was not found, this error message has been issued. |
Action |
Check that the correct control records are written to the sequential file. |
Text |
All objects from work file 1 loaded. |
Explanation |
This message indicates that all objects have been loaded successfully. |
Text |
Name + Prefix + Suffix > 32 Characters. |
Explanation |
The new name of the object has been truncated to 32 characters because the resulting name, the concatenation of name prefix and suffix, was too long. |
Action |
Do not use such a large prefix and/or suffix. |
Text |
Warning: no owner loaded. |
Explanation |
The DDA has set the owner switch to 'force'. The loaded object must have some owner attributes, but it did not. This message is only a warning. |
Action |
Please add the required owners to the object. |
Text |
No description for the object was found. |
Explanation |
For the specified object no description exists. |
Action |
Add later the required description to the object. |
Text |
Object already exists. |
Explanation |
An object with the same object-id exists. |
Action |
Check the object id and correct error. |
Text |
No available file number found. |
Explanation |
An attempt was made to define more than 10 files with the same Adabas file number. The Predict file number is a four-digit number, i.e. a number of the form N001 through N255. The first digit of the Predict file number 'N', is used to distinguish between files. The last three digits specify the Adabas file number. |
Action |
Check whether all files are necessary; delete nonessential files. |
Text |
DDM incorporated successfully. |
Explanation |
A DDM not generated by Predict has been incorporated into the dictionary. |
Text |
File buffer too small. |
Explanation |
The file buffer must be large enough to incorporate a DDM. Since the buffer was too small, the DDM was not incorporated. The file buffer size is specified in the dynamic parameter FSIZE. |
Action |
Increase the size of the file buffer. |
Text |
No Object Loaded. |
Explanation |
There was no object qualified. |
Action |
Check program and correct error |
Text |
Object Loaded. |
Explanation |
The object is successfully loaded. |
Text |
Invalid record found. |
Explanation |
The record, which was read, is invalid, e.g. the length was wrong. |
Action |
Generate correct records. If the input file was generated by the unload function of MIGRATE utility contact SAG. |
Text |
File number must be entered. |
Explanation |
In order to incorporate an FDT, a file number is required to establish the relationship between the FDT and the file. |
Action |
Enter a valid file number. |
Text |
Warning: KEYWORD not defined. |
Explanation |
The Predict data are checked during loading. if at that moment no key exists a warning will be send. The KEYWORDs belonging to this data set could be laoded later. |
Action |
Check the keys after all data loaded. |
Text |
Warning: OWNER not defined. |
Explanation |
During load of Predict data it will be checked that the OWNERS of the loaded object are defined. This message is a warning. Possibly the OWNER records will be loaded afterwards. They must belong to the same data set. |
Action |
Check the data after all records are loaded. |