HP3000-L Archives

March 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Mon, 16 Mar 1998 12:13:52 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Dave,

Try :RESUMELOG from the console. If you get a message similar to "can't
fopen LOGnnnn.PUB.SYS" then either rename or purge LOGnnnn.PUB.SYS and try
the :RESUMELOG again. There are other reasons that logging may shut down and
the logging error number will indicate that.

Doug Werth                                     Beechglen Development Inc.
[log in to unmask]                                       Cincinnati, Ohio

The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.

>>My memory of having encountered this situation in the past was a
>>runaway job creating a spoolfile which used up all disc space.  I
>>believe the only way to restart logging is to restart the system.
>>Perhaps you could look in the last logfile that remains to see if there
>>was any indication of the problem leading to logging being turned off,
>>however it may not have been able to log the condition before having
>>lost logging.

ATOM RSS1 RSS2