Using CA Datacom/DB Utility (DBUTLTY) › Area Level DBUTLTY Control › Summary of Restrictions and Requirements

Summary of Restrictions and Requirements

User applications and CA Datacom utility functions provide execution requirements by defining a User Requirements Table and issuing an open for it. If all requirements are not met, the open is rejected. If all are met, control is established to allow the successful completion of the application or utility function.

The following restrictions related to area level DBUTLTY control and the ACCESS Multi-User startup option should be noted:

• To specify YES for the MULTUSE= keyword, in the DBUTLTY functions that have MULTUSE= as an option, the database must be running in the OPTIMIZE mode, set with the ACCESS Multi-User startup option established during the Multi-User Facility startup.
• Area level DBUTLTY control cannot be used when executing against a Multi-User Facility that is running as part of a MUFplex, when more than one Multi-User Facility is enabled. Return code 94(116) occurs when attempting to run in this configuration.
• Area level DBUTLTY control cannot be used in a database defined to be VIRTUAL. The catalog from CA Datacom/DB is still at the database level only.

Note: Area level DBUTLTY control supports, but works independently of, table partitioning.

Area level DBUTLTY control is best used when it is important for one area in a database to be open for normal processing while another area needs to be reorganized or rebuilt, presuming the applications use the available areas, not the unavailable area. However, if applications open tables in all areas, for example in CA Datacom/DB when one-table areas are used, we recommend that execution be allowed to run in full Single User mode, which is the default.