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 are
missing the library.
Jon.
On Monday, September 2, 2019, 03:13:36 PM PDT, Joseph Reichman
<[email protected]> wrote:
The syslin which the following IMPORT cann't find the DLL CELQV003
BROWSE CEE.SCEELIB(CELQS003)
Command ===>
IMPORT CODE64,CELQV003,'FFLUSH',068
IMPORT CODE64,CELQV003,'fopen',069
I have the following SYSLIB
//SYSLIB DD DISP=SHR,DSN=CEE.SCEEBND2
// DD DISP=SHR,DSN=CEE.SCEELKEX
// DD DISP=SHR,DSN=CEE.SCEELKED
// DD DISP=SHR,DSN=CEE.SCEECPP
// DD DISP=SHR,DSN=CBC.SCLBDLL2
The IBM proc link for 64 BIT only has only CEE.SCEEBND2 I added some hoping
it would be found
Have you done C AMODE64 compile would you know where the DLL for
fopen,malloc for amode 64 lives
Thanks
BROWSE CBC.SCCNPRC(CBCQB) Line 0000000030 Col 001
080
Command ===> Scroll ===>
CSR
//BIND EXEC PGM=IEWL,REGION=&BREGSIZ,
// PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,&BPARM'
//STEPLIB DD DSN=&LIBPRFX..SCEERUN2,DISP=SHR
// DD DSN=&LIBPRFX..SCEERUN,DISP=SHR
//SYSLIB DD DSN=&LIBPRFX..SCEEBND2,DISP=SHR
//SYSLIN DD DSN=&INFILE,DISP=SHR
// DD DSN=&LIBPRFX..SCEELIB(CELQSCPP),DISP=SHR
// DD DSN=&LIBPRFX..SCEELIB(CELQS003),DISP=SHR
// DD DSN=&LIBPRFX..SCEELIB(C64),DISP=SHR
// DD DSN=&CLBPRFX..SCLBSID(IOSX64),DISP=SHR
// DD DDNAME=SYSIN
//SYSLMOD DD DSN=&OUTFILE
//SYSDEFSD DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
-EDIT *DSLIST
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Don Poitras
Sent: Monday, September 2, 2019 6:01 PM
To: [email protected]
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" number of them? That
would be news to us. We've been using this compiler/library for many years
and we've encountered a few problems, especially in the early days of
64-bit. But IBM (unlike other places I could name) responds quickly and
intelligently to any issue we bring to them.
In your latest problem, the question doesn't make sense. I can't tell if
you're seeing a compiler error, a pre-link error, a link-error or a run-
time error. The run-time library for 64-bit is in CEE.SCEERUN2. Do you have
that in your steplib when you run your program? Most shops put that in LLA
for better performance. If it's a build error, show the jcl and the error
message.
In article <[email protected]> you wrote:
> 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 deficiencies
> > On Sep 1, 2019, at 8:17 PM, Jon Perryman <[email protected]> wrote:
> >
> > 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 PDT, Joseph Reichman
<[email protected]> wrote:
> >
> > 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
--
Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive
[email protected] (919) 531-5637 Cary, NC 27513
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
