I would also add to remove network logs as well. These get very large.

do a listf nmlg####.pub.sys,2

If you have many, do  PURGE NMLG####.PUB.SYS and respond yes when prompted. It will not purge the active log, then do a switchnmlg and a switchlog

HTH :-)
Joe

From: Craig Lalley <[log in to unmask]>
Date: 2007/12/06 Thu PM 04:53:21 CST
To: [log in to unmask]
Subject: Re: [HP3000-L] System Logging Error

--- Marti Jarsey <[log in to unmask]> wrote:

> One of our servers is reporting the following error when we execute
> switchlog.
>  
> :switchlog
> 
> NMEV#200@221 System logging is not enabled at the present time.
> 
> System Logging message 900
> 
> :
> 
>  
> We've verified that system logging is enabled.  And I see current
> console logs in the active log file.  
>  
> The server is a 987 running POWERPATCH C6504 P4
>  
> Has anyone seen this before?

Marti,

Yes I have seen it SEVERAL times before, one time very recently.

There are a couple of causes, mainly 
1) out of disc space on the system volume set
2) pre-existing logfiles

I would recommend, 

1) purge all log file LOG####.PUB.SYS

if you don't want to get ride of them, then rename them into a new group

NEWGROUP OLDLOGS
COPY LOG????.PUB.SYS, LOG????.OLDLOGS.SYS

2) Make sure you have enough free space

DISCFREE "C,,MPEXL_SYSTEM_VOLUME_SET"

Generally I would like to see at least 30% available.

3) Reboot, I have yet to find a way to re-start logging without rebooting.

-Craig

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


joseph dolliver
e3k solutions , inc
41630 marie court
leonardtown, md 20650

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *