|
|
|
CA MIM provides seamless integration with CA OPS/MVS in several areas, including VARY delay events.
You do not need to do anything for CA MIM to enable the product interface to CA OPS/MVS and you do not need to issue any CA MIM initialization statement or commands to activate the interface. If CA MIM and CA OPS/MVS are active in the same z/OS image, CA MIM automatically communicates CA MIM automation events to CA OPS/MVS.
Before the CA MIM-to-CA OPS/MVS interface existed, CA OPS/MVS could automate CA MIM events through console messages, and CA OPS/MVS can still use CA MIM console message traffic for automation events. Console messages are processed by CA OPS/MVS )MSG rules. Depending upon the particular automation event, CA OPS/MVS rules may need to correlate console messages and, in some instances, issue commands and interrogate command responses to collect information about a given event.
On the other hand, the CA MIM-to-CA OPS/MVS interface is an integrated two-way communication mechanism. CA MIM passes automation event information directly to CA OPS/MVS, including all pertinent data related to the automation event in the form of OPS REXX variables. These events can be automated using a CA OPS/MVS )API rule. This interface is more efficient and reduces the complexity of CA OPS/MVS automation rules as the event data in readily available in REXX variables. This internal interface also eliminates the dependence on the format and content of console message text.
Also, CA MIM can take action on an automation event as directed by a CA OPS/MVS )API automation rule. CA MIM and CA OPS/MVS seamlessly work together to automate the management of shared-system resources.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |