I have seen logging suspended due to several reasons. The simplest way is to
have an existing log file
get into the way the logging processes next numbering sequence. You can
simulate this by building a file
LOG####, were #### will be the next log file. Then at the next SWITCHLOG
logging will be suspended.
The cure is to purge the offending log files and issue the RESUMELOG
command.



Brad Straiton wrote in message <000f01bd50cb$65af1c80$330106c0@brad>...
>My system logging has been suspended... (I didn't know this was possible).
>
>If I issue the 'switchlog' command I get the following message:-
>
>"NMEV#200@221 System logging is currently suspened"
>"System logging message 902"
>
>It looks as if system logging was suspended/disabled in November sometime
so
>I don't know if there were any other error messages pertaining to our
system
>logfiles.
>
>Does anyone know if there is a way of enabling my system logging ?
>
>TIA
>
>BTW - We're running on a HP 979[mpe 5.5]
>
>Brad Straiton
>Systems Manager
>BMD Textiles
>Cape Town