5. Maintenance › 5.8 Add New System ID or LPAR to an Existing Database
5.8 Add New System ID or LPAR to an Existing Database
The following checklist assists you in adding a new SYSID or
LPAR for PR/SM to a CA MICS database unit. It assumes that
the operating system measurements have not changed.
__ 1. Review References to SYSID or ORGSYSID
Review option statements in the following members for
any reference to SYSID or ORGSYSID. Determine whether
logic for the new SYSID or LPAR should be added to the
account code derivation logic routines, and update as
required.
'sharedprefix.MICS.PARMS(ACCTRTE)'
'sharedprefix.MICS.PARMS(cccACRT)'
where ccc is the component identifier.
__ 2. (OPTIONAL) Execute the RMFCGEN
The CPUID parameter in
'sharedprefix.MICS.GENLIB(RMFGENIN)' may need to be
modified. If changes are made, submit the following
job to accept your updates:
'sharedprefix.MICS.CNTL(RMFCGEN)'
Ensure that there are no error messages in ISPLOG and
MICSLOG, and that the job completes with a condition
code of zero.
__ 3. (OPTIONAL) Review References to SYSID or ORGSYSID in
EXITS
Review the #cccEXIT members in
'sharedprefix.MICS.SOURCE,' where 'ccc' is the
component identifier or architecture (BAS). Determine
whether the user exits in these members contain any
reference to SYSID or ORGSYSID. Update each exit as
required.
__ 4. Review Installation Customization for SYSID References
Review user-defined SAS code and formats for SYSID
specific references.
__ 5. Verify Checkpoint File Size
Review Checkpoint File size to ensure that there are
enough entries for the systems/subsystems that are
being added.
+---------------------------------------------------+
| Reference(s): Section 2.3.2.4 |
+---------------------------------------------------+
__ 6. (OPTIONAL) Specify Complex Computing System Parameter
Definitions
Specify the complex-level computing system parameter
definitions. Complex-level computing system
definitions are located in
sharedprefix.MICS.PARMS(CPLXSID). Carefully read the
referenced section listed below before specifying the
option values.
+---------------------------------------------------+
| Reference(s): Section 2.3.1.9 |
+---------------------------------------------------+
__ 7. (OPTIONAL) Execute CPLXGEN
Run the CPLXGEN job to generate complex option
definition global switches, system and time zone
definitions, default YEARS time-span, week start, and
fiscal calendar parameters. Submit the following job:
'sharedprefix.MICS.CNTL(CPLXGEN)'
+---------------------------------------------------+
| Reference(s): Section 2.3.1.8 (CPLXDEF) |
| Section 2.3.1.9 (CPLXSID) |
| Section 2.3.1.10(CPLXZONE) |
| Section 3.4.2 (cccGENIN) |
+---------------------------------------------------+
*************************************************************
* Repeat the above steps for each database unit that will *
* process data from the new SYSID or LPAR. *
*************************************************************
__ 8. Suspend Operation
Suspend production operations for the unit database by
using the Operational Status and Tracking SUSPEND
command in MWF to deactivate production scheduling.
__ 9. Review and Update 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 |
+---------------------------------------------------+
__ 10. 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 |
+---------------------------------------------------+
__ 11. Review/Modify UNITGEN Options
Review sharedprefix.MICS.PARMS(UNITGEN) for the
options in effect.
+---------------------------------------------------+
| Reference(s): Section 5.6.1 |
+---------------------------------------------------+
__ 12. 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.
__ 13. (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)'
__ 14. 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 |
+--------------------------------------------------+
__ 15. 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 |
+---------------------------------------------------+
__ 16. (CONDITIONAL) Define Accounting Rates
If Accounting and Chargeback is installed, use the
CA MICS Workstation Facility (MWF) to complete the
RATETBL panels. Select option 4;2;3;6 from the MWF
primary options panel. The JCL for the MAGRUN will be
displayed automatically if any of the RATETBL
specifications are altered.
NOTE: If the logical SYSID is checked before
assigning a comp code value, review the
ACTFnnnn members in sharedprefix.MICS.SOURCE,
where 'nnnn' is the number of an accounting
comp code. If the CPU processor or processor
speed is used in determining your site's
accounting logic, then logic for the new CPU or
LPAR will need to be added.
__ 17. Final Review
The system is fully generated and ready for check-out.
Make final review of all definitions and JCL, applying
any final user modifications at this time. Also
review the prefix.MICS.USER.SOURCE(#BASEXIT) member.
Determine if the _USRSEL exit contains any references
to ORGSYSID. Update the exit if required.
Optionally, review the #cccEXIT members in
prefix.MICS.USER.SOURCE, where 'ccc' is the component
identifier. Determine whether the user exits in these
members contain any reference to ORGSYSID or SYSID.
Update each exit as required.
__ 18. Resume Operations
Enable CA MICS operational jobs for this unit
database. Use the Operational Status and Tracking
RESUME command in MWF to enable CA MICS operational
jobs.
__ 19. Resume Daily Processing
Use the Operational Status and Tracking DAILY command
in MWF to resume daily processing.
+---------------------------------------------------+
| Reference(s): Section 3.5.7 |
+---------------------------------------------------+
*************************************************************
* Repeat the above steps for each database unit that will *
* process data from the new SYSID or LPAR. *
*************************************************************
__ 20. (OPTIONAL) Execute EXTFILE
If your site uses external files for processing,
select option 4;2;3;7 from the MWF primary option
panels. Examine the algorithms and rates for external
files. If any external file specifications are added
or changed, submit the following:
Submit 'sharedprefix.MICS.CNTL(EXTFILE)'
__ 21. Notify Affected Users
Notify the affected users that a new SYSID or LPAR has
been added to CA MICS so that they can account for the
difference in CPU trend reports, chargeback, or
database inquiries.
