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.2 Database Complex Library Definitions
2.3.1.6.2 Database Complex Library Definitions
Library definitions supply the fully qualified data set names
and other information that is needed to define the procedure, SAS,
sort, and ISPF libraries that are associated with the database
complex.
.
JCLGEN Parameter Sharing lets you specify the commonly used
JCLGEN parameters in sharedprefix.MICS.PARMS(JCLDEFC), where
they then become default parameters for
prefix.MICS.PARMS(JCLDEF) at the unit level.
Use of this facility can greatly reduce the amount of coding
in the JCLDEF and JCLDEFC members.
With JCLGEN Parameter Sharing activated, most of the JCLDEFC
and JCLDEF parameters are shared, with the following
exceptions:
Complex Only
(JCLDEFC)
Parameters Description
------------ ---------------------------------------------
ACCTMGDG - Generation definition for complex audit files
AUTHLIB - Name of Authorized Library for Q&R if JES3
CAILIB - CA Common Services Library for z/OS
DOCUMENT - SYSOUT class used for printing documentation
JES - Specifies job entry subsystem version in use
ISPLLIB1 - IBM ISPF Program Load Library
ISPLLIB2 - IBM ISPF Program Load Library
ISPMLIB1 - IBM ISPF Message Library
ISPMLIB2 - IBM ISPF Message Library
ISPPLIB1 - IBM ISPF Panel Library
ISPPLIB2 - IBM ISPF Panel Library
ISPSLIB1 - IBM ISPF Skeleton Library
ISPSLIB2 - IBM ISPF Skeleton Library
ISPTLIB1 - IBM ISPF Table Library
ISPTLIB2 - IBM ISPF Table Library
SASAUTOS - SAS auto include library
SASCONFIG - SAS configuration member
SASCONFIG1 - SAS configuration member
SASCONFIG2 - SAS configuration member
SASCONFIG3 - SAS configuration member
SASCONFIG4 - SAS configuration member
SASENV - SAS environment file
SASHELP - SAS help library
SASLIB - SAS executable library
SASMSG - SAS message data set
SASNAME - SAS program name
Unit Only
(JCLDEF)
Parameters Description
------------ -----------------------------------------------
COMPONENTS List of components in the unit
DATABASE Name used to identify the database unit
EXCLUDESTEP Exclude certain steps from operational jobs
PREFIX Name used to form the data set name of the unit
SMFDIRECTOR Components that use SMF Director input files
SMFRECORDING Identifies components that use SMF input files.
TAPEPREFIX Name that is used to form the tape data set names.
The components, database, and prefix statements are required
in prefix.MICS.PARMS(JCLDEF) for each database unit.
JCLGEN Parameter Sharing is always active, but it must be
enabled by specifying the following in
sharedprefix.MICS.PARMS(JCLDEFC) or
prefix.MICS.PARMS(JCLDEF):
COMPLEXPARMS YES
When specified in JCLDEFC, the value of COMPLEXPARMS is the
default for all units. If specified in JCLDEF, COMPLEXPARMS
overrides the COMPLEXPARMS action that is specified in JCLDEFC.
Section 5.5 provides an optional checklist that shows how to
activate JCLGEN parameter sharing for all units in the CA
MICS complex.
Notes:
o COMPLEXPARMS must be the first statement in JCLDEFC
and JCLDEF. If it is not, an error message is generated.
o For the ISPF data set and the STEPLIB definitions,
specifying the first definition (that is, ISPTLIB1) will
automatically blank out the second definition (that is,
ISPTLIB2). Therefore, always specify these
definitions in numeric order.
AUTHLIB:
The name of an authorized library at your site, where the
CA MICS MQRJES3C program resides. This program is
used exclusively by the Q&R Workstation Mainframe Server
and only at JES3 installations, to cancel a Q&R query
when requested by a user.
CAILIB:
The name of the CA Common Services Library for z/OS.
This library is used for CA Examine Auditing integration.
Refer to Section 4.11 in the PIOM for more information.
The ISPxLIBn definitions are used to supply the data set
names of your site's IBM ISPF and ISPF/PDF product libraries.
The TSO LISTALC command can be used to assist you in
determining the correct names to specify for the ISPxLIBn
definitions that follow:
ISPLLIB1-2:
The names of your site's IBM ISPF Program Product load
libraries. Both parameters are optional and need not to be
specified if the ISPF load libraries are in your
linklist. If ISPF and PDF are combined into one library
at your site, there is no need to specify ISPLLIB2.
ISPMLIB1-2:
The names of your IBM ISPF Program Product messages
library. ISPMLIB1 is required. If ISPF and PDF are
combined into one library, there is no need to specify
ISPMLIB2.
ISPPLIB1-2:
The names of your IBM ISPF Program Product panels
library. ISPPLIB1 is required. If ISPF and PDF are
combined into one library, there is no need to specify
ISPPLIB2.
ISPSLIB1-2:
The names of your IBM ISPF Program Product skeletons
library. ISPSLIB1 is required. If ISPF and PDF are
combined into one library, there is no need to specify
ISPSLIB2.
ISPTLIB1-2:
The names of your IBM ISPF Program Product table
libraries. ISPTLIB1 is required. If ISPF and PDF are
combined into one library at your site, there is no need
to specify ISPTLIB2.
PROCLIB:
The name of the system PROCLIB that the CA MICS
procedures should be added to. JCLGEN creates a job in
MICS.CNTL that, when run, adds the CA MICS procedures to
the PROCLIB specified instead of modifying it directly.
The System Administrator might need authorization to
update PROCLIB. The default value for PROCLIB is
SYS1.PROCLIB.
SASAUTOS:
The name of the SAS macro autocall library. Sometimes
named AUTOLIB.
SASCONFIG, SASCONFIG1-4:
The full SAS data set and member name of the file
containing the starting SAS configuration statements.
These statements are contained in member BATW0 under SAS
version 9.1.3. Specify SASCONFIG for this SAS version.
SAS version 9.2 and higher typically use more than one
member. Specify the full data set and member names with
SASCONFIG1-4. SASCONFIG1 overrides SASCONFIG if both
are specified. CA MICS job streams add to or override
these statements, using either sharedprefix.MICS.PARMS
members MABATCH, ICFBATCH, or MATSO. MABATCH affects
batch PROCS except MICSRPTS; ICFBATCH affects MICF batch
execution; ICFDMS affects MSAS; and MATSO affects MICF
foreground and MICF Production and User Reporting (the
MICSRPTS PROC.) The configuration files are optional.
SASENV:
The name of the SAS environment file. The TKMVSENV file
is used to make a list of pseudo environment variables.
Option values in SAS configuration files can contain
symbolic references. The values of these symbolic
references are resolved from a variable that is set in
the TKMVSENV file. This file is also necessary for SAS
features that use JAVA. Whether this SAS library is
optional depends how SAS is installed, and used
at your installation.
SASHELP:
The name of the SAS help library.
SASLIB:
The name of the SAS Program Product load library that
holds the version of SAS used for CA MICS database update
processing. Consult the CA MICS System Administrator
Guide for information about the levels of SAS currently
supported for updating the CA MICS database.
SASMSG:
The name of the SAS message library.
SASNAME:
The program name of the SAS Program Product in the load
library that is specified in SASLIB or in your LPA libraries.
SAS is the default value for SASNAME.
SORTLIB:
The name of the library containing your sort product.
This parameter should only be specified when your sort
product cannot be loaded through the normal LINKLST
process. When this parameter is specified, JCLGENwi
adds a SORTLIB DD statement to all CA MICS JCL procedures.
STEPLIB1-2:
These optional parameters can be used to add the name of
any library to the STEPLIB DD of all CA MICS JCL
procedures. STEPLIB1 is included only if specified and,
if specified, is included before the SAS program library.
STEPLIB2 is included only if specified and always after
the SAS program library.
USEROBJLIB:
The name of the SAS data library that contains user-
written informats and formats. User-written informats
and formats are created by PROC FORMAT and stored in this
SAS data library. You must store your informats and
formats in the FORMATS catalog that is used by CA MICS jobs that
implement standard CA MICS JCL procedures.
Your SAS data library is last in the search order for
catalogs that contain user-written informats and formats.
When you use the MICSCOM JCL procedure from a unit-level
reporting job, the USEROBJLIB value that is specified in
sharedprefix.MICS.PARMS(JCLDEFC) is used instead of
the value that is specified in prefix.MICS.PARMS(JCLDEF).
OBJACCESS:
Note: This parameter applies to both complex-level
(sharedprefix.MICS.MCOLIB) and unit-level
(prefix.MICS.MUOLIB) data sets.
The type of access that operational jobs have to the
sharedprefix.MICS.MCOLIB and prefix.MICS.MUOLIB data
sets.
The OBJACCESS parameter is followed by one of these
values:
SHARE
COPY (This is the default value.)
Coding a value of SHARE will cause the operational jobs
to dynamically allocate the sharedprefix.MICS.MCOLIB and
prefix.MICS.MUOLIB data sets with DISP=SHR and with a
ddname of MCOLIB or MUOLIB, respectively.
Coding a value of COPY causes the operational jobs to
allocate temporary sharedprefix.MICS.MCOLIB and
prefix.MICS.MUOLIB data sets, into which the entire
contents of USERFMT1, MICSFMTS, and USERFMT2 format
catalogs are copied.
The OBJACCESS parameter does not affect CA MICS
generation jobs, which include cccCGEN, JCLGENx, cccPGEN,
and MAGRUN.
When you use the MICSCOM JCL procedure from a unit-level
reporting job, the OBJACCESS value that is specified in
sharedprefix.MICS.PARMS(JCLDEFC) is used instead of
the value that is specified in prefix.MICS.PARMS(JCLDEF).
OBJWAIT:
Note: This parameter applies to both complex-level
(sharedprefix.MICS.MCOLIB) and unit-level
(prefix.MICS.MUOLIB) data sets.
This optional parameter specifies the amount of time, in
minutes, dynamic allocation of sharedprefix.MICS.MCOLIB
and prefix.MICS.MUOLIB waits if the data sets are
not immediately available. The default is 5 minutes.
If data set allocation fails because another batch job or
online user is already using a data set, CA MICS jobs
waits 15 seconds and then try the allocation again.
This allocation attempts repeatedly every 15
seconds until, by default, a total of 5 minutes have
elapsed. After 5 minutes, the operational job will
abort.
If the default value is too short, you may want to use
the OBJWAIT parameter to increase the maximum number of
minutes the jobs waits for the data sets to become
available.
To implement a change to OBJWAIT, do the following:
o Update the JCLDEFC or JCLDEF member according to your
preference.
o If at the complex level, empty
sharedprefix.MICS.PARMS(JCLGENUC) of all statements but
comments. Execute the sharedprefix.MICS.CNTL(JCLGENUC)
job. Verify successful completion.
o If at the unit level, empty prefix.MICS.PARMS(JCLGENU)
of all statements but comments unless you want to
generate some particular JCL simultaneously.
Execute the prefix.MICS.CNTL(JCLGENU) job. Verify
successful completion.
Copyright © 2014 CA.
All rights reserved.
|
|