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

Conference bulean::decnetvax

Title:DECnet-VAX Conference
Notice:The WORLD's Leader in Networking
Moderator:BULEAN::BENOIT
Created:Sun Feb 02 1986
Last Modified:Sun Jun 01 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5887
Total number of notes:24029

5879.0. "FAL restriction in VMS 6.2?" by BARNA::DSMAIL () Fri Apr 04 1997 08:56

    Hello:
    
    I have a customer with several Alphas with VMS 6.2 and several
    VAX with 5.5-2 in cluster. He has too an Alpha running Windows NT 3.51
    and Pathworks Client 4.1B.
    
    The customer from the VMS systems makes the command :
    $ DELETE NODE::"d:\temp\file.txt" over the NT system (the node NODE is
    the NT system)
    
    This command works fine if it's executed from the VAX systems and
    returns the error "file not found" when executed form the Alpha systems
    and the file/directory is in other partition or device diferent than
    the local directory pointed by the user DECNET on the NT system.
    The DECNET account on the NT is the account mapped by the FAL object in
    the NT's NCP. The FAL is correctly defined as long i verified against
    TIMA article:
    
    ncp>show obj fal char
    
    Object Volatile Characteristics as of Fri Apr 04 14:54:17  1997
    
    Object = fal
    
    Number                             = 17
    File                               = %P/fal %U
    Default User                       = decnet
    Default Password                   = . . .
    Type                               = Sequenced Packet
    Accept                             = Immediate
    Interface                          = Winsock
    Logging                            = Disabled
    ncp>
    
    If he makes a DIR command by DECNET from the ALPHA systems the file 
    is seen correctly.
    
    Anyone knows some incompatibility or limitation with OpenVMS AXP 6.2
    with their FAL object?
    
    Any ideas will be wellcomed
    
    Thanks in advance.
    
    Crist�bal.
T.RTitleUserPersonal
Name
DateLines
5879.1Check With NT FAL Maintainers...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri Apr 04 1997 14:2810
   You'll want to take this up with the DECnet FAL maintainers on the
   NT system, via QAR or IPMT...  (This might be a bug on the NT end,
   or it might be a bug on the OpenVMS Alpha end.)

   Make sure this is not a case-related problem.

   See if the NT FAL supports logging -- see if you can enable any
   sort of debug-related logging, and enable it.  Then try the test,
   to see if you can detect any obvious differences.
5879.2I have find the same problemEVTAI1::5dhcp36.evt.dec.com::gramainSimonWed May 14 1997 05:2529
	 Hi Christobal

 For your info , I have find exactly the same problem. 
 I don' really understand why the pb does not appear with VMS V5 and appear with VMS v6. 
 According my tests the pb appear only on decnet phase IV. 

 I have not submit an IPMT because my customer want to work on just ONE directory on the NT
 so I have define the home directory of the "FALUSER" on NT to this directory and it works. 

 I have made some tests on Pathworks 32 for NT (PW32 is the upgrade of PW 4.1B on NT)	
 but I have not the "file not found" on the delete command but I have detected great 
performance problem.

 For me, if your customer need to acces the Whole NT disk space from a VAX VMS v6 via Decnet,
 you create n FAL account. FAL-C (for disk C), FAL-D, FAL-E. For each account define the home 
directory to be  C:\ , D:\ , E:\ ...
 If you want delete file in a directory on E, use the command. 

  delete  NTNODE"FAL-E password"::"E:\directory\file.xx"

IF THIS IS NOT ACCEPTABLE, I think that it will be difficult to get correction on PW 4.1B, 
so try tests on Pathworks 32. If you find performance pb, let me know. 

For your info, on NT 4.0 there is a FTP server. If your customer has UCX on VMS, FTP may be 
another solution to manage file on NT from VMS.  


					Simon