Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Default language.

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Load for Db2 13.1.

Matrix

The matrix ensures the integrity of data base objects in error. The matrix prevents objects, which are currently being processed or which are flagged by processing as being in error, from being used concurrently with other jobs.

Information
Example

Suppose that in job LOAD22, BMC AMI Load is loading table space DB1.GLEDGER. If CLEANUP(YES) is not specified and table space DB1.GLEDGER experiences a problem, job LOAD22 is marked as in error and the matrix holds the object DB1.GLEDGER for job LOAD22.

The next night, you run job REORG95 using BMC AMI Reorg. Processing will see table space DB1.GLEDGER in the matrix and alternate processing will occur. There are two basic choices for alternate processing:

  • Processing continues to wait on the object in the matrix. In this scenario, if the job LOAD22 is corrected that same night and run to a successful completion, table space DB1.GLEDGER is freed from the matrix, allowing the BMC AMI Reorg job REORG95 to continue.
  • Processing skips the object in the matrix and continues with the next statement or object. In this scenario, table space DB1.GLEDGER is not processed further until the original error condition is resolved.

Related topics

Concurrent-access-control

Overview-of-BMC-AMI-Utilities-concepts

Controlling-contention

 

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

BMC AMI Load for Db2 12.1