Conference iosg::all-in-1_v30

    Regina,
    
    Firstly I assume you mean that OA$TXL_SEARCH_ORDER is 1 and not
    OA$FILE_SEARCH_ORDER as you state?
    
    Your OA$FILE_SEARCH_ORDER doesn't look like on of the ones out of the
    box - do you know which one of the .ESO files it is?
    
    the second occurrence of the [] is unusual and I don't know
    what OAX$PM is either - i'm confused.
    
    Try setting your search order to CM_APPLICATION and recompiling the
    search order for that should be ok.
    
    Regards,
    
    Andrew.D.Wicks

Regina,

> When recompiling the A1TXL from within ALL-IN-1 the OA$BLP_ENGLISH
> directory does not get linked in. It does compile OA$BLP_SHARE.

Please check the Authorized Live Location for ENGLISH BLP OA$SITE_BLP_ENGLISH: 
via options CM AM MAL. Check if the TXL field is set to 'Y'. Also check of the 
TXL Type field is set to BLP. If not, please correct this and OA$BLP_ENGLISH: 
should be taken into the A1TXL.TXL.

> When I do this from ALLIN1/NOINIT, it will link.

Keep in mind that option CTX and the interactive command OA$TXL_COMPILE work 
    from a totally different base. Also, the OA$FILE_SEARCH_ORDER entries
    don't have anything to do with defining what's in the TXL.

> To my knowledge we haven't changed anything in search orders. Why aren't
> there any BLP and SCP directories, btw? 

Whe CM is started it puts the entries of the elements search order template and 
put it on top of your current OA$FILE_SEARCH_ORDER. This must explain the 
OAX$PM. However, the second occurrence of '[]' seems strange to me also, as 
    duplicate entries will be filtered out (except for OALIB: or OA$LIB: in
    combination with OA$*LIB*:).

> Also, when in ALL-In-1 the ENGLISH logicals are not only defined in
> the system table, but also in OA$ENGLISH_TABLE. Is this a particularity
> of our systems or normal?

Do you mean e.g. the OA$SITE_LIB_ENGLISH logical or the OA$SITE_LIB_LLV 
logicals. In case of the last one, that's normal. There will always be *_LLV 
logicals System wide, but only for the Default Language. There will always be 
*_LLV logicals in the OA$<language>_table, for the language you're running 
ALL-IN-1 in.

>    Try setting your search order to CM_APPLICATION and recompiling the
>    search order for that should be ok.

If CM_APPLICATION.A1$ESO doesn't exist in your directory, try and look for 
CM_MANAGER.A1$ESO or CM_PROGRAMMER.A1$ESO.

Ciao,
	
	Simon

Simon,

now you lost me.

AM MAL shows only one authorized location with TXL = "Y" and that is
OA$SITE_SCP_ENGLISH. But we have quite some customs and none of them is
missing!

Also, the problem is with A1TXL. How does CM$AUTH$LOCATIONS influence
the recompile of A1TXL, if this file contains only site logicals?

And yes to both of you, I meant of course OA$TXL_SEARCH_ORDER.

OAX$PM is from the Asset Phone memos.

In the set search order in SCE I only have DEFAULT and CM_MANAGER.
Should I have a CM_APPLICATIONS?

Thanks
/rhr

    
    Hi Regina,
    
    CM$AUTH$LOCATIONS does contain the valid Live locations, but if you
    have elements in the Base area, then you will have entries in the Base
    Location fields also. Do CM AM MAL and use GOLD VIEW with one of the
    enrties of the ENGLISH or SHARE area. 
    
    Now, only OA$SITE_SCP_ENGLISH: the only location with TXL = 'Y'. Has
    this system been updated during ALL-IN-1 V3.0 development (several Base
    Levels)? I've a fresh new system here, and also 2 upgraded systems, and
    the information for the TXL field for the OA application is OK:
    
    	OA$SITE_BLP_ENGLISH:		! Both for BLP and BLPW types
    	OA$SITE_BLP_SHARE:
    	OA$SITE_DO_ENGLISH:
    	OA$SITE_DO_SHARE:
    	OA$SITE_SCP_ENGLISH:
    	OA$SITE_SCP_SHARE:
    
    The fact that none of your customs is missing is that someone might
    have done an interactive OA$TXL_COMPILE CMTXL, which would compile the
    default Site directories of OA$BLP, OA$DO and OA$SCP and doesn't bother
    about CM$AUTH$LOCATIONS.
    
    Should you have a CM_APPLICATIONS? No, If you're a CM Manager, then you
    will have CM_MANAGER.A1$*SO. If you were only a CM Maintainer, then you
    would have CM_APPLICATION.A1$*SO.
    
    Ciao,
    	
    	Simon

Ok,

we copied the site and cm stuff from our test machine to the life
machines. Inadvertantly we also copied the CM$AUTH$LCOATIONS and
had to adapt them by hand. By doing this the TXL = "N" fields were
set. Once I put the TXL to Y for the BLP's it was working just fine.

Thanks for your help.
/rhr