We were early adopters of SMF logger. Only used in parallel sysplexes, i.e. with CFs. A few additional differences from traditional MANx environment.
-- Captured SMF data is offloaded periodically to dynamically allocated data sets. In contrast to MANx, where a full data set is written out somewhere (often but not necessarily to tape), SMF logger gives you essentially unlimited space. Except that space is never truly unlimited. If you run out of logger offload space, you're in trouble. -- Since there is never any detectable 'full' condition, you must run your offload-to-tape process periodically. Literally, at regular time intervals. -- Be sure to provide for a fallback switch to MANx data sets by keeping an SMFPRMxx member that names them rather than logger. If all else fails, going back to MANx should give you some breathing room. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Horne, Jim Sent: Friday, November 15, 2019 7:46 AM To: [email protected] Subject: (External):Re: [EXTERNAL] Re: Collecting SMF dataset using LogStream Al forgot about message flooding. If you are having issues losing SMF data because it sometimes arrives too fast and swamps the MANx datasets, logstreams can help with this. I don't know how effective DASD only logstreams would be with this because we don't use them but they may help if you have that issue. If you are not losing data then I agree with Al, that DASD only logstreams do not really help a lot. Logstreams, though, are a wonderful thing. We converted to sysplex-wide logstreams back in 2011 and have never looked back. Jim Horne -----Original Message----- What others have said, Read the books,.... You did not say what your environment is (single image, base sysplex, parallel sysplex). IMO, unless/until you are running a parallel sysplex, logstreams are of minimal (if any) benefit. A parallel sysplex requires a coupling facility to support logstreams. If you do not have a coupling facility, DASD only logstreams are available. DASD only logstreams cannot be shared. This negates the major benefit of defining the logstreams in the first place. So unless you are running a parallel sysplex, the only thing you have changed from what you are doing today, is the method of recording and possibly increased the maximum recording rate ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
