Re: Compile error and also possible library bug with Metal/C metal.h

Another problem you have is you're not calling __cinit() [1] to initialize the Metal/C environment so the call to malloc() will fail as no heap has been created. You really must *always* check malloc() even in a test driver. [1]

Re: Compile error and also possible library bug with Metal/C metal.h

: 630.325.6137 > M: 630.660.8040 > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Joe Monk > Sent: Monday, January 11, 2021 6:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Compile error and also possible library bug with Metal/C > met

Re: Compile error and also possible library bug with Metal/C metal.h

-Original Message- From: IBM Mainframe Discussion List On Behalf Of Joe Monk Sent: Monday, January 11, 2021 6:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error and also possible library bug with Metal/C metal.h "I'd be perfectly happy for someone to tell me I missed some ob

Re: Compile error and also possible library bug with Metal/C metal.h

"I'd be perfectly happy for someone to tell me I missed some obvious compiler option or did something else really stupid." Found this on another website ... The issue was with the search order. Although I did search(/usr/metal/include) from with in my JCL I didn't proceed it with a nosearch

Re: Compile error and also possible library bug with Metal/C metal.h

ssion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Don Poitras Sent: Monday, January 11, 2021 3:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error and also possible library bug with Metal/C metal.h I've never used Metal C, but for the first problem (undeclared __MEMSET), I would l

Re: Compile error and also possible library bug with Metal/C metal.h

I've never used Metal C, but for the first problem (undeclared __MEMSET), I would look to see if there's a string.h that can be used. That's normally where memcmp is defined. As for the runtime problem, I'd guess it had something to do with using 'sizeof' incorrectly. It looks as if you are

Compile error and also possible library bug with Metal/C metal.h

I'm a developer working with a client to develop Metal C functions for their products. Up until recently I've defined __METAL_STATIC and linked with SCCR3BND. I decided recently to play with the dynamic library in LPALIB so I removed that #define. What I'm getting is compile errors on the

Re: Compile error

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Mike Schwab > Sent: Friday, January 22, 2016 12:32 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Compile error > > On Fri, Jan 22, 2016 at 11:54 AM, Gib

Re: Compile error

On Fri, Jan 22, 2016 at 11:54 AM, Gibney, David Allen,Jr wrote: > I've never worked with JES3. What does it offer in "disk and tape control" > that DFSMS doesn't? Or, are we talking a different kind of control? It doesn't start until the dataset names / tape volumes are not in

Re: Compile error

I ran OS/VS1 on a 4341 and later I think on a 4381. We also ran VM, OS/VS1 had a VM "Assist" mode where it didn't page, but let VM page for it. I think OS/VS1 ran JES, just JES, no 2 or 3 after it, but it looked a lot like JES2.

Re: Compile error

Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of McCabe, Ron Sent: Friday, January 22, 2016 11:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error So where does DL1 fit in? Ron McCabe Mutual of Enumclaw -Original Message- From: IBM Mainframe Discussion List [

Re: Compile error

jo.skip.robin...@att.net (Skip Robinson) writes: > The name 'DB2' seems to have followed the 1980s tradition of what I call > 'name bloat', the practice of inflating a moniker in one way or another to > make a product look more mature or more elegant. The paragon in my mind was > dBASE II from

Re: Compile error

other trivia from ibm jargon: MVM - n. Multiple Virtual Memory. The original name for MVS (q.v.), which fell foul of the fashion of changing memory to storage. MVS - n. Multiple Virtual Storage, an alternate name for OS/VS2 (Release 2), and hence a direct descendent of OS. OS/VS2 (Release 1) was

Re: Compile error

I need Volume X" but another job is current using it issues. IOW: It insures that once a job is allowed to start, there will be no delays to gain access to the devices and files it needs. At 17:54 + on 01/22/2016, Gibney, David Allen,Jr wrote about Re: Compile error: I've never worked

Re: Compile error

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error: There never was a plain old 'JES'. I thought the spooling subsystem in OS/VS1 was called JES. -- For IBM-MAIN subscribe / signoff / archive access

Re: Compile error

apter with its own title (which often reflected the cliffhanger being resolved or the plot point of that chapter). At 09:57 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error: It's Friday, right? After the release of Mel Brooks' History of the World Part I, he was often asked when we

Re: Compile error

In the opening crawl for the original release of Star Wars not only did not say "A New Hope", it also did not say Episode IV. See it here: https://www.youtube.com/watch?v=UKRIUiyF0N4 Frank > Date: Fri, 22 Jan 2016 16:52:01 -0500 > From: hal9...@panix.com > Subject: Re: Comp

Re: Compile error

Meanwhile there did emerge a 'JES3', but it was not an evolutionary descendant of JES2. Both products have coexisted, albeit uneasily, for decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic proclivity) that would somehow combine the best features of both products, but

