2. Planning for Installation and Use of CA MICS › 2.3 Installation Planning and Parameter Specification › 2.3.1 Database Complex Planning and Parameters › 2.3.1.3 Parameter Generation Overview
2.3.1.3 Parameter Generation Overview
There are three types of parameter generation processes:
JCL: Custom CLISTs, MACROs, JCL jobs, and PROCs are
created. Some are used in the remainder of
the generation process, while others are used
in the operation of the CA MICS system.
JCLGEN0 through JCLGEN3, and JCLGENA through
JCLGENG are the jobs used for this generation
process. In addition, parameter tables for
use in other processes, including the online
functions, are created.
MACROs: Operational parameters are translated into
tables and into SAS macros that will be
executed by the CA MICS system. Some of the
macros refer to SAS formats that are generated
from parameters. BASPGEN and the generators
for each component being installed (for
example, SMFPGEN, RMFPGEN, CICPGEN, and so on)
are used for this process. They are executed
by the job ALLPGEN, which selects the
appropriate generators for the components that
are being installed.
DATABASE: Database definition parameters are translated
into SAS macros that will be executed by the
CA MICS system.
Figures 2-1 through 2-3 illustrate the JCL, MACROs, and
DATABASE generation process flows.
Note: The consolidated UNITGEN process is a combination of
JCL, MACRO, and DATABASE generation processing that
consolidates most generation processes for a database
unit into a single batch process. The UNITGEN process
is not specifically included in figures 2-1 through
2-3, as it is actually a composite of the database
unit-level generation jobs described in the following
tables. See section 5.6 for more information on the
UNITGEN process.
+------------------+-------------------+-------------------+
| | | |
| INPUT | JOB | OUTPUT |
+------------------+-------------------+-------------------+
| sharedprefix. | | sharedprefix. |
| MICS.CNTL | | MICS.CNTL |
| | | |
| sharedprefix. | JCLGEN0 | sharedprefix. |
| MICS.GENLIB | JCLGEN1 | MICS.MACAUTOS |
| | JCLGEN2 | |
| | | |
| sharedprefix. | | sharedprefix. |
| MICS.PARMS | | MICS.CLIST |
| | | |
| sharedprefix. | JCLGEN3 | sharedprefix. |
| MICS.PROTOLIB | | MICS.GENLIB |
| | | |
| | | sharedprefix. |
| | | MICS.ISPTLIB |
| | | |
| | | sharedprefix. |
| | | MICS.MCOLIB |
+------------------+-------------------+-------------------+
| | | |
| prefix. | | prefix. |
| MICS.PARMS | JCLGENA | MICS.CNTL |
| | JCLGENB | |
| sharedprefix. | JCLGENC | prefix. |
| MICS.GENLIB | JCLGEND | MICS.PARMS |
| | JCLGENE | |
| sharedprefix. | JCLGENF | prefix. |
| MICS.PROTOLIB | JCLGENG | MICS.MUOLIB |
| | | |
| prefix. | | prefix. |
| MICS.CNTL | | MICS.USER.SOURCE |
| | | |
| | | sharedprefix. |
| | | MICS.GENLIB |
| | | |
| | | sharedprefix. |
| | | MICS.ISPTLIB |
| | | |
| | | sharedprefix. |
| | | MICS.MACAUTOS |
| | | |
| | | sharedprefix. |
| | | MICS.SOURCE |
+------------------+-------------------+-------------------+
Figure 2-1. JCL Generation Process Flow
+------------------+-------------------+-------------------+
| INPUT | JOB | OUTPUT |
+------------------+-------------------+-------------------+
| prefix. | | prefix. |
| MICS.CNTL | | MICS.CNTL |
| | | |
| | | prefix. |
| prefix. | ALLPGEN | MICS.MUOLIB |
| MICS.PARMS | cccPGEN | |
| | | prefix. |
| | | MICS.PARMS |
| | | |
| | | prefix. |
| | | MICS.USER.SOURCE |
+------------------+-------------------+-------------------+
Figure 2-2. Macro Code Generation Process Flow
+------------------+-------------------+-------------------+
| INPUT | JOB | OUTPUT |
+------------------+-------------------+-------------------+
| prefix. | | |
| MICS.CNTL | | |
| | | Database Space |
| | DBSIZE | Estimator Report |
| prefix. | | |
| MICS.PARMS | | |
| (DBMODEL) | | |
+------------------+-------------------+-------------------+
| | | |
| prefix. | | |
| MICS.CNTL | | prefix. |
| | CYCLEGEN | MICS.USER.SOURCE |
| prefix. | | |
| MICS.PARMS | | |
| (DBMODEL) | | |
+------------------+-------------------+-------------------+
Figure 2-3. Database Generation Process Flow