Conference iosg::all-in-1_v30

2233.0. "Relink/SDF problems w/V3.0" by GANTRY::HULL (Digital Services Delivery - Motown) Mon Feb 08 1993 18:56

I'm trying to port our V2.4 SDFs over to a V3.0 concurrent system.

If I've done a $SET DEF OA$BUILD: and then run @A1LNKDRV the following 
problem occurs:

%DCL-I-SUPERSEDE, previous value of VMI$KWD has been superseded
%DCL-I-SUPERSEDE, previous value of A1$XPORT has been superseded
%DCL-I-SUPERSEDE, previous value of LNM$BUILD has been superseded
%DCL-E-OPENOUT, error opening LNM$BUILD:OALNM.MAR as output
-RMS-F-DIR, error in directory name
%VMSINSTAL-E-FATAL, Correct the reported problems before re-linking

To get past that, I have to explicitly $ SET DEF OA$BUILD_LLV: (why???) 
OA$BUILD is a search-list, it ought to find the file....

Then, once it gets going into the Relink questions, it cannot correctly 
parse out the DATATRIEVE version (we run V6.0-1) from the Shared Image file: 

* Do you want to integrate DATATRIEVE with ALL-IN-1 [YES]?
%A1 -I-DTRLINK, DATATRIEVE will be linked with ALL-IN-1
* What is the name of the DATATRIEVE image you want to link with [DTRSHR]:
%A1 -I-DTROK, DTRSHR has been chosen as the DATATRIEVE image to link with
%A1 -W-LOWDTR1, Your DATATRIEVE version should be at least V5.0
%A1 -W-LOWDTR2, You have V , the installation will continue, but the
                         ^^
                         ^^
%A1 -W-LOWDTR3, link with DATATRIEVE is not supported.

I've turned off linking all the other OA images, as all I want to do is 
incorporate our V2.4 SDF's.  After the relink finishes 'successfully' 
(at least no errors), I run the new OA1$MAIN.EXE image to see if the SDF 
functions got linked in, and they aren't there.  They never even got 
referenced in the A1LINK.OPT file, so for some reason SITELINK30 isn't 
getting read at all.

link driver com files are all in:
USER19:[ALLIN1V3.SOURCES_ENGLISH]A1LINK.COM;1, A1LNKDRV.COM;1  (oa$build_llv)

USER19:[ALLIN1V3.SOURCES_SHARE]A1LNKASK.COM;1  (oa$build_share)

Site object library is in:
USER19:[ALLIN1V3.SITE.SOURCES_SHARE]SITEOALIBR.OLB;2  (oa$site_build_share)

SITELINK30 is in:
USER19:[ALLIN1V3.SITE.SOURCES_ENGLISH]SITELINK30.COM;1 (oa$site_build_llv)
(listed below):

$!      Include Site Defined Functions for Ford ED  (16-Jun-1988 DSL)
$wo "! Site Defined Functions for Ford ED"
$wo "OA$BUILD:SITEOALIBR/INCLUDE=(-"
$wo "! Modules for Ford EMS"
$wo "ADD_TO_EMSQUEUE, PROCESS_EMS_ADDRESSEE,-"
$wo "! String processing wrap module for calendar functions"
$wo "OAX$WRAP,-"
$wo "! String processing Capitalization module"
$wo "OAX$CAPITALIZE,-"
$wo "! Team Action Items action routines module"
$wo "OAX$TAI_FUNCTIONS,-"
$wo "! REPORT action routines module"
$wo "OA$TXT_REPORT,OA$TXT_REPORT_EDIT,-"
$wo "! AFVA - FMS Field Video Attributes"
$wo "OAX$AFVA)"
$wo "! [END OF SITEOALIBR.OLB MODULES]"

Why isn't a normal relink procedure working:
  1) where its supposed to, 
  2) why isn't it finding the site modules

HELP!!

	Al

    see note 2127 for the datatrieve problem.

    Second answer: move SITELINK30 to OA$BUILD_LLV and i'll bet it works
    
    No don't ask me why I only reported it during v3.0-1 FT.
    
    Regards,
    
    Andrew.D.Wicks

Andrew - thanks - both your pointers worked fine.  Of course I forgot to
set A1$DEFER == 0 the first time and got zillions of "multiply-defined
symbol" warnings, etc.  All my SDF's now appear in the function list, and
the one I tested worked fine, so I'm assuming at this point that they will
all work.

I hope these restrictions on SDF/relink file placement (location) get fully
documented in the update for the manuals.  This is the kind of info that
should also be published in the ALL-IN-1 Update.

Regards,

	Al

    Al,                   
    
    Glad to hear it - please SPR this since the QAR I logged during FT
    appears to have gotten lost (:==:)
    
    Regards,
    
    Andrew.D.Wicks

    Actually we're intending to examine the code and try to make it work
    regardless of where you are set default to, or where all the files are!
    
    Graham

Graham - I was under the (apparently mistaken) impression that using
OA$BUILD: should have worked, as it points to a 4 logical areas.  You'd
think the routines would be able to handle that...

Even Tony's book on V3.0 leads one to assume that just using OA$BUILD: is
ok, and John's new book also refers only to OA$BUILD:.

	-Al

    Re: .6
    
>Even Tony's book on V3.0 leads one to assume that just using OA$BUILD: is
>ok, and John's new book also refers only to OA$BUILD:.

    I agree I should have covered the potential for problems in the default
    directory more thoroughly but there is actually a reference to your
    problem on page 76 under "Wrong SITELINK30.COM".  It would have been a
    good idea to also talk about setting default to search-lists but I
    guess I missed that one.
    
    John