After a decade of parallel sysplexing, I feel like a rookie with log streams. Up to now we've used system logger only for CICS and RRS. No operlog, no logrec. So we've never had to deal with the question of how to handle real data that needs to be kept (archived), massaged, and cleaned up.
I'm now playing with the new SMF log stream available in z/OS 1.9. Not many folks have done this yet, but I think the problems are similar to other data-type log streams. Capturing the SMF data in a CF structure is easy. Logger writes the data out to data sets of the form 'hlq.IFASMF.xxx' where you choose the qualifier and tell the system what the name is. There is a new dump utility called IFASMFDL. Here's the problem. IFASMFDL does most of what IFASMFDP does (and more), but what it *doesn't* do is clear out the dumped SMF data. In other words, after archiving the contents of a log stream to a flat file, the now dumped records are still sitting just where they were. A subsequent run of IFASMFDL appears to pick up the same records all over again. The output file just gets bigger and bigger each time the dump is run. For those of you who use system logger for operlog or logrec, how do you clean up log streams so that you get one and only copy of all the data produced? . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
