Re: XL C\C++ missing DLL for fopen you are right I apologize
I took out all the SYSLIB besides BND2 I added SCEERUN for DEBUG TOOL While we are on the subject I was told that I can only invoke Debug tool from EXEC PGM=EQANMFBG Not by calling CEETEST in amode64 would you know anything about that thanks -Original Message- From: IBM Mainframe 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 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 are probably mixing modes in the modules you are linking together. Jon. On Monday, September 2, 2019, 04:30:56 PM PDT, Joseph Reichman wrote: These are the error messages or some of them honestly I just went thru every CBC a CEE library and cannt find CELQV003 IEW2322I 1220 8934IMPORT CODE64,'IOSX64','WS__FR7istream' IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FOPEN DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FREAD DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD MALLOC DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 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 are probably mixing modes in the modules you are linking together. Jon. On Monday, September 2, 2019, 04:30:56 PM PDT, Joseph Reichman wrote: These are the error messages or some of them honestly I just went thru every CBC a CEE library and cannt find CELQV003 IEW2322I 1220 8934 IMPORT CODE64,'IOSX64','WS__FR7istream' IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FOPEN DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FREAD DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD MALLOC DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
LINK I know I have extra SYSLIBs besdies SCEEBND2 but that should nt hurt anything //* //* LINK EDIT THE PROGRAM * //* //STEP0200 EXEC PGM=IEWL,COND=(4,LT,STEP0110), // PARM='AMODE(64),LIST,MAP,XREF,RENT,REUS,DYNAM=DLL' //STEPLIB DD DISP=SHR,DSN=CEE.SCEERUN // DD DISP=SHR,DSN=CEE.SCEERUN2 //SYSLOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //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 //SYSLIN DD DSN=*.STEP0110.SYSLIN,DISP=(OLD,DELETE) // DD DSN=CEE.SCEELIB(CELQSCPP),DISP=SHR // DD DSN=CEE.SCEELIB(CELQS003),DISP=SHR // DD DSN=CEE.SCEELIB(C64),DISP=SHR // DD DSN=CBC.SCLBSID(IOSX64),DISP=SHR //*DD DDNAME=SYSIN //SYSDEFSD DD DSN=IBMUSER.DBGR.SIDDECK(SYSADATA),DISP=SHR //SYSLMOD DD DISP=SHR,DSN=IBMUSER.DBGR.DLLLIB(SYSADATA) // -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 compiled with the LP64 and DLL options? In article <006901d561e6$72682d60$57388820$@gmail.com> you wrote: > These are the error messages or some of them honestly I just went thru > every CBC a CEE library and cannt find CELQV003 > IEW2322I 1220 8934IMPORT CODE64,'IOSX64','WS__FR7istream' > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FOPEN DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FREAD DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD MALLOC DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Jon Perryman > Sent: Monday, September 2, 2019 7:03 PM > To: IBM-MAIN@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 are missing the library. > Jon. > On Monday, September 2, 2019, 03:13:36 PM PDT, Joseph Reichman wrote: > > The syslin which the following IMPORT cann't find the DLL CELQV003 > BROWSECEE.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
Re: XL C\C++ missing DLL for fopen
That all looks as though you're mixing 31-bit and 64-bit objects. Was SYSADATA compiled with the LP64 and DLL options? In article <006901d561e6$72682d60$57388820$@gmail.com> you wrote: > These are the error messages or some of them honestly I just went thru every > CBC a CEE library and cannt find CELQV003 > IEW2322I 1220 8934IMPORT CODE64,'IOSX64','WS__FR7istream' > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO > NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO > NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA > DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO > NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO > NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA > DO NOT MATCH THE ATTRIBUTES OF THE TARGET > SYMBOL. REASON 2 > > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FOPEN DOES NOT MATCH THAT > SPECIFIED ON THE IMPORT STATEMENT. > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FREAD DOES NOT MATCH THAT > SPECIFIED ON THE IMPORT STATEMENT. > IEW2439E 9228 THE AMODE OF THE REFERENCING ESD MALLOC DOES NOT MATCH THAT > SPECIFIED ON THE IMPORT STATEMENT. > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Jon Perryman > Sent: Monday, September 2, 2019 7:03 PM > To: IBM-MAIN@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 are > missing the library. > Jon. > On Monday, September 2, 2019, 03:13:36 PM PDT, Joseph Reichman > wrote: > > The syslin which the following IMPORT cann't find the DLL CELQV003 > BROWSECEE.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 > BROWSECBC.SCCNPRC(CBCQB) Line 30 Col 001 > 080 > Command ===> Scroll ===> > CSR //BIND EXEC PGM=IEWL,REGION=, > // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,' > //STEPLIB DD DSN=,DISP=SHR > //DD DSN=,DISP=SHR > //SYSLIB DD DSN=,DISP=SHR > //SYSLIN DD DSN=,DISP=SHR > //DD DSN=(CELQSCPP),DISP=SHR > //DD DSN=(CELQS003),DISP=SHR > //DD DSN=(C64),DISP=SHR > //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 > Don Poitras > 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 prog
Re: XL C\C++ missing DLL for fopen
I see fopen in this DLL
ROWSECBC.SCLBDLL2(IOSX64) Li CHARS 'fopen'
found
ommand ===> Scroll ===>
PAGE
d_put__EI7ostreamFc..cout..dbp__EI9streambufFv..dec__Fli..dec__FR3ios..detac
h_
..fclose..fflush..fopen..fprintf..sprintf..sscanf..fgets..fputs..getc..putc.
.u
´Õú[ ..{
...
...´Õú[ ..H ..{
...
...´Õú[...h...-.
..
...´Õú[ ..{´Õú[ ..{
...
´Õú[ ..{
...
... ..H ..{
...
..Ù...-../°..½...±...±...ý}..þ{.
..
..µ...Ì´Õú[...Ø...-.
..
.øÇ...0...Ø.
..
..
, TRAILENUM, TYPEDEFCLASS, NOUCS, VARARGMACROS, NOVARIADICTEMPLATES,
GNU_INCLU
G, NONEWEXCP, OFFSETNONPOD, NOOLDDIGRAPH, OLDFRIEND, NOOLDMATH, NOOLDSTR,
OLDT
XNORETURN, COMPLEXINIT, NOC99LONGLONG, NOC99PREPROCESSOR, C99VLA,
C99__FUNC__,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Don Poitras
Sent: Monday, September 2, 2019 7:23 PM
To: 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 eyecatchers for fopen (and other library routines). The run-time code
is going to be somewhere in there or linked in from bnd2. If your SYSLIN
contains CELQS003 and your SYSLIB contains SCEEBND2, then you shouldn't be
getting a link error from just calling fopen. DLLs don't get linked, they
get loaded and executed at run time. The side deck with the IMPORT
statements is all that needs to be passed to the binder to get successful
output.
In article <005f01d561db$a5de0260$f19a0720$@gmail.com
<mailto:005f01d561db$a5de0260$f19a0720$@gmail.com> > you wrote:
> The syslin which the following IMPORT cann't find the DLL CELQV003
> BROWSECEE.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
> BROWSECBC.SCCNPRC(CBCQB) Line 30 Col 001
> 080
> Command ===> Scroll ===>
> CSR
> //BIND EXEC PGM=IEWL,REGION=,
> // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,'
> //STEPLIB DD DSN=,DISP=SHR
> // DD DSN=,DISP=SHR
> //SYSLIB DD DSN=,DISP=SHR
> //SYSLIN DD DSN=,DISP=SHR
> // DD DSN=(CELQSCPP),DISP=SHR
> // DD DSN=(CELQS003),DISP=SHR
> // DD DSN=(C64),DISP=SHR
> // 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 mailto:IBM-MAIN@LISTSERV.UA.EDU> > On Behalf Of
> Don Poitras
> Sent: Monday, September 2, 2019 6:01 PM
> To: IBM-MAIN@LISTSERV.UA.EDU <mailto: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" 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.SCE
Re: XL C\C++ missing DLL for fopen
These are the error messages or some of them honestly I just went thru every CBC a CEE library and cannt find CELQV003 IEW2322I 1220 8934IMPORT CODE64,'IOSX64','WS__FR7istream' IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fread FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO fopen FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2469E 9907 THE ATTRIBUTES OF A REFERENCE TO malloc FROM SECTION SYSADATA DO NOT MATCH THE ATTRIBUTES OF THE TARGET SYMBOL. REASON 2 IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FOPEN DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD FREAD DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. IEW2439E 9228 THE AMODE OF THE REFERENCING ESD MALLOC DOES NOT MATCH THAT SPECIFIED ON THE IMPORT STATEMENT. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jon Perryman Sent: Monday, September 2, 2019 7:03 PM To: IBM-MAIN@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 are missing the library. Jon. On Monday, September 2, 2019, 03:13:36 PM PDT, Joseph Reichman wrote: The syslin which the following IMPORT cann't find the DLL CELQV003 BROWSECEE.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 BROWSECBC.SCCNPRC(CBCQB) Line 30 Col 001 080 Command ===> Scroll ===> CSR //BIND EXEC PGM=IEWL,REGION=, // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,' //STEPLIB DD DSN=,DISP=SHR //DD DSN=,DISP=SHR //SYSLIB DD DSN=,DISP=SHR //SYSLIN DD DSN=,DISP=SHR //DD DSN=(CELQSCPP),DISP=SHR //DD DSN=(CELQS003),DISP=SHR //DD DSN=(C64),DISP=SHR //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 Don Poitras 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 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 C
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 eyecatchers for fopen (and other library routines). The run-time code is going to be somewhere in there or linked in from bnd2. If your SYSLIN contains CELQS003 and your SYSLIB contains SCEEBND2, then you shouldn't be getting a link error from just calling fopen. DLLs don't get linked, they get loaded and executed at run time. The side deck with the IMPORT statements is all that needs to be passed to the binder to get successful output. In article <005f01d561db$a5de0260$f19a0720$@gmail.com> you wrote: > The syslin which the following IMPORT cann't find the DLL CELQV003 > BROWSECEE.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 > BROWSECBC.SCCNPRC(CBCQB) Line 30 Col 001 > 080 > Command ===> Scroll ===> > CSR > //BIND EXEC PGM=IEWL,REGION=, > // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,' > //STEPLIB DD DSN=,DISP=SHR > // DD DSN=,DISP=SHR > //SYSLIB DD DSN=,DISP=SHR > //SYSLIN DD DSN=,DISP=SHR > // DD DSN=(CELQSCPP),DISP=SHR > // DD DSN=(CELQS003),DISP=SHR > // DD DSN=(C64),DISP=SHR > // 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 > Don Poitras > 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 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 <710f339f-a985-4152-83ca-fb86f440b...@gmail.com> 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 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 > 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 sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 are missing the library. Jon. On Monday, September 2, 2019, 03:13:36 PM PDT, Joseph Reichman 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 30 Col 001 080 Command ===> Scroll ===> CSR //BIND EXEC PGM=IEWL,REGION=, // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,' //STEPLIB DD DSN=,DISP=SHR // DD DSN=,DISP=SHR //SYSLIB DD DSN=,DISP=SHR //SYSLIN DD DSN=,DISP=SHR // DD DSN=(CELQSCPP),DISP=SHR // DD DSN=(CELQS003),DISP=SHR // DD DSN=(C64),DISP=SHR // DD DSN=(IOSX64),DISP=SHR // DD DDNAME=SYSIN //SYSLMOD DD DSN= //SYSDEFSD DD DUMMY //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY -EDIT *DSLIST -Original Message- From: IBM Mainframe Discussion List On Behalf Of Don Poitras 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 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 <710f339f-a985-4152-83ca-fb86f440b...@gmail.com> 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 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 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 sas...@sas.com (919) 531-5637 Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
The syslin which the following IMPORT cann't find the DLL CELQV003 BROWSECEE.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 BROWSECBC.SCCNPRC(CBCQB) Line 30 Col 001 080 Command ===> Scroll ===> CSR //BIND EXEC PGM=IEWL,REGION=, // PARM='MAP,RENT,DYNAM=DLL,CASE=MIXED,' //STEPLIB DD DSN=,DISP=SHR // DD DSN=,DISP=SHR //SYSLIB DD DSN=,DISP=SHR //SYSLIN DD DSN=,DISP=SHR // DD DSN=(CELQSCPP),DISP=SHR // DD DSN=(CELQS003),DISP=SHR // DD DSN=(C64),DISP=SHR // 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 Don Poitras 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 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 <710f339f-a985-4152-83ca-fb86f440b...@gmail.com> 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 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 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 sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 <710f339f-a985-4152-83ca-fb86f440b...@gmail.com> 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 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 > > 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 sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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 Unix was simple for programmers. Instead of complexity being in the OS, Unix relies on the programmer taking care about every minor detail. E..g. security, optimization and much more. How many people realize that a z/OS sysplex is a private cloud without any modifications? IBM has never advertised it as cloud. In Unix, you must enable your code to use cloud services (e.g. SaaS, PaaS, FaaS or ???). >> I would hope that on z/OS, 2GB is sufficient for most programs. >> If not, how are you going to get 1000 users on a single machine? >Virtual Storage? Of course virtual storage. Do the math (1000 * 2GB = 2TB). For Unix, the rule of thumb for paging is 2X ram. 3 X 128GB is 384GB (20%). I haven't been on z/OS in a long time, so I'm guessing. The fortunate thing with z/OS is that you could tell the programmer to use a file and this file could exist in memory or on media appropriate for the application. In Unix, you must change the application to fix it. Jon. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
OT Desktop going pure 64 bit is MAC-OS was Re: XL C\C++ missing DLL for fopen
[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 >> 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. >> >Simpler is better. > >I know a popular desktop system which is discontinuing >support for 32-bit addressing. Gil is referring to MAC-OS. Clark Morris > >>I would hope that on z/OS, 2GB is sufficient for most programs. If not, how >>are you going to get 1000 users on a single machine? >> >Virtual Storage? > >>On Sunday, September 1, 2019, 05:40:06 PM PDT, Joseph Reichman wrote: >> >> I saw thats but all the said he re-did application >> >>Probably told him to go to amode 31 >> >I see in the APAR above: >Problem conclusion >Code has been modified to correct this problem. > >I take that to mean IBM's code, not the customer's code. > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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 > 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 not, how are you going to get 1000 > users on a single machine? > > Jon. > > >On Sunday, September 1, 2019, 05:40:06 PM PDT, Joseph Reichman > 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 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 >> 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 >> >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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. > Simpler is better. I know a popular desktop system which is discontinuing support for 32-bit addressing. >I would hope that on z/OS, 2GB is sufficient for most programs. If not, how >are you going to get 1000 users on a single machine? > Virtual Storage? >On Sunday, September 1, 2019, 05:40:06 PM PDT, Joseph Reichman wrote: > > I saw that’s but all the said he re-did application > >Probably told him to go to amode 31 > I see in the APAR above: Problem conclusion Code has been modified to correct this problem. I take that to mean IBM's code, not the customer's code. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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 not, how are you going to get 1000 users on a single machine? Jon. On Sunday, September 1, 2019, 05:40:06 PM PDT, Joseph Reichman 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 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 > 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 > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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 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 > 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 > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ missing DLL for fopen
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 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
XL C\C++ missing DLL for fopen
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 email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
