On Thu, 26 May 2022 10:10:24 -0500, Steve Beaver <[email protected]> wrote:
>I have a friend whose systems produces BILLIONS of SMF records per month and > >He is basically using the following DEFINE for his DEFAULT LOGSTREAM. > > > >I will tell you simply that I have no IDEA if the NUMBERS for STG_SIZE and >LS_SIZE > >Are crazy or inline. I know those numbers can be revised on the fly > > > > DEFINE LOGSTREAM NAME(IFASMF.&SYSNAME..SMFDFLT) > > DASDONLY(YES) > > STG_SIZE(119880) /* IN 4K BLOCKS */ > > STG_DATACLAS(MVSLOGR) > > LS_DATACLAS(MVSLOGR) > > LS_SIZE(119880) /* IN 4K BLOCKS */ > > HIGHOFFLOAD(85) > > AUTODELETE(YES) > > RETPD(90) > Suggest analyzing SMF type 23 data for SMF recording activity - this information will help determine minimum sizing based on anticipated max SMF LS offloading needed - this information will help contribute to your LOGR attribute sizing interests. And along the way, analyze your SMF 88 activity to monitor LOGR with SMF LS data-handling. Scott Barry SBBTech LLC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
