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.3 Database Complex JCL Definitions
2.3.1.6.3 Database Complex JCL Definitions
The JCL definitions let you control how JCLGEN tailors the
generated JCL in terms of SYSOUT designations, JES usage,
DASD and sort generic device names, temporary sort space
amounts, sort utility initialization parameters, SAS WORK
file allocations, submit internal reader privileges, and
generated job member renumbering. The following parameter
statements are available:
ASSEMBLER
This option defines which IBM assembler will be used by
the MICSASM JCL procedure. The values that can be coded
include H for Assembler H (IEV90), and HL for the High
Level Assembler (ASMA90). If this option is omitted,
it defaults to H.
AUTOSUBMIT
If this option is set to YES, some of the CA MICS jobs
will submit jobs through the internal reader. If this
option is set to NO, the functions of the jobs that
would have been submitted to the internal reader will be
included in the jobs that would have submitted them. An
example of this is the DAILY job. If this option is YES,
then the CA MICS Management Objectives and Exception
Reports will not run as part of the DAILY job. Rather,
DAILY will submit another job, DAILYRPT, to the internal
reader, to create these reports.
The CA MICS jobs that optionally use the internal reader
are DAILY, WEEKLY, SCHEDULE, BACKUP, and MONTHLY.
Specify either YES or NO to indicate whether the DAILY,
WEEKLY, BACKUP, and MONTHLY jobs should submit jobs into
the internal reader. If NO is specified, the jobs that
would have been submitted become steps in the job that
would have submitted them. The SCHEDULE job always uses
the internal reader, regardless of this option.
The default value for AUTOSUBMIT is YES.
Note: The MICF inquiry production interface operates
from the DAILYRPT, WEEKRPT, and MONTHRPT jobs, but not
directly in DAILY, WEEKLY, or MONTHLY. If AUTOSUBMIT is
NO, you must schedule MICF inquiry production reporting
with your site's own scheduling facilities. For more
information about MICF production reporting, see section
5.1.6 of the MICF Reference Guide.
COLIBSPACE
The type of space, primary quantity, and secondary
quantity to use for temporary MCOLIB file allocations
when operating in OBJACCESS COPY mode.
If the COLIBSPACE parameter is coded, the type of space
and primary quantity are required, and the secondary
quantity is optional.
The values for type of space are TRK, CYL, or block
length (nnnnn). The primary quantity should be a numeric
value greater than 1. The secondary quantity should be a
numeric value or left blank.
Specify the COLIBSPACE parameter as follows:
COLIBSPACE type primary_quantity secondary_quantity
If the COLIBSPACE parameter is omitted, the following
values will be used:
COLIBSPACE 6144 1000 500
The type of space value will be saved in a symbol named
COLIBSPACE. The primary quantity value will be
available in symbol COLIBSPPRIM, while the secondary
quantity will be available in COLIBSPSEC.
DASDUNIT
The generic unit name to be used for work data set
allocations. The default is SYSDA. DASDUNIT will be
used in place of VCATUNIT for allocating the model
data set if VCATUNIT is not specified.
DASDSMSPARMS
Optional parameter for specifying System Managed Storage
(SMS) keywords (for example, STORCLAS=storclas) to be
used for CA MICS data set allocations. Specify one or
more SMS parameters according to JCL language syntax,
separated by commas. There is no default and
continuation is not allowed.
DIRSTATS
Specify either YES or NO. Create ISPF member statistics
for all modules generated by JCLGEN. The default value is
NO.
WARNING! Activating DIRSTATS can consume up to three
times the current number of directory blocks. If a PDS
runs out of directory blocks, then the JCLGEN job will
abend. Prior to activating, the following CA MICS data
sets should be tested to verify they have sufficient
directory blocks.
sharedprefix.MICS.MACAUTOS
sharedprefix.MICS.CNTL
sharedprefix.MICS.PARMS
sharedprefix.MICS.SOURCE
prefix.MICS.PARMS
prefix.MICS.CNTL
prefix.MICS.USER.SOURCE
DOCUMENT
The SYSOUT class parameters to use for printing
uppercase/lowercase documentation at the site. In the
CA MICS generated JCL, the parentheses are generated, so
DO NOT supply them yourself. Class A is the default.
Note: If you want to supply additional information to
control documentation output, code this information here
by ending the parameter with a trailing blank. This
causes the generated right parenthesis to be treated as a
comment. For example, you might code the following:
DOCUMENT 'A),CHARS=GT12,FCB=8A4 '
DYNAMWAIT
This optional parameter specifies the amount of time, in
minutes, dynamic allocation processes in CA MICS
operational jobs will wait for an unavailable data set.
The default is 15 minutes.
Internal Step Restart, Incremental Update, Stand-Alone
Archive Tape, and other CA MICS facilities use z/OS
dynamic allocation services to create new data sets and
to access existing data sets. Data set naming
conventions and internal program structure are designed
to minimize data set contention. However, if data set
allocation does fail because another batch job or online
user is already using a data set, CA MICS operational
jobs will wait 15 seconds and then try the allocation
again. This allocation will be attempted repeatedly
every 15 seconds until, by default, a total of 15 minutes
has elapsed. After 15 minutes, the operational job will
abort.
If data set contention in your site does cause frequent
operational job failures, and you are unable to resolve
the contention through scheduling changes, you may want
to use the DYNAMWAIT parameter to increase the maximum
number of minutes the operational jobs will wait for the
data set to become available.
On the other hand, if your site standards require that
operational jobs fail immediately if required data sets
are unavailable, specify the following:
DYNAMWAIT 0
Note: You can override the DYNAMWAIT parameter:
o At the unit level in prefix.MICS.PARMS(JCLDEF).
o At the product level in prefix.MICS.PARMS(cccOPS).
For more information, see the individual DIA guides.
o At execution-time for DAILY and INCRccc jobs using the
//PARMOVRD facility. For more information about
execution-time override of dynamic data set allocation
parameters, see section 2.3.6.
INTRDRCLASS
The SYSOUT class used by CA MICS for the internal reader.
The default class is A. Normally, this definition is not
required since the INTRDRCLASS is the default MSGCLASS
for jobs submitted through the internal reader.
JES
Specifies whether the CA MICS operational jobs will be
run on a JES2 or JES3 system. Specify 2 or 3. The
default JES value is 2.
LOGS
The SYSOUT class parameters for log-type outputs. Class
A is the default.
MICSLOG
The SYSOUT class parameters for MICSLOG output. Class
specified for LOGS is the default.
MICSDMDELIM
Delimiter character for the MICSDM/MICSDU PROC. This
value cannot be alphanumeric or a special character (A-Z,
0-9, @#$). The tilde (~) is the default. This value
should only be changed if the tilde cannot be used.
RENUMBER
Specify either YES or NO to indicate whether or not the
generated job should be renumbered. The default is NO.
This option is forced to NO if JOB7380, discussed in
Section 2.3.3.2.1.6, has been specified.
REPORTS
The SYSOUT class parameters for report outputs. Class A
is the default.
SORTCYL
The number of cylinders to allocate for each sort work DD
statement used in CA MICS procedures. The default value
for SORTCYL is 6. The maximum value for SORTCYL is 999.
SORTUNIT
The generic unit name to be used for sort work data set
DASD allocations. The default is SYSDA.
SORTWKNO
The number of unique sort work data set allocations. The
default is 6. The range of acceptable values is 0 to 99.
SORTSMSPARMS
Optional parameter for specifying System Managed Storage
(SMS) keywords (for example, STORCLAS=storclas) to be
used for sort work data set allocations. Specify one or
more SMS parameters according to JCL language syntax,
separated by commas. There is no default and
continuation is not allowed.
SORTUTILITY
The name of the sort utility to use. Specify CASORT,
DFSORT, SYNCSORT, or OTHER. The default is SYNCSORT.
If CASORT is specified the following JCL is included:
//SORTCNTL DD DISP=SHR,
// DSN=sharedprefix.MICS.PARMS(CASORT)
If DFSORT is specified the following JCL is included:
//SORTCNTL DD DISP=SHR,
// DSN=sharedprefix.MICS.PARMS(DFSORT)
If SYNCSORT is specified the following JCL is included:
//$ORTPARM DD DISP=SHR,
// DSN=sharedprefix.MICS.PARMS(SYNCSORT)
You can modify the appropriate member in
sharedprefix.MICS.PARMS to accommodate any unique
requirements for sort initialization parameters.
No statements are generated if OTHER is specified.
(If you want to concatenate your load libraries either
before or after the CA MICS and SAS load libraries,
see Section 4.4.7.)
STEPCPULIMIT
Specify YES or NO. If YES, then JCLGEN will add TIME=60
to the EXEC statement of each PROC. This is done to
prevent "runaway" steps.
Note: This option will apply to select PROCs. The
default is YES.
UOLIBSPACE
The type of space, primary quantity, and secondary
quantity to use for temporary MUOLIB file allocations
when operating in OBJACCESS COPY mode.
If the UOLIBSPACE parameter is coded, the type of space
and primary quantity are required, and the secondary
quantity is optional.
The values for type of space are TRK, CYL, or block
length (nnnnn). The primary quantity should be a numeric
value greater than 1. The secondary quantity should be a
numeric value or left blank.
Specify the UOLIBSPACE parameter as follows:
UOLIBSPACE type primary_quantity secondary_quantity
If the UOLIBSPACE parameter is omitted, the following
values are used:
UOLIBSPACE 6144 200 100
The type of space value will be saved in a symbol named
UOLIBSPACE. The primary quantity value will be
available in symbol UOLIBSPPRIM while the secondary
quantity will be available in UOLIBSPSEC.
WORKSPACE
The type of space, primary quantity, and secondary
quantity to use for SAS WORK file allocations.
If the WORKSPACE parameter is coded, the type of space
and primary quantity are required, and the secondary
quantity is optional.
The values for type of space are TRK or CYL. The primary
quantity should be a numeric value greater than 1. The
secondary quantity should be a numeric value or should be
left blank.
Specify the WORKSPACE parameter as follows:
WORKSPACE type primary_quantity secondary_quantity
If the WORKSPACE parameter is omitted, the following
values are used:
WORKSPACE TRK 500 250
The type of space value will be saved in a symbol named
WORKSPACE. The primary quantity value will be available
in symbol WORKSPPRIM while the secondary quantity will
be available in WORKSPSEC.
WORKUNIT
The generic unit name to be used for SAS WORK file
allocations. The default is the value specified for the
DASDUNIT keyword.
WORKVOLSER
The volume serial number to be used for SAS WORK file
allocations.
WORKSMSPARMS
Optional parameter for specifying System Managed Storage
(SMS) keywords (for example, STORCLAS=storclas) to be
used for SMS WORK file allocations. Specify one or more
SMS parameters according to JCL language syntax,
separated by commas. There is no default and
continuation is not allowed.
