DOVANO,MICHAEL writes:
...stuff about MOVER corrupting ISL utilities in MPEXL.SYS deleted...
>
> So what are we doing about it? We have removed the offending patch from the
> HP ESC web site, and are taking additional steps to insure that no further
> patches containing ISL utility files will go to HP ESC in the short term. In
> addition, we are escalating the priority of the MOVER to Store-to-disk
> conversion. When we have a more solidified schedule, I will make another
> announcement here.
I realize that "short term" is imprecise and that impatience is an occasional
personality trait of mine, but eight days after the above paragraph was posted,
the following problems exist in the patches at ftp://us-ffs.external.hp.com:
1) /mpe-ix_patches/c.55.00/catalog refers to MPEKXQ1A as "SA1047 after
installing MPEKXN9B", yet the actual patch files MPEKXQ1A and MPEKXQ1A.txt do
not exist. I believe MPEKXQ1A was an ISL patch, and I suspect it was forcibly
deleted due to the MOVER issue. Is it a good thing or is it a confusing thing
for these deleted patches to still be listed in the catalog?
2) /mpe-ix_patches/c.55.00/catalog refers to MPEJX41B as "SA 1050 When Running
SYSDIAG/SYSMAP On ALINK Card With No D". The actual patch files MPEJX41B and
MPEJX41B.txt both exist, but if you read the remarks in the .txt file, you
see the patch is an ISL patch (subject to the MOVER problem) and that the
status is marked bad. IF IT'S A BAD MOVER PATCH, THE TRUCK FILE SHOULD BE
DELETED!!!
3) The original c.60.00 patch that caused me to discover this MOVER issue,
MPEKXK7C, has been deleted. But unfortunately it's been superseded by MPEKX37I
which is listed in /mpe-ix_patches/c.60.00/catalog as a normal valid patch
with both a MPEKX37I truck file and a MPEKX37I.txt documentation file. THIS IS
A BAD MOVER PATCH, AND THE TRUCK FILE SHOULD BE DELETED!!!
So to summarize, bad MOVER-corrupted patches are still available for download
from us-ffs, and the patch catalogs are inconsistent when it comes to listing
or not listing bad patches.
If I were in charge of the MPE patches on us-ffs, I would immediately switch
to building the truck files with MOVER651 and change UNPACKP to refer to
MOVER651 instead of the evil MOVER635. Immediate problem solved with minimal
effort. Doesn't rely on humans following (or forgetting) a policy of manual
exception. Take your time migrating to Store-To-Disk in order to do it right.
But I'm not in charge of the MPE patches on us-ffs. However I *am* in charge of
my patchman script :-), and I've enhanced it to look for catalog inconsistencies
as well as MOVER-corrupted patches (by looking for the problem MPEXL.SYS files
in the patch remarks). Look for a patchman update announcement on HP3000-L
shortly.
--
Mark Bixby E-mail: [log in to unmask]
Coast Community College Dist. Web: http://www.cccd.edu/~markb/
District Information Services 1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
|
