Conference specxn::decevent

289.0. "DUnix setld does not remove all old knl file from /var/DIA" by OLD1S::SYSTEM (PM&D PSE Tools Support) Tue Apr 29 1997 11:09

	We have come across a problem with the setld -d install routine used to
remove DECevent from the system prior to install of a new kit. setld will not
remove subsets that have been modified since the installation of the old kit.

	The failure to remove all of the KNL's may cause corruption. The prm
state db is the main culprit in this sceanario. During certain situations, the 
prm state db may have been opened by more than one process. When this occurs
the knl get corrupted. The corruption ocurrs because the end of file pointer is
not in it's expected position.

	In many cases the IVP run at install will fail because of KNL
corruption. This is generally the case of trying to update the system
information in the prm state db. If this occurs, the prm state db must be
deleted and a new copy created. The new copy can be created by a copy of the
factory state db to the prm state db  

  #cp FMG_ANA__FAC_STATE_DB.KNL FMG_ANA__PRM_STATE_DB.KNL

	Once the copy is complete, the system info must be entered via the set
sys info command. I would also suggest that you delete the local knl file in
your login directory. 


Cheer's

Keith