3. Installation › 3.8 Installation Checklists › 3.8.3 Adding a New Product to a New Database Unit › 3.8.3.1 Define and Generate New Product(s)
3.8.3.1 Define and Generate New Product(s)
__ 1. Define Products to be Generated
Check off the products that require generation:
Note: CAP, PER, STG, LDE, VCC, and VMT do not require
generation.
Standard Products
___ BAS - CA MICS base platform
___ ACT - Accounting and Chargeback Option
___ AST - CA ASTEX Option
___ AUM - Analyzer Option for MeasureWare
___ CIC - Analyzer Option for CICS
___ DB2 - Analyzer Option for DB2
___ DEX - Analyzer Option for VAX/VMS
___ HSM - VCA support for DFHSM
___ IDM - Analyzer Option for CA IDMS
___ IMS - Analyzer Option for IMS
___ MQS - Analyzer Option for MQSeries
___ PWR - Analyzer Option for VSE/Power
___ RMF - Hardware and SCP Analyzer
___ SMF - Batch and Operations Analyzer
___ SNT - Network Analyzer Option
___ SRL - System Reliability Analyzer Option
___ TDM - Tandem Option
___ TLM - Tape Analyzer Option, TLM Component
___ TSO - Analyzer for TSO
___ VCA - Space Analyzer Option
___ VMC - Analyzer Option for VM/CMS
___ VTS - Tape Analyzer Option, VTS Component
___ WEB - Web Analyzer Option
Field Developed Applications (Including MSI and MTI)
___ (___) - ____________________________
___ (___) - ____________________________
___ (___) - ____________________________
+---------------------------------------------------+
| Reference(s): Section 3.4.1 |
+---------------------------------------------------+
************************************************************
* Repeat Steps 2 through 6 in this section for all *
* products that have been checked off for generation. *
************************************************************
__ 2. Review Component Generation Options
Review component generation options in Chapter 7 of
the product guides for the data integration
applications (DIAs) you are installing. Some products
provide global element tailoring options that you may
wish to review. Products that process user SMF data
sources also provide an option for record selection.
+---------------------------------------------------+
|Reference(s):Section 3.4.2 |
| Section 4.4 |
| Section 4.2, System Modification Guide|
| Chapter 7, ccc Analyzer Guide(s) |
+---------------------------------------------------+
__ 3. (CONDITIONAL) Copy Load Module for the CICS Analyzer
Copy the appropriate load modules for the CICS
Analyzer to the sharedprefix.MICS.LOAD library based
on your installation's needs.
INPUT SOURCE Load Module
------------ -----------
The Monitor
Versions 8.0/8.1, 2.0/2.1 $CRCPRS
Versions 7.0/7.1 TMV611
EPILOG 1000 BGUDCMP
+---------------------------------------------------+
| Reference(s): Section 6.1, CICS Analyzer Guide |
+---------------------------------------------------+
__ 4. (CONDITIONAL) Define Appropriate PARMS Members
Customize the PARMS members that define account
codes, cost center codes, and the exit routines with
which they are associated.
For the ccc Analyzer and Other Standard Products
(Including FDAs, MSI and MTI):
cccACCT - Account Code Specification
cccACRT - Account Code Exit Routine
For Batch and Operations Analyzer (SMF):
ACCOUNT - Batch Accounting Structure
ACCTRTE - Batch Accounting Exit Routine
For Accounting and Chargeback (ACT):
COSTCTR - Accounting Cost Center Structure
COSTRTE - Accounting Cost Center Exit Routine
For VAX/VMS Analyzer (DEX):
DEXACRTD - DEX Disk Usage Accounting Exit Routine
+---------------------------------------------------+
| Reference(s): Section 2.3.1.7, all subsections |
| Section 4.1, Accounting and |
| Chargeback User Guide |
| Chapter 7, ccc Analyzer Guide(s) |
+---------------------------------------------------+
For MTI Components supporting account codes:
cccACCT - Account Code Specification
cccACRT - Account Code Exit Routine
__ 5. (CONDITIONAL) Execute JCLGENUC for MTI Components
During the creation of an MTI component,
sharedprefix.MICS.PARMS(cccINPUT) is generated. This
member contains the data sets that will be used during
component creation to determine which CA NSM
performance management resources and resource-subtypes
will be included in the component.
Ensure that this member contains the input data sets
for this component.
If changes were made to cccINPUT, then
__ Edit sharedprefix.MICS.PARMS(JCLGENUC) and copy the
contents of sharedprefix.MICS.PARMS(JCL$0ccc) into
this member (JCLGENUC).
__ Submit the following job:
'sharedprefix.MICS.CNTL(JCLGENUC)'
Ensure that there are no error messages in MICSLOG or
SYSTSPRT, that the MICSLOG contains the normal
termination message BAS10999I, and that the job
completes with a condition code of zero.
+---------------------------------------------------+
|Reference(s):Section 8.5, System Modification Guide|
+---------------------------------------------------+
__ 6. Execute cccCGEN for Each Product
Generate the product.
Run the component generation process for each product,
where ccc is the component identifier.
Submit the following job:
' sharedprefix.MICS.CNTL(cccCGEN)'
Ensure that there are no error messages in ISPLOG
and MICSLOG; that MICSLOG contains the normal termination
message, BAS60199I; and that the job completes with a
condition code of zero.
Check off each component generation as it is done,
running the BASCGEN first:
__ BASCGEN
__ ACTCGEN __ ASTCGEN __ AUMCGEN __ CICCGEN
__ DB2CGEN __ DEXCGEN __ HSMCGEN __ IDMCGEN
__ IMSCGEN __ MQSCGEN __ PWRCGEN __ RMFCGEN
__ SMFCGEN __ SNTCGEN __ SRLCGEN __ TLMCGEN
__ TDMCGEN __ TSOCGEN __ VCACGEN __ VMCCGEN
__ VTSCGEN __ WEBCGEN
__ cccCGEN for FDA, MSI, and MTI (if applicable)
+---------------------------------------------------+
| Reference(s): Section 3.4.3 |
+---------------------------------------------------+
MTI Components
___ (___) - ____________________________
___ (___) - ____________________________
************************************************************
* Repeat Steps 2 through 6 in this section for all *
* products that have been checked off for generation. *
************************************************************
