The new install process uses the SIMPLIFY feature of CA Datacom/DB. To use the full Simplify feature, the same MUF data set naming standards are required. The naming conventions for your site can be different.
For more information regarding the Simplify feature, see the CA Datacom/DB Database and System Administration Guide and the CA Datacom/DB DBUTLTY Reference Guide for z/OS before starting your new installation. This information will help you to understand the Simplify feature.
CAI.NEWHLQ.9CXX_NAME.V150.* where asterisk (*) defines CUSLIB, CUSMAC, and CUSPROC. CAI.NEWHLQ.9CXX_NAME.* defines all the database areas and MUF control data sets except the PXX. The install process controls the last node for these data sets. 9CXX_NAME and MUF name are the same value in this dialog. The CAI.NEWHLQ can be a user-defined length of 19 bytes. Due to data sharing requirements, the CXX name should only be a maximum value of 7 bytes. V150 is 4 bytes and in some cases, the last node uses all 8 bytes. For example, CAI.NEWHLQ2.9CXX_NAME.AREANAMEDBID, CAI.NEWHLQ can be one node or as many nodes as you can use within the 19-byte restriction.
The following examples show how this looks if the CXXNAME is PRODMUFA:
Once the customization is done, this new install process does loads for all bases. Every possible base is loaded on this installation. After completing, the CICS portion that builds the VLS files are generated in the next job. No MUF is used during the new install process. The IVP process requires you to bring up a MUF to verify that the installation was successful. A sample MUF member, MUFSTRTS, in the **.INSTJCL is provided for your use. Be sure that the libraries for the MUF have been APF authorized. Make any required changes to the DBDATIN2 member before attempting to use this MUF.
DQ backup from the new install loads functional CA Dataquery systems through DBUTLTY LOAD. To modify the CA Dataquery options, refer to **.CABDSAMP in member DQSIM01. Be sure to copy it to another place to modify it. SMP/E controls **.CABDSAMP so this PDS is not an appropriate place to edit or save.
The System Identification Block (SID) assembly assumes the full implementation for Simplify and all of its protections. Do not remove any of the SID options that deal with Simplify. For more information about Simplify, see the CA Datacom/DB Database and System Administration Guide and the CA Datacom/DB DBUTLTY Reference Guide for z/OS.
This naming standard is a recommended best practice. With this fully implemented feature, MUF and DBUTLTY no longer need the DD cards for CXX/LXX/FXX. When the Simplify feature is installed, the primary benefit is that the DB RC 46/51 should be eliminated and the MUF has full ownership of the CXX except for a few DBUTLTY functions that can run with MUF down. Your MUFs have more protection against a database outage by init/load going to the wrong CXX/MUF after implementing this feature.
|
Copyright © 2014 CA.
All rights reserved.
|
|