Re: Compile error

] On Behalf Of Skip Robinson Sent: Friday, January 22, 2016 10:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error The name 'DB2' seems to have followed the 1980s tradition of what I call 'name bloat', the practice of inflating a moniker in one way or another to make a product look more

Re: Compile error

to:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Anne & Lynn Wheeler > Sent: Thursday, January 21, 2016 10:53 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Compile error > > thomas.sa...@fiserv.com (Savor, Thomas , Alpharetta) writes: > > Management System or DBMS in

Re: Compile error

JES2 was a half ASP project, just a little play on words :) --- jo.skip.robin...@att.net wrote: From: Skip Robinson <jo.skip.robin...@att.net> To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error Date: Fri, 22 Jan 2016 08:50:43 -0800 The name 'DB2' seems t

Re: Compile error

M-MAIN@LISTSERV.UA.EDU] > On Behalf Of Staller, Allan > Sent: Friday, January 22, 2016 09:02 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Compile error > > > Meanwhile there did emerge a 'JES3', but it was not an evolutionary > descendant of JES2. Both products h

Re: Compile error

So where does DL1 fit in? Ron McCabe Mutual of Enumclaw -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Friday, January 22, 2016 9:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error Probably just an old

Re: Compile error

Sent: Friday, January 22, 2016 9:45 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Compile error > > As we saw in the recent thread on converting from JES3 to JES2, JES3 from the > beginning provided function--especially in the area of data device control-- > that was neve

Re: Compile error

...@gmail.com > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Pommier, Rex > Sent: Friday, January 22, 2016 09:05 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Compile error > > Probably just

Re: Compile error

hal9...@panix.com (Robert A. Rosenberg) writes: > And then there was Star Wars (AKA: A New Hope [which was added when > the film was rereleased as part of the release of The Empire Strikes > Back]) which opened with a crawl saying Episode 4". That was just > because they were emulating the old

Re: Compile error

From: Robert A. Rosenberg There never was a plain old 'JES'. "I thought the spooling subsystem in OS/VS1 was called JES." You are correct: JES Did that (VS1/JES) through a lot of of the '70's. Then VS1 under VM, then SVS, then DOS, VS1, and MVS under VM (different place), then finally MVS.

Re: Compile error

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error: There never was a plain old 'JES'. "I thought the spooling subsystem in OS/VS1 was called JES." You are correct: JES (for VS1). Through most of the '70's did VS1, VS1 under VM/370, SVS, then at a diffe

Re: Compile error

. . . "But others have pointed out that hex literals were not allowed in the OS/VS compiler, so this particular combination of source and JCL could never have worked. " For clarity: The problem code was almost certainly inserted by the DB2 pre-compiler. With a level of DB2 contemporary with

Re: Compile error

ements were probably compatible with then-existing COBOL. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc Sent: Thursday, January 21, 2016 3:10 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error On 21 January

Re: Compile error

On 21 January 2016 at 12:31, Chris Bowen wrote: > For clarity: > The problem code was almost certainly inserted by the DB2 pre-compiler. With > a level of DB2 contemporary > with the COBOL compiler it would have worked - different code would have been > inserted. The

Re: Compile error

