Previous Topic: 3.3.1 SAS Libraries Used by CA MICSNext Topic: 3.3.2.1 Generate Complex-Level Q&R Templates


3.3.2 Generate Complex-Level JCL Jobs, PROCs, CLISTs

Section 2.3.1.6, Database Complex JCL Definitions (JCLDEFC),
 describes the CA MICS parameters that control the process by
 which the JCL procedures, batch jobs, and TSO CLISTs required
 for complex-level functions are created.
 
 Before you run JCLGEN0, provide the environmental parameter
 values in sharedprefix.MICS.PARMS, as described here.  Any
 changes that you make using the facilities that are described
 in section 2.3.3.3, JCLGEN Parameters for Special
 Requirements, must also be complete before JCLGEN0 is
 submitted.
 
   JCL OPTIONS
 
     Member:  sharedprefix.MICS.PARMS(JCLDEFC)
     See section 2.3.1.6
 
   USER JOB CARD JCL
 
     Member:  sharedprefix.MICS.PARMS(USERJCL)
     See section 2.3.3.2.2
 
 Review and complete the JOB statement and the symbolic
 parameters on the EXEC statement of
 sharedprefix.MICS.CNTL(JCLGEN0).
 The EXEC statement is written as follows:
 
   //STEP1  EXEC MICSDM,
   // ISPTLB1='__________________',
   // ISPTLB2='__________________',
   // ISPMLB1='__________________',
   // ISPMLB2='__________________',
   // WKUNIT='SYSDA',
   // SHRPFX='sharedprefix.MICS',
   // SASNAME='entry',
   // SASPFX='sas.prefix',
   //*SASENV='TKMVSENV(TKMVSENV)',
   // SASCFG1='config',
   //*SASCFG2='CONFIG(COMMON)',
   //*SASCFG3='CONFIG(ENW0)',
   //*SASCFG4='CONFIG(SITE)',
   //*AUTOLIB='fixed.block.AUTOLIB',
   // LANG1='',
   // LANG2='

' 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.
 

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:
 
 ISPTLB1-2
 
     The names of your IBM ISPF Program Product table
     libraries.  ISPTLB1 is required.  If ISPF and PDF are
     combined in one library at your site, specify
     ISPTLB2 with the same name in ISPTLB1.
 
 ISPMLB1-2
 
     The names of your IBM ISPF Program Product message
     libraries.  ISPTLB1 is required.  If ISPF and PDF are
     combined in one library at your site, specify
     ISPMLB2 with the same name in ISPMLB1.
 
 WKUNIT
 
     The unit for the SYSUT3 and SYSUT4 work data sets needed
     by IEBCOPY.
 
 SHRPFX
 
     The sharedprefix for the database complex. Include the CA
     MICS level node as needed by your site.  Specify the
     sharedprefix name without the trailing period.
 
 SASNAME
 
     The program name of the SAS Program Product in the load
     library specified in SASLIB or in your LPA libraries.  It
     is also the entry point name.  SAS is the default value
     for SASNAME.
 
 SASPFX
 
     The common data set name prefix for your SAS libraries.
     Specify the name without the trailing period.
 
 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.  Whether this file is optional depends
     on how SAS was installed at your installation.
 
 SASCFG1
 
     The library name suffix and member name of your SAS
     configuration file.
 
     For SAS version 9.1.3, usually the library is the SAS
     CNTL data set and the member is BATW0.
 
     For SAS version 9.2 and above, usually the library is
     the SAS CONFIG data set and the member is BATCH.
 
 SASCFG2
 
     The library name suffix and member name of an additional
     configuration file that is needed for SAS versions 9.2
     and higher.  Usually this file is a member of the SAS
     CONFIG data set and the name is COMMON.
 
 SASCFG3
 
     The library name suffix and member name of an additional
     configuration file that is needed for SAS versions 9.2
     and above.  Usually this file is a member of the SAS
     CONFIG data set and the name is ENW0.
 
 SASCFG4
 
     The library name suffix and member name of an additional
     configuration file that is needed for SAS versions 9.2
     and higher.  Usually this file is a member of the SAS
     CONFIG data set and the name is SITE.
 
 AUTOLIB
 
     The SAS AUTOCALL library that is being converted to fixed
     block with SAS 9.1.3. This library is not required for
     SAS version 9.2 and above.
 
 LANG1
 
     The language code that is required for SAS.  For example,
     EN stands for English.
 
 LANG2
 
     The encoding value that is required for SAS.  The value
     for EBCDIC is W0 and must have a trailing period (.).
 
 When you have completed editing the job, submit it as
 follows:
 
   SUB 'sharedprefix.MICS.CNTL(JCLGEN0)'
 
 There are other JCL generation requirements at the complex
 level, but they are for creating JCL specific to certain
 products such as Accounting and Chargeback (JCLGEN1).  The
 guides for these products describe these complex-level
 requirements.