GT.M processes may detect errors at run-time. These errors trigger the GT.M error handling mechanism, which generally places the process in direct mode, or triggers the application programs to transcribe an error context to a sequential file or to a global. For more information on error handling, refer to the "Error Processing" chapter of the GT.M Programmer's Guide.
Most run-time errors are related to the application and its environment. However, some errors reflect the inability of a process to properly deal with a database. Some errors of this type are also, or only, generated by the GT.M utility programs.
For descriptions of individual errors, refer to the GT.M Message and Recovery Procedure Reference Manual.
IF YOU CANNOT REPRODUCE SUCH ERRORS WITH ANOTHER PROCESS PERFORMING THE SAME TASK, or with an appropriately directed MUPIP INTEG, they were most likely reported by a damaged process. In this case, refer to section P1.
The following table lists run-time errors, alphabetically by mnemonic, each with a section reference for further information.
|
Run-Time Error Messages Identifying Potential System Problems |
||
|
ERROR MNEMONIC |
ERROR MESSAGE TEXT |
SECTION |
|
BADDVER BITMAPSBAD BTFAIL CCPINTQUE CRITRESET |
Incorrect database version vvv Database bitmaps are incorrect The database block table is corrupt Interlock failure accessing Cluster Control Program queue The critical section crash count for rrr region has been incremented |
I2 M1 R3 R7 I8 |
|
DBCCERR DBCRPT DBFILERR DBNOFILEP DBNOTGDS |
Interlock instruction failure in critical mechanism for region rrr Database is flagged corrupt Error with database file No database file has been successfully opened Unrecognized database file format |
R7 I8 I5 I5 I5 |
|
DBOPNERR DBRDERR FORCEDHALT GBLDIRACC GBLOFLOW |
Error opening database file Cannot read database file after opening Image HALTed by MUPIP STOP Global Directory access failed, cannot perform database functions Database segment is full |
I5 I5 R4 I5 R5 |
|
GVKILLFAIL GVORDERFAIL GVPUTFAIL GVQUERYFAIL GVRUNDOWN |
Global variable KILL failed. Failure code: cccc Global variable $ORDER or $NEXT function failed. Failure code: cccc Global variable put failed. Failure code: cccc Global variable $QUERY function failed. Failure code: cccc Error during global database rundown |
R2 R2 R2 R2 I5 |
|
GDINVALID GTMCHECK GVDATAFAIL GVDIRECT GVGETFAIL |
Unrecognized Global Directory format: fff Internal GT.M error–report to Fidelity Information Services Global variable $DATA function failed. Failure code: cccc Global variable name could not be found in global directory Global variable retrieval failed. Failure code: cccc |
I5 R6 R2 I5 R2 |
|
GVZPREVFAIL MUFILRNDWNFL UNKNOWNFOREX TOTALBLKMAX WCFAIL |
Global variable $ZPREVIOUS function failed. Failure code: cccc File rundown failed Process halted by a forced exit from a source other than MUPIP Extension exceeds maximum total blocks, not extending The database cache is corrupt |
R2 I5 R4 R5 R3 |