>"The name DB2, or IBM Database 2, was first given to the Database Management >System or DBMS in 1983 when IBM >released DB2 on its MVS mainframe platform." >-- Wikipedia, citing an IBM manual as authority. All these years, I've have only known of DB2. The name seems to have stuck. Was

Re: Compile error

thomas.sa...@fiserv.com (Savor, Thomas , Alpharetta) writes: > Management System or DBMS in 1983 when IBM >released DB2 on its MVS > mainframe platform." -- Wikipedia, citing an IBM manual as authority. > > All these years, I've have only known of DB2. The name seems to have stuck. > > Was

Re: Compile error

W dniu 2016-01-20 o 03:11, Dale R. Smith pisze: On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills wrote: "(c) International Business Machines Corporation 1974, 1976, 1981" 35 to 42 years old! Charles The last supported release of the OS/VS COBOL Compiler and Library was

Re: Compile error

On Behalf Of Pinnacle > Sent: Tuesday, January 19, 2016 12:14 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Compile error > > On 1/19/2016 1:58 PM, Ron Thomas wrote: > > I looked at the endevor processor group setting and it is showing the > program that is used is

Re: Compile error

DU Subject: Re: Compile error On 1/19/2016 1:58 PM, Ron Thomas wrote: > I looked at the endevor processor group setting and it is showing the program > that is used is PGM=IKFCBL00. is this won't work ? Thanks! > > -- &g

Re: Compile error

On 19 Jan 2016 07:23:57 -0800, in bit.listserv.ibm-main Ron Thomas wrote: As others have pointed out the IKF messages are from an OS/VS compiler (or another compiler set to the OS/VS mode). This compiler does not recognize hexadecimal values. I'm surprised it isn't complaining about the COMP-4

Re: Compile error

Let me also suggest you do not use the stand-alone external DB2 translator, but use the SQL compiler option. Then any errors will be included in-line and it will be easier to debug. Likewise the CICS compiler option vs the translator. Also today, all the DB2 artifacts are GLOBAL such as the

Re: Compile error

ERV.UA.EDU Subject: Re: Compile error It has been so long since I had a VS COBOL Manual, I did not recognize it. So it seems what everyone is saying is Fix would be to use a more current compiler. Lizette -Original Message- >From: Pinnacle <pinnc...@rochester.rr.com> >Sent:

Re: Compile error

I looked at the endevor processor group setting and it is showing the program that is used is PGM=IKFCBL00. is this won't work ? Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Compile error

On 1/19/2016 10:23 AM, Ron Thomas wrote: Hello We are trying to compile a very old cobol/db2 program and getting the below error . Could someone let me know how to get this fixed ? 00210 77 SQL-TEMP PIC X(128). 00211 77 DSN-TEMP PIC S9(9) COMP-4. 00212

Re: Compile error

Correct. That's a very old COBOL compiler. Today's compiler is IGYCRCTL. On Tue, Jan 19, 2016 at 12:58 PM, Ron Thomas wrote: > I looked at the endevor processor group setting and it is showing the > program that is used is PGM=IKFCBL00. is this won't work ? Thanks! > >

Re: Compile error

. If someone *really* needs to know I know where I can look it up. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Tuesday, January 19, 2016 10:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error I looked

Re: Compile error

gt;To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Compile error > >On 1/19/2016 10:23 AM, Ron Thomas wrote: >> Hello >> >> We are trying to compile a very old cobol/db2 program and getting the below >> error . Could someone let me know how to get this fixed ? >> &g

Re: Compile error

On 1/19/2016 1:58 PM, Ron Thomas wrote: I looked at the endevor processor group setting and it is showing the program that is used is PGM=IKFCBL00. is this won't work ? Thanks! -- For IBM-MAIN subscribe / signoff / archive

Re: Compile error

PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Compile error On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills <charl...@mcn.org> wrote: >"(c) International Business Machines Corporation 1974, 1976, 1981" > >35 to 42 years old! > >Charles The last supported releas

Re: Compile error

