3. CAPACITY PLANNING DATABASE › 3.3 Resource Element Files › 3.3.3 Resource Element File Case Studies › 3.3.3.4 Tracking Applications › 3.3.3.4.1 Problem Description

3.3.3.4.1 Problem Description

 
The tracking applications case study addresses the following
areas:
 
o  Summarizing multiple SYSIDs and ZONEs into a composite
   SYSID and ZONE.  Although you may normally expect an
   application to run during a specific zone or on a specific
   processor, summarizing data from all zones and systems
   prevents the loss of data when the application runs in an
   unexpected manner.

o  Using a selection exit to limit the volume of data that is
   processed by the program.  Rather than summarizing the
   data for all jobs, the selection exit retains data for the
   application being studied and excludes data for all of the
   other jobs.

Note that identifying applications in the MONTHS timespan of
the BATJOB File depends on the way that you define the BATJOB
File accounting fields.  In the test installation,
applications are identified by two three-character account
codes (ACCTNO1 and ACCTNO2).  The payroll application is
identified by the account codes P39 and 028.  We chose the
following data elements to characterize the application for
this case study:
 
  Data Element                Description
  ============ ==============================================
 
    JOBTCBTM   Total TCB CPU time used by the application
 
    JOBSRBTM   Total SRB CPU time used by the application

    JOBNLR     Total lines printed by the application
 
    JOBMXWSS   The maximum working set size of the
               application

    JOBCOUNT   The total number of jobs executed during the
               month
 
    JOBSTEPS   The total number of job steps executed during
               the month

    JOBSYSAB   The total number of system ABENDs experienced
               by the application during the month
 
    JOBUSRAB   The total number of user ABENDs experienced
               by the application during the month

Although these data elements do not provide a complete
characterization of all resources used by the application,
they are examples of key indicators that capacity planners
would find interesting.  The CA MICS BATJOB File contains
many other data elements which you could select to augment
this capacity database file, based on your own interest.