Conference rocks::dec_edi

3100.0. "V2.1D DECED$APPSHR_V2.EXE and V2.1C DECED$APPSHR_V2.EXE" by UTRTSC::SMEETS (Workgroup support) Tue Apr 15 1997 13:28

Hi,

This morning I've upgraded our interal test VAX/VMS system running 
DECforms V1.4, Objectbroker V2.5B-09 and DEC/EDI V2.1C to DECforms V2.1B, 
Objecbroker V2.6-07 and DEC/EDI V2.1D.

Everything went fine until I tried to execute a C program which performs
Trade Track and Trade Fetch commands.

First I got the message 

$ run MARTIN_FETCH.EXE;4
%DCL-W-ACTIMAGE, error activating image OBB$SHR
-CLI-E-IMGNAME, image file $2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]OBB$SHR.EXE
-SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image

Alright no problem, so I relinked my program via:

LINK MARTIN_FETCH,SYS$INPUT:/OPTIONS
SYS$SHARE:DECEDI$APPSHR_V2.EXE /SHARE
^z

and suddenly the linker complainted about symbols like PRINTF and STRLEN which 
were undefined.

As I'm using VAX C I relinked my program via:

LINK MARTIN_FETCH,SYS$INPUT:/OPTIONS
SYS$SHARE:DECEDI$APPSHR_V2.EXE /SHARE
SYS$SHARE:VAXCRTL.OLB/LIB
^z

And now everything works like a charm.

After this I compared the DECEDI$APPSHR_V2.EXE of V2.1C and V2.1D. I noticed 
that the V2.1D  DECEDI$APPSHR_V2.EXE isn't any longer linked against VAXC.

V2.1C					V2.1D

Shareable Image List			Shareable Image List

0)  this image				0)  this image
1)  "OBB$SHR"				1)  "OBB$SHR"
2)  "LIBRTL"				2)  "LIBRTL"
3)  "LIBRTL2"				3)  "LIBRTL2"
4)  "SECURESHR"				4)  "SECURESHR"
5)  "SECURESHRP"			5)  "SECURESHRP
6)  "VAXCRTL"				6)  "DECC$SHR"
7)  "CMA$TIS_SHR"			7)  "MTHRTL"
8)  "MTHRTL"				8)  "CMA$TIS_SHR"
9)  "DECC$SHR"

Is there a reason why this has been done ? If yes, why isn't this mentioned in
the release notes. ?

Another possibility is to install DEC C but than you'll have to compile your
programs with CC/STANDARD=VAXC otherwise you'll have problems compiling the
program.

Regards,

Martin

    Hi Martin,
    
    I believe you encountered the reason why V2.1D has come out.
    Objectbroker changed compilers, from VAXC to DECC.
    This resulted in OBB V2.6 not being supported on VMS before DECEDI
    V2.1D
    Now DECEDI V2.1D uses DECC as well, and voila!! OBB V2.6 Must be used 
    with V2.1D.
    
    GJ

Well almost!

We have always used DECC for DEC/EDI V2.1 and later. ObjectBroker are
Johny-come-lately's to DECC. 

As of OBB V2.6, OBB put the GSMATCH stuff in to force a re-link. The stange
thing is that DEC/EDI probably wasn't supported on ObjectBroker because it
used the wrong Compiler. In theory OBB V2.6 would have meant that
DEC/EDI V2.1C and OBB were a perfect match (both on DECC) but when
they put the GSMATCH on the image we were required to re-link.

To be honest I hadn't realised that they had done that as early as V2.5B-08.
I thought it was V2.6 and later.

So for DEC/EDI V2.1C and earlier -- use ObjectBroker V2.5A
   for DEC/EDI V2.1D and later   -- use ObjectBroker V2.6 and later (e.g. V2.7)

Mark

Hi Mark and GJ,

You're both right but the point I'm reffering to is the following:

IF you're a VAX C user AND running DEC/EDI V2.1C AND OBB V2.5(a or b) 
THEN
   link program, sys$input:/options
   SYS$SHARE:DECEDI$APPSHR_V2.EXE
   ^Z
ENDIF

IF you're a VAX C user AND running DEC/EDI V2.1D and OBB V2.6
THEN
   link program, sys$input:/options
   SYS$SHARE:DECEDI$APPSHR_V2.EXE
   SYS$SHARE:VAXCRT.OLB/LIB			<-----------
   ^Z
ENDIF

This is due to the fact that V2.1D DECEDI$APPSHR_V2.EXE isn't linked anymore
against VAXCRTL.

I hope you'll understand it now !

Martin

Martin,

That's a good tip.


Just be aware though that ObjectBroker did this because of memory
leaks caused by the different run-time libraries. 

So they may say you are unsupported because you are introducing
the VAXC library back into the image. 

M