|
|
|
When installing more than one of the CA Technologies mainframe testing tools, we recommend that you install and maintain only one version of CA Technologies common symbolic component that is shared by all of the testing tool products.
Several testing tool products (CA InterTest Batch, CA InterTest for CICS, CA SymDump for CICS, CA SymDump Batch, CA Optimizer/II, and CA Mainframe Application Tuner) each distribute the common symbolic component in the VH FMID. This FMID was named CVHrr00 in previous versions and is now named CAVHrr0. The rr portion of the FMID contains the version number. For example, CAVH900 contains the symbolic common component provided with Version 9.0.
When installing any of these CA Technologies testing tool products, first query your Consolidated Software Inventory (CSI) to determine whether you already have a version of CVHrr00 or CAVHrr0 installed. If you use one CSI for all of your testing tool products then you need to perform only one query for these FMIDs. If you have one CSI for each testing tool product then you will need to query each CSI.
If you locate an installed version of CVHrr00 or CAVHrr0 during your query, compare the rr in your installed version of that FMID with the rr in the FMID provided with the product you are installing. Replace your existing FMID only if the rr in the product you are installing is higher than the rr in your existing function.
Business Value:
By installing and maintaining a single version of the CA Technologies common symbolic component, you reduce your maintenance effort, save disk space, and eliminate the possibility of executing symbolic utilities that are not up to date with the latest maintenance.
Additional Considerations:
The APPLY job of the installation places an SMP/E copy of the CAVHrr0 function in a library; however, many companies do not execute the testing tool products from this library. Therefore, always be sure to make the executables for the common symbolic component available for the testing tools products to use.
There are many ways to make the executables for the common symbolic component available, including:
Always update your LNKLIST library after applying maintenance to CAVHrr0 if you have copied the executables for the common symbolic component from CAVHrr0 into a separate load library that you have added to your LNKLIST for all products to share.
We recommend using the LNKLIST method because it has the specific advantage of making the executables available to all CA Technologies products with no additional changes to any JCL or CLISTs. If you cannot use LNKLIST for some reason (for example, your company has issues with updating LNKLIST or has specific rules prohibiting or limiting the use of LNKLIST), it is acceptable to add these executables to your STEPLIB or CLIST allocations. However, using STEPLIB or CLIST requires more initial setup and can be difficult to maintain if library names change.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |