Text |
The disc must be formatted and must not be write-protected. |
Explanation |
The disc in the drive is either unformatted, or formatted but write-protected. |
Action |
Use another disc which is formatted and not write-protected. |
Text |
The specified path does not exist. |
Explanation |
The path must exist in the environment for correct processing. |
Action |
Specify a path that exists. |
Text |
Import failed: the object(s) are not known to Natural. |
Explanation |
The import failed due to an internal error in the FTOUCH routine. |
Action |
Contact Software AG support. |
Text |
Invalid name for object. |
Explanation |
This name is not specified for an object or does not exist in a library. |
Action |
Check the name of the object. |
Text |
A file cannot be created or written because it cannot be opened. |
Explanation |
The file is already open or is write-protected, or an internal error occurred. |
Action |
Check whether the file is already open or write-protected. If not, contact Software AG support. |
Text |
Due to an error in the write buffer, a file cannot be written. |
Explanation |
Error in write buffer. |
Action |
Try to write the work file again. If this has no effect, contact Software AG support. |
Text |
A source file cannot be deleted. |
Explanation |
Either the file is write-protected, or an internal error occurred. |
Action |
Check whether the file is write-protected. If it is not, contact Software AG support. |
Text |
A cataloged file cannot be deleted. |
Explanation |
Either the file is write-protected or an internal error occurred. |
Action |
Check whether the file is write-protected. If it is not, contact Software AG support. |
Text |
The record of a file cannot be deleted in directory FILEDIR.SAG. |
Explanation |
Either the directory FILEDIR.SAG is missing, or its contents is corrupt. Ask your administrator to check if the directory FILEDIR.SAG is missing or its contents is corrupt. A corrupt directory can be deleted and should then be recreated automatically for the first file that is copied or moved into the library. The records of the other files in the library must then be imported into the directory. Until an importing program is available to all users, the administrator uses the program FTOUCH to import these records. If the directory is missing, contact Software AG support because an internal error occurred. |
Action |
see explanation |
Text |
A file record cannot be inserted in the directory FILEDIR.SAG. |
Explanation |
The directory FILEDIR.SAG is missing, its contents is corrupt, or it has no space for the new record. Ask your administrator to check if the directory FILEDIR.SAG is missing or its contents is corrupt. A corrupt directory can be deleted and should then be recreated automatically for the first file that is copied or moved into the library. The records of the other files in the library must then be imported into the directory. Until an importing program is available to all users, the administrator uses the program FTOUCH to import these records. If the directory is missing, contact Software AG support because an internal error occurred. |
Action |
see explanation |
Text |
Rename failed: path is incorrect or file name not in directory. |
Explanation |
A file was not renamed because it was not found. Perhaps the path of the file or the extension of the file name has been changed. Otherwise, an internal error occurred. |
Action |
Ask your administrator to check the path of the file and the extension of the file name, and to correct any errors. If both are correct, contact Software AG support. |
Text |
Rename failed: file with same name already exists in library. |
Explanation |
The file could not be renamed because a file with the suggested new name already exists in this library. |
Action |
Either choose a different new name for the file, or delete the existing file. |
Text |
The object has an invalid extension so it cannot be imported. |
Explanation |
An object can be imported only if its extension is valid in Natural. |
Action |
Use the operating system to change the extension so that it is valid in Natural. |
Text |
Two objects with the same name cannot be imported. |
Explanation |
Two objects with the same name (but not necessarily the same extension) have been selected to be imported. Only one of them can be imported. |
Action |
Select only one of the two objects. |
Text |
This module name already exists in a system or step library. |
Explanation |
A module name which is already used in a system library or in a step library cannot be used for a DDM in this library. |
Action |
Choose another module name for this DDM. |
Text |
The new name must be shorter than the old names. |
Explanation |
Several objects can be selected and then renamed by changing the first character or characters of their names. At least one character must remain unchanged at the end of every name. The new character strings must be shorter than the old ones. |
Action |
Specify a new name which is shorter than any of the old names. |
Text |
The header of a DDM has an incorrect format. |
Explanation |
The header of a DDM must have a specific format. |
Action |
Either use the DDM editor to edit the header and correct its format, or ask your administrator to use the editor of your operating system to edit the header and correct its format. |
Text |
The module name of a DDM is incorrect. |
Action |
Either use the DDM editor to edit and correct the module name, or ask your administrator to use the editor of your operating system to edit and correct the module name. |
Text |
No valid library with this name can be found. |
Explanation |
You either entered the name incorrectly or the library you are looking for is not part of this environment. |
Action |
Correct your input or create a new library. |
Text |
Invalid DBID/FNR. |
Explanation |
A library with this DBID/FNR does not exist and cannot be created. |
Action |
You can declare a new DBID/FNR in NATPARM -> global CFG File -> System File Assignment -> Modify System File Assignment |
Text |
The file ... for choice/help menu cannot be found. |
Explanation |
Copy this file to the correct path. |
Action |
Check if the file exists and if it is in the correct path. |
Text |
The file ... cannot be written into the memory file. |
Explanation |
Read error when trying to read the file ... in order to write it to a memory file. |
Action |
Check if the file exists and if its contens is correct. |
Text |
Identical DDM names in cur. lib, step lib or SYSTEM not allowed. |
Explanation |
A DDM cannot be copied to the library System, or Step Lib because of identical names. |
Action |
Change the name of the DDM or move the DDM if you want to use the old name. |
Text |
Library full. |
Explanation |
A library can only contain a certain number of objects (depending on the type). This number has been reached. |
Action |
Choose another library. |
Text |
Unable to open/create ... for logging, logging is switched off. |
Explanation |
The file NATSYSM.LOG for logging taces from SYSMAIN cannot be opened/created, so SYSMAIN continues to work without logging |
Action |
Doesn't matter, go on without logging ! |
Text |
Overwrite not possible if the max. number of objects is reached. |
Explanation |
When the max.limit of objects in one library has been reached you can no longer use COPY, MOVE, RENAME, or IMPORT. |
Action |
Delete one object. |
Text |
Not enough space available on disk |
Explanation |
The function could not be executed successfully because there is not enough space available on drive / discette. |
Action |
Increase free space on disk. |
Text |
DosQFSInfo (check free space) returns error ... |
Explanation |
Internal error returned by the system function DosQFSInfo when checking whether enough free space is available for the imported file. |
Action |
Check the error return code and check your system! |
Text |
The maximum size permitted for a Natural object is 65k. |
Explanation |
A Natural object cannot exceed 65k. If you create an object larger than this externally, you will not be able to import it into Natural. |
Action |
Reduce the size of the object to less than 65k. |
Text |
Not enough memory to create a file buffer. |
Explanation |
Perhaps too many programs have been loaded. |
Action |
Restart the program SYSMAIN. If this has no effect, contact Software AG support because an internal error occurred. |
Text |
Not enough memory to create an array. |
Explanation |
Not enough memory to create an array in which to store a selection list. Perhaps too many programs have been loaded. |
Action |
Restart the program SYSMAIN. If this has no effect, contact Software AG support because an internal error occurred. |
Text |
Internal error .... |
Explanation |
A system call has resulted in an internal error. |
Action |
Restart Natural. |
Text |
Environment variable ... not found. |
Explanation |
An environment variable which can be set with the 'Set' command cannot be found. |
Action |
Set the environment variable you want to use, or type in the full path name. |
Text |
No Natural object found, path invalid or no permission. |
Explanation |
You cannot read any object in this path. Either there is no Natural object in this directory, the directory of this path is not valid or permissions are denied. |
Action |
Check directory, path specifications and read permissions. |
Text |
... returned by stack or nucleus call. |
Explanation |
Nucleus cannot perfom a stack command. |
Action |
Retry the action. If error occurs again contact Software AG Support. |
Text |
... lib(s) found, access denied by Security. |
Explanation |
... lib(s) found, access denied by Natural Security |
Action |
Make sure you have the permission to work within this lib. |
Text |
... lib(s) found for this file, access denied by Security. |
Explanation |
... lib(s) found, access denied by Natural Security. |
Action |
Make sure you have the permission to work within this lib. |
Text |
Invalid USER̲ID. |
Explanation |
Object(s) with this USER̲ID do not exist. |
Action |
Type in the correct USER̲ID or '*' for wildcard. |
Text |
Invalid DATE/TIME. |
Explanation |
Object(s) with this DATE/TIME or newer do not exist. |
Action |
Type in the correct DATE/TIME or '0' for all. |
Text |
Invalid MODE. |
Explanation |
Object(s) with this mode (source or cataloged) do not exist. |
Action |
Select another MODE or both. |
Text |
Cannot delete file. |
Explanation |
Natural tried to delete a file, but access to the file was denied by the operating system. |
Action |
Check permission for the files in question. |
Text |
Sharing violation received during file/folder deletion |
Explanation |
Natural cannot access the file because it is being used by another process. |
Action |
Release usage of file or folder. |
Text |
Too many matches, Please use more specific selection criteria |
Explanation |
The List utility can not display all matching objects of a library |
Action |
Please use another selection criteria |