On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills wrote: >"(c) International Business Machines Corporation 1974, 1976, 1981" > >35 to 42 years old! > >Charles The last supported release of the OS/VS COBOL Compiler and Library was V1.2.4. It was withdrawn from marketing in

Re: Compile error

On Jan 19, 2016, at 8:11 PM, Dale R. Smith wrote: On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills wrote: "(c) International Business Machines Corporation 1974, 1976, 1981" 35 to 42 years old! Charles The last supported release of the OS/VS COBOL Compiler and Library

Compile error

Hello We are trying to compile a very old cobol/db2 program and getting the below error . Could someone let me know how to get this fixed ? 00210 77 SQL-TEMP PIC X(128). 00211 77 DSN-TEMP PIC S9(9) COMP-4. 00212 77 DSN-TMP2 PIC S9(18) COMP-3. 00213

Re: Compile error

M-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Tuesday, January 19, 2016 8:24 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Compile error > > Hello > > We are trying to compile a very old cobol/db2 program and getting the below > error . Could someone let me know h

Re: Compile error

What compiler are you using? The code looks OK for a _modern_ COBOL compiler. I.e. for Enterprise COBOL (IGYCRCTL), but not for the older IKJCBL00 compiler. The older compiler did not have hex literals. eg: X'00' On Tue, Jan 19, 2016 at 9:24 AM, Ron Thomas wrote: > Hello > >

Re: Compile error

: Compile error What platform are you running this on? This does not appear to be COBOL compiler on z/OS An internet search on IKF1017I appears to be Hercules390 compiler? z/OS Cobol is IGY typically. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mail

Re: PL/I Compile error unresolved symbols

Like others already mentioned, to get rid of the syntax errors, you will have to add a declaration like DCL P PTR; and you should remove STR from the DCL ... BUILTIN; But another idea or question: the program IMO tries to read some DBRMs (DB2 data base request modules), extract some

Re: PL/I Compile error unresolved symbols

In cajtoo59q4_cypgbcmo0qjpeeovbcqfhjsihomjoqcjiu6a2...@mail.gmail.com, on 09/29/2012 at 10:42 AM, Mike Schwab mike.a.sch...@gmail.com said: Looks like there is some missing code in LOAD_DIR: PROC; This is routine to read a PDS directory, and P is an pointer within the directory block. But I

Re: PL/I Compile error unresolved symbols

Yes, the UNSPEC construct is at once labored and surpassingly ugly. I'm not located on this Sunday morning where I can conveniently chase down when exactly the bif POINTERADD was added to the language, but even without it one can do pointer arithmetic perspicuously using constructs of the form

Re: PL/I Compile error unresolved symbols

- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Cifani, Domenic Sent: Friday, September 28, 2012 1:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PL/I Compile error unresolved symbols Hi I have a user running PL/I implementation in Endevor, and the PL/1

Re: PL/I Compile error unresolved symbols

this compile? No source changes were made. Thanks Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Cifani, Domenic Sent: Friday, September 28, 2012 1:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PL/I Compile error unresolved

Re: PL/I Compile error unresolved symbols

-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I Compile error unresolved symbols On 28 September 2012 16:13, Cifani, Domenic domenic.cif...@hp.com wrote: I have a user running PL/I implementation in Endevor, and the PL/1 compile step has a return code=008. I don't have much experience with this, does

Re: PL/I Compile error unresolved symbols

Here is the library page for Enterprise PL/I http://www-01.ibm.com/software/awdtools/pli/plizos/library/ The Compiler and Run time migration books should contain what changes you need between versions. There is a DCL STR BUILTIN, but it is not actually refered to by anything. You can remove it.

Re: PL/I Compile error unresolved symbols

-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Comstock Sent: Friday, September 28, 2012 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I Compile error unresolved symbols On 9/28/2012 2:13 PM, Cifani, Domenic wrote: Hi

Re: PL/I Compile error unresolved symbols

On 9/28/2012 3:29 PM, John Gilmore wrote: I will not repeat the good advice you have already been given, but I do want to add that the error message IBM1058I I 239.0Conversion from BIT to FIXED BIN(31) will be done by library call. should receive your