You will not be able to change the bootup log file number without
priv mode bit twiddling. Rename or store & purge LOG3715 and
any higher numbers then restart the system. If you just purge the
logfiles Murphy's Law will guarantee you need them later.

Bob J. -- Ideal Computer Services
http://www.icsgroup.com



kpmiller wrote:

> I have an HP3000 that when it boots up,
> it suspends system logging, because a logfile already exists.
>
> ie, it attempts to log to LOG3715,
> but files LOG3715-3756 exist.
>
> How do I clean this up?
> I thought with sysgen, creating a tape, I could control/change the log 
> number.
> But the only parms are NOLOGNUM or LOGNUM. Not sure if that can help.
>
> Is it best to just purge the LOG files, and then let it startup?
> or can I change the LOG number?
>
> Thanks,
> Keven Miller   [log in to unmask]
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>

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