Database Unit Control Definitions

The control definitions define:
mics142
The control definitions define:
  • The
    MICS
    products that are used
  • The database name
  • The products that take their input from SMF. SMF is an optional data source.
  • The data set names, that is qualifiers or prefixes that are used for data set naming and cataloging.

COMPLEXPARMS

(Optional) Controls the parameter sharing status. 'YES' indicates that parameter sharing is active; 'NO' deactivates parameter sharing. If used, this parameter must be the first statement in JCLDEFC.
For more information about JCLGEN Parameter Sharing, see JCLGEN Parameter Sharing.

DATABASE

A DATABASE statement must be provided. The first parameter is the database name, a one through eight character name that is used to identify the database during generation. The name begins with an alphabetic character and cannot contain any special values or embedded blanks.
The second parameter, following the database name, is a one-character JCL procedure identifier that is named the Database Identifier. Valid values are A-Z and 0-9. This identifier must be specified; a blank is
not
a valid identifier.
Note
: Use numeric database identifiers (0-9) until you have exhausted all possible alphabetic identifiers (A-Z). Due to syntax restrictions on ddnames and SAS names, special constructs are required for numeric units. For example, MICF allocates the A unit DAYS timespan with the ddname ADAYS and for the Hardware Information Area, references this ddname by the &AHARD macro variable. However, for the 5 unit, the ddname and macro variable are N5DAYS and &_5HARD.
The identifier is appended to the names of the following JCL procedures that are created by JCLGEN:
MICSDB
Access database DISP=OLD
MICSDU
Batch TSO Execution
MICSNDB
Invoke SAS without database allocation.
MICSSHR
Access database DISP=SHR
When it is necessary to have different JCL procedures for each
MICS
database unit at an installation. To prevent two databases from using the same procedure identifier, a table of previously used identifiers is maintained in sharedprefix.MICS.GENLIB(DBTABLE). This table is checked to see whether the identifier specified has been used with a different PREFIX statement. If the identifier has been previously used with a different PREFIX statement, JCLGEN processing is immediately terminated.
Since the DBTABLE is in sharedprefix.MICS.GENLIB, the duplicate procedure protection extends only to
MICS
unit databases in a complex. The
MICS
System Administrator is responsible to ensure the uniqueness of the procedure identifier, when multiple databases do not share shareprefix.MICS.GENLIB library. For techniques on using alternate procedure names for multiple complexes sharing a single PROCLIB, see
MICS
User Names Table (JCLNAMES).
The third keyword parameter on the DATABASE statement is the database type. The possible values are PRIMARY, UNIT, SPECIAL, or TEST. For preliminary testing purposes, a TEST database unit can be installed without defining a PRIMARY database unit. However, the first production database unit that is installed in a database complex should have PRIMARY specified. Only the PRIMARY database backs up the complex level data libraries. Other database units can then be designated as UNIT, SPECIAL, or TEST.
Information from TEST database units is not included in
MICS Accounting and Chargeback
processing if at least one UNIT or PRIMARY unit in the complex contains
MICS Accounting and Chargeback
. TEST units are also treated differently by JCLGEN. SPECIAL databases are temporary databases for special studies or other uses.

COMPONENTS

One or more COMPONENTS statements must be provided to specify which
MICS
products should be included in the
MICS
unit. The parameters for component identification are the standard three character product identifiers.
Products that do not have processing activity at the database unit level (that is, no step in the DAILY job), can be specified but they are ignored in JCLGEN processing.PER and STG are examples of such products.
All components are optional, but at least one must be selected. Note the following special considerations:
  • BAS (
    MICS
    Platform) is not specified on the COMPONENTS statement, but is automatically included in every database unit.
  • The ACT identifier for
    MICS Accounting and Chargeback
    may not be specified in a SPECIAL database unit.
  • If you want to include sharedprefix.MICS.CAPACITY in the PRIMARY unit database BACKUP process, you can specify the CAP component on the COMPONENTS statement in the PRIMARY database unit. Otherwise, there is NO need to specify the CAP component on any COMPONENTS statement. Note, CAP is only valid when the third keyword of the DATABASE statement is PRIMARY (indicating the PRIMARY unit).
