GT.M uses the data elements of the file header for accounting, control, and logging purposes. The DSE command DUMP /FILEHEADER displays the file header fields.
For information on modifying some of these elements with the DSE CHANGE /FILEHEADER command, refer to the "Database Structure Editor" chapter.
The file header data elements are listed in alphabetical order below for easier access, rather than the order in which they appear in the file header.
|
Data Element |
Description |
|
Before imaging |
Indicates whether or not before image journaling is allowed; only reported by DSE if journaling is ENABLED (or ON). |
|
Block size (in bytes) |
A multiple of 512; value taken from Global Directory. |
|
Collation version |
The version of the collation sequence definition assigned to your database. DSE only reports this if an external collation algorithm is specified. |
|
Create in progress |
True only during the MUPIP CREATE operation. If this is true at another time, then MUPIP CREATE did not complete its operation and the database is corrupt. |
|
Current transaction |
Number of the most recent database transaction. Reducing the current transaction number with DSE may make incremental backups impossible to restore. Increasing the current transaction number is harmless except that it hastens the time when the transaction number must be reset with MUPIP INTEG /TN_RESET. Another alternative is to use BACKUP /ONLINE. |
|
Default collation |
The collation sequence currently defined for your database. DSE only reports this if an external collation algorithm is defined. |
|
Extension count |
The number of GDS blocks by which the database file extends when it becomes full. |
|
Free blocks |
The number of GDS blocks in the data portion of the file that are not currently part of the indexed database (i.e., not in use). |
|
Incritical section |
The process identification number (PID) of the process in the write-critical section, or zero if no process holds the critical section. The critical section is a stream of instructions executed by a GT.M process or utility to control a database segment. These instructions cannot be interrupted by other GT.M processes or utilities accessing the same database segment. The DSE CRITICAL command allows examination and manipulation of this field. |
|
Journal allocation |
The number of blocks initially assigned to your journal file. DSE only reports this field if journaling is ENABLED (or ON). |
|
Journal buffer size |
The amount of memory allotted to buffer journal file output. |
|
Journal extension |
The number of blocks by which the journal file can expand if it becomes full. |
|
Journal file |
The name of the journal file. DSE only reports this field if journaling is ENABLED (or ON). |
|
Journaling |
Indicates whether journaling is ON, OFF, or not allowed. The original value is taken from the Global Directory, modified with MUPIP SET. |
|
Lock space |
Hexadecimal number indicating the pages of space dedicated to LOCK information. |
|
Maximum key size |
Must be at least three (3) or four (4) less than the record size; never more than 255; original value taken from Global Directory. |
|
Maximum record size |
A value less than or equal to the block size minus reserved bytes; original value taken from Global Directory. |
|
Modified cache blocks |
Current number of modified blocks in cache waiting to be written to the database. |
|
Mutex hard spin count |
Number of attempts to grab the mutex lock before initiating a less CPU-intensive wait period. |
|
Mutex sleep spin count |
Number of timed attempts to grab the mutex lock before initiating a wait based on interprocess wake-up signals. |
|
Mutex spin sleep time |
Number of milliseconds to sleep during a mutex sleep attempt. |
|
No. of KILLs in prog |
Number of processes currently cleaning up after multi-block KILLs. |
|
Nullsubscripts |
True if null subscripts are legal, false otherwise; original value taken from Global Directory. |
|
Number of local maps |
(Total blocks + 511)/512. |
|
Online Backup NBB |
Block to which online backup has progressed. Only displayed by DSE when an online backup is currently in progress. |
|
Reference count |
Number of GT.M processes and utilities currently accessing that segment on a given node; informational only. GT.M does not rely on this field. A database segment initially has a reference count of zero. When a GT.M process or utility accesses a segment, GT.M increments the reference count. GT.M decrements the reference count upon termination. GT.M counts DSE as a process. When examining this field with DSE, the reference count is always greater than zero. When DSE is the only process using a region, the reference count should be one. |
|
Region seqno |
The current replication relative time stamp for a region. |
|
Replication state |
Either CLOSED or OPEN.> |
|
Resync seqno |
The current relative time stamp confirmed with the replication partner. |
|
Resync transaction |
The per-region transaction number corresponding to the transaction that marks the primary-secondary synchronization point for that region. |
|
Reserved bytes |
Number of bytes reserved. |
|
Starting VBN |
Virtual Block Number of the first GDS block after the GDS file header; this is block 0 of the database and always holds the first local bitmap. |
|
Total blocks |
Total number of GDS blocks, including local bitmaps. |
|
Note |
|---|---|
|
(total-blocks * block-size + size-of-file-header) / 512 = number of VMSblocks in the GDS file. |