[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

1834.0. "Distributed Shared option, file does not exist" by KERNEL::COOPER (Suzanne Cooper UK Customer Support (833)3502) Mon Nov 23 1992 10:25

    I have a bit of a problem with the ALL-IN-1 file cabinet distributed
    shared option.  (like I only have one working 3.0 node so I cannot even
    try it out).  If someone has system running the file cabinet
    distributed shared option I would appreciate it if I can have access so
    that I can try and set up a shared drawer and access it remotely, 
    Thanks in advance.
    
    Or, has anyone seen this problem.  
    
    User A had been set up on node Blue to access an file cabinet on node
    Orange using users B as a proxy.   On node Orange user B has been
    granted read access to User C's shared file.  
    
    When User A tries to read the files in the shared file cabinet he is
    getting "file does not exist"  If the access on the shared drawer is
    set to read and write,  User A can then edit the document but he still
    can read it and gets the error "file does not exist".
    
    Any Idea's
    
    Suzanne
T.RTitleUserPersonal
Name		DateLines
1834.1Can B access the file??CHRLIE::HUSTONMon Nov 23 1992 13:3812
    
    If I understand you correctly, no node Orange, users A and B are 
    the same person once the security it done (A proxies into B). 
    
    You say A cannot read the document, can B?
    
    It is possible to have a document with no content (at least from the
    FCS not sure if you can set this up with IOS), if this is the case
    it would act like what you are seeing.
    
    --Bob
1834.2KERNEL::COOPERSuzanne Cooper UK Customer Support (833)3502Mon Nov 23 1992 15:026
    B on node Orange can read the document, 'A' via the Proxy to B cannot
    read the document. 
    
    Doesn't make sense does it?
    
    Suzanne
1834.3Some questions...CHRLIE::HUSTONMon Nov 23 1992 18:1228
    
    Before I ask you this, let me summarize what I think you are saying
    your proxy setup is (these can get confusion enough when we are
    all talking about the same setup):
    
    
    node                   node              
    
    BLUE                   ORANGE (has the physical document)
    
    UserA lives on BLUE, but has a proxy of the form BLUE::USERA --> USERB
    which is in the NETPROXY.DAT on ORANGE?
    
    Now for some questions:
    
    1) Are there any other proxies of the form BLUE::USERA --> anything 
       on ORANGE?
    
    2) What is the ACL on the ACCESS.DAT for the drawer being accessed?
    
    3) What is the ACL of the docn.dir for the document being accessed?
    
    4) What is the ACL on the content file in the docn.dir?
    
    5) Does anything show up in the FCS trace about this?
    
    --Bob
1834.4KERNEL::COOPERSuzanne Cooper UK Customer Support (833)3502Tue Nov 24 1992 12:0017
    I've found it.  It was because the account that I was trying to access
    the drawer in was captive.  the netserver.log in the account is as
    follwows.
    $set noon
    $set noverify
    
    Initialising ALL-IN-1...
    
    
    
    FORM Main Menu
    %OA-E-EIF, Error occurred while form !AS was current
      GIRLING_T    job terminated at 24-NOV-1992 11:04:35.33
    
     I am getting them to put an if mode thing in the captive login.
           
    Suzanne
1834.5COMICS::BARHAMNorbert:Fri May 21 1993 10:1726
    FYI,
    
    I just had this problem too. It was because the captive login had a
    line
    
    $ assign/nolog 'f$logical("sys$output")' sys$input
    
    which was being translated into
    
    $ assign/nolog $255$dua15: sys$input (i.e. a disk name instead of
    						terminal device)
    
    
    The f$logical is out of date and should be replaced by f$trnlnm.
    
    We also put an
    
    if f$mode() .eqs. "NETWORK" then $ exit
    
    in the captive login.
    
    
    HTH,
    
    Clive