Conference iosg::all-in-1_v30

>    5. Any comments about the interrelation of ALL-IN-1 V3.0/Decwindows
>    V3.0 & Motif?

    Umm, I'm not sure I understand your question!  Hope this is what you
    want...

    If you elect for CDA support, ALL-IN-1's `relationship' to DECwindows
    can be pictured thus:

    +----------+
    |          |                 o ALL-IN-1 only uses a part of CDA.
    | ALL-IN-1 |                   
    |     +----+-----+           o Some parts of CDA require DECwindows
    |     |////| CDA |             components.
    +-----+----+     |             
          |     +----+-----+     o CDA only provides the option of either
          |     |////|     |       the whole lot, or none at all.
          +-----+----+     |       
                |          |     o So, ALL-IN-1 picks up the DECwindows
                |DECwindows|       dependency from CDA - but which DECwindows
                +----------+       shouldn't matter.

    Cheers,
        Paul.

  [ Note there is no such product as DECwindows V3.0 - do you mean
    DECwindows/Motif V1.0? (When the UI changed from XUI to Motif, what was
    originally going to be DECwindows V3.0 became DECwindows/Motif V1.0)    ]

    1. Dunno.
    
    2. From the Product Management Q&A I received this morning:
    
    	#1. Does DESKtop 1.0 Server work under version 3.0 of ALL-IN-1 ?
    
                No. ALL-IN-1 Version 3.0 requires DESKtop version 1.1A.
                This will be availble sometime During Q1 FY93.
    
    3. Yes, but it didn't make it into V3.0. User Queue Management is the
    only remaining bit of this. However most of the data files controlling
    Admin. privs were set up in V2.3 to allow multiple admins, so you may
    well be able to customise it. Of course if you do this, we'd like the
    code back for the product please :-)
    
    4. You can tell VMSINSTAL to use a different disc for the temporary
    directory created under SYS$UPDATE. This is called AWD (Alternate
    Working Directory) in VMSINSTAL speak. I can't remember how you ask for
    this. There are some problems with getting the disc space calculations
    right due to a bug in VMSINSTAL.
    
    Graham

    Bit more on 3. Yes, we started on this, and got a good way along 
    before it dropped below the line. The one authorization for 
    administrators thought to be most important - authorization to manage
    queues (QMA) - was implemented quickly, using group services. You
    might want to develop your own application authorizing administrators
    to manage different resources, based on this model. Basically, it uses
    the fact that only a Manager can create MNG$ groups; then place the
    identifier of this group on your resource; take the user out of the
    group, and he no longer has the authority.
    
    Full and proper multiple administrators might come along one day, where
    you could set up "patterns" of responsibilities for each one. One thing 
    we were never sure of, though, was to what extent multiple admins, and
    indeed administrators themselves, were used on customer sites?
    
    Cheers
    DaveT
    
    

    1. This might be referring to a problem with EFT2 of TeamLinks for
    Windows (see ABBOTT::WINDOWS_OFFICE for details). This is believed to
    be caused by long ACLs.
    
    I don't now of any other problems. _Really_ long ACLs (more than
    thirty-something entries, as far as I remember) have a performance
    impact; that's one reason to use Groups, rather than long lists of
    indvividual users. (Groups are also easier to manage).

    
    
The following questions come from a Technical Update Customer class 
being done by a colleague in Australia.  Any help appreciated :
    
Question 1:
----------

Is there a "fix" for running V2.3 or V2.4 under VMS V5.5?  The customer has a
system that requires 5.5 to be installed and needs to install V2.3 and V2.4 on
these type systems...


Question 2:
----------

Will there be any "formal" recommendations for ASSETTS written for V3.0...
ie, writing them so that they are located in separate application areas?


Question 3:
----------

Does SUBSCR set to N affect DDS lookups?  It appears to from some lab exercises
that we did in class.  When we tried a SMD from an account that had SUBSCR set
to N no USER accounts were found.  When we changed the flag to Y, the USER 
accounts were found.

Question 4:
----------

When will BRITISH version be released?

Question 5:
----------

Is there any way to auto forward your mail to multiple accounts?


Thanks!
    

    
Question 2:
----------

Will there be any "formal" recommendations for ASSETTS written for V3.0...
ie, writing them so that they are located in separate application areas?

    
    As far as I know nothing formal.  But with the advantages of
    application areas it makes a lot of sense.
    
    
    Mike

    1. There are many notes about this. The bottom line is that A5.5 (v5.5
    with the 5.4 job controller) works fine. Otherwise you need a VMS
    patch, or a (not yet released, I think) v5.5-1 - anyway, check the
    other notes; I'm sure about the A5.5 being OK though.
    
    3. It isn't meant to. If you've found a bug, let us know about it.
    
    4. BRITSH = US. Same kit (for v3.0).
    
    5. No. Unless you want it badly enough to do a customisation, using the
    Command file ("AMTS") facility. Ther are other notes in here, or maybe
    the old archived conference, about how to do this.
    
    Dave.

    
    
>>    4. BRITSH = US. Same kit (for v3.0).
    
    	Not quite.  The British kit has different part numbers and a
    different Language tape.  It has however been released in the UK.
    
    
    Martin.