[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference evms::spia

Title:	Software Product Integration Architecture

Moderator:	STAR::HAMMOND

Created:	Fri Apr 28 1989
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	370
Total number of notes:	1977

366.0. "files lost when removing product" by CUJO::MURTHA () Wed Feb 19 1997 23:48

     I am having trouble with a kit I am converting from VMSINSTAL to PCSI.
The kit replaces a number of vms files.  When building the PDF file I
specified these files as 'archive'.  When the kit is installed, the original
files are renamed to .EXE_OLD.  I thought when I removed the kit, the new
.EXE files would be deleted, and the .EXE_OLD files would be renamed back
to .EXE.  However, the .EXE files get deleted, but the .EXE_OLD files
stay .EXE_OLD.  In the PDF file I specified the kit type as full but I'm not
sure that's correct since vms files are affected.
    I am building the kit to install on vax vms 6.2 but it acts the same on 
vax vms 7.1.  Can someone help me out with this?  I think I must be missing
something.  Thanks,

                                     Amy

T.R Title User Personal
Name Date Lines

366.1 Feature not currently implemented STAR::KRYCKA Fri Feb 21 1997 11:19 22

T.R	Title	User	Personal Name	Date	Lines
366.1	Feature not currently implemented	STAR::KRYCKA		`Fri Feb 21 1997 11:19`	22
	To support product removal fully, the PCSI utility should restore archived (._OLD) files to their original names, but this capability is not currently implemented. We will consider providing this capability in OpenVMS V7.2. As a workaround, you can use the EXECUTE INSTALL...REMOVE statement to provide a remove command procedure that is executed when your product is removed to rename the *.EXE_OLD files. Refer to the OpenVMS V7.1 PCSI Developer's Guide for a description of the EXECUTE INSTALL...REMOVE statement. This manual has been significantly upgraded from V7.1, particularly the product description language reference section, so discard your V6.1 or V7.0 manual and print the new one. In the next note I will post the location of the V7.1 PCSI documentation. Finally, you say that you are replacing OpenVMS files. I suggest that you contact Charlie Hammond, OpenVMS kitting project leader, to discuss your product's requirements. Charlie (PEEK::HAMMOND) has worked with other products that need to replace OpenVMS files and can tell you in detail the techniques used by these layered products and about any coordination with the OpenVMS product that may be needed. - Jim Krycka

To support product removal fully, the PCSI utility should restore archived
(*.*_OLD) files to their original names, but this capability is not currently
implemented.  We will consider providing this capability in OpenVMS V7.2.

As a workaround, you can use the EXECUTE INSTALL...REMOVE statement to provide
a remove command procedure that is executed when your product is removed to
rename the *.EXE_OLD files.

Refer to the OpenVMS V7.1 PCSI Developer's Guide for a description of the
EXECUTE INSTALL...REMOVE statement.  This manual has been significantly
upgraded from V7.1, particularly the product description language reference
section, so discard your V6.1 or V7.0 manual and print the new one.  In the
next note I will post the location of the V7.1 PCSI documentation.

Finally, you say that you are replacing OpenVMS files.  I suggest that you
contact Charlie Hammond, OpenVMS kitting project leader, to discuss your
product's requirements.  Charlie (PEEK::HAMMOND) has worked with other
products that need to replace OpenVMS files and can tell you in detail the
techniques used by these layered products and about any coordination with the
OpenVMS product that may be needed.

- Jim Krycka