Conference iosg::all-in-1_v30

1478.0. "Customer curious about GPC" by OASS::GREEN_W () Tue Sep 22 1992 20:17

    I have a customer that is delighting in going through the ALL-IN-1 GPC
    scripts.  While he is doing this, he is asking me "why is it written
    this way?"
    
    I don't know, I tell him.  I did not write the code.  So he wants me to
    ask the engineer(s) who wrote the code.  His reason being that if he is
    going to do any customizations he needs to understand the logic behind
    the code as it exists.
    
    The particular code he is curious about now is in the
    OAN$CREATE_CONFERENCE.SCP.  It is in the section where a membership
    record is created.  It reads as follows:
    
    .LABEL ADD_MEMBERSHIP_RECORD
    !       Added for ALL-IN-1 V3.0
    
            NOTES SET_MODERATOR OA$Y
    
    !       Cater for the case where the ALL-IN-1 user name is different to
            the
    !       VMS user name (i.e. REDMOND.TONY is different to REDMOND)
    !
            .IF OA$USER NES OA$PROFIL_VMSUSR
            .THEN
                NOTES ADD_MEMBER OA$USER, #OAN_MODERATOR, #OAN_MODERATOR, -
                       OA$Y, OA$Y, OA$Y
                NOTES MODIFY_MEMBER "ACCESS", #OAN_MODERATOR, OA$USER
                NOTES MODIFY_MEMBER 
                  "MAIL_ADDRESS",#OAN_MODERATOR,OA$PROFIL_VMSUSR
                NOTES MODIFY_MEMBER "ACCESS", #OAN_MODERATOR,
                  OA$PROFIL_VMSUSR
                OA$MSG_PURGE
            .ELSE
                NOTES MODIFY_MEMBER "ACCESS", #OAN_MODERATOR, OA$USER
                NOTES MODIFY_MEMBER "MAIL_ADDRESS", #OAN_MODERATOR, OA$USER
                NOTES MODIFY_MEMBER "MODERATOR_PRIV", OA$Y, OA$USER
                NOTES MODIFY_MEMBER "KEYWORD_PRIV", OA$Y, OA$USER
                NOTES MODIFY_MEMBER "WRITE_PRIV", OA$Y, OA$USER           
                  OA$MSG_PURGE
            .END_IF
    
    
    He wants to know, why modify_member "access"  twice?
    
    

    Why is MODIFY_MEMBER called twice?  Because of a feature...
    
    Seriously, I think (seem to remember) that there were some problems
    writing everything into a membership record with a single call, so the
    function was merely repeated to make sure that the records were
    correctly updated.
    
    As the Irish say: to be sure, to be sure.
    
    Tony

    Thank you Tony.  Sometimes it seems like customer's have nothing better
    to do than to read script files :^}
    
    Wendy