Oppolzer - Informatik / Blog

It is not that easy to mix XPLINK and non-XPLINK modules, BTW. I had to do it
once, when I had to establish the linkage between a PL/1 caller and an
encryption library (open SSL) which was written in C and compiled using XPLINK.
This was kind of hard, because the only way to do this is to have dynamic
linkage (like MVS LOAD or PL/1 FETCH) and some strange compile options in the
interface between the non-XPLINK and the XPLINK part.

So normally at our site we don't use XPLINK, because we need the communication
between C, C++ and PL/1 (and ASSEMBLER, BTW, which is not all the time
LE-enabled).

Kind regards

Bernd



Am 20.08.2014 12:50, schrieb L.S.:
> I justr remembered a nice share-session:
>
> session 8121 'converting your LE-environment c/c++-applications to
> XPLINK'
>
> http://www.google.at/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0CCYQFjAB&url=
> ftp%3A%2F%2Fftp.software.ibm.com%2Fs390%2Fzos%2Fle%2Flb8121a.pdf
> &ei=XHz0U5K-G6304QTFi4GwDA&usg=AFQjCNETncT2dNwk2sTQpn9hZuBmvCeB4Q&bvm=bv.73373277,d.bGE
>
>
> On 20.08.2014 12:09, D.C. wrote:
>> It's also worth a look at the redbook (quite old)
>> http://www.redbooks.ibm.com/abstracts/sg245991.html XPLINK uses page
>> protection to trap overlays to trigger stack frame extension. Rather
>> clever idea and it removed several instructions from C/C++ prolog code.
>>
>>
>> On 20/08/2014 5:43 PM, L.S. wrote:
>>> Look at 'zOS Language Environment Vendor Interfaces'.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to listserv@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@listserv.ua.edu with the message: INFO IBM-MAIN