Central Version Considerations

The following considerations apply when executing a utility under a central version through the online or batch command facility.
idmscu
The following considerations apply when executing a utility under a central version through the online or batch command facility.
Area usage mode
To execute a utility under a central version, the affected areas must be available to the central version in the appropriate mode. For utilities that perform updates, the affected areas must be in update mode to the central version. For utilities that perform only retrievals, the affected areas must be in retrieval or update mode. If the previous requirement is not met, you receive a DB002352 error message indicating that the required lock mode is not available.
Committing prior work
Before executing certain utilities through central version, you must commit any previous work that has been done within the current session. This requirement applies to the following utilities:
  • FIX PAGE
  • FORMAT AREA
  • FORMAT SEGMENT
  • LOCK AREA
  • LOCK SEGMENT
The following sequence of statements illustrates how to commit prior work before issuing a FORMAT AREA statement:
SELECT * FROM SYSTEM.TABLE; COMMIT; FORMAT AREA VSAMT.KSDS2;
If you omit the COMMIT, you receive a DB002043 error message: Command not allowed with an open transaction.
Log messages
If you run a FORMAT statement or FIX PAGE statement under central version, an informational message is written to the log identifying the area name being updated and the time of the update.
Batch-only utilities
If you attempt to execute a utility under central version that is supported only in batch local mode, such as UNLOCK or FORMAT FILE, you receive a DB002990 error message indicating that the statement is not supported in central version.