[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

2326.0. "SM MSY SSP does redundant checking." by KERNEL::LOAT (Ahead groove factor 5! Yeah!) Thu Feb 25 1993 09:39

    
    VMS 5.5 ALL-IN-1 3.0
    
    When going into the SM MSY SSP option, the validation which is done on
    the account follows this path through the named data (I'll just name
    the XOPS, make it a bit easier!)
    
     ~~CHECK_FOR_MANAGER~~
     ~~CHECK_CMS_PRIVS~~
     ~~CHECK_FOR_FORMLIB~~
    
    The XOP ~~CHECK_FOR_FORMLIB~~ does the following:
    
    ;;~~CHECK_FOR_FORMLIB~~;;
    
    GET #SM_HAS_MGR = 0\
    GET #SM_HAS_ADM = 0\
    .IF PROFIL.FRMLIB[#SM_USERNAME] <=> "MANAGER"
     THEN
         GET #SM_HAS_MGR = 1\
    .IF PROFIL.FRMLIB[#SM_USERNAME] <=> "ADMIN"
     THEN
         GET #SM_HAS_ADM = 1\
    .IF (#SM_HAS_ADM EQ 1) AND (#SM_HAS_MGR EQ 1)
     THEN
         OA$VAL_SET_VALID
     ELSE
        XOP "~~LIB_MISSING~~"
    
    Why does it do this check? I was under the impression that if an
    account had the OA$MANAGER identifier, and they had the correct privs,
    then they could act as a manager, as ALL-IN-1 would open the form
    library MANAGER for them when they enter the SM option (which is done
    by the script OA$LIB:SM_INIT_MGT.SCP)
    
    It doesn't look like there is a valid reason for doing the form library
    check, unless anyone out there knows different? 8-]
    
    Any ideas why this check is still there?
    
    Steve.

T.R Title User Personal
Name Date Lines

2326.1 left from V2.3 IOSG::TYLDESLEY Thu Feb 25 1993 10:15 16

T.R	Title	User	Personal Name	Date	Lines
2326.1	left from V2.3	IOSG::TYLDESLEY		`Thu Feb 25 1993 10:15`	16
	Steve, As you indicate, the form lib check was the old way of checking for Manager before we had the RIGHTS functions. This check does not appear to have been removed. We still advise that the Manager account carry MANAGER & ADMIN in the FRMLIB field, because there are some batch procedures run under Manager that do not explicitly open the form libraries. There are still three things that constitute a Manager - possession of the oa$manager & oa$admin id's., possession of the form libraries and being named as such in the Policies. We still recommend that a system has only one Manager (we design on that basis), though obviously you can have as many as you want. DaveT

    Steve,
    As you indicate, the form lib check was the old way of checking for
    Manager before we had the RIGHTS functions. This check does not appear
    to have been removed.
    
    We still advise that the Manager account carry MANAGER & ADMIN in the
    FRMLIB field, because there are some batch procedures run under Manager
    that do not explicitly open the form libraries.
    
    There are still three things that constitute a Manager - possession of
    the oa$manager & oa$admin id's., possession of the form libraries and
    being named as such in the Policies. We still recommend that a system
    has only one Manager (we design on that basis), though obviously you
    can have as many as you want.
    
    DaveT