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.5 Database Complex Extended Job Card Definitions

2.3.1.6.5 Database Complex Extended Job Card Definitions

            Definitions

Extended JOB statement parameters let you individually define
each of the supported JOB statement options as listed below.
Keep in mind that the JOB statement may be supplied at the
beginning of the USERJCL PARMS member described in section
2.3.3.2.2, Job and JES Definitions.  If you choose to have CA
MICS construct JOB statements, specify the following
parameters:

ACCT

    Standard accounting field(s) required by the installation
    on JOB statements. A maximum of 53 characters may be
    specified.  The value specified in this parameter is
    enclosed in parenthesis on the JOB statement. For
    example, if you specify the following definition:

       ACCT 'MICS,ACCOUNT'

    a JOB statement is generated with the following:

       //jobname JOB (MICS,ACCOUNT),

CLASS

    For JES2, the single character job class to be specified
    on the JOB statement. For JES3, the one to eight
    character job class to be specified on the //*MAIN
    statement.

GROUP

    The RACF GROUP parameter to be specified on the JOB
    statement.  The default is not to specify GROUP on the
    JOB statement.

JCLLIB

    Specify YES to include, with the generated JOB statement,
    a JCLLIB statement for the CA MICS PROCLIB data set.  The
    generated JCLLIB statement is of the form:

         //MICS JCLLIB ORDER=(proclib_dsn)

    Specify NO (the default) to omit the JCLLIB statement.

    Warning: Do not use this option if you have a JCLLIB
             statement specified in USERJCL.
JOBNAME

    The user may specify a single job name to be used for
    every job created by CA MICS (this is strongly
    discouraged) or may provide a job name prefix that is
    used by the JCLGEN process to build the job name.

    The CA MICS JCL generation process will provide standard
    job names for each job that it creates (e.g., the daily
    CA MICS update stream's job name is DAILY).  There are
    times, however, when the standard job names generated by
    CA MICS may not conform to an installation's job naming
    convention.  We strongly recommend using the standard job
    names generated by CA MICS if at all possible.  However,
    if it is necessary to have job names different from those
    generated by CA MICS, use the JOBNAME statement to
    specify your changes.  If the CA MICS standard job names
    are satisfactory, either omit the JOBNAME statement from
    JCLDEFC or code it with no value following the JOBNAME
    keyword.

    If you want to qualify all CA MICS job names with a
    special prefix, define a prefix of 1 to 7 characters for
    the value for the JOBNAME statement.  The JCL generator
    uses the prefix value to concatenate the prefix with the
    standard CA MICS job name truncating the result to an
    eight character job name.  For example, the JOBNAME value
    ABC would result in the standard CA MICS job name MONTHLY
    to now have the job name ABCMONTH.  The new name is built
    using the job name prefix and the first n characters of
    the standard CA MICS job name up to the allowable eight
    character job name.  The standard CA MICS JOBNAMEs may be
    found in sharedprefix.MICS.PARMS members beginning with
    JCL$I.

         JOBNAME ABC

    If you want the same job name for all CA MICS jobs,
    specify a full eight-character name in quotes (trailing
    blanks are acceptable).  Again, this job name option is
    strongly discouraged.

         JOBNAME 'ABCD    '

JOB7380

    A few installations require job parameters to be entered
    in columns 73 through 80 of the first statement of the
    (possibly continued) JOB statement.  These entries can be
    done using the JOB7380 parameter.  Use of this parameter
    is not recommended unless required by your standards.
MSGCLASS

    The job output message class to be specified on the JOB
    statement. The default MSGCLASS is A. Valid values are
    A-Z and 0-9.

MSGLEVEL

    The job output message level to be specified on the JOB
    statement. The default MSGLEVEL is 2,1.

NOTIFY

    The TSO user ID to be used for the JOB statement NOTIFY
    parameter, which sends a message to the specified user ID
    upon batch job completion.  If you specify the value,

         &SYSUID

    the JOB statement is generated with NOTIFY=&SYSUID, which
    will direct the job completion message to the userid of
    the user who submitted the batch job.

PASSWORD

    The RACF PASSWORD parameter to be used on the JOB
    statement.  The default is to not specify a PASSWORD on
    the JOB statement.

PERFORM

    The performance group to be specified on the JOB
    statement.  The valid range of values is a numeric from 1
    to 999.  The default is to not specify a value for the
    performance group.

PROG

    The 1- to 20-character programmer name required on the
    JOB statement by the installation. The value specified in
    this parameter is enclosed in quotes on the generated JOB
    statement.

PRTY

    The job input priority to be specified on the JOB
    statement.  For JES2 systems, the maximum priority that
    may be specified is 15.  For JES3 systems, the maximum
    priority that may be specified is 14.  The default is not
    to specify a PRTY value on the JOB statement.
REGION

    The job region size to be used on all JOB statements. The
    value can be specified in one of the following forms:

    nnnn  - region size in units of 1024 bytes (Kilobytes)
    nnnnK - region size in units of 1024 bytes (Kilobytes)
    nnnM  - region size in units of 1048576 bytes (Megabytes)

    Note - 0K and 0M are valid specifications.
         - leading zeros are not required.

    We recommend that you do not specify this parameter
    unless it is required by installation standards.  All CA
    MICS PROCs have appropriate step region sizes specified.

USER

    The RACF USER parameter to be specified on the JOB
    statement.

CA MICS supports an option to hard-code a JOB statement in
MICS.PARMS(USERJCL) instead of having CA MICS generate one
from the parameters described above.  All the parameters
listed above may be used as symbolic variables whose values
may be referenced, along with those of certain other CA MICS
variables, in JCL that you supply in the USERJCL member in
MICS.PARMS.  For more information, see section 2.3.3.2.2, Job
and JES Definitions (USERJCL).