We run an SDSF LOG command in batch periodically to try and reduce
the long wait for the first log access.
Bill
On Thu, 24 Jul 2008 06:33:33 +0200, Barbara Nitz [EMAIL PROTECTED] wrote:
How much syslog do you keep in your spool (hours, days, weeks)? Also,
that depends on how often someone does
On Wed, 23 Jul 2008 06:44:49 +0200, Barbara Nitz [EMAIL PROTECTED] wrote:
When I established operlog here, I got temporary update access to all ISPF
profiles for the company to change the default log a in SDSF to log s to not
'irritate everybody'.
Since it was too late for me to change the
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
] On
Behalf Of Mark Zelden
Sent: Wednesday, July 23, 2008 7:50 AM
To: IBM-MAIN@BAMA.UA.EDU
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
: 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
How much syslog do you keep in your spool (hours, days, weeks)? Also,
that depends on how often someone does it and update HASPINDX.
24 hours on every system. Which is why I'd rather use operlog when I know
something stretches across midnight.
I'll keep in mind that the long time for the first
I keep dumps for 6 months, as I recall reading that is how long
DAE remembers an SVC dump occurred...
Bruce Hewson
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the
How old is the oldest dump you recall having to go back to?
That was the one occurance, and since all dumps get filtered through me,
anyway, I *knew* there was a saved one that was about 3 weeks old.
Anyway, it took me long enough to get a consistent erep saving set up here, so
that I can
On Tue, 22 Jul 2008 04:17:11 -0500, Bruce Hewson [EMAIL PROTECTED]
wrote:
I keep dumps for 6 months, as I recall reading that is how long
DAE remembers an SVC dump occurred...
Sort of. DAE ignores entries that haven't been updated in 180 days. Sounds
like a good reason to use 6 months.
On Tue, 22 Jul 2008 14:13:27 +0200, Barbara Nitz [EMAIL PROTECTED] wrote:
I have been unable so far to convince the powers that be that operlog is
much better as it definitely shows more (everythings after a $pjes2 during
shutdown), so no one really cares about operlog.
That is a minor
That is a minor benefit.
Not to me, it isn't. To me this is a HUGE benefit. I am the one who is supposed
to figure out why 'automation didn't work' during system shutdown, especially
when the operator forced down Jes2 after he couldn't see the jobs/stcs that
hadn't come down *before* JES. Or
Quoting Mark Zelden:
Why not migrate them directly to ML2 with HSM? That is what we do.
They are only on DASD for a short time.
We use MPF to kick off a task to extract the dump summary and create an
ISPF table I use to manage the dumps. The dump itself is flicked to ML2
- on virtual tapes
Shane Ginnane wrote:
Quoting Mark Zelden:
Why not migrate them directly to ML2 with HSM? That is what we do.
They are only on DASD for a short time.
We use MPF to kick off a task to extract the dump summary and create an
ISPF table I use to manage the dumps. The dump itself is
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs
Shane Ginnane wrote:
Quoting Mark Zelden:
Why not migrate them directly to ML2 with HSM? That is
what we do.
They are only on DASD for a short time.
We use MPF to kick off a
On Mon, 21 Jul 2008 10:28:39 -0400, Mark Jacobs [EMAIL PROTECTED]
wrote:
Shane Ginnane wrote:
Quoting Mark Zelden:
Why not migrate them directly to ML2 with HSM? That is what we do.
They are only on DASD for a short time.
We use MPF to kick off a task to extract the dump summary and
Mark Zelden wrote:
On Mon, 21 Jul 2008 10:28:39 -0400, Mark Jacobs [EMAIL PROTECTED]
wrote:
Shane Ginnane wrote:
Quoting Mark Zelden:
Why not migrate them directly to ML2 with HSM? That is what we do.
They are only on DASD for a short time.
We use MPF to
snip---
We have had several occurrences of needing both dumps and archived
syslog/operlog data from several months in the past. As you stated tape
is cheap and I would much rather have it and not need it than the reverse.
Rick Fochtman wrote:
snip---
We have had several occurrences of needing both dumps and archived
syslog/operlog data from several months in the past. As you stated
tape is cheap and I would much rather have it and not need it than
,(2400,100),RLSE),MGMTCLAS=MNIG9
//*
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rick
Fochtman
Sent: Monday, July 21, 2008 10:45 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Dump management
snip
On Mon, 21 Jul 2008 11:45:03 -0500, Rick Fochtman [EMAIL PROTECTED] wrote:
--unsnip
I'm curious; are you using an automated process to get SYSLOG to tape?
We use an automatic command to close the current log and open a new one
every
That sounds good, Mark, but I don't have the advantage of the level of
automation you seem to have. If I can't get it via JES2 Automatic
Commands or MPF exits, I just plain ain't got it. But a MPF exit to stop
the External Writer when it goes idle doesn't seem like much of a
challenge. :-)
I
21 matches
Mail list logo
