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.6 Database Complex JCL Definitions (JCLDEFC) › 2.3.1.6.1 Database Complex Control Definitions
2.3.1.6.1 Database Complex Control Definitions
The following control statements define the database complex,
including the data set name qualifiers for complex-level DASD
and tape data sets, and the root sub-directory name for CA
MICS Hierarchical File System (HFS) files.
COMPLEXPARMS:
This optional statement controls the default mode for
parameter sharing. 'YES' indicates that parameter
sharing will be active for all units; 'NO' deactivates
parameter sharing. If used, this must be the first
statement in JCLDEFC.
See Section 2.3.1.6.7 for more information on JCLGEN
parameter cascading. In addition, Section 5.5 provides
an optional checklist that shows how to activate JCLGEN
parameter sharing for all units in the CA MICS Complex.
SHAREDPREFIX:
This statement defines the prefix used to uniquely
identify CA MICS data sets that are common to all CA MICS
database units. The SHAREDPREFIX should be different
from all of the database unit's PREFIXes and
TAPEPREFIXes. SHAREDPREFIX can consist of more than one
data set name node (qualifier), but cannot exceed 14
characters in length. The SHAREDPREFIX is used to
complete the data set names for the following data sets:
sharedprefix.MICS.ASM
sharedprefix.MICS.BIN
sharedprefix.MICS.CLIST
sharedprefix.MICS.CNTL
sharedprefix.MICS.DIC.TEXT
sharedprefix.MICS.DOC.TEXT
sharedprefix.MICS.DTF.INDEX
sharedprefix.MICS.GENLIB
sharedprefix.MICS.HOLD.PARMS
sharedprefix.MICS.HOLD.USER.SOURCE
sharedprefix.MICS.INC.TEXT
sharedprefix.MICS.INCLLIB
sharedprefix.MICS.ISPHLIB
sharedprefix.MICS.ISPMLIB
sharedprefix.MICS.ISPPLIB
sharedprefix.MICS.ISPSLIB
sharedprefix.MICS.ISPTLIB
sharedprefix.MICS.LIBLOAD.CNTL
sharedprefix.MICS.LOAD
sharedprefix.MICS.LOCALMOD.CNTL
sharedprefix.MICS.MACAUTOS
sharedprefix.MICS.MACLIB
sharedprefix.MICS.MCOLIB
sharedprefix.MICS.MQR.TEMPLATE
sharedprefix.MICS.MWFPDS.DATA
sharedprefix.MICS.MWFSAS.DATA
sharedprefix.MICS.OBJ
sharedprefix.MICS.PARMS
sharedprefix.MICS.PROTOLIB
sharedprefix.MICS.SASFLS
sharedprefix.MICS.SCREENS
sharedprefix.MICS.SOURCE
sharedprefix.MICS.TABLES
sharedprefix.MICS.TEST.INCLLIB
sharedprefix.MICS.TEST.SOURCE
sharedprefix.MICS.USER.SOURCE
TSHAREDPREF:
The TSHAREDPREF statement is optional. It is only used
at the complex level if you have CA MICS Accounting and
Chargeback installed and you want to maintain a complex
level audit tape.
The TSHAREDPREF statement is used to uniquely identify
tape data sets created by CA MICS. The prefix can
consist of more than one node (qualifier), but cannot
exceed 14 characters in length. If this statement is not
specified or left blank, the tape data sets will have the
same prefix defined on the SHAREDPREFIX statement.
Note that many generation data group (GDG) data sets will
be cataloged under this index. If the prefix is a TSO
user ID, it may impair that user's use of the LISTCAT
command due to the voluminous output.
The TSHAREDPREF statement is used to form the name of the
tsharedpref.MICS.MONTHC data set.
HFSROOT:
The name of the CA MICS Root Directory. This is the name
of the Hierarchical File System (HFS) sub-directory to be
used as the default location for storing HFS files for
the CA MICS Platform, CA MICS Data Integration
Applications, and CA MICS Management Applications.
Within the CA MICS Root Directory, subdirectories will
contain files for specific CA MICS products and
applications.
Note: The name of the root directory must be no longer
than 64 characters. If it is, DOC2HTML will abend.
HFSROOT defaults to
/MICS/&sharedprefix
where &sharedprefix is the value specified on the
SHAREDPREFIX statement. Note, the MICSLEVEL/NOMICSLEVEL
option does not apply to HFSROOT -- .MICS is never
appended to the &sharedprefix value when generating the
default HFSROOT string.
See Section 5.7 for more information on the CA MICS Root
Directory and HFS file usage in CA MICS.
Generation of CA MICS Data Set Names
You can specify whether or not ".MICS." follows the
sharedprefix and tsharedpref when data set names are
generated. If you want ".MICS." appended to the data set
name, specify the keyword "MICSLEVEL". If you do NOT want
".MICS." appended to the data set name, specify the keyword
"NOMICSLEVEL". Place the keyword "MICSLEVEL" or
"NOMICSLEVEL" after, but on the same line as, the definition
of SHAREDPREFIX and TSHAREDPREF. When "NOMICSLEVEL" is
specified, the SHAREDPREFIX and TSHAREDPREF length limit
increases from 14 to 19. If no keyword is specified, the
default MICSLEVEL is used so that ".MICS." follows the
sharedprefix and tsharedpref. Figure 2-7 shows examples of a
data set name generated with the same sharedprefix and
tsharedpref with both "MICSLEVEL" and "NOMICSLEVEL"
specified.
+-----------------------------------+-----------------------+
|JCLDEF Keyword Value | Data Set Names Formed |
+-----------------------------------+-----------------------+
|SHAREDPREFIX EYCS MICSLEVEL | EYCS.MICS.SOURCE |
|SHAREDPREFIX EYCS NOMICSLEVEL | EYCS.SOURCE |
+-----------------------------------+-----------------------+
|TSHAREDPREF EYCS MICSLEVEL | EYCS.MICS.ACCT.MONTHC |
|TSHAREDPREF EYCS NOMICSLEVEL | EYCS.ACCT.MONTHC |
+-----------------------------------+-----------------------+
As noted earlier, and illustrated below, the
MICSLEVEL/NOMICSLEVEL option does not apply to
the derivation of the default HFSROOT value.
+-----------------------------------+-----------------------+
|JCLDEF Keyword Value | Default HFSROOT Value |
+-----------------------------------+-----------------------+
|SHAREDPREFIX EYCS MICSLEVEL | /MICS/EYCS |
|SHAREDPREFIX EYCS NOMICSLEVEL | /MICS/EYCS |
+-----------------------------------+-----------------------+
Figure 2-7. NOMICSLEVEL Data Set Name Formation
Note that more comprehensive control over CA MICS system data
set names is available. See Section 2.3.3.3.2.3, "CA MICS
User Names Table (JCLNAMES)" for more information.
