I just have our scheduler system submit a batch SDSF job every morning @0700 that issues a "LOG S" followed by ++ALL and that updates HASPINDX. No more waiting on SYSLOG when I get in the morning. Dennis
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden Sent: Wednesday, July 23, 2008 7:50 AM To: [email protected] Subject: Re: Dump management On Wed, 23 Jul 2008 06:44:49 +0200, Barbara Nitz <[EMAIL PROTECTED]> wrote: > >The thing that I really hate is that it also takes just about forever when I look into syslog - log s (even on the same system). > How much syslog do you keep in your spool (hours, days, weeks)? Also, that depends on how often someone does it and update HASPINDX. Sometimes my first access in the morning is slow if it is one of the systems that operators don't look at the syslog (LPARs that don't run batch jobs like SAP and WebSphere). Some of our systems keep 24 hours, others only 12 hours. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
