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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3866.0. "FCS lock NETPROXY.DAT - SCA installation fails" by OSLACT::BJARNEC_P (The last boat left without me .....) Wed Feb 09 1994 15:34

    Hi,
    
    
    A customer had problems installing a product (SCA) - the installation
    failed - because the FCS Server had taken out a lock on the
    NETPROXY.DAT file.
    
    I did some testing by connecting to an A1 FC from Teamlinks, and as
    soon as I had established a connection, the NETPROXY.DAT was permanently
    locked by the FCS Server process, and it seemed to stay locked even
    though I did a disconnect from within Teamlinks.
    
    Is this the way the FCS is supposed to work?  The workaround was to
    stop the FCS while they installed the product, but I was not able to
    explain to them why the FCS had to take out a lock on the NETPROXY.DAT
    (although I'm sure there is a perfectly logical explanation for this
    ......).
    
    I have flagged this issue in the SCA_V2_BUGS conference because the 
    SCA installation procedure should manage such situations anyway, I
    think.
    
    
    Just wondering ......
    
    
    	Bjarne
    
    
    
T.RTitleUserPersonal
Name
DateLines
3866.1Not nice.\IOSG::STANDAGEWed Feb 09 1994 15:4713
    
    
    Bjarne,
    
    This is not the only datafile that the FCS keeps hold of. You'll
    probably also see what it continuously has SYSUAF.DAT too.
    
    I believe this was done for performance reasons more than anything
    else...
    
    Kevin.
    
    
3866.2Yea, I kind of thought that .....OSLACT::BJARNEC_PThe last boat left without me .....Thu Feb 10 1994 08:4016
    Thanks Kevin.
    
    My understanding is that the SCA installation tries to take out an
    exclusive lock and this, of course, will not work when another lock has 
    already been taken out on the file.
    
    As I mentioned in .0, I have entered a note in the SCA_V2_BUGS
    conference pointing out the situation to the SCA people - maybe they
    can modify the way the product is being installed to allow for such a
    situation.
    
    
    Thanks,
    
    
    	Bjarne