3. Installation › 3.8 Installation Checklists › 3.8.1 Installing a CA MICS Complex › 3.8.1.2 Define the Database Complex
3.8.1.2 Define the Database Complex
__ 1. Execute MICSLS1
Activate the LOAD and PARMS libraries' release
dependent modules for the SAS version in use.
__ Edit sharedprefix.MICS.CNTL(MICSLS1) and fill in
the parameters on the CNVTMCO EXEC statement. Do
not enter parameters on the PROC statement.
__ Submit the following job:
'sharedprefix.MICS.CNTL(MICSLS1)'
+-------------------------------------------------+
| Reference(s): Section 3.2.5 |
+-------------------------------------------------+
NOTE: For SAS 9.1.3, use the fixed block library
created in the previous section.
__ 2. (OPTIONAL) Execute EARLYDOC
Print the CA MICS documentation guides.
If you choose to print guides before the database
complex is defined, they will only reflect the default
definitions shipped with the system.
To print CA MICS documentation guides or chapters
before defining the database complex:
__ Edit sharedprefix.MICS.CNTL(EARLYDOC) and fill in
the job card and the parameters on the EXEC
statement at the end of the member. DO NOT enter
parameter values on the PROC statement.
__ Submit the following job:
'sharedprefix.MICS.CNTL(EARLYDOC)'
+---------------------------------------------------+
| Reference(s): Section 3.6.1 |
+---------------------------------------------------+
__ 3. Define Complex Databases
Define the primary, unit, and test databases that are
to comprise your installation's database complex.
Note that the identity, contents, and options for each
database unit must be completely defined.
+---------------------------------------------------+
| Reference(s): Section 2.3.1.4 |
+---------------------------------------------------+
__ 4. Apply Required SAS Maintenance
Apply required maintenance to the SAS program library.
Ensure that a supported SAS release is being used.
Refer to the System Requirements section of the
CA MICS System Administrator Guide for any special
considerations and for the recommended maintenance for
your CA MICS copy of SAS. This section describes
modifications that are to be applied to the level of
SAS in use. Make sure that any of the zaps defined
are properly applied before proceeding.
__ 5. Review SAS Libraries
Review individual SAS libraries for CA MICS.
Refer to the System Requirements section of the
CA MICS System Administrator Guide for the levels of
SAS supported by CA MICS. Create a special set of SAS
libraries for CA MICS use only. You provide the name
of these libraries to CA MICS using the parameters in
sharedprefix.MICS.PARMS(JCLDEFC) and also in the
prefix.MICS.PARMS(JCLDEF) member for each database
unit.
NOTE: All versions of SAS supported for CA MICS
require the use of the SAS LIBRARY, AUTOLIB,
SASCNTL, SASHELP, and SASMSG data sets. Create
a copy of these data sets for CA MICS use only.
You provide the name of these data sets to
CA MICS: SASLIB, SASAUTOS, SASCONFIG, SASHELP,
and SASMSG, respectively.
+---------------------------------------------------+
| Reference(s): Section 2.3.1.6 and |
| Section 6.6, System Administrator |
| Guide, (System Requirements) |
+---------------------------------------------------+
__ 6. Customize JCLDEFC
Customize the sharedprefix.MICS.PARMS(JCLDEFC) member
to reflect your organization's standards.
+---------------------------------------------------+
| Reference(s): Section 2.3.1.6 |
+---------------------------------------------------+
__ 7. Verify Parameters in JCL$Iccc, JCLNAMES, and JCLINFO
Review the contents of the JCL$Iccc, JCLNAMES, and
JCLINFO members in sharedprefix.MICS.PARMS.
Parameters in JCL$Iccc, where ccc is the three
character component identifier, may require
modification to properly set job attributes such as
TIME=, COPIES=, JOBNAME=, CLASS=, PRTY=, and LINES=.
Make your modifications in the JCLINFO member of
sharedprefix.MICS.PARMS.
JCLNAMES may require modification if the default PROC
or data set names used by CA MICS are not acceptable
at your installation.
+---------------------------------------------------+
| Reference(s): Section 2.3.3.3.2.2 (JCLINFO) |
| Section 2.3.3.3.2.2 (JCL$Iccc) |
| Section 2.3.3.3.2.3 (JCLNAMES) |
+---------------------------------------------------+
__ 8. Customize USERJCL
Customize the sharedprefix.MICS.PARMS(USERJCL) member
to reflect organization standards.
+---------------------------------------------------+
| Reference(s): Section 2.3.3.2.2 |
+---------------------------------------------------+
__ 9. Verify ISPF Environment
Customize sharedprefix.MICS.PARMS to ensure the
correct ISPF environment is defined and that it
conforms with conventions at your site. Make updates
if needed.
This review must include the names and blocksizes for
standard ISPF data sets and the naming conventions for
data sets allocated by the CA MICS Workstation
Facility (MWF) for each user. Note that, except for
unusual requirements, the options provided in the
members JCLDEFC and JCLNAMES of
sharedprefix.MICS.PARMS should accommodate most
installations' standards.
+---------------------------------------------------+
| Reference(s): Section 3.3.6.1 |
| Section 2.3.1.6 (JCLDEFC) |
| Section 2.3.3.3.2.3 (JCLNAMES) |
+---------------------------------------------------+
__ 10. Execute JCLGEN0
Generate the database complex-level JCL.
__ Edit sharedprefix.MICS.CNTL(JCLGEN0) and define the
parameters on the EXEC statement. DO NOT enter
parameter values on the PROC statement.
__ Submit the following job:
'sharedprefix.MICS.CNTL(JCLGEN0)'
+---------------------------------------------------+
| Reference(s): Section 3.3.2 |
+---------------------------------------------------+
__ 11. Move PROCs by Executing PROCJOB1
Move CA MICS PROCs to the installation PROCLIB.
__ Check the JCL generated by JCLGEN0 by examining the
following sharedprefix.MICS.CNTL members:
PROCJOB1 MICSASM MICSCOM MICSDM MICSDOC
MICSDOCH MICSGT MICSGU MICSRPTS
__ (CONDITIONAL) You must determine whether the JCL
and JES parameters are acceptable at your
installation. If they are not, update the
sharedprefix.MICS.PARMS members JCLDEFC or USERJCL
and repeat the "Customize USERJCL" step.
OR
__ If the JCL is acceptable, move CA MICS PROCs to the
installation PROCLIB by submitting the following
job:
'sharedprefix.MICS.CNTL(PROCJOB1)'
+---------------------------------------------------+
| Reference(s): Section 3.3.3 |
+---------------------------------------------------+
__ 12. Customize Money Format
Customize monetary formats used with CA MICS if
desired. CA MICS provides the MONEY and MONEYR
formats for writing monetary values in output reports.
A corresponding informat, @MONEY, is used for reading
monetary values. If you use some currency notation
other than U.S. dollars, edit sharedprefix.MICS.SOURCE
alter the format or the informat for use with your
currency notation.
+---------------------------------------------------+
| Reference(s): Section 3.3.5 |
+---------------------------------------------------+
__ 13. Execute DOCAGEN1
Build the ISPF tables needed by CA MICS Document
Access. Submit the following job:
'sharedprefix.MICS.CNTL(DOCAGEN1)'
+---------------------------------------------------+
| Reference(s): Section 3.3.7 |
+---------------------------------------------------+
__ 14. Activate MWF
Activate the CA MICS Workstation Facility (MWF).
Read the referenced sections listed below to set up
the CA MICS ISPF environment. Enter the CA MICS
online environment and specify your site's parameters.
Note, you may only enter the CA MICS Administrator
Facility automatically the first time you enter the
environment.
+---------------------------------------------------+
| Reference(s): Sections 3.3.6 and 4.4 |
+---------------------------------------------------+
__ 15. (OPTIONAL) Activate MWF User Authorization
Activate the MWF User Authorization feature.
If you do not wish to limit access to CA MICS, skip
this step.
+---------------------------------------------------+
| Reference(s): Section 4.4.3 |
+---------------------------------------------------+
__ 16. Execute LDSASFLS
Load the SAS Screen Files and CA MICS Tables Data
Area. Submit the following job:
'sharedprefix.MICS.CNTL(LDSASFLS)'
+---------------------------------------------------+
| Reference(s): Section 3.3.4 |
+---------------------------------------------------+
