Discussion List On Behalf Of Jon
Perryman
Sent: Monday, September 2, 2019 8:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
I'm not sure how you made the leap to the DLL module was not found. These
messages imply the CELQV003 was found but the xplink attribute did
I'm not sure how you made the leap to the DLL module was not found. These
messages imply the CELQV003 was found but the xplink attribute did not match.
The binder uses the DLL module to validate attributes are correct instead of
doing this validation at run time.
I agree with Don that you
YSADATA)
//
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Don Poitras
Sent: Monday, September 2, 2019 8:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
That all looks as though you're mixing 31-bit and 64-bit objects. Was
SYSADATA c
SX64),DISP=SHR
> //DD DDNAME=SYSIN
> //SYSLMOD DD DSN=
> //SYSDEFSD DD DUMMY
> //SYSPRINT DD SYSOUT=*
> //SYSINDD DUMMY
> -EDIT*DSLIST
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> Don Poitra
o: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
I still don't see an error message. There is no DLL CELQV003. The import
statement just tells the binder how to link the program to find the
executable at run time. If you do a search inside CEE.SCEEBND2, you will
find eyeca
@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
You've missed the point. We need real details. For instance, the error message
should always be included instead of your interpretation of the message.
You could look in SMP/E and find out where CELQV003 is located. Maybe you
DD DSN=(IOSX64),DISP=SHR
> // DD DDNAME=SYSIN
> //SYSLMOD DD DSN=
> //SYSDEFSD DD DUMMY
> //SYSPRINT DD SYSOUT=*
> //SYSINDD DUMMY
>-EDIT*DSLIST
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
tras
Sent: Monday, September 2, 2019 6:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
I'm sure the compiler has deficiencies. You're previous error program showed
one. While it would be nice to claim to be able to catch every possible
coding error, that's just not
ptember 2, 2019 6:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C++ missing DLL for fopen
I'm sure the compiler has deficiencies. You're previous error program showed
one. While it would be nice to claim to be able to catch every possible
coding error, that's just not realistic. A "huge&q
I'm sure the compiler has deficiencies. You're previous error program
showed one. While it would be nice to claim to be able to catch every
possible coding error, that's just not realistic. A "huge" number of
them? That would be news to us. We've been using this compiler/library
for many years
On Sunday, September 1, 2019, 08:31:39 PM PDT, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>> As for IBM C having several deficiencies, remember that z/OS is a
>> very complex OS compared to Unix where 1 size fits all.
> Simpler is better.
I never said
[Default] On 1 Sep 2019 20:31:40 -0700, in bit.listserv.ibm-main
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) wrote:
>On Mon, 2 Sep 2019 02:39:26 +, Jon Perryman wrote:
>
>> There are 2 PTF's listed in the apar
>>
Jon
Just on the phone with IBM the date of the fix nov 2, 2016 was for 2.1 , 2.2
They said should have been resolved for 2.3
They said level 2 will get back to me
Tommorow
Thanks
> On Sep 1, 2019, at 10:39 PM, Jon Perryman wrote:
>
> There are 2 PTF's listed in the apar
>
On Mon, 2 Sep 2019 02:39:26 +, Jon Perryman wrote:
> There are 2 PTF's listed in the apar
> http://www-01.ibm.com/support/docview.wss?crawler=1=isg1PI68779
>
>As for IBM C having several deficiencies, remember that z/OS is a very complex
>OS compared to Unix where 1 size fits all.
>
There are 2 PTF's listed in the apar
http://www-01.ibm.com/support/docview.wss?crawler=1=isg1PI68779
As for IBM C having several deficiencies, remember that z/OS is a very complex
OS compared to Unix where 1 size fits all. I would hope that on z/OS, 2GB is
sufficient for most programs. If
I saw that’s but all the said he re-did application
Probably told him to go to amode 31
I have lots of storage so I want get above bar storage so the only way to do
that is amode 64
Figured when you do a malloc it would be above the bar
The XL C\C++ compiler has a huge number of
IBM PI68779: An customer PL/I 64bit application failed with CEE3501S.
|
|
| |
IBM PI68779: An customer PL/I 64bit application failed with CEE3501S.
Error Description PL/I 64bit customer has an application that is failing with
|
|
|
Jon.
On Sunday, September 1, 2019, 11:49:05 AM
Hi
I am trying to compile a AMODE 64 DLL which has a fopen
And cann't find its associated DLL
CELQV003
IMPORT CODE64,CELQV003,'fopen',069
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
18 matches
Mail list logo
