On Wed, 26 Mar 2008 09:38:10 -0700, Skip Robinson <[EMAIL PROTECTED]> wrote:
>We've had occasional episodes of lost data. > >One case, which we think we've fixed via changes to automation, is the >other side of the event-driven nature of MANx management. A strength of >traditional SMF recording is that you dump and clear a MANx cluster in >response to a message saying that it needs dumping. That's why you don't >have to worry much about whether you've collected ten hours or ten minutes >worth of data. You dump whatever's there, clear the file, and move on. A >problem crops up when you IPL with all defined SMF data sets in need of >dumping. They're not necessarily 'full'; they just can't be opened because, >well, who knows why. I've seen MANx data sets at 1% that nonetheless >require dumping. Go figure. But if all MANx data sets are full at IPL, data >starts getting buffered. In our shop, the messages that should trigger >dumping come out before our automation product has hit the ground. Our >so-far-untested automation change is to trigger a dump when buffering has >reached a certain threshold. Without that additional check, you can lose >data when you run out of buffers. > We (and many shops) use the "CBIPO" SMFDUMP program in combination with IEFU29. This is the one that dumps all the full data sets and also does a switch command. We use the SMFDUMP program at midnight to cut things off for daily processing and IEFU29 the rest of the time. I also use the SMFDUMP program at IPL time to take care of the situation described above. Both processes use the same SMFDUMP proc. Here is an example of what it looks like (some LPARs dump to tape instead of disk): //SMFDUMP PROC MAN='X',ALL=FALSE //* //* THIS PROC IS NORMALLY STARTED VIA IEFU29 SMF EXIT WHEN AN //* SMF DATA SET SWITCH OCCURS (ONLY THE FIRST STEP RUNS): //* S SMFDUMP,MAN=SMF.DATA.SET.NAME //* //* AT IPL TIME IS IS STARTED AS FOLLOWS TO RUN THE SMFDUMP //* PROGRAM TO ENSURE ALL FULL SYS1.MANX DATA SETS ARE DUMPED: //* S SMFDUMP,ALL=TRUE //* //* IT IS ALSO STARTED THIS WAY AT MIDNIGHT TO USE THE SMFDUMP //* PROGRAM WHICH FORCES AN SMF SWITCH IN ORDER TO CAPTURE ALL //* THE SMF DATA UP TO THAT POINT FOR DAILY PROCESSING. //* //TESTEXEC EXEC PGM=IEFBR14 //* //**************************************************************** //TESTONE IF (TESTEXEC.RUN NE &ALL) THEN //**************************************************************** //DUMPONE EXEC PGM=IFASMFDP,TIME=1440 //SYSPRINT DD SYSOUT=* //DUMPIN DD DSN=&MAN,DISP=SHR //DUMPOUT DD DSN=hlq.&SYSNAME..SMF(+1),DISP=(,CATLG), // DCB=(SYS1.MODEL,LRECL=X,BLKSIZE=32756,RECFM=VBS),UNIT=SYSDA, // SPACE=(CYL,(300,300),RLSE) //SYSIN DD DUMMY // ENDIF //**************************************************************** //TESTALL IF (TESTEXEC.RUN EQ &ALL) THEN //**************************************************************** //DUMPALL EXEC PGM=SMFDUMP,TIME=1440 //SYSPRINT DD SYSOUT=* //DUMPOUT DD DSN=hlq.&SYSNAME..SMF(+1),DISP=(,CATLG), // DCB=(SYS1.MODEL,LRECL=X,BLKSIZE=32756,RECFM=VBS),UNIT=SYSDA, // SPACE=(CYL,(300,300),RLSE) //SYSIN DD DUMMY // ENDIF Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
