(1) A mode of operation in which a device can simulate the function of another device or model. The device will function like a different device of the same type, ignoring some or all of the additional features that the device might possess. Compatibility mode permits a migration between devices with minimal impact on programs that have device dependencies. See also page mode, 32-name mode.
(2) A mode of processing in which the IEAIPSxx and IEAICSxx parmlib members determine system resource management.
(3) A programming model that uses existing Tivoli Distributed Monitoring monitors to gather data that is used to create the dynamic model of a new resource model. This mode is used when migrating from previous versions of Tivoli Monitoring to ensure the compatibility of the new monitoring engine with the existing monitor collection.
(4) The first mode of operation in version-to-version migration process, during which DB2 runs the executable code for the new version with preliminary changes to the DB2 catalog. In a DB2 data sharing group, members that operate in compatibility mode can coexist with members that operate at the prior version level. Compatibility mode supports fallback to the prior version of DB2. When operating in compatibility mode, the DB2 subsystem cannot use any new functions of the new version. See also enabling-new-function mode, enabling-new-function mode*, compatibility mode*.