|
|
|
This chapter shows you how to plan for the installation of
CA MICS, from the general concepts which must be understood
to the details of coding the members of the CA MICS parameter
library used by the actual installation process. The
organization and staffing tasks are identified as well. If
you have a question at any time during your review of the
material presented here, feel free to contact CA MICS Product
Support.
The mechanics of the CA MICS installation process are
documented in Chapter 3 of this manual, which includes a set
of checklists that describe each installation step. This
process has many steps, but none of them are difficult. The
"work" of installing CA MICS is gaining the necessary
understanding of your installation and its needs, and
translating that understanding into CA MICS parameters. This
chapter leads you through all of the planning and parameter
specifications required for a successful installation. In
particular, this chapter calls for you to make a number of
policy decisions, fill out a number of worksheets, and
translate the worksheet entries into the corresponding
CA MICS parameter library member entries. This effort
represents the most time consuming portion of the
installation process.
Note: The focus of this chapter is on initial installation of
CA MICS. Bringing up a new version of CA MICS at a site
where it is currently installed or applying maintenance to
the installed system is covered in special write-ups shipped
with new releases and maintenance.
We recommend that the installation process be managed as
a five-phase project:
Phase 1: Personnel assignment and preparation.
Phase 2: Preparing your site for CA MICS.
Phase 3: CA MICS implementation planning and parameter
specification.
Phase 4: CA MICS installation and check-out.
Phase 5: Turnover of CA MICS as a production system.
Phases 1 through 3 are covered in this chapter. The
Installation chapter provides a detailed, step-by-step plan
for phases 4 and 5. The following are short descriptions of
each of the tasks in the above five phases.
Phase 1: Personnel Assignment and Preparation.
Task 1-1: Establish and staff the positions of CA MICS
System Administrator and CA MICS Information
Coordinator.
Task 1-2: Have these people attend CA MICS courses:
o CA MICS Concepts and Facilities
o Implementing CA MICS
Task 1-3: Have the assigned personnel review the
contents of the CA MICS System Administrator
Guide so that the latest information on the
state of the CA MICS system will be used in
succeeding tasks.
Phase 2: Preparing Your Site for CA MICS.
Task 2-1: CA MICS requires CA LMP (License Management
Program), one of the CA Common Services for
z/OS, before you can install or run CA MICS.
For a CA MICS oriented discussion of CA LMP,
see section 3.2.2 of this guide.
For a full description of the procedure for
defining the CA LMP execution key to the
CAIRIM parameters, see the section on CA LMP
in the CA Common Services for z/OS
documentation.
Task 2-2: We recommend that a separate SAS library be
established for exclusive use by the CA MICS
database update process. While any level of
SAS may be used for inquiries into the
database, CA MICS is extremely sensitive to
the version of SAS with which the database is
updated.
Task 2-3: Ensure that the data collection processes in
place are adequate to support CA MICS.
CA MICS may require the use of various options
in the data collection programs themselves to
provide the best advantages of the product.
Review collection options in use at your site
for compatibility with CA MICS for each of the
products whose data you will analyze with
CA MICS.
Task 2-4: Task 2-4 is necessary only if you will be
using the CA MICS Space Analyzer.
To begin DASD data collection, ensure that the
CA MICS Space Collector is installed and
operational. See the CA MICS Space Collector
Guide for installation and operation
instructions.
Phase 3: CA MICS Implementation Planning and Parameter
Specification.
Task 3-1: Reproduce the CA MICS Installation Worksheets
(distributed with the CA MICS system).
Task 3-2: Define the structure of the database complex
that you will install.
Task 3-3: Define the database complex JCL parameters in
JCLDEFC and USERJCL.
Task 3-4: Define the account code structure to be used
by the CA MICS products your site is licensed
to use. Also define the SAS routines that
assign values to the account code data
elements. Code the structure and SAS logic in
sharedprefix.MICS.PARMS. See the individual
product guides for information on account code
definition for each product.
Task 3-5: Decide how many CA MICS database units you
want to install and what products and data
sources you want in each unit. We recommend
installing a test database unit.
Task 3-6: Describe the site and computer systems for
each database unit. Parameters may be
specified at the complex-level in the
following members of sharedprefix.MICS.PARMS:
Member Defines
-------- -------------------------------
CPLXSID Computer systerm description
CPLXDEF Complex and site characteristics
CPLXZONE Time zones (shifts) to summarize
JCLDEFC JCL parameters
USERJCL User additions to JCL
Parameters for each may be coded at the
unit-level in the following members of the
prefix.MICS.PARMS library to override and/or
supplement complex-level definitions:
Member Defines
-------- -------------------------------
SYSID Computer system descriptions
SITE Certain site characteristics
ZONE Time zones (shifts) to summarize
JCLDEF JCL parameters
USERJCL User additions to JCL
Task 3-7: Describe the collected data which each
database unit is to process and code CA MICS
processing exit routines for the products to
be installed in each unit, with parameters to
be coded in members in the prefix.MICS.PARMS
library. See sections 2.3.2 and 2.3.3 and the
individual product guides for lists of these
installation planning parameters.
Task 3-8: Study your input data volumes and determine
your CA MICS online data retention
requirements. Specify these to CA MICS via
parameters in prefix.MICS.PARMS.
See the chapter on planning, installation definitions, or
parameters for information on the options for each product.
Phase 4: CA MICS Installation and Check-Out.
Task 4-1: Establish catalog entries and pointers.
Task 4-2: Load the distribution libraries.
Task 4-3: Run the job in sharedprefix.MICS.CNTL(JCLGEN0)
to provide the database complex level CLISTs
and JCL procedures.
Task 4-4: Add the procedures produced in 4-3 to the
installation procedure library (PROCLIB).
Task 4-5: Load the SAS tables and screens using the SAS
LDSASFLS job.
Task 4-6: Alter the CA MICS MONEY format if you use a
currency other than U.S. dollars or U.K.
Pounds Sterling. To use dual currency MONEY
formats to support euro conversion, see the CA
MICS Accounting and Chargeback User Guide,
Appendix C.
Task 4-7: Run the DOCAGEN1 job to build the ISPF tables
needed by CA MICS Document Access.
Task 4-8: Initialize the CA MICS Workstation Facility
(MWF).
Task 4-9: For each product being installed, use the
CA MICS Component Generator to produce the
code and generated documentation for the
product.
********************************************************
* NOTE: Tasks 4-10 through 4-18 must be repeated for *
* each database unit being installed. *
********************************************************
Task 4-10: Establish catalog entries and pointers.
Task 4-11: Create the CA MICS system libraries needed for
a database unit.
Task 4-12: Run the job in prefix.MICS.CNTL(JCLGENA) to
provide JCL procedures for the unit database
installation process.
Task 4-13: Copy the product-unique parameters into the
unit parameter library with the COPYLIBU job.
Task 4-14: Add the CA MICS procedures to the installation
procedure library (PROCLIB).
Task 4-15: Edit parameter members
Task 4-16: Submit the CA MICS Parameter Generation job to
create the SAS code necessary to tailor the
CA MICS products that you will be installing
in the database unit.
Task 4-17: Run the job in prefix.MICS.CNTL(JCLGENC) to
provide the necessary JCL procedures for the
unit database installation and operation.
Task 4-18: Configure, allocate, and initialize the
CA MICS database.
Task 4-19: Run the job in prefix.MICS.CNTL(JCLGEND) to
provide the necessary JCL procedures required
for the standard CA MICS operation.
Task 4-20: Test all exits, account codes, application
unit, and relative longevity code assignments
described in Task 3-4 above.
********************************************************
* End of steps to perform for each database unit. *
********************************************************
Task 4-21: Print the CA MICS documentation.
Task 4-22: Check that CA MICS is properly established in
your DASD and tape management systems and that
offsite backup tape storage has been arranged.
Task 4-23: Review all generated code and JCL for
conformance to installation standards.
Phase 5: Turnover of CA MICS as a Production System.
Task 5-1: Activate a test system and run the prototype
database for 3 to 7 days.
Task 5-2: Code and process each of the student exercises
defined in the Implementing CA MICS Course
using the prototype database.
Task 5-3: Initiate a regular daily database update, but
with manual scheduling. Operate in this mode
for three to seven days.
Task 5-4: Switch over to automatic scheduling of the
CA MICS update process and turn the system
over to the group in your shop responsible
for production batch job scheduling.
Task 5-5: Begin using SAS interactive inquiry facilities
for problem tracking, one-time questions, etc.
Task 5-6: Begin using MICF and Documentation Access for
database inquiry, document browse, data
element browse, and subject cross reference.
Task 5-9: Execute the Exception Value Analysis process
and set "rough-cut" exception values to
address your installation's requirements.
Task 5-10: Adjust the exception thresholds and refine the
daily exception reporting process to satisfy
your installation's requirements.
Task 5-11: Review the Management Objective Reports and
tailor their options to address your
installation's requirements.
Task 5-12: Convert existing installation reporting to
operate using the CA MICS database. Gradually
consolidate your installation's reporting
process.
Task 5-13: Define an overall management reporting plan
for using the CA MICS system as an integral
part of your installation's management
process.
Areas that may be included are the following:
o Capacity Planning
o Accounting or Chargeback
o Standards Enforcement
o Programmer Productivity Analysis
o Performance Management
o Network Service
o Storage Management
Task 5-14: Define an application interfacing plan for
using extractions from the CA MICS Database
system in other strategic applications.
Consider use of the MICF CSV file generation
facility and or CA MICS Query and Reporting to
accomplish this task.
Task 5-15: Define the report distribution and use plan.
The remainder of this chapter covers the following topics:
1 - Personnel Assignment and Preparation
2 - Preparing Your Site for CA MICS
3 - CA MICS Installation Planning and Parameter
Specification
Phases 4 and 5 are described in detail in Chapter 3,
Installation.
Chapters 2 and 3 enable you to install CA MICS in a simple,
straightforward fashion. The CA MICS Product Support Group
is available to answer questions or assist if you have
problems.
This section contains the following topics:
2.1 Personnel Assignment and Preparation
2.2 Preparing Your Site For CA MICS
2.3 Installation Planning and Parameter Specification
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |