On Wed, 1 Nov 2006 10:06:45 -0600, Hal Merritt <[EMAIL PROTECTED]> wrote:
>We had a task spew console/syslog messages all night long and exhausted >our spool. We purged a lot and we are down to 50% spool, but the syslog >function under SDSF still abends. > >Before this, there was a lot of evidence of the JES environment being >corrupted because we failed to cold start after flashing the production >environment. > >Just for fun and our education. we would like to try to recover without >doing a cold start. > >I think we could just somehow blow away the SYSLOG and restart that >process on one of the two LPARS in the MAS. > >Any ideas? > >Thanks!!! > Re-allocate the HASPINDX (SDSF) data set bigger. The other option is to get the syslog out of the spool. Your daily procedures are probably already set up to do this. Depending on when you last issued a WRITELOG command (for example, "W L"), you may have to do that first. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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
