Special Usage Considerations › The JSMFANAL SMF Analysis Program

The JSMFANAL SMF Analysis Program

This section describes:

• The JSMFANAL Analysis program
• How to specify JSMFANAL rates
• How to specify currencies using JSMFANAL
• The JSMFANAL processing options
• The JSMFANAL selection options
• JSMFANAL sort fields

CA JCLCheck contains an SMF analysis program that can illuminate the high cost of JCL errors at your installation. The program processes step end, job end, and job purge SMF records (record types 4, 5, 26, and 30). JSMFANAL reports the total number of jobs and steps it finds in the input file and estimates the average resources used per job step. Using that information, JSMFANAL estimates the cost of resources wasted by:

• JCL errors (other than syntax errors)
• S213 ABENDS (missing disk data set)
• Sx06 ABENDS (includes S806 (missing program), S706 or S406 (invalid or unexecutable program), and S637 (invalid concatenations)
• S013 ABENDS (DCB problems)

The printed cost is an estimate. The following factors can cause a variance:

• Not all flushed steps are caused by JCL errors. Some are the result of steps skipped (flushed) due to condition codes.
• CA JCLCheck can prevent only about 95 percent of S013 ABENDS (most frequently those resulting from bad block sizes or missing PDS members).
• JSMFANAL does not attempt to estimate the resources wasted by the ABEND step itself. These could be substantial if the step has been in execution for some time, or prints a large dump.
• JSMFANAL does not attempt to estimate the cost of programmer or analyst time required to analyze and correct the error and resubmit the job. This may well be the most significant cost of all.

The first two variances raise the estimated costs. The last three lower it. In most installations these effects cancel each other, allowing the JSMFANAL estimate to be used directly.