No processing support is included in the generated system for products that are not specified in the COMPONENTS statement.

SMFRECORDING

Many
MICS
products that take input from external non-SMF log files also support the standard SMF data set as an optional data source. If your site uses SMF data rather than or in addition to external non-SMF log data, code one or more SMFRECORDING statements in the JCLDEF member of the prefix.MICS.PARMS data set. Valid values include AST, CICS, HSM, IDM, SNT, and VCA. For more information about products that can use SMFRECORDING, see each Product Analyzers.
If more than one
MICS
product that takes input from SMF is specified on the COMPONENTS statement, a job step that is named DAYSMF is generated as the second step of the DAILY job. DAYSMF splits the SMF input file (defined by prefix.MICS.PARMS(INPUTRDR)) into multiple work files. One file for each
MICS
product which takes its input from SMF. The ddname of INPUTSMF is used to address the work file in DAILY job steps for products that input such work files.
If only one
MICS
product uses SMF input, JCLGEN does not create a DAYSMF step to split the SMF input file. Rather, the SMF file that is defined in prefix.MICS.PARMS(INPUTRDR) goes directly into the DAILY job step for that one product. This action improves
MICS
performance.
If you are using the optional incremental update facility, you can select to execute a stand-alone version of the DAYSMF step (the SPLITSMF job) to pre-select input data for your INCRccc jobs. The SPLITSMF job dynamically allocates and populates a data set for each
MICS
product which takes its input from SMF
and
which has been marked with the INCRSPLIT USE option in prefix.MICS.PARMS(cccOPS). The ddname of INPUTSMF is used to address the input file in the INCRccc jobs.
If CICS is specified on the SMFRECORDING statement, a DD statement for ddname INPUTSMF is generated by JCLGEN according to the preceding rules. The DAY040 step can also take input from non-SMF files that are defined in prefix.MICS.PARMS(INPUTCIC) even when SMF input is used. This action depends on the parameters that are specified on the CICOPTS statements in prefix.MICS.PARMS(CICOPS). If CICS is not specified on the SMFRECORDING statement, then the only input available to the CICS (DAY040) step in the
MICS DAILY
update job is that supplied by DD statements in prefix.MICS.PARMS(INPUTCIC). The ddnames must also be identified in prefix.MICS.PARMS(CICOPS).
If VCA is specified on the SMFRECORDING statement, a DD statement for ddname INPUTSMF is generated by JCLGEN according to the preceding rules. The DAY090 step can also take input from non-SMF files that are defined in prefix.MICS.PARMS(INPUTVCA) even when SMF input is also used. All input for the VCA Analyzer is taken from the INPUTSMF DD statement. If SMF and non-SMF data are mixed, the INPUTVCA member must contain only the DD statements to be concatenated to the INPUTSMF DD statement made by JCLGEN. If VCA is not specified on the SMFRECORDING statement, the only input available to the DAY090 step in the
MICS DAILY
update job is that supplied by DD statements in prefix.MICS.PARMS(INPUTVCA). This DD statement must define the ddname INPUTSMF.
Note:
In the appropriate Product Analyzer, see the section on planning, installation definitions, or parameters.

PREFIX

