[email protected] (McKown, John) writes:
> Personally, I consider this list to be for almost anything having to
> do with zEnterprise (and its predecessors) topics. Granted, there may
> be more specific forums for some things, such as MVS-OE (z/OS UNIX),
> IBMTCP-L, Linux-390, z/VM, TSO REXX (who __do__ mean REXX in TSO, not
> REXX in general), CICS, DB2, IMS, and likely others of which I am not
> aware. IBM-MAIN is definitely __not__ "z/OS only". This despite the
> fact that most readers are z/OS, and perhaps some z/VSE.
as an aside ... IBM-MAIN mailing list originated on BITNET(/EARN) which
was almost all vm370 systems ... using technology similar to that of the
corporate internal network ... which also was almost all vm370 systems.
currently the IBM-MAIN mailing list is also gatewayed to ("USENET")
newsgroups ... although posts to newsgroups don't travel in the other
direction. Some of the other mailing lists that originated on BITNET
have at various times been also gatewayed to newsgroups ... like z/VM
... but gateway isn't currently active.
BITNET
http://en.wikipedia.org/wiki/BITNET
the early LISTSERV mailing list software for bitnet was similar to the
TOOLSRUN that had been earlier developed for the internal network
... but TOOSLRUN also supported USENET newsgroup like function ... in
addition to mailing lists ... this has BITNET migrating to the 1986
Paris-developed LISTSERV in 1987
http://en.wikipedia.org/wiki/LISTSERV
misc. past posts mentioning BITNET (and/or EARN in europe)
http://www.garlic.com/~lynn/subnetwork.html#bitnet
old email from person tasked with creating EARN:
http://www.garlic.com/~lynn/2001h.html#email840320
misc. past posts mentioning internal network (larger than
arpanet/internet from just about the beginning until
sometime late 85 or early 86)
http://www.garlic.com/~lynn/subnetwork.html#internalnet
I had been blamed for online computer conferencing on the internal
network in the late 70s and early 80s. Folklore is that when the
executive committee was told about online computer conferencing (and the
internal network), 5of6 wanted to fire me. Officially sanctioned
"discussion groups" and TOOLSRUN were somewhat the outcome of
investigations into my activities.
Internal network was result of co-worker at the science center,
reference
http://en.wikipedia.org/wiki/Edson_Hendricks
there is "typo" in the above about 1981 and ARPANET conversion to
TCP/IP, 250 ARPANET nodes and 1000 vnet nodes. All that happened in 1983
(not 1981). Also, ARPANET nodes were "IMPs" (tightly controlled by the
government and only number around 100 at the time of conversion). There
were possibly 250 "hosts" at 1983 cut-over (connected to those IMPs).
The requirement for tightly controlled IMPs is one of the contributing
factors to the internal network growing faster than the
arpanet/internet.
also from above:
In 1976, MIT Professor Jerry Saltzer accompanied Hendricks to DARPA,
where Henricks described his innovations to the principal scientist,
Dr. Vinton P. Cerf. From that point on, Vint and other DARPA scientists
adopted Hendricks' connectionless approach. The result developed into
the Internet as we know it today.
... snip ...
some number of people from MIT (IBM 7094) CTSS went to the 5th flr of
545 tech sq. for Multics & project MAC (including Jerry Saltzer) and
others went to the science center on the 4th flr, did virtual machines,
internal network, GML/SGML, bunch of other things. misc. past posts
mentioning science center
http://www.garlic.com/~lynn/subtopic.html#545tech
RSCS/VNET had layered networking (as opposed to JES2/NJI) and could
easily do drivers that talked to other systems (again as opposed to
JES2/NJI). JES2/NJI for nearly the whole time had limitations on the
maximum number of defined nodes ... which was less than the number of
internal nodes for at least a couple decades ... coupled with attribute
that JES2/NJI would trash traffic where either the origin and/or
destination node wasn't defined in its local table. JES2/NJI also had
characteristic that it tended to crash the host MVS system if traffic
was exchanged between JES2/NJI systems at different release levels. For
whatever reason, the RSCS/VNET discontinued shipping the native drivers
and only shipped the JES2/NJI drivers (with RSCS/VNET) ... even though
they continued to be used on the internal network because they were more
efficient and had higher throughput. misc. past posts mentioning HASP,
JES2, NJI, etc
http://www.garlic.com/~lynn/submain.html#hasp
--
virtualization experience starting Jan1968, online at home since Mar1970
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
