[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

2574.0. "USING THE SAME BASELOCATION IN CM$AUTH$LOCATIONS TWICE" by TAKEOF::ERNI (Ursula Erni) Thu Apr 15 1993 18:23

Hi

Within a customer application i need A1SUBMIT for discquota-reason. Therefore I 
do have to place the command-procedure in OA$LIB! 

I would like to create this command-procedure in my special application, but I 
am not allowed to do it. I'd like to have a CM$AUTH$LOCATIONS-dataset like this:

 Application Area: CAG_OFF
 Type:             COM
 Site Location:    OA$SITE_LIB_SHARE:	<---
 Base Location:    OA$LIB_SHARE:	<---
 Description:      Default directory for COM elements
 Open:             Y
 Txl Location:     N    Txl Type:
 Languages:
 Protection:       OA$LIB:CM_SET_PROT
 Site Translation: $COMMON:[ALLIN1.SITE.LIB_SHARE]
 Base Translation:
 
But I get the message: Location already in use by another area

I really don't like to put this element in area share! Why is the same 
baselocation not allowed in two applications?

Ursi
T.RTitleUserPersonal
Name		DateLines
2574.1why?IOSG::BILSBOROUGHJust testing. Please ignore!!! Fri Apr 16 1993 11:3914
    
    Why do you need to have an authorised location just for A1SUBMIT.
    Since it's part of ALL-IN-1 why does your application need to know
    about it?
    
    A work around to get two applications sharing the same location (though 
    I not sure you need it) is this.
    
    Have a new logical and define that as OA$LIB then use this new logical
    as the auth location.  I think it should work.
    
    Mike
2574.2Some explanationsIOSG::TALLETTGimmee an Alpha colour notebook...Fri Apr 16 1993 12:0113
    >Why do you need to have an authorised location just for A1SUBMIT.
    
    	Its to do with security. A1SUBMIT won't submit it from just
    	anywhere.
    
    >Since it's part of ALL-IN-1 why does your application need to know
    >about it?
    
    	A1SUBMIT is part of ALL-IN-1, but not this script that the customer
    	is creating.
    
    Regards,
    Paul
2574.3what is with the command procedure?TAKEOF::ERNIUrsula ErniMon Apr 26 1993 15:4715
    Sorry for not having answered so long.
    
    The command procedure does have to be in OA$LIB. The command from a
    script could be:
    
    get oa$dcl = 'a1submit/noprint/name=CAGOF_SETUSER/noident/que=VAX5_DEFAULT-'
    get oa$dcl = '/log=oa$log:cagof_setuser.log/user=ALLIN1-'
    get oa$dcl = '/para=("' #cagof_pfvms '","'#cagof_pfuafrevoke '",-'
    get oa$dcl = '"' #cagof_pfuafid '","' #cagof_diskquo '") -'
    get oa$dcl = ' oa$lib:cagof_setuser.com '
    
    If you tell me there is a way to put CAGOF_SETUSER.COM in CAG$LIB i am
    more than happy. 
    
    Ursi
2574.4SIOG::T_REDMONDThoughts of an Idle MindMon Apr 26 1993 16:475
    Surely the command procedure only needs to be owned by the same UIC as
    the ALL-IN-1 Manager account?  Does it really have to be stored in
    OA$LIB (or OA$SITE_LIB)?  
    
    Tony
2574.5OA$LIB requiredIOSG::TALLETTGimmee an Alpha colour notebook...Mon Apr 26 1993 20:255
    
    	I just checked the code. Ever since V2.3 it has to be in OA$LIB.
    
    Regards,
    Paul
2574.6PFR?AIMTEC::WICKS_Aon the Streets of San FranciscoMon Apr 26 1993 21:125
    So it could be added to CM as an exception element?
    
    Regards,
    
    Andrew.D.Wicks