I got this document from MPE Patch
May be related...
------------ Cut here ---------------------
Patch Package Size: 177616 sectors
General Release Text:
Known Conflicts
===============
Not applicable
Patch-to-Patch Dependencies
===========================
>From MPEJXA2 and MPEJXL8:
o MPE/iX 5.5 customers should apply MPEJX83 and MPEJXL8 at the
same time.
External Symptoms, Cause, Fix Description
=========================================
After installation of PPC5505, or patch MPEKX79 or later, apparent
data corruption is observed after doing an operation that "erases"
a database or other (e.g. Quiz) file.
The database problem is seen as:
Intermittently, following an ERASE command in DBUTIL, data is not being
completely erased from datasets. This results, for details, in image
error -3, for example:
TURBOIMAGE ERROR AT $00016710; RETURN STATUS = -3
DBPUT, MODE 1, ON RESIDENTIAL OF realty
MPE FILE ERROR 0 RETURNED BY FREADDIR ON ROOT FILE
For master datasets, dbputs fail with DUPLICATE KEY VALUE IN MASTER
(error 43).
The workaround to the problem is to use
DBUTIL PURGE -> DBSCHEMA -> DBUTIL CREATE
instead of DBUTIL ERASE. To do this, the following is necessary:
o Have a current schema of the database
o If the database is attached to Allbase/SQL, ensure current copies
of the data mappings, etc. are available.
The Quiz file problem has been seen as a situation wherein a job uses
Quiz to erase the file, then reloads the data using a Fortran program.
In some cases, the resulting file contains large chunks of blank space.
As several patches which supercede MPEKX79 have already been built
and released, the effect of this patch is to supercede all of these
patches, but back out the MPEKX79 changes.
Customer Environment Changes
============================
Not applicable
Hardware Dependencies
=====================
Not applicable
Software Product/Application Dependencies
=========================================
Not applicable
Product Version Information
===========================
See filename information for specific version changes for each module.
Dump Analysis
=============
Not applicable
Product Number/Name:
HP31900 MPE/IX
Product VUF: C.05.08
OS Release VUF: C.55.00
Fix Release Version: A
Supersedes:
( 0)MPEKXJ3 A
( 1) MPEKXG6 B
( 2) MPEJX57 B
( 2) MPEKX94 A
( 3) MPEKXE9 A
( 4) MPEKXE4 A
( 5) MPEJXL3 A
( 6) MPEHXK2 C
( 5) MPEJXQ3 A
( 6) MPEJXB4 A
( 5) MPEKXB5 A
( 6) MPEKX79 A
( 7) MPEKXB4 A
( 8) MPEKX74 A
( 9) MPEKX97 A
(10) MPEKX44 C
(11) MPEKX68 B
(12) MPEJXY8 C
(13) MPEKX72 C
(14) MPEJXF9 A
(14) MPEKX76 A
(15) MPEKX63 B
(16) MPEKX03 B
(17) MPEKX38 B
(18) MPEKX06 C
(19) MPEHXT5 C
(20) MPEKX65 A
(21) MPEKX55 A
(22) MPEJXQ1 E
(23) MPEJXA6 B
(23) MPEJX54 B
(23) MPEJXH3 B
(24) MPEKX18 D
(25) MPEJX55 B
(26) MPEJX86 A
(25) MPEJXX7 B
(26) MPEKX09 A
(27) MPEKX22 A
(28) MPEJXU2 B
(29) MPEJXG5 B
(30) MPEJXU5 D
(31) MPEJXW0 A
(32) MPEJXU6 D
(33) MPEJXD7 C
(34) MPEJXC0 B
(35) MPEJXK6 B
(36) MPEJXJ2 D
(37) MPEJXJ9 B
(38) MPEJXE0 B
(39) MPEJXD1 B
(40) MPEJX48 C
(41) MPEJX09 D
(42) MPEHXW2 B
(43) MPEHXV0 B
(44) MPEHXK5 B
(39) MPEHXT7 B
(40) MPEJXG7 B
(41) MPEJX60 C
(42) MPEJX59 C
(43) MPEHXU9 B
(37) MPEJXR6 C
(38) MPEJXM3 A
(39) MPEJXA8 C
(40) MPEJX56 E
(41) MPEJXH2 G
(42) MPEJX76 B
(42) MPEJXL0 D
(43) MPEJXA2 E
(44) MPEJXE6 D
(45) MPEJX16 D
(44) MPEJXE2 A
(45) MPEJXH1 E
(46) MPEJX80 B
(47) MPEJXA5 A
(47) MPEJXA7 B
(48) MPEJX37 B
(49) MPEJX72 B
(50) MPEJX58 C
(51) MPEJX28 C
(52) MPEHXD4 C
(53) MPEHXT8 B
Criticality:
(1) The system could experience a System failure without the patch.
Distribution Recommendation:
For a FOS product and should be installed on all systems.
Update Required: Yes
Special Instructions:
NO SPECIAL INSTRUCTIONS PROVIDED FOR THIS PATCH
Installation Instructions:
Before installing this patch, please review all instructions and the
Hewlett-Packard SupportLine User Guide or Your Hewlett-Packard Support
Terms and Conditions for precautions, scope of license, restrictions,
and limitation of liability and warranties.
There is a document which gives a detailed descripton of all tasks
required prior to installing your patch. Request this document from
HPSL using e-mail (command: send mpeguide) or download it from the web
Unless there are special instructions, logon as MANAGER.SYS and run
UNPACKP to unpackage and restore all files before installing your
patch.
Note! Please back up your system before you patch.
-----End of Document ID:
MPEKXJ3A--------------------------------------------
[log in to unmask] wrote in message
<[log in to unmask]>...
>My production environment is a 997-300 with MPE 5.5. An irregular and
>infrequent problem started happening last September where suprtool extracts
>out of large image datasets would have corrupted records in it. Simply re
>running the extracts would solve the problem. The issue was raised with
>Robelle and we was we were assured it was not suprtool and so it was taken
up
>with HP.
>
>Since then, it has been happening with increasing frequency to the point
>where my support staff are up half the night every night supporting the
batch
>process. Suprtool is crashing, Sort is crashing, Cobol programs are
crashing
>with spaces return in the cond word from Image. It is happening to flat
files
>as well as various database. Extracts may contain more records than they
>should.
>
>The problem seems to occur when the machine is under a large load. Later in
>the night when the load is reduced the extracts rerun Okay. The problem is
>getting worse to the point where it is happening during the day as well. It
>appears confined to data extracting as no corruption of databases have been
>found other that those sourced from corrupted files.
>
>HP are having difficulty of identifying the problem. They have changed
various
>hardware/software components and had no success. They have built a machine
of
>similar specification, reproduced the problem but still cannot isolate the
>problem.
>
>Instability of this magnitude and duration is only adding to the pressure
to
>move away from MPE.
>
>
>
>Has anyone seen anything like this?
>
>
>Ron McFarlane
>Project Manager
>Mercantile Mutual
>
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
|
