3. Installation › 3.8 Installation Checklists › 3.8.1 Installing a CA MICS Complex › 3.8.1.4 Generate the New Database Unit(s)
3.8.1.4 Generate the New Database Unit(s)
************************************************************
* Repeat the steps in this section for each new database *
* unit in the CA MICS complex. *
************************************************************
__ 1. Define Catalog Index Prefixes/Tapeprefixes
Define the catalog index for the prefix and the
tapeprefix.
No action is required if the high-level node name
has already been defined as an alias in the master
catalog.
+---------------------------------------------------+
| Reference(s): Section 3.5.1 |
+---------------------------------------------------+
__ 2. (OPTIONAL) Worksheet Preparation
Complete the set of Installation Preparation
Worksheets for the database unit being defined.
+---------------------------------------------------+
| Reference(s): Section 2.3, all subsections |
| Chapter 7, ccc Analyzer Guide(s) |
+---------------------------------------------------+
__ 3. Execute COPYLIBS
Build the database unit libraries.
__ Edit sharedprefix.MICS.CNTL(COPYLIBS) and fill in
the parameters on the EXEC statement. DO NOT enter
parameter values on the PROC statement.
__ Submit the following job:
'sharedprefix.MICS.CNTL(COPYLIBS)'
+---------------------------------------------------+
| Reference(s): Section 3.5.2 |
+---------------------------------------------------+
__ 4. Define JCL Parameters
Define all of the members in the prefix.MICS.PARMS
library that are required by JCLGEN:
prefix.MICS.PARMS(JCLDEF)
prefix.MICS.PARMS(USERJCL)
prefix.MICS.PARMS(INPUTRDR or INPUTccc) if an SMF
source component will be installed in this database
unit
prefix.MICS.PARMS(JCLNAMES) if the default PROC or
data set names should not be used for this unit
+---------------------------------------------------+
| Reference(s): Section 2.3.3.2.1 (JCLDEF) |
| Section 2.3.3.2.2 (USERJCL) |
| Section 2.3.3.2.3 (INPUTRDR) |
| Section 2.3.3.3.2.3 (JCLNAMES) |
| Chapter 7, ccc Analyzer Guide(s) |
+---------------------------------------------------+
__ 5. Verify JCL and CLIST Attributes
Verify the JCL and CLIST attributes for each CA MICS
product by reviewing
sharedprefix.MICS.PARMS(JCL$Iccc), where ccc is the
three character component identifier. If changes are
required, make the changes in
prefix.MICS.PARMS(JCLINFO).
+---------------------------------------------------+
| Reference(s): Section 2.3.3.3.2.2 (JCLINFO) |
+---------------------------------------------------+
__ 6. Generate Unit Installation Jobs
Generate the CA MICS Unit Installation Jobs.
__ Edit prefix.MICS.CNTL(JCLGENA). Enter the
parameters on the EXEC statement and the data set
name (DSN=) parameter on the //ULOCKIT DD
statement.
__ Submit the following job:
'prefix.MICS.CNTL(JCLGENA)'
+---------------------------------------------------+
| Reference(s): Section 3.5.3.2 |
+---------------------------------------------------+
__ 7. Review JCL in PROCJOB2
Check the JCL generated by JCLGENA by examining
the following members in prefix.MICS.CNTL:
PROCJOB2 MICSNDB MICSDU
If the JCL and JES parameters do not meet your
installation's standards, update the
prefix.MICS.PARMS members JCLDEF or USERJCL and
resubmit JCLGENA.
+---------------------------------------------------+
| Reference(s): Section 3.3.3 |
+---------------------------------------------------+
__ 8. Execute PROCJOB2
Move the first group of CA MICS cataloged JCL
procedures to the production PROC library by
submitting the following job:
'prefix.MICS.CNTL(PROCJOB2)'
+---------------------------------------------------+
| Reference(s): Section 3.5.4 |
+---------------------------------------------------+
__ 9. Execute COPYLIBU
Move the CA MICS parameter library members that are
dependent on the products installed in this database
unit. Submit the following job:
'prefix.MICS.CNTL(COPYLIBU)'
+---------------------------------------------------+
| Reference(s): Section 3.5.2.2 |
+---------------------------------------------------+
__ 10. Define Required Parameters
Define the required PARMS members.
__ CA MICS base platform (BAS):
'prefix.MICS.PARMS(SYSID)'
'prefix.MICS.PARMS(ZONE)'
'prefix.MICS.PARMS(SITE)'
Update the members in prefix.MICS.PARMS for the
appropriate products.
__ CA MICS Analyzer Option for MeasureWare (AUM):
'prefix.MICS.PARMS(INPUTAUM)'
'prefix.MICS.PARMS(AUMAURT)'
'prefix.MICS.PARMS(AUMOPS)'
__ CA MICS Analyzer Option for VAX/VMS (DEX):
'prefix.MICS.PARMS(INPUTDEX)'
'prefix.MICS.PARMS(DEXOPS)'
__ CA MICS Analyzer Option for IMS (IMS):
'prefix.MICS.PARMS(INPUTIMS)'
'prefix.MICS.PARMS(IMSAURT)'
'prefix.MICS.PARMS(IMSOPS)'
'prefix.MICS.PARMS(IMSRLRT)'
'prefix.MICS.PARMS(IMSSPND)'
__ CA MICS Analyzer Option for VSE/Power (PWR):
'prefix.MICS.PARMS(INPUTPWR)'
'prefix.MICS.PARMS(PWRCONFG)'
'prefix.MICS.PARMS(PWRGROUP)'
'prefix.MICS.PARMS(PWRGPRTE)'
'prefix.MICS.PARMS(PWROPS)'
'prefix.MICS.PARMS(PWRTNRTE)'
__ CA MICS System Reliability Analyzer Option (SRL):
'prefix.MICS.PARMS(INPUTSRL)'
'prefix.MICS.PARMS(SRLDEVS)'
'prefix.MICS.PARMS(SRLOPS)'
__ CA MICS Tandem Option (TDM):
'prefix.MICS.PARMS(INPUTTDM)'
'prefix.MICS.PARMS(TDMOPS)'
__ CA MICS Tape Analyzer Option, TLM Component:
'prefix.MICS.PARMS(INPUTTLM)'
'prefix.MICS.PARMS(TLMOPS)'
'prefix.MICS.PARMS(VOLGPRTE)'
__ Field Developed Applications (FDAs) for MSI:
'prefix.MICS.PARMS(cccOPS)'
__ Field Developed Applications (FDAs) for MTI:
'prefix.MICS.PARMS(cccOPS)'
'prefix.MICS.PARMS(INPUTccc)'
'prefix.MICS.PARMS(cccSYSID)'
__ CA MICS Analyzer Option for VM/CMS (VMC):
'prefix.MICS.PARMS(INPUTVMC)'
'prefix.MICS.PARMS(VMCOPS)'
****************************************************
* --------------INPUT SOURCE NOTE------------------*
* *
* The following components may use SMF data as an *
* input source: *
* AST, CIC, DB2, HSM, IDM, MQS, RMF, *
* SMF, SNT, VTS, TSO, VCA, WEB, and *
* FDAs (if applicable) *
* *
* For the components listed above, you must choose *
* one of the alternative methods shown below. *
* These specifications identify the data set names *
* containing the raw data that will be processed *
* by the unit's DAILY update job. *
* *
* (1) If DAYSMF ON is specified in *
* prefix.MICS.PARMS(JCLDEF), then you must *
* identify the input data set names in *
* prefix.MICS.PARMS(INPUTRDR). *
* *
* (2) If DAYSMF OFF is specified in *
* prefix.MICS.PARMS(JCLDEF) you must *
* identify the input data set names in *
* prefix.MICS.PARMS(INPUTccc) for each *
* component in the unit. *
* *
* (3) If this component is in a unit by itself, *
* then you must identify the input data set *
* names in prefix.MICS.PARMS(INPUTRDR). *
* *
****************************************************
__ CA MICS CA ASTEX Option (AST):
'prefix.MICS.PARMS(INPUTAST)'
'prefix.MICS.PARMS(ASTAURT)'
'prefix.MICS.PARMS(ASTOPS)'
__ CA MICS Analyzer Option for CICS (CIC):
'prefix.MICS.PARMS(INPUTCIC)'
'prefix.MICS.PARMS(CICALONE)'
'prefix.MICS.PARMS(CICAURT)'
'prefix.MICS.PARMS(CICMSAC)'
'prefix.MICS.PARMS(CICOPS)'
'prefix.MICS.PARMS(CICRLRT)'
'prefix.MICS.PARMS(CICTHRSH)'
__ CA MICS Analyzer Option for DB2 (DB2):
'prefix.MICS.PARMS(INPUTDB2)'
'prefix.MICS.PARMS(DB2OPS)'
__ CA MICS Analyzer Option for CA IDMS (IDM):
'prefix.MICS.PARMS(INPUTIDM)'
'prefix.MICS.PARMS(IDMAURT)'
'prefix.MICS.PARMS(IDMOPS)'
'prefix.MICS.PARMS(IDMRLRT)'
'prefix.MICS.PARMS(IDMRPTS)'
__ CA MICS Analyzer Option for MQSeries (MQS):
'prefix.MICS.PARMS(INPUTMQS)'
'prefix.MICS.PARMS(MQSOPS)'
__ CA MICS Hardware and SCP Analyzer (RMF):
'prefix.MICS.PARMS(INPUTRMF)'
'prefix.MICS.PARMS(RMFOPS)'
__ CA MICS Batch and Operations Analyzer (SMF):
'prefix.MICS.PARMS(INPUTSMF)'
'prefix.MICS.PARMS(JOBGROUP)'
'prefix.MICS.PARMS(JOBGPRTE)'
'prefix.MICS.PARMS(PRINTDEF)'
'prefix.MICS.PARMS(SMFOPS)'
'prefix.MICS.PARMS(SMFUOPTS)'
'prefix.MICS.PARMS(TURNRTE)'
__ CA MICS Tape Analyzer Option, VTS Component:
'prefix.MICS.PARMS(INPUTVTS)'
'prefix.MICS.PARMS(VTSOPS)'
'prefix.MICS.PARMS(VTSCMPID)'
__ CA MICS Network Analyzer Option (SNT):
'prefix.MICS.PARMS(INPUTSNT)'
'prefix.MICS.PARMS(NETGROUP)'
'prefix.MICS.PARMS(NETGPRT)'
'prefix.MICS.PARMS(NETAPPL)'
'prefix.MICS.PARMS(SNTCIDRT)'
'prefix.MICS.PARMS(SNTNIDRT)'
'prefix.MICS.PARMS(SNTOPS)'
'prefix.MICS.PARMS(SNTPLURT)'
'prefix.MICS.PARMS(SNTRPTD)'
'prefix.MICS.PARMS(SNTRPTM)'
__ CA MICS Analyzer for TSO:
'prefix.MICS.PARMS(INPUTTSO)'
'prefix.MICS.PARMS(TSOAURT)'
'prefix.MICS.PARMS(TSOOPS)'
__ CA MICS Space Analyzer Option (VCA):
'prefix.MICS.PARMS(INPUTHSM)'
'prefix.MICS.PARMS(INPUTVCA)'
'prefix.MICS.PARMS(HSMOPS)'
'prefix.MICS.PARMS(VCAOPS)'
__ CA MICS Web Analyzer Option (WEB):
'prefix.MICS.PARMS(INPUTWEB)'
'prefix.MICS.PARMS(WEBOPS)'
'prefix.MICS.PARMS(WEBSLIST)'
'prefix.MICS.PARMS(WLECONF)'
'prefix.MICS.PARMS(WLESCRPT)'
__ Field Developed Applications (FDAs) using SMF data
as input source:
'prefix.MICS.PARMS(INPUTccc)'
***IMPORTANT****IMPORTANT***IMPORTANT****IMPORTANT***
* *
* FDAs may or may not use SMF data as an input *
* source. *
* *
* CA MICS does NOT provide an automated interface *
* to CA SMF Director from within an FDA. This *
* means that CA MICS will NOT be able to read the *
* CA SMF Director duplicate split index and obtain *
* the necessary input files. However, any SMF data*
* sets output from CA SMF Director may still be *
* directly input as standard SMF data. *
* *
***IMPORTANT****IMPORTANT***IMPORTANT****IMPORTANT***
+---------------------------------------------------+
| References: Section 2.3.2, all subsections |
| Section 2.3.3.2, all subsections |
| Chapter 7, ccc Analyzer Guide(s) |
| Section 7.6, System Modification |
| Guide (for MSI) |
| Section 8.7, System Modification |
| Guide (for MTI) |
| Section 1.5.2.3, CA ASTEX Option |
| Guide |
| Section 7.2.2, Application |
| Extension Option for Tandem Guide |
+---------------------------------------------------+
__ 11. (OPTIONAL) Update DBMODEL
Update prefix.MICS.PARMS(DBMODEL).
The COPYLIBU job generated the DBMODEL parameter
library member. Review and modify the DBMODEL
contents.
Change the retention limits on the FILE statements
according to your retention needs.
+---------------------------------------------------+
| Reference(s): Section 2.3.4 |
| Chapter 7, System Modification |
| Guide, for user components |
+---------------------------------------------------+
__ 12. (OPTIONAL) Update COMPRESS
Update prefix.MICS.PARMS(COMPRESS).
The COPYLIBU job generated the COMPRESS parameter
library member. Review and modify the COMPRESS
contents.
+---------------------------------------------------+
| Reference(s): Section 2.3.2.6 |
+---------------------------------------------------+
__ 13. Review UNITGEN Options
Review sharedprefix.MICS.PARMS(UNITGEN) for the
options in effect.
+---------------------------------------------------+
| Reference(s): Section 5.6.1 |
+---------------------------------------------------+
__ 14. Execute UNITGEN
Submit the following job:
'prefix.MICS.CNTL(UNITGEN)'
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
If the UNITGEN NOAUTOSUBMIT, or UNITGEN AUTOSUBMIT and
NOOPJCL parameters have been specified, UNITGEN will
complete with a normal return code of 4. Otherwise,
UNITGEN and UNITGEN1 should complete with a return
code of 0.
__ 15. (CONDITIONAL) Execute UNITGEN1
Perform this step only if your installation has
specified
UNITGEN NOAUTOSUBMIT
You must manually submit the UNITGEN1 job to perform
the required JCL and parameter generations.
After the UNITGEN job from the previous step
completes successfully, submit the following job:
'prefix.MICS.CNTL(UNITGEN1)'
__ 16. Verify UNITGEN1 Results
Verify that the UNITGEN1 job executed successfully.
The UNITGEN1 job contains multiple steps that perform
COPYLIBU, CYCLEGEN, JCLGEN, cccPGEN, and GDGSGEN
processing or part of it.
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
All steps should complete with a return code of zero.
If errors are encountered during UNITGEN1 job
execution, correct the errors and rerun UNITGEN and
UNITGEN1 jobs respectively.
+--------------------------------------------------+
| Reference(s): Sections 5.6 and 5.6.1 |
+--------------------------------------------------+
__ 17. Execute JCLGENC
Generate the CA MICS database set-up PROCS. Submit
the following job:
'prefix.MICS.CNTL(JCLGENC)'
+---------------------------------------------------+
| Reference(s): Section 3.5.3.3 |
+---------------------------------------------------+
__ 18. Execute PROCJOB3
Move CA MICS database set-up PROCS to the installation
PROCLIB by submitting the following job:
'prefix.MICS.CNTL(PROCJOB3)'
+---------------------------------------------------+
| Reference(s): Section 3.5.4 |
+---------------------------------------------------+
__ 19. (CONDITIONAL) Execute JCLGEND
Perform this step only if your installation has
specified
UNITGEN NOOPJCL
If NOOPJCL is specified, UNITGEN1 did not generate the
CA MICS operational jobs.
To generate these jobs, submit the following job:
'prefix.MICS.CNTL(JCLGEND)'
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
All steps should complete with a return code of zero.
+---------------------------------------------------+
| Reference(s): Section 5.6.1 |
+---------------------------------------------------+
__ 20. Complete Accounting and Chargeback Processes
If Accounting and Chargeback is being installed,
define the parameters and execute the generation
processes required for this product. Use the
checklists in the Accounting and Chargeback User
Guide. Once you have completed the checklist sections
that deal with planning, installation, and activation;
continue the installation process.
+---------------------------------------------------+
|Reference(s): Chapter 2, Accounting and Chargeback |
| User Guide |
+---------------------------------------------------+
__ 21. (OPTIONAL) Estimate Database Space
Estimate the database space to allocate on disk.
Review the JCL in prefix.MICS.CNTL(DBSIZE). The input
data sets should contain data of about one day.
__ Submit the following job:
'prefix.MICS.CNTL(DBSIZE)'
+---------------------------------------------------+
| Reference(s): Section 2.3.4.2 |
+---------------------------------------------------+
__ 22. Allocate Database Files
Allocate the Online Database and associated files.
__ Edit prefix.MICS.CNTL(ALLOCATE) and fill in the
SPACE, VOLSER, and UNIT keyword values.
__ Submit the following job:
'prefix.MICS.CNTL(ALLOCATE)'
+---------------------------------------------------+
| Reference(s): Section 3.5.6.2 |
+---------------------------------------------------+
__ 23. Review EXECDEF
Review the default values for the dynamic execution
options in prefix.MICS.PARMS(EXECDEF) and update as
needed. Carefully review the entries affecting data
retention limits.
+---------------------------------------------------+
| References: Section 2.3.5 |
| Section A.3 |
| Section 7.3.6 Batch and Operations |
| Analyzer Guide |
+---------------------------------------------------+
__ 24. Initialize Daily Audit Tape for Accounting and
Chargeback
If Accounting and Chargeback is being installed in
this database unit, initialize the daily audit tape
used for journal consolidation as the first tape in a
generation data group series. Submit the following
job:
'prefix.MICS.CNTL(ACTINITA)'
__ 25. Incremental Update Preparation
If you activated an incremental update for one or more
products in this unit database, run the cccIUALC job
for each of these products. The cccIUALC job
allocates the product's incremental update checkpoint
and database files.
__ Edit the member according to your organization's
data set allocation parameter standards and DASD
space requirements. Submit the following job:
'prefix.MICS.CNTL(cccIUALC)'
__ If you specified
INCRDB TAPE
for one or more of these products, run the
product's cccIUGDG job to create GDG indices for
the incremental update tape database files. Submit
the following job:
'prefix.MICS.CNTL(cccIUGDG)'
+---------------------------------------------------+
| Reference(s): Chapter 7, ccc Analyzer Guide(s) |
+---------------------------------------------------+
__ 26. Initialize Database Checkpoint File
Before performing the first database update,
initialize the checkpoint file. Submit the following
job:
'prefix.MICS.CNTL(CKPTINIT)'
+---------------------------------------------------+
| Reference(s): Section 3.5.7 |
+---------------------------------------------------+
__ 27. Review Generated Unit
The system is fully generated and ready for checkout.
Make a final review of all definitions and JCL,
applying any final user modifications.
+---------------------------------------------------+
| Reference(s): Section 3.5.7 |
+---------------------------------------------------+
__ 28. Execute DAILY
Run the first daily process. Submit the following
job:
'prefix.MICS.CNTL(DAILY)'
or
Use the Operational Status and Tracking DAILY command
in MWF to submit daily processing.
+---------------------------------------------------+
| Reference(s): Section 3.5.7 and Chapter 4 |
+---------------------------------------------------+
__ 29. (OPTIONAL) Verify Results in Database
Run a database check job for each product in the unit
to verify that key database definitions have been
correctly defined and implemented. Submit the
following job:
'prefix.MICS.CNTL(cccCHECK)'
+---------------------------------------------------+
| Reference(s): Section 3.5.7 |
+---------------------------------------------------+
__ 30. (OPTIONAL) Ensure Backup and Restore Are Valid
Run the backup and restore jobs. Submit the following
jobs:
'prefix.MICS.CNTL(BACKUP)'
'prefix.MICS.CNTL(RESTORE)'
or
Use the Operational Status and Tracking BACKUP and
RESTORE commands in MWF to submit the processing.
+---------------------------------------------------+
| Reference(s): Section 3.5.7 and Chapter 4 |
+---------------------------------------------------+
__ 31. Implement Production Operation
If the database unit being installed is a production
unit, implement production operation for CA MICS daily
processing.
+---------------------------------------------------+
| Reference(s): Section 3.7.1 |
+---------------------------------------------------+
************************************************************
* Repeat the steps in this section for each new database *
* unit in the complex. *
************************************************************
