Error Codes and Messages
- Last UpdatedJan 05, 2024
- 6 minute read
Errors are mostly handled by the return of an error code by each DARs routine. Details are included in Error Handling, Monitoring and Detailed Subroutine Specifications of this manual.
The following error codes exist. The returned value can only be positive or zero. A positive value denotes an error condition; zero denotes no error.
The listed text messages are returned by D3EMSG; the maximum text length is 50 characters.
The codes are grouped according to the type of error, as follows:
|
0 - 99: |
General |
|
101 - 199: |
Initialization |
|
201 - 299: |
Navigation |
|
301 - 399: |
Retrieval |
|
401 - 499: |
Database |
The error codes and their corresponding interpretations are as follows:
|
0 |
Success |
|
No errors have occurred |
|
|
1 |
Unknown error |
|
An undocumented error has occurred. Please record the two numbers that accompany this message and contact your Marine support engineer. |
|
|
2 |
Internal error code set on entry |
|
An error has occurred during a previous call to a data access routine. No further actions can be can be carried out by data access routines until the internal error code is reset with a call to routine D3ERST. |
|
|
3 |
Routine D3INIT has not been called |
|
A successful call to routine D3INIT must precede all use of data access navigation and attribute retrieval routines in each project. |
|
|
4 |
Routine D3MMDB has not been called |
|
A successful call to routine D3MMDB must precede all use of data access navigation and attribute retrieval routines in each project. |
|
|
5 |
Character string output argument too short |
|
The character string supplied by the programmer to take an output argument is too short. A truncated string will not be returned. |
|
|
6 |
Invalid position keyword |
|
A position keyword other than 'FIRS', 'LAST', 'NEXT' or 'PREV' has been supplied. |
|
|
7 |
Invalid coordinate system keyword |
|
A coordinate system not recognizable as a Marine name, reference number, noun or the keyword 'OWNE' has been supplied. |
|
|
8 |
Invalid PPoint keyword |
|
The character string entered for PPoint is not a valid option. Valid keywords are 'PH/EAD', 'PT/AIL', 'PA/RRIVE', 'PL/EAVE' and 'Pval', where val is an integer. |
|
|
9 |
Bad name/reference argument |
|
A name has been supplied without a leading / character, or a reference number without = and / characters. |
|
|
10 |
Argument has illegal value |
|
The value of the argument is invalid. For example, a negative value may have been entered where a positive value is required. |
|
|
11 |
Invalid project data keyword |
|
The character string entered for project data item is not a valid option. Valid keywords are: NUM/BER, NAM/E, DES/CRIPTION, MES/SAGE, COD/E. |
|
|
12 |
Invalid date/time |
|
The character string entered for date/time is not a valid text string. |
|
|
13 |
Entered date/time later than current |
|
The date/time argument is later than the current date/time and is therefore invalid. |
|
|
101 |
Error opening Dabacon workfile |
|
This should not normally occur. It can occur if the user does not have access to the Marine work area or if he attempts to run a DARs program within Marine using the SYSCOM command (both programs try to open the same workfile). |
|
|
102 |
Bad password |
|
The specified password is not valid for the specified username in the specified project. |
|
|
103 |
Unknown username |
|
The specified username is not defined in the specified project. |
|
|
104 |
Too many users in project |
|
The number of users in the project has exceeded the maximum allowed. |
|
|
105 |
Project currently locked |
|
The specified project is locked and access is denied. |
|
|
106 |
Project is incompatible version |
|
An attempt has been made to open a database belonging to an incompatible version of Marine. The current versions of the project and of Marine DARs are incompatible. |
|
|
107 |
Too many failed initializations |
|
The application program has called D3INIT three times (or more) in succession, each failing to initialize DARs. |
|
|
108 |
Project not found |
|
The directory corresponding to the specified project could not be found, or if found does not contain a Marine project. |
|
|
109 |
Error opening runfile data file |
|
This should not occur. Ensure the user has access to the Marine project. |
|
|
110 |
MDB not found |
|
The specified MDB is not defined in the specified project. |
|
|
111 |
No databases to open |
|
There are no current databases in the specified MDB. Alternatively, there are no databases of the various types required for the specified default database. For example, if the default database is type DESI and there are no DESI, CATA or PROP databases in the MDB. |
|
|
112 |
Corrupt databases |
|
Database corruption has been detected. |
|
|
113 |
Databases in use |
|
Databases on the specified MDB are held busy by another user. This can occur even though DARs access is read-only, because Marine will allow only one user for any database in an MDB. |
|
|
114 |
Error opening database file |
|
This error can occur if a required database file does not exist or if it cannot be accessed for any reason. |
|
|
115 |
Sitefile/Security error |
|
Error returned by sitefile check. The nature of the error will be output to the terminal in the same way as occurs for Marine. Unlike Marine, the program will not stop, but will simply return this error. |
|
|
116 |
Invalid project name |
|
The entered project name (after truncation to three characters) is not a valid name. A valid name consists of three alphabetic characters. |
|
|
117 |
Invalid default database type |
|
Invalid keyword string entered for default database type. It must be one of the valid options or a valid abbreviation. |
|
|
118 |
No databases of default type in MDB |
|
The specified MDB does not contain a database of the default type. |
|
|
The program cannot open the system database. The nature of the error will be output to the terminal in the same way as occurs for Marine (for example, PNS Privileges not sufficient). Unlike Marine, the program will not stop, but will simply return this error. |
|
|
120 |
Database not found |
|
Named database not present in current project. |
|
|
121 |
Database not in current MDB |
|
Named database not present in current MDB. |
|
|
122 |
Database already current |
|
Database cannot be made current because it already is current. Or, databases cannot be exchanged because both are current. |
|
|
123 |
Database not current |
|
Database cannot be deferred because it already is deferred. Or, databases cannot be exchanged because both are deferred. |
|
|
124 |
Too many current databases |
|
Database cannot be made current because the maximum number of databases is already current. |
|
|
125 |
Invalid database position |
|
Specified database position is less than 1 or is greater than maximum number of databases |
|
|
126 |
Too many saved database levels |
|
Nesting of D3MSAV and D3MRST exceeds a depth of 10. |
|
|
127 |
No saved database position. |
|
D3MRST has been called with no previous matching call to D3MSAV. This may be the result of unbalanced nesting of D3MSAV and D3MRST, due to a program logic error. |
|
|
201 |
Element has no list part |
|
An attempt has been made to go to a member of the current element but it cannot own elements. |
|
|
202 |
No members |
|
An attempt has been made to go to a member of the current element but it has no members (though it can own them). |
|
|
203 |
List exhausted |
|
An attempt has been made to go beyond the end of the current list of elements. |
|
|
204 |
Current element has no owner |
|
An attempt has been made to go to the owner of the current element when it has no owner. This only applies to the world. |
|
|
205 |
Cannot access this type of element |
|
A Marine noun of unrecognized type has been supplied, either as element type or coordinate system. |
|
|
301 |
Attribute not found |
|
The current element does not have the requested attribute. |
|
|
302 |
Attribute of wrong type |
|
The requested attribute is of a different data type to that retrieved by the this routine. |
|
|
303 |
Element does not have PPoints |
|
The current element does not have PPoints. |
|
|
304 |
Illegal PPoint number |
|
The current element does not have a PPoint with this number. |
|
|
305 |
Wrong element type |
|
Attempt to read an attribute specific to a particular element type, when the current element is of an inappropriate type. Not applicable at present. |
|
|
306 |
No date-stamp found |
|
Databases in MDB do not have a date-stamp. MDB not used since project created or reconfigured. |
|
|
307 |
UDA not found |
|
The current element does not have the requested user-defined attribute. |
|
|
308 |
Attribute unset |
|
If text, the requested attribute is unset (that means, null '', as distinct from blank ' '). If an array, all array elements are unset. |
|
|
309 |
Element not on spatial map |
|
The database spatial map is not up-to-date. Use the MAP command in Design to rebuild the spatial map. |
|
|
310 |
Leave or head tube does not exist |
|
The surrounding box for an element's leave tube, or branch head tube, has been requested and there is no such leave or head tube. |
|
|
401 |
Dabacon error |
|
A Dabacon system error has occurred. Please record the two numbers that accompany this message and contact your Marine support engineer. |
|
|
402 |
Undefined name/reference |
|
A name or reference number has been supplied which is not defined in a database which is currently open, either to move to it, or as a coordinate system. |
|
|
403 |
Reference to database not open |
|
The element referenced is not in a database that is current on the selected MDB. |
|
|
404 |
File write error |
|
This should not occur. Ensure the user has access to the Marine work area and to the Marine project. |
|
|
405 |
File read error |
|
This should not occur. Ensure the user has access to the Marine work area and to the Marine project. |