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?
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.