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.3 JCLGEN Parameters for Special Requirements › 2.3.3.3.5 OS Job Names

2.3.3.3.5 OS Job Names

As distributed, most generated CA MICS jobs will have the
same name as the MICS.CNTL member in which they are saved
(e.g. the database job will have the name ALLOCATE).  These
job names will probably not be acceptable at most
installations.  Three alternatives are available for creating
job names for CA MICS jobs.

The easiest way of changing the CA MICS job names is to use
the extended jobcard parameter JOBNAME.  This parameter
allows the specification of a one to eight character prefix
to be added to the standard job names.  The use of this
parameter is described in Section 2.3.3.2.1.6.

If the use of the JOBNAME parameter is not acceptable, two
alternatives are available:  the job name for each job to be
generated can be specified individually in the JCLINFO
parameters member, or the USERJCL parameters member can be
used to create job cards with job names generated with your
GCL statements.

Section 2.3.3.3.2.2 describes the JCLINFO parameters member.
One of the optional fields which can be used to provided job
attributes is UJOBNAME.  This is a user job name which will
override the standard CA MICS job name.

The final alternative for creating job names is to create
the job card with the USERJCL parameters member.  Section
2.3.3.2.2 describes how to define the USERJCL parameters
member.