Re: Fair comparison C vs HLASM

2018-01-28 Thread Pieter Wiid
Hierarchical databases (IMS) was released in 1968. I suspect IDMS (network DB) was not far behind. Pieter -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Bernd Oppolzer Sent: 28 January 2018 23:47 To: ASSEMBLER-LIST@LISTSERV.UG

Re: Fair comparison C vs HLASM

2018-01-28 Thread Jon Perryman
> Ze'ev wrote: > You basically say "System System on the wall, > please bring me my file" and automagically, your > file appears! (even if it was stored on a third > level storage). You basically cannot implement that in Unix. This is totally possible and easy to create using a virtual file s

Re: Fair comparison C vs HLASM

2018-01-28 Thread Paul Gilmartin
On 2018-01-28, at 18:55:32, Steve Thompson wrote: > On 01/26/2018 10:05 PM, Paul Gilmartin wrote: >> On 2018-01-26, at 19:20:02, Jon Perryman wrote: Paul Gilmartin Wrote: Isn't a PL/X flavor of DCB provided? >>> There may be DCB in PL/X. The DCB has many fields to be filled in. Does >>

Re: Fair comparison C vs HLASM

2018-01-28 Thread Jon Perryman
> Databases were invented in the mid to late 1970s > at IBM (System R, later SQL/DS, later DB2) IMS and Codasyl were invented in 1960's. > the first database systems were implemented in PL/1 on the mainframe Since I've never seen source code, I can't say for sure but I suspect that IMS and D

Re: Fair comparison C vs HLASM

2018-01-28 Thread Steve Thompson
On 01/26/2018 10:05 PM, Paul Gilmartin wrote: On 2018-01-26, at 19:20:02, Jon Perryman wrote: Paul Gilmartin wrote: Is "full functionality of DCB" useful for any OS other than for z/OS? For z/OS, allocate with BPXWDYN or JCL DD statement and open by fopen("//DDN:..." ). BPXWDYN is dynamic al

Re: Fair comparison C vs HLASM

2018-01-28 Thread Ze'ev Atlas
Jon wrote:MVS programmers are in awe when they hear about these Unix features and will quickly tell a Unix programmer they wish they had that (e.g. createfile). So let me add my two cents to the discussion:In Unix (and Windows,) you have to know where is your file.  In MVS, utilizing system cat

Re: Fair comparison C vs HLASM

2018-01-28 Thread Jon Perryman
>>> Eric Chavalier wrote: Going even further, many platforms allow a file to be >>> mapped into an >>>application's address space. I work with an unmanaged C++ Windows >>>application that does CreateFile() to open a file, >> Binyamin Dissen wrote: You are referring to a LDS. > Paul Raulerson

Re: Fair comparison C vs HLASM

2018-01-28 Thread Eric Chevalier
On 1/28/18 2:31 PM, Seymour J Metz wrote: "fstat() the image file to get its size" What if it isn't an image file, or any other kind of DASD file. Unix has other kinds of files for which there is no way to know the size a priori. Pedantically speaking, you're correct. However, I don't lose any

Re: Fair comparison C vs HLASM

2018-01-28 Thread Bernd Oppolzer
Sorry, but you are mixing up things in a somehow a-historic manner, which needs some corrections: Databases were invented in the mid to late 1970s at IBM (System R, later SQL/DS, later DB2), and the first database systems were implemented in PL/1 on the mainframe, and this has nothing to do with

Re: Fair comparison C vs HLASM

2018-01-28 Thread Seymour J Metz
"Does DCB provide functionality not available via DYNALLOC?" Apples and oranges; they do different things. Don't confuse the DCB macro with things that override DCB parameters. The DCB macro certainly has options that are not relevant to JCL or to dynamic allocation, whether via DAIR, via BPXWDY

Re: Fair comparison C vs HLASM

2018-01-28 Thread Seymour J Metz
"fstat() the image file to get its size" What if it isn't an image file, or any other kind of DASD file. Unix has other kinds of files for which there is no way to know the size a priori. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IB

Re: Fair comparison C vs HLASM

2018-01-28 Thread Jon Perryman
> Paul Raulerson wrote: > This is a funny area to compare though, since on most platforms, > C file > access is always a binary stream. The application pretty > much defines the > way the file is treated - byte by byte, > record by record, block by block, > buffer size by buffer > size, etc. To

Re: Fair comparison C vs HLASM

2018-01-28 Thread Paul Raulerson
Like a Master Catalog? Yep- same kind of idea. More widely used under *nix I think. Typos courtesy of my iPhone and my fat fingers! > On Jan 28, 2018, at 12:53, Binyamin Dissen wrote: > ... ... ... > You are referring to a LDS. > > -- > Binyamin Dissen > http://www.dissensoftware.com > >

Re: Fair comparison C vs HLASM

2018-01-28 Thread Binyamin Dissen
On Sun, 28 Jan 2018 09:40:55 -0700 Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: :>On 2018-01-27, at 13:03:48, Binyamin Dissen wrote: :>> On Sat, 27 Jan 2018 05:13:36 + Jon Perryman wrote: :>> :>On Friday, January 26, 2018 7:05 PM, Paul Gilmartin wrote: :>> :>> P

Re: Fair comparison C vs HLASM

2018-01-28 Thread Binyamin Dissen
On Sun, 28 Jan 2018 10:16:51 -0600 Eric Chevalier wrote: :>On 1/28/18 12:35 AM, Paul Raulerson wrote: :>> This is a funny area to compare though, since on most platforms, C :>> file access is always a binary stream. The application pretty much :>> defines the way the file is treated - byte by b

Re: Fair comparison C vs HLASM

2018-01-28 Thread Paul Gilmartin
On 2018-01-27, at 13:03:48, Binyamin Dissen wrote: > On Sat, 27 Jan 2018 05:13:36 + Jon Perryman wrote: > > :>On Friday, January 26, 2018 7:05 PM, Paul Gilmartin wrote: > > :>> Paul wrote: Does DCB provide functionality not available via DYNALLOC? > :>DCB is all about the program. There are

Re: Fair comparison C vs HLASM

2018-01-28 Thread Eric Chevalier
On 1/28/18 12:35 AM, Paul Raulerson wrote: This is a funny area to compare though, since on most platforms, C file access is always a binary stream. The application pretty much defines the way the file is treated - byte by byte, record by record, block by block, buffer size by buffer size, etc.