[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

1702.0. "FCS Attribute Questions" by MELKOR::RUDDY (Home is where overhead is) Tue Nov 03 1992 07:53

    Hello,
    
    I was reading in the ALL-IN-1 Management Guide about the FC Server and
    it's characteristics. One item jumped right out at me.
    
    What is Server Attriute AUTHORIZED TIMEOUT. It states it is used to
    refresh the authorizatin cache.  What's the authorization cache.
    
    Second, there are some options for SAI (show auditing information). Is
    there a document that explains threads, connections, tasks, etc.  And
    why does it refresh every time I press return?  Is there something I am
    looking for after each refresh?
    
    This is my first teach of ALL-IN-1 Manager and I'd like to be able to
    answer my students question.  I've read the manuals but no help.
    
    Help!
    
    Mia Ruddy
    Santa Clara Learning Center
T.RTitleUserPersonal
Name		DateLines
1702.1Who has which access to a DrawerCESARE::EIJSAll in 1 PieceTue Nov 03 1992 10:3619
    
    Hi Mia,
    
    > What's authorization cache?
    
    The FCS caches the authorized access to a drawer and refreshes that
    information once every while. Basically who has which access to a
    specific drawer. It's held in cache for performance reasons.
    
    > Is there a document that explains threads, connections, tasks, etc.
    
    Please refer to notes 203, 205 and 304 in the conference. Also refer to
    note 769.1 (Terry Porter) for more information on a particular document
    written on the FCS.
    
    Ciao,
    
    	Simon
1702.2Some Basic FCS termsCHRLIE::HUSTONTue Nov 03 1992 15:2937
    
    re .0
    
    Mia
    
    
    as .1 said the authorization time out is the drawer authorization.
    For performance reasons, when the FCS opens a drawer, it caches the
    access info on teh drawer, info like the ACL, prot mask etc. 
    Every once in a while this info is flushed and re-read. The ensures
    that the FCS is not granting access based on stale access data.
    When you change the info the FCS that changes it will refresh its cache
    then so that FCS will have the new info immediately. The potential 
    problem that the authorization TMO gets around is that if you hve
    multiple servers running on a cluster, the access info is cluster wide.
    If srvA does the access modify, then if srvB also has teh drawer open
    it will not pick up the new info until it refreshes its cache.
    
    THREADS -- The FCS is multi-threaded. You can almost think of this
               as being parallel processing. Each request made of the FCS
               is given its own thread of execution. What this means is
               that the FCS can handle multiple tasks at the same time. 
               Tasks do not block waiting for the one infront of them
               to complete. It gives the appearence of multi-processing
               or parallel processing. Clear enough? (if not ask more)
    
    CONNECTIONS -- This is the count of client connections made to the
               server. Every time an IOS user opens a non-default drawer,
               or does a cross drawer operation a connection is made to
               the FCS. This will also include ALL TeamLinks connects.
    
    TASKS -- Each request made to the FCS is called a task.
    
    Any more??
    
    --bob