Re: Who is Glenn Henry?

["Keith Carpenter" <CarpCon@xxxxxxx>]

Actually, the S/38 preceeded both the S/36 and DB2.

Because the S/38 didn't prove to be a popular replacement for the S/34, the
S/36 was introduced to fill the gap.  On the upper end, it competed with the
small 4300s

Early CPF releases did not have join LFs or OPNQRYF.  IBM did not offer SQL
(I think ASC did).  Classifying it's nameless database as relational was
always debatable.


Keith


----- Original Message ----- 
From: "Pat Barber" <mboceanside@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, July 29, 2004 11:51 AM
Subject: Re: Who is Glenn Henry?


> I "suspect" no one individual came up with any of those
> subjects. Remember, the S/38 took a LOT of it's ideas
> from the S/36. The relational data base came from the
> big iron guys who had it for years prior to the S/38.
> The calls came from the big iron folks. The S/38 was
> truly a collection of ideas from everywhere.
>
> CLP was a combo of OCL(S/36) and JCL(MVS) in my opinion.
>
> The S/38 was a very odd bird at the time but really a
> big collection of "other" ideas that finally got put
> in a single machine.
>
> The MI abstract layer was the first of "new" ideas.
> This so called "microcode" was really somthing new at
> the time. It later proved to be a VERY good idea.
>
> Of course the S/36 had microcode several years earlier
> from it's beginning in the S/34 and even much earlier
> with the S/3.(back when the earth's crust was cooling)
>
>
> Steve Richter wrote:
>
> > Who invented command definitions and CL?
> >
> > Who added externally described files to RPG?
> >
> > Who added the CALLX to MI which made it possible for an RPG program to
call
> > another CL/RPG/COBOL program with parameters?
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>