Previous Topic: 7.3.1.19 CONFIGURATION File Retention Limit (CONFIGLIMIT)

Next Topic: 7.3.2.1 JOBGROUP Definition

7.3.2 Batch Workload Classification (JOBGROUP)


The JOBGROUP data element in the Batch User Job Activity File
(BATJOB) is used to classify batch job activity according to
service requirements, job resource requirements (e.g., setup
vs.  non-setup), or any other factor the user deems
appropriate.  The definition in prefix.MICS.PARMS(JOBGROUP)
sets the values that appear in the JOBGROUP data element.
The values are assigned to each job by the user exit routine
in prefix.MICS.PARMS(JOBGPRTE).

USE OF THE JOBGROUP DATA ELEMENT

Job group definition is extremely important for the data
stored in the Batch Information Area files because
summarization at the system and batch user levels is by
JOBGROUP.  JOBGROUP is also part of the key of the BATJOB
file.  In other words, if an installation uses a combination
of job class and priority for grouping jobs, it should define
a job group for each unique job class/priority service
category (e.g., all class A jobs requesting priority 10).
Then all batch user and system summarization will be
performed to aggregate the activity according to the job
group classifications.

CA MICS contains special data base and reporting support that
uses JOBGROUP as a specification of expected service
(turnaround) for batch jobs.  Once a job is assigned a job
group by the user exit, CA MICS computes its turnaround time
using the specifications in prefix.MICS.PARMS(JOBGROUP).
CA MICS then compares it to the turnaround time objective for
its job group, which is also specified via parameters in
prefix.MICS.PARMS(JOBGROUP).  Depending on whether the job's
service commitment was met, exceeded, or missed, CA MICS will
increment one of three counters:       Jobs Meeting Target
(JOBSRVMT), Jobs Exceeding Target (JOBSRVEX), or Jobs Missing
Target (JOBSRVMS), respectively.  CA MICS has standard
reports that show how well your installation is meeting its
service objectives.

CLASSIFYING BATCH WORKLOADS

Methods for classifying batch workloads vary among
installations and may be based on any of the following
approaches:

  o  Job classification by estimated resource usage.

     Normally this approach utilizes a JES-based Job Stream
     Manager, which, based on estimates of items such as CPU,
     device, and spool usage, classifies the job by assigning
     it a particular job class, priority, or performance
     group number.

  o  Job classification based on service requested.

     This approach classifies jobs based on service requested
     (batch turnaround) by the user, usually through the
     specification of a particular job class, priority,
     performance group, or combination of the three.

  o  Job classification based on user.

     This approach classifies jobs based on the identity of
     the user who submitted the job.  The CA MICS approach is
     to use batch account codes for this purpose rather than
     the job group.

Generally, written procedures exist that explain the site's
job classification scheme.  If these are not available,
consider spending time documenting the method of batch job
classification or, if none is in use, to define an
appropriate scheme for your site.

The key items that the CA MICS System Administrator should
look for are:

    o  The coding system (e.g., job class, priority, or
       performance group).

    o  If, and how, the items are verified to ensure that
       they correspond to a valid definition.  We recommend
       that job classification validation be performed when
       the job is submitted to the system.  It may be
       implemented through use of reader/interpreter exits
       (IEFUJI) provided by SMF.  This approach validates the
       job's classification codes and flushes the job if the
       codes are invalid.

    o  Is the job classification system used for requesting
       batch service, identifying a type of work, or
       classifying work according to resource usage?

The following sections describe the parameters you must
supply in prefix.MICS.PARMS(JOBGROUP):

    1 - JOBGROUP Definition
    2 - TURNTIME Statements
    3 - GROUP Statements
    4 - DEADLINE Statements
    5 - OPEN Statements