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.2 Standard JCLGEN Parameters

2.3.3.2 Standard JCLGEN Parameters

 Because installation standards and practices in the area of
 Job Control Language (JCL) and TSO Command (CLIST) language
 vary widely, CA MICS provides a facility for tailoring the
 JCL and CLISTs it uses.
 
 Though experience has shown that the parameters supported in
 the members of MICS.PARMS discussed in the following sections
 provide sufficient flexibility for almost all CA MICS users,
 if you cannot meet your requirements using these members,
 more flexible (and complex) support exists and is documented
 in section 2.3.3.3, JCLGEN Parameters for Special
 Requirements include:
 
     o A data volume so great that certain database data sets
       is split into multiple OS data sets to supply the required
       DASD space. For example, MICS.DETAIL.
 
     o When you want to insert certain DD statements into the CA
       MICS database inquiry procedures For example //SYSUDUMP.
 
     o When you want to change the time and lines limits for
       certain CA MICS jobs.
 
     o Data set naming standards different from those of
       CA MICS For example, if you HAD to name
       sharedprefix.MICS.SOURCE sharedprefix.MICS.PROGRAMS.
 
     o When you want to have all JCL control for multiple CA MICS
       databases centralized in one library (MICS.PROTOLIB)
       rather than being distributed across many (MICS.PARMS).
 
     o Any other modification which cannot be accomplished through
       the standard JCLGEN parameters discussed here.
 
 The JCLGEN parameters exist in members in the CA MICS
 parameter library (MICS.PARMS).  Complete these parameters before 
 executing the CA MICS JCL generation process.  JCLGEN
 parameters fall into three categories:
 
     o The JCLDEF member is by far the most complex containing
       all of the standard JCLGEN parameter statements.  This
       parameter must be coded.
 
     o The USERJCL member is used to supply a JOB statement
       (optional) and any JES control statements that must
       come after the JOB statement (required), for
       jobs to run in your shop.  This parameter must be
       coded.
 
     o The INPUTccc members supply the DD statements to be
       used to read the raw measurement data.  For more
       information about these optional members, see the data
       integration product guides.
 
 
 The following sections describe how to complete these
 parameters:
 
     1 - JCL Option Definitions (JCLDEF)
     2 - Job and JES Definitions (USERJCL)
     3 - Input DD Statements for SMF (INPUTRDR)