HP3000-L Archives

January 2000, 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:
Gilles Schipper <[log in to unmask]>
Reply To:
Gilles Schipper <[log in to unmask]>
Date:
Fri, 21 Jan 2000 18:21:22 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
At 03:52 PM 2000-01-21 -0500, Jeff Kell wrote:
>Just be *certain* that your last boot was a 'start norecovery' and your
>next boot will be a 'start norecovery'.  Using the defaults of IOCONFIG
>will try to save your changes to the BOOTUP group, and that will fail
>if your last boot was a simple 'start'.  You can workaround this by
>using SYSGEN/DOIONOW and setting your basegroup to CONFIG before you
>save changes.
>
>If you typically use 'start norecovery' you should have no problems.
>

Which raises the question that I raised a while back - which I have not yet
tried and do not have the answer yet:

What if I had used IOCONFIG or SYSGEN/DOIONOW to add one or disc drives,
then VOLUTIL to add same to MPEXL_SYSTEM_VOLUME_SET?

Several weeks later, I shut down the system and perform a START RECOVERY
because I need to preserve some waiting and/or scheduled jobs.

Presumeably, I would encounter severe difficulties which could  be overcome
by shutting the system down and performing a START NORECOVERY - thus losing
my jobs.

If all these assumptions are correct, one needs to be very careful if
dynamically adding disk drives.
---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]
---------------------------------------------------------------------------

ATOM RSS1 RSS2