VMCF and TNF may still be on your systems for the few remnants depending on the PASCAL stack API. It was ported out of VM and did not perform well either. Another factor which slowed the adoption of TCP/IP in the z/OS (them MVS world) was the IBM Communications group resistance. They had all their bets and plans revolving around keeping and protecting SNA
> -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Charles Mills > Sent: Thursday, February 04, 2021 5:11 PM > To: [email protected] > Subject: Re: TCP/IP relationship to OMVS > > Are there not occasional fleeting references here and there to "the Pascal > TCP stack"? > > The first I personally wrote any z/OS socket code was around 2010. (I had an > employee who wrote socket code for Z in the 90's but I am not the least bit > intimate any more with the details. I seem to recall that perhaps it was a > SAS-licensed TCP stack? Does that ring a bell?) > > Anyway, the Comm Server doc at that time (2010) -- I see it still around for > z/OS V1R13 -- had a manual "IP Sockets Application Programming Interface > Guide and Reference." I think I originally got going in 2010 using that doc, > and it was not right at all for the TCP implementation I was using, which is > correctly documented in the C Library manual. I think it may be doc for the > Pascal stack. Does that make sense? I quickly got straightened out. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On > Behalf Of Frank Swarbrick > Sent: Thursday, February 4, 2021 3:47 PM > To: [email protected] > Subject: Re: TCP/IP relationship to OMVS > > Looks like OS/390 V2R4 (Sept 1997?) contained "A new TCP/IP stack, for > applications using OS/390 UNIX System Services (formerly called > OpenEdition) > sockets". > > Prior to that was TCP/IP Version 3 Release 2, which I believe was based on a > port of TCP/IP for VM (and written in Pascal!). Or something like that. > > References: > https://urldefense.com/v3/__https://www- > 01.ibm.com/common/ssi/ShowDoc.wss?docURL=*common*ssi*rep_ca*6*8 > 7__;Ly8vLy8!!JmPEgBY0HMszNaDT!_11xmxKMzbWFPba3c4Ph4oLlxM8bXcTY > A6cYdNqZeSdE15KOYRjphExehsA6FA$ > 7/ENUSZP97-0486/index.html&request_locale=en > https://urldefense.com/v3/__https://www- > 01.ibm.com/common/ssi/rep_ca/9/897/ENUS296- > 339/index.html__;!!JmPEgBY0HMszNaDT!_11xmxKMzbWFPba3c4Ph4oLlxM8 > bXcTYA6cYdNqZeSdE15KOYRjphEzIZ2CIDg$ > https://urldefense.com/v3/__https://groups.google.com/g/bit.listserv.ibm- > main/c/M7wIMma2Ig4__;!!JmPEgBY0HMszNaDT!_11xmxKMzbWFPba3c4Ph > 4oLlxM8bXcTYA6cYdNqZeSdE15KOYRjphEyixtv9-w$ > > > ________________________________ > From: IBM Mainframe Discussion List <[email protected]> on > behalf of > Pew, Curtis G <[email protected]> > Sent: Thursday, February 4, 2021 4:09 PM > To: [email protected] <[email protected]> > Subject: Re: TCP/IP relationship to OMVS > > On Feb 4, 2021, at 4:24 PM, Mike Schwab <[email protected]> > wrote: > > > > z/OS FTP required a RACF OMVS flag in 2001 when I started submitting > > dumps to IBM. > > > > I have a vague recollection that in the early 1990s IBM provided a TCP/IP > stack on MVS that was ported from VM, but sometime in the OS/390 era it > was > replaced by a new Unix-based implementation. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
