Subject: | |
From: | |
Reply To: | |
Date: | Mon, 15 Mar 1999 09:30:00 -0800 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
Last week I posted the message below and have not seen any comments about it.
Am I the only 'lucky' one that got burned by this?
Paul Christidis
____________________Reply Separator____________________
Subject: SA1486 and PERFLOG.MPEXL
Author: "paul h christidis"@mime.mail.hac.com
Date: 3/8/99 1:10 PM
On Sunday 3/7/99 we were scheduled to upgrade our HP3000 to PP6 of MPE/iX
5.5. We were proceeding along nicely when, during the UPDATE, we got a
'System Abort 1486' while the file 'PERFLOG.MPEXL.SYS' was being restored.
We also got the same error when we tried using the SLT tape that was
created before we begun the PP6 upgrade.
I called the HPRC and after some effort we were able to bring up the system
booting from the primary path, renaming the 'perflog' file and then perform
the update again. This time we got an error message but the process
continued on and the upgrade was successful. The RC engineer found 28
recent references to this problem with the recommended solution of removing
the file from the 'system file' list and restarting the upgrade from the
beginning.
I know that some discussion about this file, (that a system would not
'boot' if said file is missing, and that it must reside on LDEV1, and that
be default is NOT included on the SLT tape, and instructions on how to
'make' it reside on LDEV1 and how to 'include' it on the system files list,
etc.. ) did occur on this list not too long ago. In fact I followed those
instructions for 'perflog..' and 'editor.pub.sys', and yet I still fell
'victim' to the problem that I was trying to guard against.
Did anyone else have a similar experience? There is another system in a
remote site where the 'perflog' file has been added to the 'system file'
list and I'm wondering if they'll have a similar problem the next time they
perform an update.
Regards
Paul H. Christidis
|
|
|