Conference iosg::all-in-1_v30

re: .0

>    The management guide p 2-11 says set def oa$build_llv and
>    @A1LNKDRV. Most customising hints/release notes (and T.
>    Redmond!) say move SITELINK30 to OA$SITE_BUILD_SHARE.

I can understand that it is a little frustrating to receive
conflicting advice.  Personally, I would move it to
OA$SITE_BUILD_SHARE since it is, after all, a site-modified
element.  The same goes for the object modules that you
wish to put into OA$BUILD.
    
>    But: SITELINK30.com must live in the default directory
>    when you want to relink. So, what's wrong what's right.
    

This is the key point.  It doesn't matter where SITELINK30.COM
(and SITELLV.COM) are located.  They can be in your SYS$LOGIN
directory if you like.  But always make sure that you set
your current directory to be the one that contains these files.
Otherwise the link procedures will not find them and will not
include your modules in the image.

I hope this helps,

John

    The reason that the management guide says to set default to the 
    OA$BUILD_SHARE directory is probably because that is where the link
    driver command procedure is located (and you cannot set default to
    OA$BUILD because it is a search list which the command procedure does
    not like).
    
    If you set default to somewhere else you obviously need to specify the
    directory of the procedure when you invoke it (i.e. @OA$BUILD:A1LNKDRV
    rather than @A1LNKDRV).
    
    John

    John,
    
    the management guide says OA$BUILD_LLV, at least the version 
    I have. That was confusing...
    
    /rhr
    
    

    re: .3
    
    You are right that it is OA$BUILD_LLV rather than OA$BUILD_SHARE.  I
    think they moved the command procedure from 2.4 to 3.0.  In any case,
    if you want to to execute the procedure without typing in the directory
    where it is located then you must be set default to the directory.  So
    if you want to type in @A1LNKDRV rather than @OA$BUILD:A1LNKDRV and the
    procedure is only in OA$BUILD_LLV you must first set default to
    OA$BUILD_LLV.  This is why I suspect the documentation recommends this
    directory.
    
    As long as you have no site-specific modules there is no reason not to
    follow this recommendation.  However if you have some and they are
    declared in SITELINK30.COM then you need to make sure you set default
    to the directory where the SITELINK30.COM is located - otherwise it
    will not be used.  Where you put this procedure is up to you, in the
    sense that it will work no matter where it is.  From a formal point of
    view OA$SITE_BUILD_SHARE is probably most correct since it should be
    site-specific but not language-specific.
    
    Does this make more sense?
    
    John
    
    P.S.:  Personally, I think that the references in A1LINK.COM to
    SITELINK and SITELLV should be changed from A1$WORK to A1$LINK_FILES
    which would resolve this whole problem and be more consistent.  But
    since that is not the case you have to do the best with how it is.

    A1LNKASK is still in SHARE.
    
    A1LINK and A1LNKDRV were moved to the language kit, and hence to the
    BUILD_language directory in V3.0, because they needed to be different
    in some of the language kits, principally Asian ones.
    
    I'm sorry if this has caused *some* confusion.
    
    It certainly confused me last time I tried to do a link :-)
    
    Graham

    I guess I replied to note 681 and disagreed with Tony so I should
    reply here and disagree with you so as not to show any favourtism (:==:)
    
    I still believe that SITELINK30.COM should go in OA$SITE_BUILD_ENGLISH
    primarily because it will then be in the same directory as customised 
    versions of A1LINK.COM (WordPerfect, EARS etc...) or A1LNKDRV.COM
    (since they start in OA$BUILD_ENGLISH that appears to be the right
    place when practising safe CM)
    
    here at the CSC we've had enough confusion/scope for relinking errors
    after K603/WPS-PLUS v4 patches with a new A1LINK here and an old
    customised A1LINK there and a SITELINK24 somewhere else in the OA$BUILD
    search list that it would be MUCH MUCH NICER if the "official" 
    documentation would have actually included a recommendation as Regina
    was asking for - but I guess we're going to get OA$SITE_BUILD_SHARE
    in Tony's new book right?
    
    Also it would nice if someone could fix A1LNKDRV after breaking Uncle
    Dave's 7 year-old rule about how to link since it still thinks that
    A1LNKASK.COM and A1LINK.COM are in the same directory and thus stops 
    you relinking in the case where one is customised.
    
    Regards,
    
    Andrew.D.Wicks
                                  

    Wherever you put it, eventually you will find some package that creates
    a new one in the other directory.  Definitely we need to have a
    definitive answer given in the documentation.
    
    Ben

    
    I know I'm going to regret asking this question but here goes anyway.
    
    Did the question as to where to put SITELINK30.COM get resolved?

    I have to agree with Ben in .7.  This is a no win situation.  I've
    encountered the same problem that Regina did.  The previous notes
    mentioned different locations and as to why each is correct.  However
    since you must invoke A1LNKDRV.COM from the directory containing
    SITELINK30.COM, it appears that it can be in any of the 4 build
    directories and can probably be justified for being there.  

    Has an "official" recommentation been made?  If so, where should it go?
	
    Thank you,
    
    Terry