Conference iosg::all-in-1_v30

    Dear Confused,
    
    Maybe what you need is my course "CM+ for the brain dead by the brain
    dead"? I could teach it when I pass through Basingstoke in
    December/january if you like.
    
    This note is the same as the STARS article which is derived from note
    255 in the old FT conference I think.
    
    The basic problem is that you have OA$LIB_LLV in there instead of
    OA$LIB.
    
    Just take out the "_LLV" out and all your problems will go away!
    
    Cue Simon for a much more accurate response ...
    
    Regards,                           
    
    Andrew.D.Wicks

    Ahhhhhhh,
    
    I can save default with out the oa$lib_llv but it keeps comimg back
    
    i.e. MC from MLO and change oa$lib_llv:cm to oa$lib:cm and then Gold
    file. I then RS to make sure that default is ok.  I then SSO to set
    default and then back to MLO to VC and Voila oa$lib_llv:cm is back....
    
    all I need is the steps to change it permanently.
    
    Suzanne

    
    Check what the entry is in OAUSER:DEFAULT.A1$LSO and
    OAUSER:CM_MANAGER.A1$LSO.
    
    The search order the manager sees is based on this unless you remove it
    from both it'll still appear.
    
    ta,
    
    Mike
    

    Mike,
    
    this is what I have in both of those files 
    
    $ty CM_MANAGER.A1$LSO
    OA$LIB:SITEMEMRES.FLB
    OA$LIB:MEMRES.FLB
    OA$SITE_DEV_BRITISH:DEVELOP.FLB
    OA$SITE_DEV_SHARE:DEVELOP.FLB
    OA$LIB:SITECM$MANAGER.FLB
    OA$LIB:CM$MANAGER.FLB
    OA$LIB:SITECM.FLB
    OA$LIB:CM.FLB           <-----
    OA$LIB:SITEOAFORM.FLB
    OA$LIB:OAFORM.FLB
    
    $ty DEFAULT.A1$LSO
    OA$SITE_LIB_LLV:SITEMEMRES
    OA$LIB_LLV:MEMRES
    OA$SITE_DEV_BRITISH:DEVELOP.FLB
    OA$SITE_DEV_SHARE:DEVELOP.FLB
    OA$LIB:SITECM$MANAGER.FLB
    OA$LIB:CM$MANAGER.FLB
    OA$LIB:SITECM.FLB
    OA$LIB:CM.FLB     <-----
    OA$SITE_LIB_LLV:SITEOAFORM
    OA$LIB_LLV:OAFORM
    OA$LIB:MANAGER
    OA$LIB:ADMIN
    
    
    I do have multiple version of default.a1$lso and version 1 does have
    the dreaded OA$LIB_LLV:CM,  is this the problem?
    
    Suzanne

    Maybe the multiple version isn't the problem as I've just renamed those
    files out of the way
    
    Suzanne

    
    Hi Suzanne,
    
First: Don't get confused!

Second: let me try and explain what happens.

Third: Now get extremly confused of Basingstoke ;-).


Please don't mix terms like default search order up with DEFAULT.A1$*SO files 
in OAUSER:.

First:
Because CM offers the possibility to 'get out of CM' it creates DEFAULT.A1$*SO 
during initialization (this if it doesn't find the files already). These files 
contain the current OA$FILE_SEARCH_ORDER and OA$FORM_SEARCH_ORDER before you 
start CM. By restoring DEFAULT you restore a situation without CM.

Second:
Every level of access to CM uses its own template:

	CM_PROGRAMMER	-> Programmer
	CM_APPLICATION	-> Maintainer
	CM_MANAGER	-> Manager

When calling CM it checks if, according to the level of access, one of these 
templates is in OAUSER:. If not then it will copy the template from OA$LIB: 
into OAUSER:. This means that everytime you call CM the template in OAUSER is 
used to set up the CM environment (on top of the existing enviornment). So, 
when you perform CM SCE MLO MC, you'll see your current library search order 
consisting of:

	search order before starting CM
	CM specifics put on top of the search order


> I go into CM SCE MLO MC and my default search list contains OA$LIB_LLV:CM
> I try and add a formlib (anywhere in the list) and then save the list, I 
> then get the error 
>     
>    "Warning: OA$LIB:CM.FLB will not be in your library search
>     order.  This will make Customization Management unavailable"

Unfortunately the routine which checks if CM is still in the search order is 
not that very cleaver and cannot deal with the OA$LIB_LLV: logical. This is 
a known problem.

This basically refers to problems described in 550.

>    $ty CM_MANAGER.A1$LSO
>    OA$LIB:SITEMEMRES.FLB
>    OA$LIB:MEMRES.FLB
>    OA$SITE_DEV_BRITISH:DEVELOP.FLB
>    OA$SITE_DEV_SHARE:DEVELOP.FLB
>    OA$LIB:SITECM$MANAGER.FLB
>    OA$LIB:CM$MANAGER.FLB
>    OA$LIB:SITECM.FLB
>    OA$LIB:CM.FLB           <-----
>    OA$LIB:SITEOAFORM.FLB
>    OA$LIB:OAFORM.FLB

Please check:

1) Does PROFIL.FRMLIB contains OA$LIB:CM? 

If so, that would explain why, although CM_MANAGER.A1$LSO contains 
OA$LIB:CM.FLB, CM still syas that OA$LIB_LLV:CM.FLB is in your search order. 
WHat happens with the code of OA$FORM_SEARCH_ORDER is (in a loop):

	What is the new form library
	Is the form library openen in the old OA$FORM_SEACH_ORDER. If yes,
		then leave the entry as is

So, you see, although you want OA$LIB:CM.FLB in the symbol, the symbol just 
says: Sorry chap, I have this form library already defined.
	
I can't tell you why, when ALL-IN-1 is started, the form library entries in 
OA$FORM_SEARCH_ORDER have *_LLV:.

> I can save default with out the oa$lib_llv but it keeps comimg back

You can save DEFAULT, but it's not used when initilizing CM!
    
>    i.e. MC from MLO and change oa$lib_llv:cm to oa$lib:cm and then Gold
>    file. I then RS to make sure that default is ok.  I then SSO to set
>    default and then back to MLO to VC and Voila oa$lib_llv:cm is back....

Hope this is explained now.
    
Confused?

Ciao,
	
	Simon

    I think I understand,  Default is not default.a1$*so,  Don't try to
    save anything without setting your default order to something other
    than the default one (the one used when initializing CM not any other
    one called deafult).
    
    I'm try this "confuse the hell out of them" tatic on the customer and see
    if it works!
    
    Suzanne

    
    Hi Suzanne,
    
    > Don't try to save anything without setting your default order to
    > something other than the default one (the one used when initializing CM
    > not any other one called deafult).
    
    ?????
    
    Ciao,
    
    	Simon