HP3000-L Archives

November 2000, Week 1

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:
Dennis Heidner <[log in to unmask]>
Reply To:
Dennis Heidner <[log in to unmask]>
Date:
Thu, 2 Nov 2000 23:31:50 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
I've got AUTORESTARTiX on several machines.  It works as describe, but
takes some getting used to and a little work to set it up so it is
effective.

1.   You need a disk just for dumps.  The larger the drive the better
(9GB).  If possible create at least three dump areas on the drive.

2. You create a autoboot file which describes the actions after the system
aborts -- or sits at the CM prompt for too long.   I.E. rebooting for
patches and forgetting to "press any key in 10 seconds" will result in the
autoboot file executing and a memory dump being taken.  This is the reason
for creating multiple dump areas... that way if you forgot and it takes a
memory dump on the way up, there still is at least one other dump area for
real panics. This need to watch the console and press any key is one of
those features you need to get used to...  it is possible to turn off
AUTOBOOT  for patches, but I seem to always forget.

3.  Change the SYSSTART so you startsession on someother user besides
manager or operator.  A special BOOTUP user for example.  You can then
setup a logon UDC that does most of the dirty work to bring the machine
back up in a good known state... then logon the console as operator.sys.

4.  The AUTOBOOT file typically contains two lines:   DUMP and START -R
RECOVERY,   because you are starting in a recovery mode, jobs and spool
files will hang around (as desired), but it also means that the system will
have booted up on the BOOTUP.SYS  group and not the CONFIG.SYS, which means
should you decided to make system configuration changes, that you will have
to change the BASE group in SYSGEN.

5.  You will need to run DTODSIZE periodically to see if the dump areas are
large enough.  It is best to run DTODSIZE middle of the day when the
machine is heavily loaded (lots of users and processes).  That will give
you the best size estimate.

6.  Creating the dump areas or changing the sizes can chew up lots of CPU
and wall clock time.  Best to do these changes when production is NOT at
the peak, i.e. late evening or weekends, not middle of day.

ATOM RSS1 RSS2