Jay, Make certain that SMFPRMxx has DDCONS=NO, NODETAIL, EMPTYEXCPCSEC(SUPPRESS), and INTERVAL is set to at least an hour
Then check out for DB2 traces That should cut down your DB2 SMF records Steve -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Campbell Jay Sent: Wednesday, June 20, 2012 4:25 PM To: [email protected] Subject: Re: SMF volume - follow-up This is just type 100 - 102 records on 2 out of 11 LPARS BTW. For some reason - the word "overkill" came to mind. So I decided to conduct "Operation Overkill". 36 MAN* datasets per LPAR... MAN0 - MANZ... 3337 cylinders per MAN*. 24 hourly jobs to MOD the DUMPXY contents to virtual tape. ( First job each day is DISP=NEW just to keep things pretty ) The following day we have a problem. IEFU29 isseued "I SMF" every 3 minutes. Here's what 1 of the 2 LPARs looked like... Jay Campbell -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Campbell Jay Sent: Monday, June 11, 2012 6:01 PM To: [email protected] Subject: SMF volume Is anyone else is required to collect and retain 500,000 cylinders + of SMF data on an LPAR in one day... how do you handle the downstream copies ? Jay Campbell ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
