Stop the SDSF server on the systems. Then define a larger ISFINDX file. Then restart the SDSF server.
On Wed, 1 Nov 2006 10:18:27 -0600, Hal Merritt <[EMAIL PROTECTED]> wrote: >Sorry, I failed to mention that this is a testplex. > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On >Behalf Of Hal Merritt >Sent: Wednesday, November 01, 2006 10:07 AM >To: [email protected] >Subject: SYSLOG Broken > >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!!! > ---------------------------------------------------------------------- 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
