Re: C++ fstream, iostream and z/OS

2009-12-20 Thread Shmuel Metz (Seymour J.)
In 053f2631ec9c584883847c8b4970a228059dc...@josqems1.jsq.bsg.ad.adp.com, on 12/19/2009 at 12:52 PM, Farley, Peter x23353 peter.far...@broadridge.com said: Small rant Why oh why didn't they ever write QPAM? Nobody wrote up a business case that they found compelling. Or internal politics.

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Bernd Oppolzer
If it helps: you can open a PDS or PDSE without a member name using fopen () in binary mode and read the directory. After having read the member names, you can fopen the individual members, if you want. Kind regards Bernd David Stephens schrieb: There's no doubt that z/OS specific functions

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Charles Mills
...@bama.ua.edu] On Behalf Of Bernd Oppolzer Sent: Saturday, December 19, 2009 6:17 AM To: IBM-MAIN@bama.ua.edu Subject: Re: C++ fstream, iostream and z/OS If it helps: you can open a PDS or PDSE without a member name using fopen () in binary mode and read the directory. After having read the member

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Farley, Peter x23353
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: Saturday, December 19, 2009 8:18 AM To: IBM-MAIN@bama.ua.edu Subject: Re: C++ fstream, iostream and z/OS Snipped write an assembler program with FIND, then call

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Ted MacNEIL
I find it really amusing that IBM simulated a PDS directory for a PDSE. Why would this be amusing. PDSE is supposed to be compatable/transparent to applications. So, how would they do that without simulating a PDS directory? - Too busy driving to stop for gas!

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Paul Gilmartin
On Sat, 19 Dec 2009 14:29:24 +, Ted MacNEIL wrote: I find it really amusing that IBM simulated a PDS directory for a PDSE. Why would this be amusing. PDSE is supposed to be compatable/transparent to applications. In that case, any number of readers of this forum can tell you how widely they

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Charles Mills
blocks that are not there. But if you are not amused, that's okay too. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Saturday, December 19, 2009 9:29 AM To: IBM-MAIN@bama.ua.edu Subject: Re: C++ fstream, iostream and z

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Charles Mills
and deblocking and ... (correct me if I'm wrong). Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Farley, Peter x23353 Sent: Saturday, December 19, 2009 9:01 AM To: IBM-MAIN@bama.ua.edu Subject: Re: C++ fstream, iostream and z/OS

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Paul Gilmartin
On Sat, 19 Dec 2009 11:25:29 -0500, Charles Mills wrote: Well, we can debate all day what is or is not amusing, but I am not sure reading the 256-byte directory blocks was a supported programming interface, so if it had gone away I don't think anyone could have screamed not compatible. My

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Farley, Peter x23353
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: Saturday, December 19, 2009 11:35 AM To: IBM-MAIN@bama.ua.edu Subject: Re: C++ fstream, iostream and z/OS Thanks. That's a good thought. Yes, first sentence

Re: C++ fstream, iostream and z/OS

2009-12-19 Thread Ted MacNEIL
PDSE is supposed to be compatable/transparent to applications. In that case, any number of readers of this forum can tell you how widely they missed the mark. Yes, I've btdt many times. Especially since the introduction of non-SMS-Managed PDSE's. My point was: of course PDSE is going to

C++ fstream, iostream and z/OS

2009-12-18 Thread Charles Mills
Does anyone know of one lick of documentation *specific to z/OS* for the subject C++ classes? The words DD and PDS, for example, do not appear anywhere in IBM z/OS Standard C++ Library Reference. (Well, DD does appear in the context of date formats.) I don't see one word on the filename formats

Re: C++ fstream, iostream and z/OS

2009-12-18 Thread Tony Harminc
2009/12/18 Charles Mills charl...@mcn.org: Does anyone know of one lick of documentation *specific to z/OS* for the subject C++ classes? The words DD and PDS, for example, do not appear anywhere in IBM z/OS Standard C++ Library Reference. (Well, DD does appear in the context of date formats.)

Re: C++ fstream, iostream and z/OS

2009-12-18 Thread Sam Siegel
The IBM z/OS Standard C++ Library Reference. documents the STL and other industry standard C++ functions. It does not document (to my examination) any IBM specific facilities. Sam On Fri, Dec 18, 2009 at 8:37 PM, Tony Harminc t...@harminc.net wrote: 2009/12/18 Charles Mills charl...@mcn.org:

Re: C++ fstream, iostream and z/OS

2009-12-18 Thread Charles Mills
: Re: C++ fstream, iostream and z/OS 2009/12/18 Charles Mills charl...@mcn.org: Does anyone know of one lick of documentation *specific to z/OS* for the subject C++ classes? The words DD and PDS, for example, do not appear anywhere in IBM z/OS Standard C++ Library Reference. (Well, DD does appear

Re: C++ fstream, iostream and z/OS

2009-12-18 Thread David Stephens
There's no doubt that z/OS specific functions aren't documented that well, but the Run-Time Library Reference is where it all is. Functions are for both C and C++. It includes some z/OS specific functions like __cabend (abend a process) and _malloc24 (getmain storage below the line), but you