The management of a CA Datacom environment has been simplified and protection has been increased.
Because there are conversion considerations, the SIMPLIFY feature is forced only for CA Datacom/AD z/OS users and is optional but recommended for CA Datacom/DB z/OS users.
Note: The SIMPLIFY feature is not currently an option for z/VSE users because the environment is simpler and there is much less need of the feature, and the z/VSE platform does not provide the required tools.
The main benefits of the simplification are to force the MUF to always be enabled and actively connect all DBUTLTY functions with the MUF. The MUF is the only updater of the CXX and is in complete control with full knowledge of all the on-going activities. Without this control, situations can occur that require research to understand and present risk to data and roadblocks to the normal 24x7 MUF availability.
With the MUF enabled, no DBUTLTY opens the CXX but instead obtains current information from the CXX through the MUF. Only a few users need security access to the CXX making it much more secure. Without the feature, you must have full write access to the CXX if you are executing any DBUTLTY function using the CXX .
Substantial additional safety of datasets is provided to prevent accidental misuse along with fundamental 24x7 processing.
Because of these reasons, it is mandatory for the CA Datacom/AD users to provide the safe 24x7 access required by the using product. We also recommend SIMPLIFY for the CA Datacom/DB z/OS users for the same reasons. However, it is not appropriate for every user because it enforces many best practices and tightens many abilities. For example, without this feature, it is possible for a production MUF and a test MUF to share a single CXX causing you to be responsible for controlling the databases that each use. It is never acceptable for multiple MUF executions other than MUFplex to share LXX and FXX datasets.
One MUF is the controller of the environment and needs to be enabled to perform that task. It is enabled during or soon after each IPL and remains enabled until the next IPL. Few CA Datacom requirements exist that require an outage and it is very rare for the MUF not to be enabled on purpose or due to an unscheduled outage. There should be no condition where a MUF cannot restart itself and continue processing. If an event prevents the restart, then it is handled as a very special condition with special controls.
The one MUF always knows the status of every part of the environment. The needed control is handled simply, efficiently, and safely. Because the MUF is always enabled, the DBUTLTY functions can run safely by using more MUF services. For example, DBUTLTY uses MUF for CXX activity that allows accurate information to constantly be provided and controlled. There are only a few rare conditions where MUF is not enabled and DBUTLTY is forced to open the CXX and where it uses the same protections as when not running SIMPLIFY.
The database control in the CXX directory is always opened with update intent. With MUF enabled, the MUF fully controls the CXX. The URT option of UPDATE is honored for specific read versus write command support.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|