Re: Linking Problem

Richard wrote:

> I EMailed an extract from the brochure that
> indicated that .int could be run an any system within a processor type
> (eg Windows to Intel Unix) and she actually rang back and appolgised.

I'll have to check that out -- do you recall where you'd read this?

I can state that applications communicating to RDBMS's are *not*
int-code portable, due to byte-ordering requirements of the code
generated by precompilers (I've had this confirmed from both IBM and
Oracle).



I can see that as both may need COMP-5 to be their way around. However,
what happens when a client program talks to a server and they are not
on the same architecture ?

Differences between the client and server architecture aren't really an issue (to the best of my knowledge). Oracle, for example, expects any parameters to its' APIs to be passed with a specific byte ordering. They themselves document this on their MetaLink site, as on Intel- and Alpha- based platforms, getting this wrong can lead to execution errors.

What I was referring to -- and I apologise for not being clear here -- was (say) precompiling a Pro*COBOL application on Linux Intel, and attempting to execute the int code on Solaris SPARC. As the architectures between the two *client* systems differ, you would have to re-precompile -- and therefore COBOL compile -- on the target client platform, as the precompilers on those respective platforms generate different code.

SimonT.
.