  Recovering from Corrupt PCSI Database? 
 The Question is:
 
A previous system manager has installed TCPIP Services 5.3 on top of unpatched
 OpenVMS7.2-1. The PCSI database seems to be slightly corrupt after this. It is
 neither possible to install nor uninstall any products.
 
The installation instructions for TCPIP5.3 does not require that other system
 patches are installed, but I assume system managers has followed the good
 practice to install them first. There were similar problem before with VMS
 7.1-2 and dwmotif, but all 7
.2 versions should have this problem fixed.
 
A large number of customers are using VMS7.2-1, so we have a problem upgrading
 to a supported version right now. Still, we would like to avoid scratching the
 VMS installations...
 
Any way to save the product database without scratch?
 
 
Error message when installing products:
The following product will be installed to destination:
    DEC AXPVMS VMS721_PCSI V1.0            DISK$ALPHASYS:[VMS$COMMON.]
 
Portion done: 0%
%PCSI-E-UNSDOCENC, unsupported product document encoding version
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
 
$ prod sh obje/full tcpip_services
----------------------------------------------- ----------------- -------- -----
--------------------------- ------------------------
OBJECT NAME                                     OBJECT TYPE       STATUS   DESTI
NATION ROOT DIRECTORY       PROVIDED BY
----------------------------------------------- ----------------- -------- -----
--------------------------- ------------------------
%PCSI-E-UNSDOCENC, unsupported product document encoding version
%PCSI-E-READERR, error reading SYS$COMMON:[SYSEXE]PCSI$FILE_SYSTEM.PCSI$DATABASE
;1
-DDIS-E-INCSEQCAL, inconsistent sequence of calls
%PCSI-E-READERR, error reading SYS$COMMON:[SYSEXE]PCSI$FILE_SYSTEM.PCSI$DATABASE
;1
-DDIS-E-INCSEQCAL, inconsistent sequence of calls
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
 
 
Excerpts from database
00090cd0: 810e 5359 535f 5041 5241 4d45 5445 5253  ..SYS_PARAMETERS
00090ce0: 8301 0aa6 8030 8080 010a 8101 0100 0030  .....0.........0
00090cf0: 8080 0109 8413 5b53 5953 484c 505d 4845  ......[SYSHLP]HE
00090d00: 4c50 4c49 422e 484c 4200 0030 8080 0103  LPLIB.HLB..0....
00090d10: 8104 02fc c540 0000 3080 8001 0281 0101  .....@..0.......
00090d20: 0000 0000 0000 3080 8001 3781 0e54 4350  ......0...7..TCP
00090d30: 4950 5f53 4552 5649 4345 5383 0109 a680  IP_SERVICES.....
00090d40: 3080 8001 0984 135b 5359 5348 4c50 5d48  0......[SYSHLP]H
00090d50: 454c 504c 4942 2e48 4c42 0000 3080 8001  ELPLIB.HLB..0...
00090d60: 0281 0101 0000 3080 8001 0184 205b 3030  ......0..... [00
00090d70: 3030 3030 5d54 4350 4950 2454 4f50 5f4c  0000]TCPIP$TOP_L
00090d80: 4556 454c 5f48 454c 502e 484c 4200 0000  EVEL_HELP.HLB...
00090d90: 0000 0030 8080 0137 8103 5446 4683 010a  ...0...7..TFF...
 
 
 The Answer is :
 
  Topics (8958), (2434) and (6160) may be of interest, among other topics.
  Without details of the corruption beyond what is normally feasible
  here in Ask The Wizard and information on the ECOs installed, no answer
  is particularly possibly -- beyond the topic citations and a request to
  contact the customer support center directly, of course.
 
 Answer written or last revised on  17-FEB-2004 
