I'm making a first attempt at C code on z/OS and I'm having trouble making
the compiler work the way I understand it should from the manual. This is
such a basic function and it fails so miserably I'm sure this is some sort
of setup misunderstanding.
The problem is that the compiler is not locati
http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.cbcux01%2Fcbcug19023.htm
On Fri, Mar 28, 2014 at 12:19 PM, Chuck Arney wrote:
> I'm making a first attempt at C code on z/OS and I'm having trouble making
> the compiler work the way I understand it should from the m
On Fri, 28 Mar 2014 12:19:33 -0500, Chuck Arney wrote:
>...
>JCL snippet:
>...
>What am I missing?
>
You shouldn't use JCL with C. You're just torturing yourself.
-- gil
--
For IBM-MAIN subscribe / signoff / archive acc
Yeah, like using spell checkThere's gobs of samples, do they work?
In a message dated 3/28/2014 6:21:18 P.M. Central Daylight Time,
paulgboul...@aim.com writes:
You're just torturing yourself.
--
For IBM-MAIN subscr
Chuck:
Heres how I do it:
//ADCDMETA JOB SYSTEMS,MSGLEVEL=(1,1),MSGCLASS=X,CLASS=A,PRTY=8,
// NOTIFY=&SYSUID,REGION=0M
// EXEC EDCCL,
// INFILE='SFORD.C.SOURCE(SUBPCHK)',
// OUTFILE='SFORD.TEST.LINKLIB(SUBPCHK),DISP=SHR',
// CPARM='LIS,SO,EXP,DEF(MVS)',
// CPARM2='NOMARGINS,LOCA
Chuck,
Best to leave SEARCH alone unless you've customized the installation. It
will default to SEARCH(//'CEE.SCEEH.+') which will pick up all the
header file data sets.
I see that you are trying to include C++ iostream headers. If you want
to compile C++ then you should take a look at the J
On Sat, 29 Mar 2014 08:08:06 +0800, David Crayford wrote:
>
>IMO, it's much easier to build C/C++ programs in the z/OS UNIX shell.
>You can then take advantage of other tools like makefiles. It's possible
>to build programs that reside in PDS(E) libraries from z/OS UNIX.
>
Yes, but dammit! When w
I can only speak for C, we don't have C++ at our site.
So I would ask you to try the #include first and leave out
the #include for the beginning, because that is a C++ header
which you will not be able to use in a C program.
We allocate for USERLIB exactly the same DD chain as for SYSLIB.
The
On Fri, 28 Mar 2014 12:19:33 -0500, Chuck Arney wrote:
>The problem is that the compiler is not locating the header files that are
>included in the source program. My understanding from the manual is that
>the compiler PARM SEARCH controls the library search sequence used for
>system headers and
Like Bernd, I only speak C and some C# on Windows..no C++, not yet.
Regards,
Scott
From: Bernd Oppolzer
Sent: Saturday, March 29, 2014 6:18 AM
To: IBM Mainframe Discussion List
I can only speak for C, we don't have C++ at our site.
So I would ask you to try the #include
http://www.facebook.com/arneycomputer
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Phil Sidler
Sent: Sunday, March 30, 2014 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C Compiler Library Search
On Fri, 28 Mar 2014 12:19:33
11 matches
Mail list logo