From my 'library'... originally from Derek Drummond/DISC Notes on TPI NOXM * We provide a program, xm.util.disc, to tell if files are attached to xm or not. TYPE: xm.util.disc <dbname>@ Note: The program is not harmful to your files, but will error on non-PRIV files and files that are currently accessed. Don't be alarmed. * The <dbname>0A, rootfile, is never attached to XM. * The only programmatic way to know that NOXM is active is via a bit in the ODX rootfile - as far as DBUTIL and IMAGE are concerned we're using vanilla TPI. Most programs, even OmniUtil, are unable to distinquish the difference from TPI ON and TPI NOXM. * The DBUTIL command DISABLE <dbname> FOR INDEXING clears the TPI flag in the IMAGE rootfile, but doesn't detach the index files. So DBINSTAL is the only reliable way to enable/disable TPI or TPI NOXM. OmniUtil is an attractive front in [sic] for DBINSTAL, but OmniUtil is only aware of TPI ON/OFF, it has not yet been enhanced to SET TPI NOXM. * The TPI_NOXM flag is stored in the rootfile and it can be queried by a call to dbinfo() mode 331, which returns five 32-bit integer values, as follows: 0: Kernel version 1: DBINSTAL version used to install this DB. 2: Install date (data type 'time_t', from the POSIX time() function) 3: Number of index files 4: TPI_NOXM flag (1 = True, 0 = regular TPI or non-TPI) * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *