[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

402.0. "2 ALL-IN-1 V3.0 systems on a cluster" by AIMTEC::PORTER_T (Terry Porter, ALL-IN-1 Support, Atlanta CSC) Thu Apr 02 1992 18:42

I have a setup that is probably unsupported, but we are forced to do this
setup to make full use of the (limited) hardware we have.

On an LAVC two of the nodes (workstations) run seperate ALL-IN-1 V3.0 systems,
everything works fine except when trying to access drawers on the other system
remotely.

The two FCSs are licensed to export information.

Here's what happens...

A user on NODEA does an IAD for NODEB and sees a list of drawers as expected. 
They then type ADR to add the drawer to their file cab. If a drawer of that 
name exists on NODEA as well as NODEB then the ADR appears to work, but the 
local drawer is added. If the drawer does not exist on NODEA then the error 
"There is no such drawer" is displayed.

You get a similar problem trying to select the drawer directly. If you press
SEL and in the Drawer field do a GOLD/E, then fill out the form with the
remote node name and user name, then press FIND on the Drawer field. The 
expected list of (remote) drawers is displayed but if one is selected and 
RETURN pressed the "There is no such drawer" message is displayed again.

Looking at trace output (from the first case above) from the FCS it appears 
that IAD is using the FCS to get the list of drawers, but when the ADR is done 
ALL-IN-1 sees that NODEB is part of the cluster that it is running on and 
tries to access the drawer as a local drawer (which fails because it does
not exist locally).

Is there any way to force ALL-IN-1 to consider the other nodes in the cluster
as remote?

Thanks for any help,

Terry
T.RTitleUserPersonal
Name
DateLines
402.1Unsupported, probably, possible, maybeCHRLIE::HUSTONFri Apr 03 1992 16:0228
    
    Terry,
    
    What you are doing is very difficult to get to work from a FCS point
    of view and close to impossible (if not impossible) if you are running
    at distribution level 0.
    
    You have 2 problems here:
    
    1) ALL-IN-1 does not use the FCS for all FC functions. It uses it only
       when either a remote drawer is accessed, or a cross drawer 
       operation is done. It also used it for all IAD functions as you
       saw.  Your first problem is to convince ALL-IN-1 that the cluster
       is really not a cluster. I will leave that to Stuart or others
       to tell you if and how it can be done.
    
    2) You second problem is convincing the FCS that the cluster really
       contains multiple partitions.  Keep in mind that a "remote" drawer
       is simply a drawer in another partition that is not serviced by 
       the current server. The physical location does not really matter.
       There is a way to do this, but you need to run your servers at
       distribution level 1 and use DNS partitions.  This is how our
       tests work when testing brokering (some of them at least).
       If you are interested in this let me know, it is an undocumented
       thing so I would rather not put it in the notes files.
    
    --Bob
    
402.2Not an FCS problemAIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCFri Apr 03 1992 23:0925
Bob,

The problem does not seem to be with the FCS. The two ALL-IN-1 systems are
completely seperate except for anything in SYS$COMMON. This means that both
use the same FCS image, but the OA$* logical names on each system are different
so the server on NODEA finds a different PARTITION.DAT and PARTITION_MASTER.DAT
than the one running on NODEB.

I turned tracing on and IAD went via the FCS, but when I tried to add the
drawer to the file cab (ADR) there was no FCS access. It appears that ALL-IN-1
somehow decided that the drawer was local (presumably because it was on a node
in the same cluster) and tried to access it directly. If the drawer happens
to exist on both ALL-IN-1 systems the add works but add the local drawer
instead of the remote one. If the drawer only exists on the remote system
the error is output.

I believe the problem is that ALL-IN-1 decides not to use the FCS under 
these circumstances, but I may be wrong of course.

I guess there is no way to change this behaviour, but just in case there was
I thought I would ask.

Thanks,

Terry
402.3No wayPEARS::GRAEFGhinees hies good for you.Mon Apr 06 1992 11:3613
    Terry,
    
    there is no way to have more than one partition on a system as long
    as you run at distribution level 0. ALL-IN-1 (and the FCS too as far
    as I remember) will check the nodename of a drawer against the names
    of all cluster members. The effect is that ALL-IN-1 considers all your
    drawers as being local and expects to find them in the PARTITION.DAT
    it has access to. And the same problem would arise in the FCS if you 
    would pass one of the "remote" drawer names to the server through 
    a FILECAB function.
    
    Cheers,
    	helmut
402.4ThanksAIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCMon Apr 06 1992 16:148
Thanks Helmut.

I thought that would be the case, but just in case there was an undocumented way
of getting round it I thought I'd ask.

Regards,

Terry