HP3000-L Archives

September 1997, Week 5

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:
Rick LITTLE <[log in to unmask]>
Reply To:
Rick LITTLE <[log in to unmask]>
Date:
Mon, 29 Sep 1997 13:50:00 -0400
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (29 lines)
Point - CounterPoint

MPEX will allow you to move anything anywhere - When processing the ALTFILE
command to move files, some files are not moved.  I guess the OS protects some
files.  This is also true of the RESTORE command of MPE.  Certain files are
"protected" and you cannot purge the old and restore.

The short, easy answer is to leave all files in PUB, MPEXL, and DIAG groups of
the SYS account alone - The problem of the START NORECOVERY failing was due
to PERFLOG.MPEXL.SYS not being found.  According to HP there is a history of
this file migrating off of LDEV1.  And if the IO files from the CONFIG group of
the SYS account would have been on LDEV1, the system could have found the
PERFLOG file and the system would have started.

UPDATE does not bring in CONFIG files.  This makes sense, when applying a SLT
from HP you do not want to load any config files which would purge your own
unique configuration.  So, if you need to have your config files restored during
an UPDATE process - be sure to UPDATE CONFIG

**I feel the key files moved from LDEV1 manually by MPEX were the files in the
  CONFIG group of the SYS account.
**Files in the BOOTUP group of SYS account are "PROTECTED" as seen by doing
  a LISTF @.BOOTUP.SYS,3

If HP can "PROTECT" some files, why not all the files needed in the Bootup and
Startup processes???

Just Maybe?

ATOM RSS1 RSS2