IMAGE/SQL error 164; TurboIMAGE error -242; TurboIMAGE 
   intrinsic 420, and Auxiliary error 6554488.  (DBERR 13552) 

The TurboImage error -242 means: 

       MESSAGE   MDBX transaction failure 
       MEANING   DBXBEGIN has encountered a problem 
       ACTION    Purge the TURBOGTX.PUB.SYS file 


This file is privileged. To purge the file the following can be used; 

1) FSCHECK.MPEXL.TELESUP 
   PURGEFILE TURBOGTX.PUB.SYS 

2) Use a third party program such as MPEX which allows a user 
   to purge a privileged file. 

3) Use STORE;PURGE using a file equation to $null or to tape. 

NOTE: The error will continue until the file is PURGED, this is the ONLY 
way at this time to get rid of the error.  Another TURBOGTX file will be 
created by TURBOIMAGE when needed. 

Before purging the file; 

   Do a listfile TURBOGTX.PUB.SYS,9 
   If the file is busy, all databases on the system must be closed in order 
   to free the file.  Once this occurs the file can be purged. A new file 
   will be created upon the first dbxbegin call. 

TURBOGTX: Is the Global Transaction Table (TURBOGTX.PUB.SYS). Its 
          function is to keep track of multiple database dynamic trans- 
          actions on the system. 

          It is a long mapped file, with a filecode of -407. It is built 
          by the first process on the system to call DBXBEGIN in mode 3 
          or 4. The file is then attached to XM and saved as a permanent 
          file in PUB.SYS. 

          There is one TURBOGTX file per system. It must remain on the 
          system, after system startup, to ensure that all multiple 
          database transactions that were in progress, at the time of 
          the system failure are rolled back. 

          The TURBOGTX contains an entry for each process (pin/USER) that 
          has multiple database DBXBEGIN in progress. When a DBXEND, mode 
          3 or 4 is called, the TURBOGTX entry for that pin is flagged 
          as unused. A DBXUNDO will also cause the entry to be flagged 
          as unused. 

Why does the error occur? 

1)  An error occured with TPI [Third Party Indexing] which could not be 
    recovered. 

2)  Image database was opened by a posix process....a problem 
    occured with the dbxbegin. 

3)  An error occured on a IMAGE/SQL table during or before a commit 
    work.  DBXbegin is called for all isql commands issued against a 
    image database.  DBXEND is issues at the end of COMMENT WORK. 

 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *