Conference iosg::all-in-1

    
    Elin,
    
    I'm sure it's possible, but I don't think it will be supported!
    
    You might be lucky and it will be ok, but as I've never tried it I
    can't say for sure. 
    
    Can't they upgrade to V3.1 ?
    
    -Kevin.
    
    
    

    
    It's our Parliament, and they have planned to upgrade to v3.2 when the
    members go on summer vacation. 
    
    Till then we'll attempt to keep them running on v3.0A.
    
    The saveset A1_FIX030031_VAX.BCK in ICF#30 contains these files:
    
    OA$AIDA_DSSHR.EXE;1                     OA$AIDA_GCMSHR.EXE;1
    OA$AIDA_RTLSHR.EXE;1                    OA$AIDA_SECSHR.EXE;1
    OA$AIDA_SERVER.EXE;1                    
    
    and a PATCH_BASEARCH.ELE that says:
    
    IMAGE OA$AIDA_SERVER.EXE SYS$COMMON:[SYSEXE]
    IMAGE OA$AIDA_RTLSHR.EXE SYS$COMMON:[SYSLIB]
    IMAGE OA$AIDA_GCMSHR.EXE SYS$COMMON:[SYSLIB]
    IMAGE OA$AIDA_DSSHR.EXE SYS$COMMON:[SYSLIB]
    IMAGE OA$AIDA_SECSHR.EXE SYS$COMMON:[SYSLIB]
    
    
    Can I "install" the patch by just copying the five image files to their
    locations and do  $ INSTALL REPLACE  on them?
    
    Is the distribution list fix contained in a specific file so that I
    could just copy that file to the customer system on top of the ICF#27
    fixes (ICF#56)?
    
    Are any other files from A1_FIX030031.A needed in order to assure that
    OA$AIDA_SECSHR.EXE gets created correctly if ALL-IN-1 gets relinked?
    
    Elin
    
    PS. 
    I don't have ICF#38. I have examined the ICF#30 kit, but I expect
    answers to be valid also for ICF#38.

    
    Elin,
    
    In *theory* everything you say is correct, however, in practice this
    may not work. The patch does not include a full set of AIDA images, so
    you will be mixing V3.0A and V3.1 AIDA executables together. That in
    itself means that it probably won't work, not only might the code
    differences provide a problem, but the executables themselves have
    probably been linked against different VMS and CMA version. 
    
    In fact, I've almost convinced myself now that this is not going to be
    successful, sorry!
    
    OA$AIDA_SECSHR.EXE gets linked native to your system via
    OA$AIDA_SECSHR.OLB incidnetly...
    
    
    -Kevin.
    
    

    
    I'll tell the customer that they have to live with the distribution
    list problem till they can upgrade ALL-IN-1....
    
    
    >  but the executables themselves have
    >  probably been linked against different VMS and CMA version.
    
    ALL-IN-1 V3.1 is also installed on different VMS versions, and I am
    sure this customer has a CMA patch installed. It's a VAX with VMS v6.1
    or 6.2, so I am not worried about the VMS version.
    
    I understand that it is worrying to mix V3.0A and V3.1 AIDA executables
    together. But it was my impression that the images that went into
    ICF#56 for v3.0 were identical with those in ICF#27, and so I thought I
    could also use ICF#30 or ICF#38 images in v3.0.
    
    > OA$AIDA_SECSHR.EXE gets linked native to your system via
    > OA$AIDA_SECSHR.OLB incidently...
    
    - Doesn't that mean that the patch gets blown away if the system gets
    relinked after a VMS upgrade? 
    
    Elin

    
    Elin,
    
    If the patch doesn't include the SECSHR OLB then yes, I would have
    thought this might be a problem after a VMS upgrade !  I'm not familiar
    with these ICFs as they were produced when I wasn't working on the
    servers, so I'm afraid I can't comment fully on them.
    
    -Kevin.
    
    

    
    Kevin,
    
    I just checked ICF#56 and ICF#27 in the old IOSG patch chart and found
    that they only install one image, OA$DSL$SHR.EXE. 
    When I wrote the base note, I thought ICF#27 was an AIDA patch which
    had later been obsoleted by ICF#30 and that ICF#56 and ICF#27 contained
    the same OA$AIDA* images as ICF#30.
    
    I thought the system had AIDA server images from ICF#56 which I could
    copy the ICF#30 images on top of.  I now see that I was wrong and that
    these patches are not at all identical. 
    
    Thank you for your replies, Kevin!
    
    Elin

    
    Elin,
    
    I think I'm very confused now !
    
    Anyway, so long as your happy and there's no outstanding questions...
    
    -Kevin.