2. Planning for Installation and Use of CA MICS › 2.3 Installation Planning and Parameter Specification › 2.3.3 CA MICS JCL Planning and Parameters › 2.3.3.3 JCLGEN Parameters for Special Requirements › 2.3.3.3.2 JCLGEN Definition Tables
2.3.3.3.2 JCLGEN Definition Tables
Standard JCLGEN parameters are contained in the MICS.PARMS
members JCLDEFC, JCLDEF, USERJCL and the various INPUTccc and
WORKccc members described in prior sections.
Another set of special definitions, provided with the
distributed CA MICS system, are contained in definition
tables in MICS.PARMS. The generation lists (JCLGENx), JOB
information (JCLINFO and JCL$Iccc), data set name override
(JCLNAMES), and database location (DBSPLIT) tables do not
normally require modification. They do, however, provide
extensive tailoring of JCLGEN's output should the standard
JCLGEN parameters not address installation-unique
requirements.
Each is explained in the following sections.
1 - Job/CLIST Generation Lists
2 - Job/CLIST Attribute Table (JCLINFO/JCL$Iccc)
3 - CA MICS User Names Table (JCLNAMES)
4 - CA MICS Database Split Table (DBSPLIT)
2.3.3.3.2.1 Job/CLIST Generation Lists
The GENLIST parameter specified in the SYSIN data stream of
the JCLGEN process, as described in Section 2.3.3.3,
specifies a member in MICS.PARMS where JCLGEN will find a
list of jobs and/or CLISTs to be created. The following
GENLISTs are shipped with CA MICS: members JCLGEN0 through
JCLGEN2 and JCLGENUC in sharedprefix.MICS.PARMS and JCLGENA
through JCLGENG and JCLGENU in prefix.MICS.PARMS. They are
used by jobs stored under the same member names in the
corresponding MICS.CNTL library. The contents of the
GENLISTs are documented in Section 2.3.3.1.1, "Processing
Done by Standard JCLGEN Jobs."
Use sharedprefix.MICS.PARMS(JCLGENUC) to specify which items
you want generated at the complex level. Use
prefix.MICS.PARMS(JCLGENU) to specify unit level generations.
Use one of these GENLISTs, instead of the standard GENLISTs,
to reduce the number of members generated. Only those
members modified in MICS.PROTOLIB; or those members that
would be affected by changes made in JCLDEFC, JCLDEF,
JCLINFO, JCL$Iccc, JCLNAMES, or DBSPLIT; would have to be
regenerated. This way you reduce the JCLGEN run time and
reduce the number of members that have to be reviewed by your
production change control process. For example, to
regenerate the DAILY, WEEKLY, and MONTHLY job streams, you do
the following:
edit prefix.MICS.PARMS(JCLGENU)
DAILY
WEEKLY MONTHLY
sub 'prefix.MICS.CNTL(JCLGENU)'
Specify one or multiple member names on each statement. In
the example above, only members DAILY, WEEKLY, and MONTHLY
would be generated in prefix.MICS.CNTL.
2.3.3.3.2.2 Job/CLIST Attribute Table (JCLINFO/JCL$Iccc)
The Job/CLIST Attribute Table is split into two types of
members. The first have names that begin with JCL$I and are
delivered only in sharedprefix.MICS.PARMS. They define the
known CA MICS jobs, CLISTs, and macros that may be generated
by the JCLGEN process. The second is a member named JCLINFO,
which is provided for your use. JCLINFO is found in both
sharedprefix and prefix.MICS.PARMS and should be used to hold
your local overrides to our definitions as found in the JCL$I
members. JCLGEN will use these members to:
o Validate the job, MACRO, or CLIST to be created
o Identify the library to be updated
o Specify the true PROTOLIB member name if different from
the GENLIST name
o Define the TIME, CLASS, PRIORITY, and unique JOBNAME to
be placed on the job card
o Define the number of LINES and/or COPIES to be requested
on the JES parameter cards
You can use this table in a number of ways. For example,
CLASS and PRTY can be used to override for individual jobs
the overall CLASS and PRTY specifications from JCLDEF or
JCLDEFC.
Note: The CA MICS defaults for TIME, defined in the JCL$I
members, are based on an IBM 3033. If you run on a faster
machine, the TIME entries in this table are adequate.
If you supply the job card and/or JES parameters either via
the USERJCL member or the facilities provided by
MICS.PROTOLIB, then you are responsible for the proper
specification of TIME, LINES, COPIES, and JOBNAME. Refer to
Section 2.3.3.2.2, Job and JES Definitions (USERJCL), and
Section 2.3.3.3.1, Prototype Library (PROTOLIB), for more
information about these facilities.
The Job/CLIST Attribute Tables are free-form but positional;
missing fields must be denoted by a period. Comments are
specified by starting the line with an asterisk.
Note: Do not make changes to the JCL$I members. Instead,
make your changes in the JCLINFO members provided. In this
way, JCLINFO will be a record of your local modifications to
the delivered CA MICS values.
Changes to JCLINFO in sharedprefix.MICS.PARMS will affect the
complex and all unit JCLGENs unless an entry is also
specified in the JCLINFO member in prefix.MICS.PARMS.
Changes made to prefix.MICS.PARMS(JCLINFO) member will
override all values defined in sharedprefix.MICS.PARMS
members including JCLINFO.
The information contained in this table includes:
MEMBER - The search argument used to extract
information from the table. The MEMBER
named "DEFAULT" sets the values to be used
when a match is not found in the table.
JCLGEN obtains the search argument to
match against this field from the
"GENLIST" (see Section 2.3.3.3.2.1,
Job/CLIST Generation Lists). The member
may be specified with three underscores as
the first three characters. In this case,
the match will be decided based on the
remaining characters and the first three
characters of a component defined for the
unit.
TYPE - The library into which the generated
member will be saved. This may be CLIST,
MACRO, or CNTL.
COMP - The CA MICS component to which the
generated member belongs. This field is
used by the JCL generation process to
select the jobs to be generated based on
the components defined in the COMPONENTS
statement in JCLDEF. Since the BAS
component is in every unit, a value of
"BAS" in the COMP field will always cause
this member to be eligible for generation.
MBRNAME - The name of the member in MICS.PROTOLIB
that will be used for the generation of
this member. If missing, the default name
is the same as the MEMBER name.
The following fields are used only if TYPE=CNTL:
TIME - Value to be used for the job card TIME
parameter.
LINES - Value to be used for the JES LINES
parameter.
COPIES - Value to be used for the JES COPIES
parameter.
UJOBNAME - JOBNAME to be used on the job card. If
missing, the default is the value
specified in MEMBER.
CLASS - Value to be used for CLASS parameter. For
JES2, the CLASS parameter is placed on the
job card; for JES3, the class parameter is
placed on the *MAIN card.
PRTY - Value to be used for the job card PRTY
parameter.
Figure 2-27 shows some entries of the Job/CLIST Attribute
Table.
+---------------------------------------------------------+
| PARMS(JCL$IBAS): C |
| L O C |
| T I P L P |
| PROTO I N I A R |
| ------------------ M E E S T |
| MEMBER TYPE COMP MBRNAME E S S UJOBNAME S Y |
+---------------------------------------------------------+
| * GENERIC COMPONENT JOBS |
| ___CHECK CNTL . CCCCHECK 15 20 1 . . . |
| ___EVA CNTL . CCCEVA 15 25 1 . . . |
| ___CGEN CNTL . CCCCGEN 20 30 1 . . . |
| ___PGEN CNTL . CCCPGEN 10 10 1 . . . |
| * BASE JOBS |
| ALLOCATE CNTL BAS . 1 5 1 . . . |
| ALLPGEN CNTL BAS . 20 10 2 . . . |
| CKPTINIT CNTL BAS . 1 5 1 . . . |
| CYCLEGEN CNTL BAS . 2 5 1 . . . |
| DAILY CNTL BAS . 30 80 1 . . . |
| DAILYRPT CNTL BAS DYRPT400 15 19 1 . . . |
| DAYSMFR CNTL BAS . 15 19 1 . . . |
| DBSIZE CNTL BAS . 2 5 1 . . . |
| DOCUMENT CNTL BAS . 2 200 1 . . . |
| EXCFULL CNTL BAS . 15 80 1 . . . |
| GDGSGEN CNTL BAS . 3 7 1 . . . |
| JCLGEND CNTL BAS JCLGEN 5 20 1 . . . |
+---------------------------------------------------------+
+---------------------------------------------------------+
| sharedprefix.MICS.PARMS(JCL$IACT): |
| C |
| L O C |
| T I P L P |
| PROTO I N I A R |
| ------------------ M E E S T |
| MEMBER TYPE COMP MBRNAME E S S UJOBNAME S Y |
+---------------------------------------------------------+
| ACTDAY1R CNTL ACT . 10 5 1 . . . |
| ACTUPDTB CNTL ACT . 10 5 1 . . . |
| ACTINITA CNTL ACT . 1 1 1 . . . |
| ACTLGRSP CNTL ACT . 10 5 1 . . . |
| ACTPRORT CNTL ACT . 10 5 1 . . . |
| ACTRTSIM CNTL ACT . 10 10 1 . . . |
| BGTCNTL CNTL ACT . 5 5 1 . . . |
| CLOSETBL CNTL ACT . 5 5 1 . . . |
| FINRPTU CNTL ACT . 10 30 1 . . . |
| INVOICEU CNTL ACT . 10 30 1 . . . |
+---------------------------------------------------------+
Figure 2-27. Sample Job/CLIST Attribute Table
2.3.3.3.2.3 CA MICS User Names Table (JCLNAMES)
The CA MICS User Names Table allows alternatives to be
specified for the data set and procedure names used by
CA MICS to satisfy two requirements. First, an installation
may require names different than the defaults used by CA MICS
to satisfy installation standards. For example, CA MICS uses
a final qualifier of "LOAD" for data sets that contain
executable load modules. JCLNAMES provides the capability to
change the name of those data sets to end in "LOADLIB" or
anything else the installation may require.
The second requirement satisfied by JCLNAMES is the changing
of the CA MICS procedure names. This may be required by
installation standards, or to support multiple complexes in
an environment where multiple PROCLIBs are not available.
If you do not HAVE to change the data set or procedure names,
do not do it. It is your responsibility to ensure that the
changes you make in JCLNAMES are reflected in every unit for
a complex. Also, JCL distributed for loading tapes for new
components or PSP tapes will contain the default data set
names and procedure names.
The CA MICS User Names Table consists of a set of statements
in member JCLNAMES of sharedprefix.MICS.PARMS and
prefix.MICS.PARMS. This table is free-form. Comments are
specified by starting the line with an asterisk.
Two fields are defined in the table. The first field is the
symbol used by JCLGEN to represent the name. The second
field is the value to be assigned. The value may be a
constant or may also begin with one of the following
combinations of symbolic variables:
&SHAREDPREFIX..&SMICS
&SHAREPREFIX..&SMICS
&PREFIX..&PMICS
&TAPEPREFIX..&TMICS
As distributed, the User Names Table is empty. This is done
to reduce processing time during generation. Figure 2-28
shows a sample of the CA MICS User Names Table with names
defined. In actual use, only the names that did not conform
to the CA MICS defaults would be in the table. Member
ALLNAMES of sharedprefix.MICS.PARMS and prefix.MICS.PARMS
contains all of the names that may be specified in JCLNAMES.
If alternate procedure names are specified, be sure to retain
the symbolic &PROCIDENTIFIER as shown in the example below.
This is to ensure that different procedure names are used for
different units. Also, after the PROCJOBn jobs are run to
move procedures to your PROCLIB, you must manually change the
PROCLIB member name of a procedure with an alternate name.
* SAMPLE JCLNAMES
*
* SHARED DATA SETS
*
ASM &SHAREDPREFIX..&SMICS.ASM
BIN &SHAREDPREFIX..&SMICS.BIN
CAPACITY &SHAREDPREFIX..&SMICS.CAPACITY
DTFINDEX &SHAREDPREFIX..&SMICS.DTF.INDEX
CLIST &SHAREDPREFIX..&SMICS.CLIST
GENLIB &SHAREDPREFIX..&SMICS.GENLIB
HPARMS &SHAREDPREFIX..&SMICS.HOLD.PARMS
HUSOURCE &SHAREDPREFIX..&SMICS.HOLD.USER.SOURCE
INCLLIB &SHAREDPREFIX..&SMICS.INCLLIB
LOAD &SHAREDPREFIX..&SMICS.LOAD
LOCKIT &SHAREDPREFIX..&SMICS.LOCKIT
MACAUTOS &SHAREDPREFIX..&SMICS.MACAUTOS
MACLIB &SHAREDPREFIX..&SMICS.MACLIB
MCOLIB &SHAREDPREFIX..&SMICS.MCOLIB
MICSHLIB &SHAREDPREFIX..&SMICS.ISPHLIB
MICSMLIB &SHAREDPREFIX..&SMICS.ISPMLIB
MICSPLIB &SHAREDPREFIX..&SMICS.ISPPLIB
MICSSLIB &SHAREDPREFIX..&SMICS.ISPSLIB
MICSTLIB &SHAREDPREFIX..&SMICS.ISPTLIB
MWFPDS &SHAREDPREFIX..&SMICS.MWFPDS.DATA
MWFSAS &SHAREDPREFIX..&SMICS.MWFSAS.DATA
OBJ &SHAREDPREFIX..&SMICS.OBJ
PROTOLIB &SHAREDPREFIX..&SMICS.PROTOLIB
SASFLS &SHAREDPREFIX..&SMICS.SASFLS
SCREENS &SHAREDPREFIX..&SMICS.SCREENS
SOURCE &SHAREDPREFIX..&SMICS.SOURCE
TABLES &SHAREDPREFIX..&SMICS.TABLES
DOCDIR &HFSROOT./documents
VDIC &SHAREDPREFIX..&SMICS.DIC.TEXT
VDOC &SHAREDPREFIX..&SMICS.DOC.TEXT
VINC &SHAREDPREFIX..&SMICS.INC.TEXT
*
* UNIT DATASETS (DASD)
*
CHECKPT &PREFIX..&PMICS.CHECKPT.DATA
CICDATA &PREFIX..&PMICS.CIC.DATA
CNTL &PREFIX..&PMICS.CNTL
DETAIL &PREFIX..&PMICS.DETAIL
DETAIL2 &PREFIX..&PMICS.DETAIL2
RESTART &PREFIX..&PMICS.RESTART.CNTL
USOURCE &PREFIX..&PMICS.USER.SOURCE
*
* UNIT DATASETS (TAPE)
*
ACCTAUDIT &TAPEPREFIX..&TMICS.ACCT
AUDIT &TAPEPREFIX..&TMICS.AUDIT
BACKUP &TAPEPREFIX..&TMICS.BACKUP
HISTW &TAPEPREFIX..&TMICS.HISTW
HISTM &TAPEPREFIX..&TMICS.HISTM
MBACKUP &TAPEPREFIX..&TMICS.MBACKUP
*
* CA MICS PROCEDURE NAMES
*
MICSASM MICSASM
MICSCOM MICSCOM
MICSDB MICSDB&PROCIDENTIFIER
MICSDM MICSDM
MICSDU MICSDU&PROCIDENTIFIER
MICSDOC MICSDOC
MICSGT MICSGT
MICSGU MICSGU
MICSNDB MICSNDB&PROCIDENTIFIER
MICSRPTS MICSRPTS
MICSSHR MICSSHR&PROCIDENTIFIER
Figure 2-28. Sample CA MICS User Names Table
2.3.3.3.2.4 CA MICS Database Split Table (DBSPLIT)
The CA MICS Online Database is composed of five timespans:
DETAIL, DAYS, WEEKS, MONTHS, and YEARS. CA MICS allows the
files associated with each timespan to be spread across one
to 37 OS files. This table is used to specify which CA MICS
Information Areas (a logical grouping of component files)
will be in which OS files.
The CA MICS Database Split Table consists of a number of
statements in member DBSPLIT in prefix.MICS.PARMS. This
table is free-form but positional. Comments are specified by
starting the line with an asterisk. The first field is the
component's Information Area name (e.g. ADM, TSO, SCP,
etc.). The other fields are the DD names where the
Information Area files are to be written. The possible DD
names are:
DETAIL DETAILs
DAYS DAYSs
WEEKS WEEKSs
MONTHS MONTHSs
YEARS YEARSs
where s is the split id 0-9 or A-Z.
NOTE: When a numeric database id is used, split id L
cannot be used for DETAIL and S cannot be used for
MONTHS.
As distributed, the Database Split Table is empty indicating
that all Information Area files are to be written to DETAIL,
DAYS, WEEKS, MONTHS, and YEARS DD names. Figure 2-29 shows
the CA MICS Database Split Table for a database with the
DETAIL timespan split into three additional OS files and the
MONTHS timespan split into two additional OS files. In
actual use, only the statements for Information Areas that
use some DD name other than the standard DETAIL, DAYS, WEEKS,
MONTHS, and YEARS would be required in the table, as shown in
Figure 2-30.
+---------------------------------------------------------+
| INFORMATION AREA DDNAME LIST |
+---------------------------------------------------------+
| |
| ADM DETAIL DAYS WEEKS MONTHS YEARS |
| SCP DETAIL1 DAYS WEEKS MONTHS YEARS |
| HAR DETAIL DAYS WEEKS MONTHS YEARS |
| BAT DETAIL2 DAYS WEEKS MONTHS YEARS |
| TSO DETAIL2 DAYS WEEKS MONTHS YEARS |
| CIC DETAIL DAYS WEEKS MONTHS2 YEARS |
| IMS DETAIL3 DAYS WEEKS MONTHS YEARS |
| OPS DETAIL DAYS WEEKS MONTHS YEARS |
| SRL DETAIL3 DAYS WEEKS MONTHSB YEARS |
| ACT DETAIL DAYS WEEKS MONTHS YEARS |
| |
| |
+---------------------------------------------------------+
Figure 2-29. CA MICS Database Split Table Example 1
+---------------------------------------------------------+
| INFORMATION AREA DDNAME LIST |
+---------------------------------------------------------+
| |
| BAT DETAIL2 DAYS WEEKS MONTHSA YEARS |
| TSO DETAIL2 DAYS WEEKS MONTHS YEARS |
| CIC DETAIL DAYS WEEKS MONTHS9 YEARS |
| IMS DETAIL3 DAYS WEEKS MONTHS YEARS |
| |
+---------------------------------------------------------+
Figure 2-30. CA MICS Database Split Table Example 2
For the installation checklist for the DBSPLIT option, refer
to Section 3.8.5.
