:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to speed up IFASMFDP SMF Dump process
Radoslaw Skorupka wrote:
>> I don't know about IFASMFDL
>AFAIK the IFASMFDL is "system logger mutation" of IFASMFDP.
Thanks. I just forgot about this explanation.
>Note, currentl
Radoslaw Skorupka wrote:
>> I don't know about IFASMFDL
>AFAIK the IFASMFDL is "system logger mutation" of IFASMFDP.
Thanks. I just forgot about this explanation.
>Note, currently IBM pushes customers to use logger instead of SYS1.MAN
>datasets.
I am just waiting for big blue's SOD that
W dniu 2018-03-15 o 10:14, Elardus Engelbrecht pisze:
Martin Packer wrote:
I always thought IFASMFDP (and now IFASMFDL) could do with an exit point - so
you could reformat (flatten, essentially) or filter records using it. That
might cut down data moves.
IFASMFDP has such exit points where
Martin Packer wrote:
>I always thought IFASMFDP (and now IFASMFDL) could do with an exit point - so
>you could reformat (flatten, essentially) or filter records using it. That
>might cut down data moves.
IFASMFDP has such exit points where USER1/2/3 exit points are given control
after each
I always thought IFASMFDP (and now IFASMFDL) could do with an exit point -
so you could reformat (flatten, essentially) or filter records using it.
That might cut down data moves.
Next time I talk to “Mr SMF” I should ask him - but I’m already tying up
enough of his time. :-)
Cheers, Martin
One thing to consider is the number, type and complexity of the control cards
being used in the dump utility request itself;
if you are using a "lot" of output targets you might consider using a "SORT"
type program instead of the IFASMFDP utility itself for the dump process (you
still need it
: 49602 3-1404
Fax: +55 11 3684-4427
-Mensagem original-
De: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Em nome de
Lizette Koehler
Enviada em: segunda-feira, 12 de março de 2018 16:38
Para: IBM-MAIN@LISTSERV.UA.EDU
Assunto: How to speed up IFASMFDP SMF Dump process
I
>>Set MANx CISIZE to half track (26624).
> Interesting. Why half track? Is it documented that it will help? Just curious
> if you don't mind, please.
Short answer ... 26K (or even 16K) of data written per I/O is much better
than the default of 4K (CI Size).
It really speeds up the writes
Let me add to my post - if you read abut SMF CI Size in member ACHAP03 of the
MXG source/documentation library, you will see a very good discussion of the
trade-off between DASD space and CISIZE in MANx datasets. Apparently SMF
doesn't do VBS in the MANx datasets in the same way "regular" VBS
Tim Hare wrote:
>Set MANx CISIZE to half track (26624).
Interesting. Why half track? Is it documented that it will help? Just curious
if you don't mind, please.
>//AMP='BUFND=60',
>60 buffers = 2 cylinders if you are using half track CI sizes.
That is a good one. I really need
Do you have MXG? They have a program, ANALSMF, which will analyze your current
SMF. In general, what I've done and which seemed to help:
Set MANx CISIZE to half track (26624).
In your IFASMFDP JCL to dump a full MANx dataset (we use IEFU29 to issue a
start for SMFDUMP JCL to dump one
Lizette Koehler wrote:
>I was wondering if there are any tricks to making the SMF Dump process more
>efficient or faster?
I have gotten many problems with the SMF dump process - anything from slow
dumping, ENQs accross SysPlex and also during IPL, Timing issues, running out
of space, name it.
I was wondering if there are any tricks to making the SMF Dump process more
efficient or faster?
And parms on the VSAM Define for the MANx files (like STRNO or RLS) that might
help?
I know about the SMF LOGSTREAM - but not ready to do that yet
I am just using the IBM program IFASMFDP for now
13 matches
Mail list logo
