Conference iosg::all-in-1_v30

401.0. "BL123 upgrade problem" by EVTAI1::PROT () Thu Apr 02 1992 17:53

    BL123 upgrade problem:

    At the end of an upgrade V2.4 to BL123A, during A1$POSTINSTALL.COM, we
    get the messages:

    UAF-E-GRANTERR, unable to grant identifeir OAFC$SYSMAN to ALLIN1.
                    duplicate identifier.

    The VMSINSTAL was done from ALLIN1 account.
    
    The cause of this problem is that during the upgrade ALLIN1 is
    granted OAFC$SYSMAN, therefore SYSUAF.DAT is updated but not the
    process context. (This context will be updated after next login)

    If the upgrade is done from another account,the VMSINSTAL has not 
    granted it OAFC$SYSMAN during the installation, then it has no problem 
    during postinstall.


    During the post-installation, A1$POSTINSTALL.COM checks that your
    process have OAFC$SYSMAN. IF not, it grants it to you, if yes it skip
    the grant operation.


    The check is done frome F$GETJPI( "","RIGHTSLIST" ), but for the current
    process:

    $rights = F$GETJPI( "","RIGHTSLIST" ) is always equal to F$LENGTH( rights),
    then the procedure try to grant the identifier in UAF, but it's wrong 
    because it's already there.


    Instead of testing if the process is granted through GETJPI it would be 
    better to check the return status after a systematic grant in authorize,
    or check the uaf record for the current process.


Regards.
Louis
    
    
                                                

    We expect (and, I think, still say so in the IG) the upgrade to be done
    from the SYSTEM account, so this shouldn't be a very common problem.
    
    However we could possibly check for this. It's hard work checking if an
    acount has an identifier in SYSUAF, since you have to parse the output
    from AUTHORIZE. I suppose we could do the simpler check for the
    installing account being ALLIN1 (sic) but that would be less general.
    
    Graham

Why not have a flag that is set if during the installation you grant
OAFC$SYSMAN to the VMS account that is doing the install and then change
the way the post-installation procedure is written to take account of the 
fact that the identifier has already been granted.

Terry

    The Post installation code would then have to check that it was being
    run from the same account as the installation was done from to allow
    re-runs.
    
    I stick with my assertion that this won't happen to people who do it
    from the SYSTEM account, and that'll be most of them.
    
    Graham