[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

2072.0. "Application areas & authorized locations" by MLNTSC::MANENTI () Tue Jan 12 1993 16:46

	Hi,

	I have created several application areas all without the base
	root directory. The problem that I found is related to the
	authorized locations. For each element type has been filled 
	either the base location and the base translation fields of 
	cm$auth$locations file. These fields should be empty because the 
	base root directory, for those application areas, doesn't exists.

	I reproduced this problem on ALL-IN-1 Italian v3.0 and I observed 
	the same behaviour also on ALL-IN-1 US 3.0.
	
	Any infos or suggestions are more appreciated!

	Many thanks in advance.

				Bye

				Graziella
T.RTitleUserPersonal
Name		DateLines
2072.1Might be a known problemUTES09::VEENHOFSimon Eijs @UtrechtWed Jan 13 1993 11:4169
    
Hi Graziella,

I think this is the same error as reported a month ago by the DEC people
located in AGIP. The problem only appears for TXL elements BLP, DO, SCP and 
BLPW for the locations *_BLP_*, *_DO_* and *_SCP_*. Is that the same in 
your case?

The following is an extract. 

Ciao,

	Simon



>Problem 6:
>----------
>
>    CM logical names definition
>    
>    During the execution of CM_DEFINE_DEV_LOGS script, that defines the 
>    CM logical names, the following error messages is displayed on 
>    several times:
>    
>    Invalid parameter delimiter - check use of special characters
>    \]\
>    
>    Analyzing this problem we discovered that ONLY when the application 
>    areas are created without specifying the base root directories, the 
>    base translation fields (CM$AUTH$LOCATIONS), for the TXLs locations, 
>    are incorrectly loaded.
    
    There seems to be a problem in the CM_SM_INIT_TEXT.SCP when defining 
    the authorized locations for TXL elements. There is no check if the 
    ROOTCODE is defined (Base location) while it is done when the general 
    authorized location is created.
        
    This will be reported against Customization Management as this is an 
    unknown problem.
        
    The temporary workaround is:
        
    1) Modify CM_SM_INIT_TEXT DO SHARE
    2) Change:
    
.LABEL BASE_LOG_TXL

        .IF #CM_LOG_BLIB NES "" THEN .GOTO WRITE_REC_TXL
        GET #CM_LOG_BLIB = #CM_ROOT_NOB:H "." #CM_TL "_" #CM_AREA "]"

.LABEL WRITE_REC_TXL

       to:

.LABEL BASE_LOG_TXL

        .IF #CM_ROOT EQS "" THEN .GOTO BASE_LOG_EMPTY_TXL

        .IF #CM_LOG_BLIB NES "" THEN .GOTO WRITE_REC_TXL
        GET #CM_LOG_BLIB = #CM_ROOT_NOB:H "." #CM_TL "_" #CM_AREA "]"
        .GOTO WRITE_REC_TXL

.LABEL BASE_LOG_EMPTY_TXL

        GET #CM_LOG_BLIB = #CM_LIVE_BDIR = ""

.LABEL WRITE_REC_TXL
2072.3Fields being cleared?BERN01::MAURERFIsn't your mouse looking for cheese?Fri Feb 05 1993 15:2324
    I have one more problem with TXL location. On my system the authorized
    location looks like this for BLP elements:
    
                               Change Authorized Location
    
     Area:             RRS_GERMAN
     Type:             BLP
     Site Location:    RRS$SITE_BLP_RRS_GERMAN:
     Base Location:    RRS$BLP_RRS_GERMAN:
     Description:      Default TXL directory for BLP elements
     Open:             Y
     Txl:              Y   Txl Type: BLP
     Languages:        GERMAN
     Protection proc.: OA$LIB:CM_SET_PROT
     Site Translation: A1DISK:[ALLIN1.SITE.BLP_RRS_GERMAN]
     Base Translation: A1DISK:[ALLIN1.BLP_RRS_GERMAN]
      
    When restoring the package on an other system, the fields Type and
    Languages are both empty, which means that the elements won't be linked
    with OA TXL's. This requires that these fields should be filled
    manually. Why are those fields cleared at package or restore operation?
    Could it be solved? (The same problem appends with other TXL's elements)
    
    Felix
2072.4Missing 2 fields in 5 placesUTES09::EIJSSimon Eijs @Utrecht, 7838-2558Tue Feb 09 1993 12:2824
    
    Felix,
    
    That's because there's a bug in CM_RESTORE_FULL_AUTH.SCP which writes
    the information in CM$AUTH$LOCATIONS.DAT. Both fields are ignored both
    if a new or old record.
    
    I'm not sure if this has been SPRd yet. 
    
    There are 5 places where CM$AUTH$LOCATIONS is changed:
    
    TXL           = CM$STORE$AUTH$LOCATIONS.TXL[#CM_RESTORE_AUTH_KEY], -
    
    This should read:
    
    TXL       = CM$STORE$AUTH$LOCATIONS.TXL[#CM_RESTORE_AUTH_KEY], -
    TXL_TYPE  = CM$STORE$AUTH$LOCATIONS.TXL_TYPE[#CM_RESTORE_AUTH_KEY], -
    LANGUAGES = CM$STORE$AUTH$LOCATIONS.LANGUAGES[#CM_RESTORE_AUTH_KEY], -
    
    I'll check the problem reports and submit an SPR if not reported yet.
    
    Ciao,
    
    	Simon