[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

1276.0. "multiple VMS accounts accessing 1 ALL-IN-1 account" by KAOFS::D_STREET () Thu Aug 20 1992 00:43

    Hello,
     I have a customer who wishes to allow more than one VMS account to
    have access to a single ALL-IN-1 account. He has tried to leave the VMS
    account name field blank, and it will not let him. He says this was how
    he did it before V3.0. Is there a way to allow this in the new version?
    
    						Derek Street
T.RTitleUserPersonal
Name
DateLines
1276.1UTRTSC::SCHOLLAERTVivaceObjectTeamWorkLinks for IOSThu Aug 20 1992 07:3175
    Derek,
    
    Per user:
    
    <write change profil user = "schollaert" , vmsusr = ""
    
    More permanent:
    
ALL-IN-1 V3.0 : Creating a Single ALL-IN-1 Account for Several VMS Accounts


COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

PROBLEM/SOLUTION ARTICLE OUTLINE

-------------------------------------------------------------------------------

BRIEF PROBLEM OUTLINE:   

Creating a Single ALL-IN-1 Account for Several VMS Accounts and is unable 
to blank the VMS account name.
                                                         
PRODUCT:   VMS,  Version 5.4-2

LAYERED PRODUCT:   ALL-IN-1, Version 3.0  

DATE:   28-MAY-1992



SYMPTOMS/PROBLEM:

A customer was trying to follow the instructions in the Management Guide to
create a single ALL-IN-1 account for several VMS accounts (4-42 to 4-43). 
When he tried to delete the VMS account name it would not let him. Brought 
up the message:

                   "Field may not be left blank - re-enter"


ANALYSIS:

The named data appeared to be too restrictive. There is a /VALID qualifier
that does not allow blank fields for the field VMSUSR.


SOLUTION:

Alter the named data on the form SM$PROFILE from:

;;VMSUSR;;

/PRE='GET #SM_VMS_INITIAL = VMSUSR'
/HARD=OA$_SM_HRD_VMS_ACCOUNT
/RECOG=UAF:.USERNAME
/VALID=UAF:.USERNAME
/POST='.IF #SM_VMS_INITIAL NES VMSUSR THEN GET #SM_VMS_CHANGE = "1"'

To:

;;VMSUSR;;

/PRE='GET #SM_VMS_INITIAL = VMSUSR'
/HARD=OA$_SM_HRD_VMS_ACCOUNT
/RECOG=UAF:.USERNAME
/VALID=UAF:.USERNAME/OPTIONAL
/POST='.IF #SM_VMS_INITIAL NES VMSUSR THEN GET #SM_VMS_CHANGE = "1"'

It is also necessary to move the whole form set live. 
i.e SM$PROFILE, SM$PROFILE2, SM$PROFILE3, SM$PROFILE4, SM$PROFILE5, 
SM$PROFILE6. 

    
    
1276.2Discussed before...IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeThu Aug 20 1992 11:146
    There were other notes about this quite recently.
    
    Generally, it's to be discouraged in V3.0, since security is based on
    VMS account.
    
    Graham
1276.3re .2IOSG::TYLDESLEYThu Aug 20 1992 11:583
    Please see note #1183.*
    Cheers,
    DaveT