Re: IEW2606S Doing C Programming

2005-06-07 Thread Big Iron
I went and RTFMed (C/C++ Runtime Library Reference) since my memory obviously needed refreshing; I found this note: If you cannot use a PDSE member or HFS file, and your program contains C++ code, or C code that is compiled with any of the RENT, LONGNAME, DLL or IPA compiler options, you must

Re: IEW2606S Doing C Programming

2005-06-04 Thread Paul Gilmartin
In a recent note, Robert Pelletier said: Date: Fri, 3 Jun 2005 16:01:56 -0400 Thanks for the quick response John. We don't use PDSE's either. Should be fun. Have a good weekend all. You should, then, consider the alternative big jump: HFS instead of PDSE. -Original

Re: IEW2606S Doing C Programming

2005-06-04 Thread Paul Gilmartin
In a recent note, Schiradin,Roland HG-Dir itb-db/dc said: Date: Fri, 3 Jun 2005 23:48:03 +0200 Unfortunally the process for the internal compress is a bit hidden to me. I had thought there is no compress. Space vacated by deleted members is simply recycled for new members; existing

Re: IEW2606S Doing C Programming

2005-06-04 Thread john gilmore
Paul Gilmartin writes You should, then, consider the alternative big jump: HFS instead of PDSE. This is good advice iff the C or C++ programs (functions) involved are to be executed under USS. It is very bad advice if they arre instead to be executed undrer MVS (which I suspect to be

Re: IEW2606S Doing C Programming

2005-06-04 Thread Edward E. Jaffe
Paul Gilmartin wrote: ... PDSE implies SMS implies ... IIRC, non-SMS-managed PDSE became generally available March 31, 2000 with OS/390 V2R9. -- - | Edward E. Jaffe|| | Mgr,

Re: IEW2606S Doing C Programming

2005-06-04 Thread Paul Gilmartin
In a recent note, john gilmore said: Date: Sat, 4 Jun 2005 14:44:04 + You should, then, consider the alternative big jump: HFS instead of PDSE. This is good advice iff the C or C++ programs (functions) involved are to be executed under USS. It is very bad advice if they

Re: IEW2606S Doing C Programming

2005-06-04 Thread Paul Gilmartin
In a recent note, Big Iron said: Date: Fri, 3 Jun 2005 16:02:37 -0500 There are also some binder options: COMPAT, CASE=MIXED, LONGNAME or DLL which can force the use of program objects. I couldn't resist trying this: //DOIT EXEC HLASMCL,PARM.C=(OBJECT,NOXOBJECT,TERM),

Re: IEW2606S Doing C Programming

2005-06-04 Thread Craddock, Chris
Edward E. Jaffe wrote: Paul Gilmartin wrote: ... PDSE implies SMS implies ... IIRC, non-SMS-managed PDSE became generally available March 31, 2000 with OS/390 V2R9. True enough and at the same time non-SMS PDSE support was retrofitted all the way back to OS/390 V2R5. But hardly

Re: IEW2606S Doing C Programming

2005-06-04 Thread Schiradin,Roland HG-Dir itb-db/dc
: IEW2606S Doing C Programming In a recent note, Schiradin,Roland HG-Dir itb-db/dc said: Date: Fri, 3 Jun 2005 23:48:03 +0200 Unfortunally the process for the internal compress is a bit hidden to me. I had thought there is no compress. Space vacated by deleted members is simply

IEW2606S Doing C Programming

2005-06-03 Thread Robert Pelletier
Hi All. I'm trying to save the compiled 'c' code to a loadlib and I'm getting the following error in my jcl during the bind process: IEW2606S 4B39 MODULE INCORPORATES PROGRAM MANAGEMENT 3 FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT. Would anyone no what is going on? This is the fisrt

Re: IEW2606S Doing C Programming

2005-06-03 Thread McKown, John
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: Friday, June 03, 2005 2:58 PM To: IBM-MAIN@BAMA.UA.EDU Subject: IEW2606S Doing C Programming Hi All. I'm trying to save the compiled 'c' code to a loadlib

Re: IEW2606S Doing C Programming

2005-06-03 Thread Bob Shannon
Hi All. I'm trying to save the compiled 'c' code to a loadlib and I'm getting the following error in my jcl during the bind process: IEW2606S 4B39 MODULE INCORPORATES PROGRAM MANAGEMENT 3 FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT. Your library needs to be a PDSE. Bob Shannon

Re: IEW2606S Doing C Programming

2005-06-03 Thread Robert Pelletier
Thanks for the quick response John. We don't use PDSE's either. Should be fun. Have a good weekend all. -Original Message- From: McKown, John [mailto:[EMAIL PROTECTED] Sent: Friday, June 03, 2005 4:00 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: IEW2606S Doing C Programming -Original

Re: IEW2606S Doing C Programming

2005-06-03 Thread Bruce Black
I was going to gently suggest to Bob that he RTFM, but I checked the 1.6 FM myself and find that the message description doesn't help much. *IEW2606S* *MODULE* *INCORPORATES* feature_level *FEATURES* *AND* *CANNOT* *BE* *SAVED* *IN* format_level *FORMAT.* *Explanation:* An attempt

Re: IEW2606S Doing C Programming

2005-06-03 Thread Robert Pelletier
Thanks Bruce and everyone. Really appreciate it again. Bob -Original Message- From: Bruce Black [mailto:[EMAIL PROTECTED] Sent: Friday, June 03, 2005 4:17 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: IEW2606S Doing C Programming I was going to gently suggest to Bob that he RTFM, but I

Re: IEW2606S Doing C Programming

2005-06-03 Thread Jeffrey D. Smith
I think it means you must save into a PDSE as a program object, instead of a PDS as a load module. Anyone know for sure? -Original Message- From: Robert Pelletier [EMAIL PROTECTED] Sent: 6/3/2005 1:58 PM To: IBM-MAIN@BAMA.UA.EDU IBM-MAIN@BAMA.UA.EDU Subject: IEW2606S Doing C Programming

Re: IEW2606S Doing C Programming

2005-06-03 Thread Farley, Peter x23353
(the other permitted repository for program objects). HTH Peter -Original Message- From: Robert Pelletier [mailto:[EMAIL PROTECTED] Sent: Friday, June 03, 2005 4:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: IEW2606S Doing C Programming Thanks Bruce and everyone. Really appreciate

Re: IEW2606S Doing C Programming

2005-06-03 Thread Big Iron
- From: Robert Pelletier [mailto:[EMAIL PROTECTED] Sent: Friday, June 03, 2005 4:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: IEW2606S Doing C Programming Thanks Bruce and everyone. Really appreciate it again. Bob -Original Message- From: Bruce Black [mailto:[EMAIL PROTECTED] Sent: Friday