Q1-Q2 Interval records are only for the interval in question and *ARE NOT* accumulated separately. The accumulation is shown in the subtype 4 and subtype 5.
Q3. According to the SMF manual the answer is YES. <quote> The termination exit (IEFACTRT) receives control on the normal or abnormal termination of each job step and job. A return code from this exit indicates whether the system is to continue the job (for job steps only) and whether SMF termination records are to be written to the SMF data set. The parameters passed to this exit are the addresses of: .... </quote> HTH, <snip> I'm analysing a perfomance issue with long running (35 hours) a batch job. Looking at JESYSMSG, I stumbled across information that our IEFACTRT exit writes at step end. There is one step that seamed to do millions of I/Os against STEPLIB. STEPLIB is a two DSN concatenation, however, I see dozens of STEPLIB related I/O numbers.... Trying to understand, I started to have a detailed look at the SMF 30 records for the step. We do have interval recording, so I can see one subtype 1, a bunch of subtype 2, followed by one subtype 3 for the lat interval, and finally 1 subtype 4 records at the end of the step. Q1: The I/O counts in the interval records are *not* cumultive, but reflect the count since the previous record has been cut, correct? This is how I read the doc. Q2: The EXCP information that was written to the interval records is repeated in the step end record, correct? Q3: IEFACTRT will only see subtype 4 records, correct? Q4: If Q1-Q3 are correct, this explains why IEFACTRT listing I/Os by DDname and device can shoe dozens or hundreds of EXCP numbers for a two DSN STEPLIB. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
