Well, at one time I expected https://en.wikipedia.org/wiki/Government_Open_Systems_Interconnection_Profile (GOSIP) to displace SNA, but the Feds went TCP/IP despite the mandate and that was all she wrote.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Monday, December 31, 2018 4:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Network names (was: System Symbols) On Mon, 31 Dec 2018 16:00:02 -0500, Tony Harminc wrote: > >In the mid 1990s, when SNA interconnection between enterprises was at its >peak, IBM had an SNA network name registry. (For all I know they may still >have it.) Names were of the form <two letter ISO country code><three >character customer code>, so e.g. IBM itself was USIBM (and CAIBM or >whatever you were connecting to). I wonder if USCAD was ever registered... > Sounds like a tiny step in the direction of a DNS. I've long wondered whether a robust DNS would have enabled SNA to compete better with TCP/IP. Or was price a determining factor? Was EBCDIC vs. ASCII ever a concern? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN