You may want to use CA OPS/MVS to implement your own customized automation of Critical Path Monitoring events. For example, you may want to increase the priority of jobs in the flow or lower the priority of other work in the system so that the flow can meet its SLA. You can do this using either an AOF message rule or an AOF request rule.
You can write an AOF message rule to drive your own automation that is triggered by the same WTOs issued by CA CPM v3 that are processed by AOF message rules CPM1602I and CPM1603I to update the special SSM resource table to track the status of SSM resources representing monitored flows.
For detailed information on the message text of WTOs issued by CA CPM v3, see the CA Critical Path Monitor Version 3 User Guide that is shipped with the documentation for the CA scheduling products.
You can also write an AOF request rule to drive your own automation that is triggered by a change in the SSM state of an SSM resource representing a monitored flow. Such a request rule would be invoked by the ACTION_TEXT of an entry in the SSM action table associated with the special SSM resource table used to track the status of SSM resources representing monitored flows. You would have to manually add an entry to the SSM action table using the RDF Table Editor.
For instructions on using the RDF Table Editor accessed from OPSVIEW, see the User Guide.
For instructions on using an SSM action table, see the User Guide.
The following section includes an example of using the SSM action table to drive automation.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|