You can access hiperspaces in COBOL using the MVS Callable Services for
HLLs Window Services
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieac100/ws.htm.
There are code examples.
On 15/01/2019 2:58 am, scott Ford wrote:
Peter:
My typos ..sorry the question
Peter:
My typos ..sorry the question was in regard to a Cobol program creating and
then referencing
Hiperspaces. You answer was what I thought, so thank you.
Scott
On Mon, Jan 14, 2019 at 12:59 PM Peter Relson wrote:
>
> > So how does a Cobol Pgm , 31bit address say a Hiperspace ?
> > I
> So how does a Cobol Pgm , 31bit address say a Hiperspace ?
> I assume an interface program units AR registers , etc., am I correct ?
> I have don’t this want to...
I could not parse this. What were you trying to ask?
Hiperspaces are not directly referenced. You use services to put data in
Sorry for the typos.. should read Cobol program , I would like to do this.
Regards,
Scott
On Fri, Jan 4, 2019 at 4:19 PM scott Ford wrote:
> Peter,
>
> So how does a Cobol Pam , 31bit address say a Hiperspace ?
> I assume an interface program units AR registers , etc., am I correct ?
> I have
Peter,
So how does a Cobol Pam , 31bit address say a Hiperspace ?
I assume an interface program units AR registers , etc., am I correct ?
I have don’t this want to...
Scott
IDMWORKS
On Fri, Jan 4, 2019 at 8:46 AM Peter Relson wrote:
> From the LE team:
>
> fetch() will indeed reject loading
>From the LE team:
fetch() will indeed reject loading load module of another AMODE.
This is related to the fact that LE will not only load the module into
storage (with the LOAD macro) but will also manage some control blocks and
data for the module, such as the load list table, the WSA and
Why not just a general LINK31 routine to be called for any program …
ACONTROL OPTABLE(ZS3)
SPLEVEL SET=6Specify OS/390 R2 MACRO Format
SYSSTATE ARCHLVL=2Program Requires Z/Architecture
alf
Of Tom Marchant
Sent: Thursday, December 20, 2018 11:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 64-bit C code fetching IGGCSI00
On Thu, 20 Dec 2018 10:17:12 -0500, Pierre Fichaud wrote:
>You can get around stack processing in 31-bit mode by using #pragma
>linkage(fred,OS) where fre
On Thu, 20 Dec 2018 10:17:12 -0500, Pierre Fichaud wrote:
>You can get around stack processing in 31-bit mode by using #pragma
>linkage(fred,OS) where fred is a non-LE module. I've done this often.
I haven't used #pragma linkage(fred,OS), but I have used
extern "OS_NOSTACK" {int fred(void);}
in
Tom,
If fetch is hard-wired to refuse a load of a 31-bit module while
running in 64-bit mode, I need to write a 64-bit assembler front-end module.
You can get around stack processing in 31-bit mode by using #pragma
linkage(fred,OS) where fred is a non-LE module. I've done this often.
On Wed, 19 Dec 2018 09:28:53 -0500, Pierre Fichaud wrote:
>I can't believe that an AMODE 31 module can't be fetched by 64-bit C
>code. __malloc31() can be used to get 31-bit storage.
Disclaimer: I am not a C guy.
64-bit C is XPLINK.
XPLINK-64 allocates the stack above the bar.
The save area
@LISTSERV.UA.EDU
Subject: Re: 64-bit C code fetching IGGCSI00
Hmm-m-m. Maybe #pragma linkage (IGGCSI00, OS_NOSTACK) would work? Also,
investigate your C compile listing, what is the compiler option XPLINK set to?
I get the impression from RTFM about the XPLINK option that
XPLINK(OSCALL(NOSTACK
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Pierre Fichaud
Sent: Wednesday, December 19, 2018 9:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 64-bit C code fetching IGGCSI00
Peter,
Using FETCHABLE gives me the same error.
With OS_DOWNSTACK I get
Peter,
Using FETCHABLE gives me the same error.
With OS_DOWNSTACK I get the followig when I build:
CCN6404 (W) The parameter "OS_UPSTACK" specified for "pragma linkage"
is not valid. The pragma is ignored.
I ran it anyway and got the same thing.
I can't
-MAIN@LISTSERV.UA.EDU
Subject: 64-bit C code fetching IGGCSI00
I have 64-bit C code that attempts to fetch() IGGCSI00.
I've used pragma linkage on IGGCSI00 but got nowhere.
I am getting the following:
EDC5256S An AMODE64 application is attempting to fetch() an AMODE31 executable.
(errno2=0xC4070068
In article <8873109401385730.wa.m42tomibmmainyahoo@listserv.ua.edu> you
wrote:
> On Tue, 18 Dec 2018 12:24:38 -0600, Pierre Fichaud wrote:
> >I have 64-bit C code that attempts to fetch() IGGCSI00.
> >I've used pragma linkage on IGGCSI00 but got nowhere.
> >I am getting the following:
> >
>
On Tue, 18 Dec 2018 12:24:38 -0600, Pierre Fichaud wrote:
>I have 64-bit C code that attempts to fetch() IGGCSI00.
>I've used pragma linkage on IGGCSI00 but got nowhere.
>I am getting the following:
>
>EDC5256S An AMODE64 application is attempting to fetch() an AMODE31
>executable.
Don,
I understand about the parameters and data areas being in 31-bit
storage.
I'm trying to fetch() IGGCSI00 in C code that is compiled for 64-bit.
The fetch fails.
Can I define IGGCSI00 somehow to C so that the fetch() works ?
Regards, Pierre.
In article <5828839252973544.wa.prf51videotron...@listserv.ua.edu> you wrote:
> I have 64-bit C code that attempts to fetch() IGGCSI00.
> I've used pragma linkage on IGGCSI00 but got nowhere.
> I am getting the following:
> EDC5256S An AMODE64 application is attempting to fetch() an AMODE31
>
I have 64-bit C code that attempts to fetch() IGGCSI00.
I've used pragma linkage on IGGCSI00 but got nowhere.
I am getting the following:
EDC5256S An AMODE64 application is attempting to fetch() an AMODE31 executable.
(errno2=0xC4070068)
The C program was compiled with :
20 matches
Mail list logo
