For scheduling products other than CA 7, the z/OS system upon which the primary instance of the scheduling product is running can change at any time due to either a manual reconfiguration or a system failure.
If the primary instance of the scheduling product shifts from one system to another, then Critical Path Monitoring needs to switch to that other system as well. In order for Critical Path Monitoring to be portable so that it can always monitor the critical flows from the primary instance of the scheduling product, both CA CPM v3 and CA OPS/MVS need to be active and customized on each z/OS system that is configured to run the primary instance of the scheduling product.
All z/OS systems in the complex of the scheduling product that are configured to run as the primary instance for scheduling can be defined to SSMO as a CPM Plex. This definition allows SSMO to create a single resource (icon) for each flow regardless of which z/OS system the primary instance is running on. Flow icons are grouped under the CPM Plex icon on the Unicenter TNG WorldView map.
For instructions on defining a CPM Plex to SSMO, see the CA NSM SSM CA OPS/MVS Option documentation.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|