Advanced Topics › Control File Internals › CA MIM Transactions

CA MIM Transactions

The other main structures that are found in CA MIM control files are CA MIM transactions. There are over 28 different CA MIM transactions that represent changes to managed resources. Each CA MIM component has transactions unique to that component. The following table illustrates some of the transaction types that are associated with each CA MIM component:

The size of a particular CA MIM transaction is variable in length. For example, the size of a CA MIC cross-system message transaction depends on the length of the message text. The simplest form of an individual CA MIM transaction mapping follows:

The routing mask field is used to direct the transaction to specific systems. For example, if a user on SYSA routes a command to SYSB, CA MIC on SYSB must be informed of this fact. In this case, CA MIC on SYSA creates a transaction having a routing mask for SYSB, and writes the transaction to the CA MIM control file. Once CA MIM on SYSB has read and processed this transaction, it is deleted from the control file. Remember that CA MIM transactions are in the control file for a brief period of time-ideally for less than one second. The more often each CA MIM address space accesses the control file, the faster CA MIM transactions are processed and deleted from the control file, so the complex-wide throughput time will be better.