Hello 3000-L folks,

Re: NMLG Files & MPE logfiles.

Now that I have completed the conduit / wiring for 3 new circuits in my
garage I am back to learking on the 3000-L (Now I can fire up my Craftsman
Drill Press and not dim the ceiling lights!  I wonder if Bill & Dave ever
had this problem?).

OK, now to the question in hand - In a past life as a customer in a HP-3000
shop I had a tool I ran which feed the current date -7 into the store
command.
when the program ran it looked something like:

:file t=$null
:store [log in to unmask],[log in to unmask];*t;show;purge;dates<=1/16/01

I have checked the HP Variables and I did not find a easy way to do this
with out writing a program, but maybe someone out here has an idea.

I ran this tool directly after I completed a full backup and disabled it
any time I had a case/call open with the RC for a problem that they might
need to look at the MPE or Network logfiles for.

One other thought about MPE or Network logfiles consuming a large amount
of disk space is to evaluate what is enabled for logging...  I can not
speak for the MPE logging, but as far as network logging goes you "might"
want to reduce the logging to:

           Class    Console Disk
Subsystem  Name     Logging Logging  Event

           CLAS0001  [Y]     [Y]     Serious internal error
           CLAS0002  [Y]     [Y]     Internal error/operator attention
           CLAS0003  [N]     [Y]     Non-critical errors
           CLAS0004  [Y]     [Y]     Nodal messages (start/stop)
           CLAS0005  [N]     [N]     Informative messages
           CLAS0006  [N]     [N]     Statistical information

for each of the network subsystems.  This will reduced the frequency these
logfiles are written to and fill up.

In the case where you are working to resolve a difficult network problem,
it is likely ALL of the CLASS for the appropriate subsystems will be
enabled for Disk Logging "Y".

Note:  Logging is enabled when you perform a :switchnmlog update.

To view your Network Logging you go to NMMGR:

:nmmgr
[open config]
[ns]
[unguided config]
[Go To Logging]
[Next Screen ...
... Exit Logging]
[Prior Screen]
[Prior Screen]
[Prior Screen]
[Exit Program]
:switchnmlog update

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.