MICS

 View Only
Back to discussions
Expand all | Collapse all

Consider the MICS BATJOB metric JOBSTEPS is not job-steps executed

  • 1.  Consider the MICS BATJOB metric JOBSTEPS is not job-steps executed

    Posted Oct 29, 2014 12:20 PM

    Hello CA MICS Community Members:

     

    Encourage all MICS family, friends, neighbors, to vote-up this MICS BATJOB enhancement request, as currently there is no BATJOB SAS variable that provides a true count of "Job Steps Executed" -- because JOBSTEPS is a sum of PGMCOUNT, and PGMCOUNT is set to a value of 1 for each job-step "encountered" which will include job-steps that were bypassed.

     

    21514509 - BATJOB - JOB STEPS EXECUTED?

     

    As well, there is somewhat of a flaw with SMF type 30 activity because there is no indicator that a job has failed during execution -- an issue to consider raising with a new SHARE requirement - any thoughts from others?

     

    Scott Barry

    SBBWorks, Inc.



  • 2.  Re: Consider the MICS BATJOB metric JOBSTEPS is not job-steps executed

    Posted Nov 06, 2014 10:58 AM

    After this post, I was asked about tailoring MICS BATJOB possibly to add a SAS variable for "Job-Steps Executed" - this is definitely a tailoring opportunity to interrogate PGMCOUNT=1 and PGMEXCTM GT 0, then count a new BATJOB variable.  The MICS SMF Component Guide, Chapter 10, discusses MICS Database Tailoring opportunities.

     

    Scott Barry

    SBBWorks, Inc.