Re: IBM C header files

2009-10-20 Thread Don Poitras
des...@verizon.net wrote: sas...@sas.com (Don Poitras) writes: Try: #include sys/types.h If you look inside the EDC4H031 member, you see this as the comment. * sys/types.h header file Note that to get hold of something in sys/ you really should not be defining the location

Re: IBM C header files

2009-10-20 Thread David Waldman
On Tue, 20 Oct 2009 08:47:51 -0400, Don Poitras sas...@sas.com wrote: des...@verizon.net wrote: sas...@sas.com (Don Poitras) writes: Try: #include sys/types.h If you look inside the EDC4H031 member, you see this as the comment. * sys/types.h header file Note that to get hold of

Re: IBM C header files

2009-10-20 Thread Don Poitras
David Waldman wrote: On Tue, 20 Oct 2009 08:47:51 -0400, Don Poitras sas...@sas.com wrote: des...@verizon.net wrote: sas...@sas.com (Don Poitras) writes: Try: #include sys/types.h If you look inside the EDC4H031 member, you see this as the comment. * sys/types.h

Re: IBM C header files

2009-10-20 Thread Kirk Wolf
FWIW, we do alot of C/C++ development on z/OS, and find it *much* easier to put source files and a Makefile in a zFS filesystem and then use make to build everything from a z/OS Unix shell. You can still target your load modules to a PDS or PDS/E when running the compiler and/or linker from the

Re: IBM C header files

2009-10-20 Thread Paul Gilmartin
On Tue, 20 Oct 2009 14:48:00 -0500, Kirk Wolf wrote: FWIW, we do alot of C/C++ development on z/OS, and find it *much* easier to put source files and a Makefile in a zFS filesystem and then use make to build everything from a z/OS Unix shell. You can still target your load modules to a PDS or

Re: IBM C header files

2009-10-19 Thread Don Poitras
Try: #include sys/types.h If you look inside the EDC4H031 member, you see this as the comment. * sys/types.h header file TYPES is an alias of EDC4H031. Sometimes it's easier to grep for symbols in the UFS location. /usr/include: pwd /usr/include /usr/include: find . -name '*.h' | xargs

Re: IBM C header files

2009-10-19 Thread Henry Willard
Pierre Fichaud wrote: Folks, I've been hired to implement SSL socket calls in an existing z/OS product. The IBM SSL API is in C. I'm changing the TCB structure to have 2 listeners, one TCP/IP and the other SSL. They listen on different ports. I've added a TCB layer and so

Re: IBM C header files

2009-10-19 Thread Kirk Wolf
What about using AT-TLS? On Mon, Oct 19, 2009 at 1:57 PM, Henry Willard hwill...@megapathdsl.netwrote: Pierre Fichaud wrote: Folks, I've been hired to implement SSL socket calls in an existing z/OS product. The IBM SSL API is in C. I'm changing the TCB structure to have 2