Database Upgrade Matrix
Database Upgrade Matrix
| NEW FUNCTIONALITY | ||||||
|---|---|---|---|---|---|---|
| GT.M Version | up to V6.3-014 | V6.0-000 and up | V7.1-000 and up | V7.0-000 and up | ||
| MUPIP SET -VERSION MUPIP REORG -UPGRADE or -DOWNGRADE | MUPIP UPGRADE | MUPIP REORG -UPGRADE | ||||
| Block version | V6 | V6p | V7m | V7m | V7 | |
| Upgrade State | “Fully Upgraded” to V7 is FALSE indicating the presence of V6 blocks. This database is ineligible to upgrade to V7. | “Fully Upgraded” to V7 is TRUE indicating that all blocks in the database are V7 | Phase 1 starting transitional state. Blocks in this format have the offset applied to 4 byte block pointers | Phase 1 complete. Directory tree blocks upgraded to 8 byte block pointers | Phase 2 complete:index blocks upgraded with 8 byte block pointers with an unknown mix of V6 data and local bit map blocks | Fully Upgraded to V7 indicating that all blocks in the database are V7 |
| Desired DB Format | V6 | V6p | V7m | V7m | V7 | |
| Starting VBN | V5 - 129; V6 - 513 | V5 - 129; V6 - 513 | Variable | Variable | Variable | V7 - 8193 |
| DB Block Mix | V5 or V6 only | V6 only | V7m (directory tree)V6p (some GVT index blocks)V6 index and data blocks | V7m index blocks Tracked quantity of V6 data blocks Unknown quantity of local bit map blocks | V7m index blocks Tracked quantity of V6 data blocks Unknown quantity of local bit map blocks | V7 only |
| Index Block “pointer” | (block_id_32) 4 bytes - 30 bits usable | (block_id_32) and (block_id_64) | (block_id_64)8 bytes - 62 bits usable | |||
| Block header | V5 campatible with V6, but not visa versa | No change | No change | No change | No change | No change |
| Record header | No change | No change | No change | No change | No change | No change |
| Data Block | V5 campatible with V6, but not visa versa | No change | No change | No change | No change | No change |
| Local bit map | No change | No change | No change | No change | No change | No change |