Hi,
You can set GO CLEANUP for these to *KEEP, but this will increase your
SAVSYS/SAVSYSINF times by *LOTS, forever. I don't think that the
architects of the System/38 ever reckoned with the scalability of today's
systems. Plausibly a new system value, QHSTLIB (my naively made up name)
could be created to specify a new library to place these, as opposed to
QSYS. In this fashion, these could be kept on disk *FOREVER, and managed
with traditional save/restore (a/k/a SAVCHGOBJ). This would require DSPLOG
to recognize the system value. A big change? I think not, but *ANYTHING
you do takes person months.
Fortunately, or unfortunately, the system keeps extending, and different
things that have worked for decades need to be rearchitected. I have
copied this note to development.
Al
Al Barsa, Jr.
Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z"
e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234
914-251-9406 fax
http://www.barsaconsulting.com
http://www.taatool.com
http://www.systemiconnection.com/
"Steve Martinson"
<smart-consultant
@sbcglobal.net> To
Sent by: <midrange-l@xxxxxxxxxxxx>
midrange-l-bounce cc
s@xxxxxxxxxxxx
Subject
Re: Saving History Log Files
01/16/2008 08:12
AM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Al said:
"Why are the log files to be saved?
We use ours for trouble shooting ... there's a problem, find out about it,
figure out what to do, fix the problem, it is history.
Thus, the issues become ... how long to we need to save them on-line GO
CLEANUP
and reverse engineer what's causing them to be created in first place, so
as not to create any where we don't need so much."
Why are they to be saved? The QHST logs can be very useful in forensic
analysis where the information needed to piece something together may not
be
in the QAUDJRN journal receivers. In these "big" companies, upper
management is often all about the ability to clearly explain root cause
information, even when an event is days or weeks old.
As far as what's causing them to be created in the first place? My
question
was not grounded on dealing with space issues or anything like that. I'm a
FIRM proponent of logging as much as possible whenever and wherever
possible. Having been on the security side since 1995, I have been
involved
in more than one situation where I had to tell management, "Gee, boss, I
can't answer that for you because we didn't log that information." I'd
rather have it and not need it, than need it and not have it.
PS - Thanks, Paul. I was looking for general trend answers like that!
Best regards,
Steven W. Martinson, CISA, CISM, CISSP
Security Consultant
Cypress, Texas
Smart-Consultant@xxxxxxxxxxxxx
Mobile: 713.277.5845
Fax: 281.758.2429
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