(Required) The PREFIX statement is used to identify the data sets associated with a
MICS
database unit. Since there can be more than one
MICS
database at your site, the prefix must be unique and cannot have the same value as the SHAREDPREFIX. A table of prefixes and the value of sharedprefix is maintained in sharedprefix.MICS.GENLIB(DBTABLE). A prefix can consist of more than one node (qualifier), but cannot exceed 14 characters in length.
The prefix is used to complete the data set names for the following data sets:
  • prefix.MICS.CHECKPT.DATA
  • prefix.MICS.CNTL
  • prefix.MICS.IMSSUS1
  • prefix.MICS.IMSSUS2
  • prefix.MICS.MODEL
  • prefix.MICS.MUOLIB
  • prefix.MICS.PARMS
  • prefix.MICS.RESTART.CNTL
  • prefix.MICS.USER.SOURCE
  • prefix.MICS.SPECIAL.SOURCE
  • prefix.MICS.DETAIL
  • prefix.MICS.DAYS
  • prefix.MICS.WEEKS
  • prefix.MICS.MONTHS
  • prefix.MICS.YEARS
Extra qualifiers (MICS) are added behind your prefix value unless you specify the optional NOMICSLEVEL parameter following your prefix value. For more information, see Generation of
MICS
Data Set Names.

TAPEPREFIX

(Optional) The TAPEPREFIX statement is used to identify unique tape data sets created by
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 have the same prefix that is defined on the PREFIX statement.
Note:
Many (GDG) data sets are cataloged under this index. If the prefix is a TSO user ID, it can impair that user's use of the LISTCAT command due to the voluminous output.
The TAPEPREFIX statement is used to form the name of the following
MICS
data sets:
  • tapeprefix.MICS.AUDIT.iiifff.GggggV00
  • tapeprefix.MICS.BACKUP.tttttt.GggggV00
  • tapeprefix.MICS.BACKUP.CHECKPT.GggggV00
  • tapeprefix.MICS.HISTW.iiifff.GggggV00
  • tapeprefix.MICS.HISTM.iiifff.GggggV00
  • tapeprefix.MICS.MBACKUP.tttttt.GggggV00
  • tapeprefix.MICS.MBACKUP.CHECKPT.GggggV00
Note:
In the list above, iiifff represents a
MICS
file name and tttttt is a time-span or can be SCREENS, TABLES, CAPACITY, or ISPTLIB.

Generation of
MICS
Data Set Names

You can specify whether ".MICS." follows the sharedprefix, prefix, and tapeprefix levels when data set names are generated. If you want ".MICS." appended to any of these prefixes, specify the keyword "MICSLEVEL.". If you do
not
want ".MICS." appended to any of these prefixes, specify the keyword "NOMICSLEVEL." Place the keyword "MICSLEVEL" or "NOMICSLEVEL" after, but on the same line as, the definition of SHAREDPREFIX, PREFIX, or TAPEPREFIX. When "NOMICSLEVEL" is specified, the prefix length limit increases from 14 to 19. If no keyword is specified, the default MICSLEVEL is used so that ".MICS." follows the prefix. NOMICSLEVEL Data Set Name Formation shows the resultant data set names that are formed when MICSLEVEL and NOMICSLEVEL are specified with the three prefixes.
NOMICSLEVEL Data Set Name Formation
JCLDEF Keyword Value
Data Set Names Formed
SHAREDPREFIX
EYCS MICSLEVEL
EYCS.MICS.SOURCE
PREFIX
EYPMICSLEVEL
EYP.MICS.CNTL
TAPEPREFIX
EYCT MICSLEVEL
EYCT.MICS.BACKUP.DAYS
SHAREDPREFIX
EYCS NOMICSLEVEL
EYCS.SOURCE
PREFIX
EYPNOMICSLEVEL
EYP.CNTL
TAPEPREFIX
EYCT NOMICSLEVEL
EYCT.BACKUP.DAYS
SHAREDPREFIX
EYCS
EYCS.MICS.SOURCE
PREFIX EYP.TEST.MICS4
NOMICSLEVEL
EYP.TEST.MICS4.CNTL
TAPEPREFIX EYCT.DAILY
NOMICSLEVEL
EYCT.DAILY.BACKUP.DAYS
A more comprehensive control over
MICS
data set names is available. For more information about
MICS
data set names, see
MICS
User Names Table (JCLNAMES).