Shared access levels of BMC utilities


BMC utility jobs register Db2 objects in the BMCSYNC table.

The registering utility assigns a sharing level to each registered object. The sharing level controls access to that object from other BMC utilities. For partitioned Db2 spaces, registration is performed at the partition level.

Related topic

Important

All BMC utility products use the BMCUTIL table to control the use of utility IDs, which identify executions of BMC utilities. Each BMC utility product must have a unique ID for restart purposes. This unique ID is stored in the BMCUTIL table. For more information about this table, see BMCUTIL-and-BMCUTIL2-tables.

The BMCSYNC table allows multiple BMC utilities (or multiple instances of a utility) to operate concurrently on different partitions of a Db2 space if no nonpartitioning indexes are involved. In addition, some BMC utilities can operate concurrently on the same object or partition. For information about which products can operate concurrently, see the following table. For additional serialization and concurrency issues for each utility, see the utility's reference information.

The 'Access level' column in the following table refers to the value of the SHRLEVEL column name in the BMCSYNC table (BMCSYNC-table). The level can be one of the following values:

  • S indicates shared access. Any other utility that registers with shared access (S) can run against the object.
  • X indicates exclusive access. No other utility can run against the object.
  • A blank value indicates that no status is requested and any other utility can run against the object.

Product

Access level

Additional information

CHECK PLUS

S

None

DASD MANAGER PLUS (BMCSTATS)

S

  • If BMCSTATS is processing multiple objects and encounters an object that is held by another utility, the BMCSTATS job issues a warning. The warning identifies the object and the utility that is using it. BMCSTATS continues processing the next object.
  • If BMCSTATS is processing an object and another utility requires exclusive control of that object, the other utility stops execution at initialization time.

LOADPLUS

X

If you specify PART, LOADPLUS registers only the specified partitions with exclusive access (X). If no nonpartitioned indexes exist on the table space, you can run other utilities on different partitions while running this job.

BMC AMI Check

S

None

BMC AMI Copy

S or blank

If you specify COPY IMAGECOPY, BMC AMI Copy registers the object with no access status (blank). Otherwise, BMC AMI Copy registers the object with shared access (S).

BMC AMI Load

X

If you are loading specific partitions, BMC AMI Load for Db2 registers only the specified partitions with exclusive access (X).

BMC AMI Recover

X, S, or blank

BMC AMI Recover registers an object with shared access (S) under the following conditions:

  • The table space for an index is registered with shared access if the index is being rebuilt and its table space is not recovered in the same job.
  • A table space partition is registered with shared access if the keys for that partition are unloaded with a RECOVER UNLOADKEYS operation.

BMC AMI Recover registers an object with no access status (blank) if you specify the following commands or options:

  • The ACCUM command
  • OUTCOPY ONLY
  • INDEP OUTSPACE

BMC AMI Recover registers the object with exclusive access (X) in all other cases.

BMC AMI Reorg

X

If you are loading specific partitions, BMC AMI Reorg for Db2 registers only the specified partitions with exclusive access (X).

BMC AMI Stats

S

None

BMC AMI Unload

S

None

BMC AMI Recovery Manager

S

None

REORG PLUS

X

If you specify PART, REORG PLUS registers only the specified partitions with exclusive access (X). If no nonpartitioned indexes exist on the table space, you can run other utilities on different partitions while running this job.

UNLOAD PLUS

S

None

Warning

Do not run an IBM utility, command, or SQL statement that attempts to manipulate the structure, data, or status of an object that a BMC utility is currently processing. For example, commands and SQL statements such as -STOP, -START, EXCHANGE, and ALTER will produce unpredictable results.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*