On Fri, 15 Aug 2008 10:26:46 -0500, Laine, Rogers <[EMAIL PROTECTED]> wrote:
>Scott, > >This is information in the SMFPRMxx member. > >SYS(TYPE(0:255),EXITS(IEFU83,IEFU84,IEFACTRT,IEFUTL, > IEFUSI,IEFUJI),NOINTERVAL,NODETAIL) > >We are allowing all type records to be written. (management request). > >We do not have any DOC to tell us what product 132 belongs, thus my problem. > >Do you think one of these exits could be producing this type record. I'm not sure what these exits do. > >Thanks, >Rogers > > >>Scott, >> >>This is what I see when dumping this SMF record. >>I see nothing that jumps out at me that would indicate who this belongs to. >> >> d k¬ "SYSBOPER004 \" >> d k¬ "SYSBOPER007 A | >> d "SYSBOPER007 A | >> d "SYSBOPER004 \" >> d "SYSBOPER004 \" >> d "SYSBOPER007 A | >> > >How unfortunate. Some, hopefully most, ISVs mark their record with some small eye-catcher string, just in case two products are writing to the same record type. Then any SMF data post-processing utility/code can validate that the record is really their own. > >So, it's time to back-track to your PARMLIB(SMFPRMxx) member and/or your intra-day DUMPXY/SMFDUMP job or your nightly SMF collection processing. >Sure hope you might have some DOC reference indicating who's writing that record type. Any authorized software product or application program could be writing this record type to your MAN dataset. > >Another option is to disable the record type in SMFPRMxx and see what program gripes about it when the SMFWTM invocation gets a non-zero RC. Then your prairie dog will pop out of its den! > >Scott Barry >SBBWorks, Inc. > An application program is writing the SMF type 132, not one of the listed exits. Time to take back your SMF recording...from management, per se. Possibly, it's a Bull Moose scenario (flog your mouse-cursor - those from the Morino Associates days, if you know Bull Moose....or if you are one!). Technical individuals who are force-groomed and promoted, sometimes side-swiped, to a manager position, dragging along their legacy SYSPROG/geek 'ness! My vote is turn off the record and see who complains first, likely to occur in your SYSLOG. Be sure that a manager-type is aware of your action for CYA protection. Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- 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
