That is the same method I used when I had the similar problem:
calling a given XPLINK C routine from PL1.
I wrote a NON-XPLINK C function which called the XPLINK function
via fetch (). I was able to call the NON-XPLINK function from PL/1.
excerpt from the "glue" function:
/***
Let me know if it works.
On Mon, Sep 22, 2014 at 12:14 PM, Kirk Wolf wrote:
> Sam,
>
> This is a really good suggestion I have used fetch() from non-XPLINK C
> before to call XPLINK C in a separate enclave, so I know that that works.
> It may be more COBOL than I can handle, though... :-)
>
Oh, FETCH is an alias of EDC4$248 and resides in CEE.SCEELKED. So it
likely means that you cannot use the COBOL DYNAM compile parameter
successfully on the compile that uses it. I don't know of many shops
which put that in the LINKLIST or in the STEPLIB. But, then, what do
__I__ know about "normal"
On Mon, Sep 22, 2014 at 2:14 PM, Kirk Wolf wrote:
> Sam,
>
> This is a really good suggestion I have used fetch() from non-XPLINK C
> before to call XPLINK C in a separate enclave, so I know that that works.
> It may be more COBOL than I can handle, though... :-)
>
> Kirk Wolf
> Dovetailed Tec
Sam,
This is a really good suggestion I have used fetch() from non-XPLINK C
before to call XPLINK C in a separate enclave, so I know that that works.
It may be more COBOL than I can handle, though... :-)
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
On Mon, Sep 22, 2014 at 10:32 AM,
Subject: Re: COBOL "LINK" without Assembler?
Kirk:
I called A Cobol routine(s) in C without an issue …threaded , the threads
started in C.
I have code if you would like to see
Regards,
Scott
www.identityforge.com
From: Kirk Wolf
Sent: Monday, September 22, 2014 10
To obtain the address of an XPLINK C/C++ routine which can be called from a
NON-XPLINK program, look at the fetch() function in the C/C++ run time
library reference.
When calling "fetch()" from COBOL, the COBOL code will have to use the
RETURNING facility of the CALL statement to get the address o
Scott -
Its not an issue to call between Cobol and C if one is using the
non-XPLINK runtime for the C programs.
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
On Mon, Sep 22, 2014 at 9:45 AM, Scott Ford <
0006f84450fa-dmarc-requ...@listserv.ua.edu> wrote:
> Kirk:
>
>
> I called A Co
Kirk:
I called A Cobol routine(s) in C without an issue …threaded , the threads
started in C.
I have code if you would like to see
Regards,
Scott
www.identityforge.com
From: Kirk Wolf
Sent: Monday, September 22, 2014 10:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Thanks Don,
On Mon, Sep 22, 2014 at 8:24 AM, Kirk Wolf wrote:
> We have a batch utility program that is built in C that uses the XPLINK
> version of the C runtime.A customer would like to "dynamically" call
> this from COBOL, but of course the LE runtimes are not compatible:
>
> IGZ0179S A dynamic call to
Thanks Don,
That is a pretty good idea, but not quite what I was looking for since
BPX1ATM would not be synchronous. I suppose that I could follow it with
BPX1WAT to reap the child process return code. So this combination is
probably one way to do it without Assembler.
Kirk Wolf
Dovetailed T
I would think you could call BPX1ATM (attach_execmvs()) from COBOL.
In article
you wrote:
> We have a batch utility program that is built in C that uses the XPLINK
> version of the C runtime.A customer would like to "dynamically" call
> this from COBOL, but of course the LE runtimes are not
We have a batch utility program that is built in C that uses the XPLINK
version of the C runtime.A customer would like to "dynamically" call
this from COBOL, but of course the LE runtimes are not compatible:
IGZ0179S A dynamic call to COZBATCH failed because the load module contains
one
or mo
13 matches
Mail list logo
