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

Conference specxn::decevent

Title:DECevent -- keywords KIT* and PAK are available
Notice:DECevent V2.2 available - SHOW KEY/FULL to find note numbers
Moderator:DSNENG::KOLBEN
Created:Fri Jan 07 1994
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:307
Total number of notes:1463

290.0. "V2.4 Install Problem ?" by KERNEL::ADAMS (Brian Adams CSC-Viables '833-3026) Thu May 01 1997 06:26

    
    Whilst working a DECevent V2.4 installation problem with one of our 
    field engineers, we came across the following problem.
    
    He had first of all, run the de-install procedure, to remove the 
    earlier version, (V2.3) as per the documentation.
    
    When he ran the installation for V2.4, it complained about not finding
    DECevent$shutdown command file (He'd just removed it)
    
    To workaround the problem, he extracted the file from the saveset and 
    copied it back onto the system. Then he edited the file so that the
    first line was $ Exit. Now when he re-ran the installation, it worked
    fine.
    
    It would appear that if he had just installed V2.4 over the top of 
    V2.3, it would have done the de-install itself and been OK.
    
    Is this related to the commented out GOSUB ASK_DELETE_SDD line in 
    kitinstal.com where the sub-routine doesn't exist, and 
    DECEVENT$SDD_DEINSTALL := NO  ??
T.RTitleUserPersonal
Name		DateLines
290.1OLD1S::SYSTEMPM&D PSE Tools SupportThu May 01 1997 09:3818
	I knew someone would find this before I got a chance to report the
problem. 

	I just came across this problem myself on Tuesday. A new kit
dia_vms*_024A.* was created Tuesday afternoon. The problem is that the
shutdown.com file gets removed during deinstall. The developer was trying to fix
the problem of the analysis process running and the install writting to the prm
state db. If two process write to prm state db, it get corrupted when one moves
the end of file pointer to location unknown to the analysis process.   

	As of yesterday we have resolved both problems. The 2.4.1 kit will
contain code to shutdown the analysis process if it is running. This will
eliminate the problem two process problem. It will ask if DECevent is currently
installed. If it is currently installed the install procedure will shut the
analysis process down and restart it after the install is complete.

	I also put a fix into the unix kit to stop the process during a
setld -d deinstall of the kit.