Lindy
... they took long time to implement a resolver.
There has always been a resolver function in TCP/IP for VM, TCP/IP for
MVS and the IP component of z/OS Communications Server (CS) (CS IP). What you
may have in mind is the introduction of the resolver *address space* in z/OS
V1R2 CS IP.
Yes, playing and I get things wrong. Sorry.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Chris Mason
Sent: Wednesday, December 07, 2011 10:35 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Since
lindy.mayfi...@sas.com (Lindy Mayfield) writes:
Interesting, if I am correct, they took long time to implement a
resolver. If so, how were hostnames resolved?
re:
http://www.garlic.com/~lynn/2011p.html#42 z/OS's basis for TCP/IP
http://www.garlic.com/~lynn/2011p.html#43 z/OS's basis for TCP/IP
Point it to a DNS that worked. We ran ours on an RS/6000 for many moons.
In a message dated 12/7/2011 12:34:12 A.M. Central Standard Time,
lindy.mayfi...@sas.com writes:
If so, how were hostnames resolved?
--
For
Scott - I assume
... TCP/IP stack came from for use in z/OS ...
Did it originate from the University of Berkley?
You will get a more comprehensive answer by asking on the following list:
For IBMTCP-L subscribe / signoff / archive access instructions, send email to
lists...@vm.marist.edu
I believe that the TCP/IP for VM product which was ported to become the
TCP/IP for MVS product which became incorporated into the Communications
Server product as the IP component follows what is described as the Berkeley
Software Distribution (BSD flavour of an implementation of the Internet
Bob
Would you care to supply some evidence for your contention? I find no trace of
such an upheaval in the z/OS V1R5 Communications Server IP Migration and
Exploitation manual:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B130/
On the other hand, while there are still
Actually, it was OS/390 1.5, not z/OS 1.5. Too long ago.
Bob
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Chris Mason
Sent: Tuesday, December 06, 2011 7:42 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Bob
Would
svet...@ameritech.net (scott) writes:
Just was wondering where TCP/IP stack came from for use in z/OS? Did
it originate from the University of Berkley?
I hadn't followed the recent.
The original mainframe tcp/ip stack product was implemented on vm370 in
(mainframe) vs/pascal ... purely IBM
LOL!
OS/390 TWO dot FIVE (OS/390 2.5 was around 1996 IIRC)
Bob
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Bob Shannon
Sent: Tuesday, December 06, 2011 8:01 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Actually
06, 2011 8:01 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Actually, it was OS/390 1.5, not z/OS 1.5. Too long ago.
Bob
IBM eNetwork Communications Server for OS/390 V2R5, March 1998
Norbert Friemel
Bob
Actually, it was OS/390 1.5, not z/OS 1.5. Too long ago.
Not too long ago for the IBM manuals web sites!
Indeed there was an upheaval in OS/390 V1R5 (VEE ONE AR FIVE)
occasioned by the incorporation of OpenEdition function.
It may be that - on close reading of what can be gleaned from
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Chris Mason
Sent: Tuesday, December 06, 2011 7:42 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Bob
Would you care to supply some evidence for your contention? I find no
trace of such an upheaval in the z/OS
On Tue, 6 Dec 2011 08:48:40 -0600, Chris Mason wrote:
Indeed there was an upheaval in OS/390 V1R5 (VEE ONE AR FIVE)
That's V2R5, as you noted below. The new Communications Server component was
introduced in V2R4, but only for Unix applications. IIRC, the CS included VTAM
and TCP/IP and they
Peter
I'm very sorry to be disappointing you!
Is there any chance that there is a z/OS equivalent of these z/VM commands
for the general (non-authorized) user?
We're on the down slope, not the up slope! In other words, the direction in
the IP component of z/OS Communications Server is to
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Chris Mason
Sent: Tuesday, December 06, 2011 10:42 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Peter
I'm very sorry to be disappointing you!
Is there any chance
: 12/06/2011 11:25 AM
Subject:Re: z/OS's basis for TCP/IP
Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
Chris,
Well, I can't say I'm surprised by your answer, but thanks for your
insights anyway.
I haven't searched around the web yet (especially the CBT site
re:
http://www.garlic.com/~lynn/2011p.html#42 z/OS's basis for TCP/IP
this talks about bsd 4.3 tahoe (june 1988) and reno (early 1990)
distributions ... I've still got original source distribution
backed up someplace
http://en.wikipedia.org/wiki/Berkeley_Software_Distribution
All the BSD stuff
Tom
That's V2R5
Quite correct, OS/390 V2R5 (VEE TWO AR FIVE)
-
The new Communications Server component was introduced in V2R4,
I don't find this really quite so correct! This appears to refer to some quick
fix called the Outboard Communications Server (OCS) which allowed a LAN- or
@bama.ua.edu
Subject: Re: z/OS's basis for TCP/IP
Peter,
Sounds like you want TSO SEND. Do TSO HELP SEND for syntax and usage.
Cheers,,,Steve
Snipped
From: Farley, Peter x23353 peter.far...@broadridge.com
To: IBM-MAIN@bama.ua.edu
Date: 12/06/2011 11:25 AM
Subject:Re: z/OS's
re:
http://www.garlic.com/~lynn/2011p.html#42 z/OS's basis for TCP/IP
http://www.garlic.com/~lynn/2011p.html#43 z/OS's basis for TCP/IP
this is post here on ibm-main last april
http://www.garli.com/~lynn/2011f.html#29 TCP/IP Available on MVS When?
http://www.garli.com/~lynn/2011f.html#30 TCP/IP
peter.far...@broadridge.com
To: IBM-MAIN@bama.ua.edu
Date: 12/06/2011 12:22 PM
Subject:Re: z/OS's basis for TCP/IP
Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
Well, I certainly thought of TSO SEND, but it is the WAKEUP part of the
process (i.e., the receiving end
On 6. Dec 2011, at 17:05 , Anne Lynn Wheeler wrote:
re:
http://www.garlic.com/~lynn/2011p.html#42 z/OS's basis for TCP/IP
this talks about bsd 4.3 tahoe (june 1988) and reno (early 1990)
distributions ... I've still got original source distribution
backed up someplace
Otherwise you can
bzeeb-li...@lists.zabbadoz.net (Bjoern A. Zeeb) writes:
Otherwise you can probably still get them from a friend or a more
complete (source) history from here (for a small fee):
http://www.mckusick.com/csrg/index.html
re:
http://www.garlic.com/~lynn/2011p.html#42 z/OS's basis for TCP/IP
http
S. J. Palmisano
Group Director
Mid-Range Systems Management
re:
http://www.garlic.com/~lynn/2011p.html#43 z/OS's basis for TCP/IP
in the mid-70s the US HONE datacenters were consolidated at 1501
(although the bldg now has another occupant). Recent references
It was still pretty buggered up with PASCAL components scattered about, so
much so it violated Software Manufacturing's policies and was only
orderable as a separate product.
In a message dated 12/6/2011 7:46:59 A.M. Central Standard Time,
robert.richa...@opm.gov writes:
OS/390 TWO dot
Chris,
I think you're referring to the Infoprint Server LPD server.
See the latest bookshelf for details:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/aopbk380?FS=TRUE
--Roger
On Tue, Dec 6, 2011 at 8:41 AM, Chris Mason chrisma...@belgacom.net wrote:
The other major server
Ed
It was still pretty buggered up with PASCAL components scattered about, ...
I believe the position today is the list I included in a post to Peter Farley,
which I will post again for your convenience:
quote
- SMTP and LPD servers
- TSO HOMETEST, LPQ, LPR, LPRM, LPRSET, TELNET, and
In
58fc7f986fcb804286e23b59decf420f334a1...@nwt-s-mbx2.rocketsoftware.com,
on 12/06/2011
at 01:00 PM, Bob Shannon bshan...@rocketsoftware.com said:
Actually, it was OS/390 1.5, not z/OS 1.5. Too long ago.
There was no OS/390 1.5. OS/390 V2R5 sounds about right, although the
old version would
Subject: Re: z/OS's basis for TCP/IP
I believe that the TCP/IP for VM product which was ported to become the
TCP/IP for MVS product which became incorporated into the Communications
Server product as the IP component follows what is described as the Berkeley
Software Distribution (BSD flavour
Just was wondering where TCP/IP stack came from for use in z/OS? Did it
originate from the University of Berkley?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the
31 matches
Mail list logo
