Hello Peter, OPERLOG captured daily to GDG. Easiest way.
SYSLOG per system captured daily. I have used three ways to capture SYSLOG. 1. old- Use and External Writer to capture explicit class reserved for SYSLOG daily. Output can be a GDG, but better is Datestamped dataset. 2. Use SDSF to capture specific system SYSLOG messages for date/time range daily, Output to datestamped dataset. 3. CA-View - use exit to modify SYSLOG file name to include SYSNAME suffix. Capture daily, or as spool dataset spun off due line count. Personally, I preferred data being captured to datestamped dataset. Let HSM to migrate. And possibly manage age based deletion. This allows easy access to diagnostic data using ISPF VIEW commands. OPERLOG for large sysplex often cannot be VIEWed by ISPF, with auto-switch to BROWSE mode, requiring alternate search activities. CA-View is sort of OK, especially if PRINT to DISK has been setup. On Tue, 27 Feb 2018 17:46:23 +0530, Peter <[email protected]> wrote: >Hi > >Just wanted to get an idea on how you are all processing your syslog to an >JES output management Products (could be anything). > >Are you running SYSLOG offload everyday , weekends ? How long you keep the >SYSLOG data online and what are the retention period etc.. ? > >I am trying to set the same thing in my shop but just wanted to know some >best practices from you all. > >Peter > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN Regards Bruce Hewson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
