On Thu, 2 Nov 2017 12:30:04 -0400, John Eells <[email protected]> wrote:
>Jesse 1 Robinson wrote: >> I'd like to echo earlier advice to avoid this whole problem altogether by >> moving to SMF logger. Among the problems solved by logger is the need to >> synchronize offload processes. This is because offload is independent of IPL >> and other system activity. There is no longer a 'full' condition to deal >> with. Setting up for logger requires some preparation, but no user code >> creation. It's all determined by parms and governed by TOD. >> >> Although I have not set it up, SMF logger, like other logger exploitation, >> should be doable without a CF by using DASD-only logging. >> > >SMF data can definitely be written to DASD-only log streams (one or more). > > >-- >John Eells >IBM Poughkeepsie >[email protected] > SMF logstream mode (defined as DASD-only log streams, sized between 2GB and 4GB-max) - definitely working like a charm for one client we support. Having 5-7 topic-related (certain SMF types) SMF LS definitions and a system-default for all others. All are DFHSM-managed (no tape subsystem dependency), and also various MGMTCLAS retention-limits defined, per AUDIT requirements. Started back in early 2010 and were then using SMF MAN files for a transition time-period, with CA SMF DIRECTOR (exit-invoked with SMFDLS) using ARCHIVE option (vs DUMP) to continually trim SMF LS and OFFLOAD datasets) allowing much flexibility to migrate LPAR-groups, again, all SMS-managed, and having intra-day SMF offloads, which allows programmer-access to desired SMF types (DB2 TRACE, security data), in addition to directly reading SMF LS via IFASMFDL when/if needed. Total dymamic-allocation used with CA SMF DIRECTOR, even during back/forth transition-testing (i.e., you tell SMF DIRECTOR a date/time, etc., and it knows where to go find the SMF data, along with optional content filtering/selection). Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
