DDCONS does not do I/O, it only consolidates SMF I/O records, costing (much)
CPU and elapstime to produce the records, but it will not add I/O counts to
the step.
Yep, I understand it accumulates all the interval counts for a given DDname and
device and writes only one entry with the total
Do you have SAS and MXG at your shop? If so, then the MXG.SOURCLIB will
have information on what you are looking at.
No, we don't.
--
Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
Sent: Wednesday, June 03, 2015 3:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: Is EXCP data from SMF 30 interval records repeated in step end
records?
Do you also see subtype 5 (Job termination)?
Yes, but they are not of interest for the question at hand.
What is your DDCONS
Do you also see subtype 5 (Job termination)?
Yes, but they are not of interest for the question at hand.
What is your DDCONS and INTERVAL setting?
DDCONS is what I was missing, well actually, I forgot about it. Thanks for the
reminder.
We do have DDCONS(NO)
--
Peter Hunkeler
:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Is EXCP data from SMF 30 interval records repeated in step end
records?
Please bear with me; I never had to dig into this detail on step end EXCP
SMF
reporting.
I'm analysing a perfomance issue with long running (35 hours) a batch job
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
Please bear with me; I never had to dig into this detail on step end EXCP SMF
reporting.
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
Peter Hunkeler wrote:
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
