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

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1800.0. "NET FILE ID# /CLOSE " by ALFSS2::JONES_J () Mon Mar 31 1997 17:13

    I have a customer using the 6.1 eco2 server for Exchange client
    personal directories.  They store their exchange mail and pab files in
    their personal directory on the Pathworks server.  Sometimes a users pc
    will lock and have to reboot the client.  The client comes back up fine
    and connects to all shares.  If the user trys to use their Exchange pab
    file to send mail they get an error that the file is allready open.
    
    Using the NET FILE command from the # prompt on the server it will
    display that the pab file is open with no locks and an id number.  If
    you use the NET FILE id# /CLOSE command to close the file you get the
    error file not found.
    
    The error is correct because if you continue to issue the NET FILE
    command you get a different id# every time.  This is not true on a NT
    server.
    
    QUESTION:	Is the file actually open?  Would changing the paramater to
    UNIX LOCKS = NO help?  Why does the NET FILE  command say a file is
    open when I only read the file and copied it to memory on my pc?  Is
    the NET FILE id# /CLOSE suppose to fix the open file error?
    
    		Lots of questions any answers will help,
    
    			Jerry
T.RTitleUserPersonal
Name		DateLines
1800.1NETRIX::"[email protected]"UNIX and PCI SupportMon Mar 31 1997 19:3630
Hello Jerry,

>Is the file actually open?
I belive yes. try lmstat -f to confirm.

>Would changing the paramater to UNIX LOCKS = NO help? 
Have to try.

>Why does the NET FILE  command say a file is
open when I only read the file and copied it to memory on my pc?

When you read a file you first open it.Depending of what kind of 
open and read the program does the file can view open until it will
be completly closed.
lmstat -fl will give you more details.

>the NET FILE id# /CLOSE suppose to fix the open file error?
It's a BUG already reported and downgrade to severity level 3.
Each time you use net file command a different file ID is returned
for the same file.
One (and my favorite) of work-around is to use the NT server tools
from NT or WIN95 to close open files.
Since your PCs are locked you can try net session /delete 
before restarting the PCs.
That diffinitively closes all things for the concerning PCs. 

Regards,
Jean-Pierre
http://mosupc.evt.dec.com
[Posted by WWW Notes gateway]
1800.2ALFSS2::JONES_JThu Apr 03 1997 09:477
    Jean-Pierre,
    
    	Thanks for for all the good information.  Will be waiting for the
    fix.  Will it be in eco3?
    
    					Jerry