  Recovering from PCSI Database Corruption ACCVIO? 
 The Question is:
 
How can I recover from PCSI Database corruption?
A colleague was working on patch procedures for
our TUXEDO product that we install with PCSI.
She aborted an installation and something has
gone wrong with the PCSI files.  Although I can
do various "product show product" commands and
all looks fine, I can neither remove nor install
TUXEDO now because PCSI ends with
%SYSTEM-F-ACCVIO.  Unfortunately, no backup
has been done, so we cannot just re-install.
 
 
 The Answer is:
 
  Please contact the Compaq Customer Support Center for assistance.
  You will need to provide the output from a PRODUCT SHOW PRODUCT/FULL
  command.
 
  The most common cause of an access violation during a PRODUCT INSTALL
  or a PRODUCT SHOW PRODUCT command is a corrupted PCSI database.
 
  Assuming no BACKUPs are available and assuming OpenVMS Alpha, you can
  attempt a recovery using the following steps:
 
  1: Make a list of all products currently installed or currently
     registered in the PCSI database.  Include each product's version
     and any dependencies on (or references to) other products that the
     product may have.  You can obtain this information from the output
     of the PRODUCT SHOW PRODUCT /FULL command, unless of course, the
     database corruption causes the execution of this command to fail.
 
     If you cannot issue PRODUCT SHOW PRODUCT/FULL, try to use the
     names of the PCSI database files to determine what products are
     installed.  Then, assuming you have no BACKUP, you will be left
     to delete the PCSI database files (see step 2) and then simply
     reinstall or reupgrade all of the products.
 
  2: Delete all of the PCSI database files.  There are the three initial
     PCSI files, plus one file for every product installed:
 
     $ DELETE /LOG SYS$COMMON:[SYSEXE]*.PCSI$DATABASE;*
 
  3: Register the OpenVMS Alpha product:
 
     $ PRODUCT REGISTER PRODUCT VMS /SOURCE=SYS$COMMON:[000000]
 
     Note:  The source points to the product description file
            (.PCSI$DESCRIPTION) of the VMS product, a file that is in
            reference format on the system disk.
 
  4: Register each layered product that had been previously installed by
     PCSI.  Use commands of the form:
 
     $ PRODUCT REGISTER PRODUCT &lt;product-name&gt; /SOURCE=location-of-PCSI-kit
 
     Register the layered products such that the dependent products are
     registered first.  That is, if Product A requires Product B, then
     you must register Product B before Product A.
 
     Do not register patch kits (eg, DECnet-OSI "ECO" kits).
 
     If a PCSI kit is not available for a product, use instructions in
     step 5 to register it.
 
     Note: Source points to the sequential kit (.PCSI) for the product
           which contains its product description file (.PCSI$DESCRIPTION),
	   or directly to the product description file (.PCSI$DESCRIPTION)
	   of a product that is in reference format on the disk.
 
  5: Register any products that you had previously registered with the
     procedure SYS$UPDATE:PCSI$REGISTER_PRODUCT.COM:
 
     $ @SYS$UPDATE:PCSI$REGISTER_PRODUCT.COM
     Product name: x
     Version: 2.5
     Producer [DEC]:
 
     PCSI$REGISTER_PRODUCT.COM also can be used to register products that
     were previously installed, but for which there is no PCSI kit available.
     Because this procedure does not capture any information about the files,
     directories, and other objects, or about the product's dependencies, the
     OpenVMS Wizard strongly recommends you use a PRODUCT REGISTER command
     (as shown in step 4) whenever a PCSI kit is available.
 
  6: Verify that the database contains what you expect, including version
     and software reference information:
 
     $ PRODUCT SHOW PRODUCT /FULL
 
