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
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Hal Merritt
Sent: Wednesday, November 01, 2006 10:07 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG Broken
We had a task spew console/syslog messages all night long and
exhausted
our
I seem to remember having to issue two commands (unsure of sequence):
W START
V SYSLOG,HARDCPY
Hth... Janek J.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message:
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: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG Broken
We had a task spew console/syslog
Not sure what your abend in SDSF is, but it is possible that the HASPINDX used
by SDSF is cluttered. See how many SYSLOG data sets you have out on SPOOL. I
think you can use the ST command and prefix SYSLOG. Or you can review the size
of the HASPINDX data set and you may need to increase the
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
6 matches
Mail list logo
