HECnet

hecnet@lists.dfupdate.se

10 participants
15598 discussions

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by gregg.drwho8＠gmail.com

On Sat, Aug 4, 2012 at 6:38 AM, Sampsa Laine <sampsa at mac.com> wrote: For various reasons to do with my general mental stability etc, I decided to learn about IBM mainframes, so got one running.. Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? Details: http://sampsa.com/2012/08/04/mvs-on-an-s390-because-openvms-is-just-too-eas… Hello! Sampsa nice going so far back there on that list. Next step will be joining the H390-MVS list to further your studies and to ask the right questions. I run that one so you're in good company. There's also a very unhappy crowd of yetis around you by the way, they lost a bet..... ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

13 years, 8 months

MVS and DecNet

by hvlems＠zonnet.nl

DEC had two hardware solutions. The channel attached gateway and a gateway that used a serial interface. The -CT was the size of a VAX 4500, the -ST the size of a LANbridge 100 (to give you an idea). The advantage of the -CT over the -ST was the simultaneous sessions it supported, 1024 vs 256. Important if one used RJE stations because each RJE station used at least one cardreader, console and printer session. I thinks the cardpunch was optional but if you needed more output streams it was useful. The -CT connected to ethernet and connected to just one IBM host via its channel interface. All systems that supported the SNA/DECnet package could set up sessions to the -CT and thus the IBM. The -ST was kind of point to point: serial to the IBM and synchronous to the VAX host. (IIRC ..) The IBM used SNA on either DOS/VSE or MVS. The latter also supported access to its filesystem, so $ DIR IBM::*.* was possible. An additional SNA gateway software product was required. The 3174 emulation was for terminals, it was implemented with yet another box. I forgot which one. It connected to a control unit and the serial backend was hard wired to two DECservers 200 that offered the (reverse) LAT service IBM to the ethernet. Worked a lot better than 3174 emulation on token ring connected Novell pc's. (All this happened between 1988 and 1994). In those days DECnet was the lingua franca on the LAN. Phase 4. No way phase 5 could talk directly to VTAM. The hardware gateway products only implemented phase 4. There was an SNA product that ran natively on a VMS system, it used a DMF32 to connect to the IBM (at least my memory thinks it was a DMF32. May just as well have been something else :-) . Same functionality as the -ST without the DEMSA box. Hans ------Origineel bericht------ Van: Sterling Garwood Afzender: owner-hecnet at Update.UU.SE Aan: Sampsa Laine Cc: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: [HECnet] MVS and DecNet Verzonden: 4 augustus 2012 16:35 Saw your note on Hecnet about MVS and DecNet I've run MVS 3.8J on Hercules for years on Macs and PCs (usually on Linux) ISTR that DEC had an interface that sat on the IBM channel and looked like a 3274 control unit --- I also remember going to a demo at DEC late in their life and watching the product crash over and over :-) The place I worked ended up installing TCPIP on the 370s to talk to the Vaxen - I believe it was a port of the Stanford or UCLA code (don't remember which). Anyone who needed terminal access to the mainframe went thru the Vax that was the gateway. Sterling Garwood slgarwood at charter.net

13 years, 8 months

MVS and DecNet

by slgarwood＠charter.net

Saw your note on Hecnet about MVS and DecNet I've run MVS 3.8J on Hercules for years on Macs and PCs (usually on Linux) ISTR that DEC had an interface that sat on the IBM channel and looked like a 3274 control unit --- I also remember going to a demo at DEC late in their life and watching the product crash over and over :-) The place I worked ended up installing TCPIP on the 370s to talk to the Vaxen - I believe it was a port of the Stanford or UCLA code (don't remember which). Anyone who needed terminal access to the mainframe went thru the Vax that was the gateway. Sterling Garwood slgarwood at charter.net

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by sampsa＠mac.com

Yeah, I think it's VTAM. Not sure what / how to connect it beyond the local box though, might need some IBM network voodoo box or something. Sampsa On 4 Aug 2012, at 16:29, Bob Armstrong wrote: Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? I don't know about DECnet, but the reverse is possible - DEC had an SNA gateway product. Good luck :-) Bob

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by bob＠jfcl.com

Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? I don't know about DECnet, but the reverse is possible - DEC had an SNA gateway product. Good luck :-) Bob

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by fcoffey＠misernet.net

On Sat, 4 Aug 2012, Sampsa Laine wrote: For various reasons to do with my general mental stability etc, I decided to learn about IBM mainframes, so got one running.. Hi Sampsa, Are you running Turnkey? I have VM/370 (well, 380 actually) and MVS/380 running here. I play with it occasionally. I also run MUSIC/SP on a Windows XP VM I have (cause it's the only way I can get TCP/IP working with MUSIC since it's not supported from what I can tell on Hercules). I'd like to get them interfaced to mail (I remember using PROFS (which I know is licensed) at a former job) or actually do *something* remotely useful with it ... :) Let me know if you make any headway. Fred

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by sampsa＠mac.com

I don't think the freeware MVS comes with SNA, as that's a commercial product. Could set up some captive accounts to run TN3270 on GORVAX I suppose. Sampsa On 4 Aug 2012, at 15:53, Kari Uusim ki wrote: How about the SNA gateway, which DEC built just for that need? On 4.8.2012 13:38, Sampsa Laine wrote: For various reasons to do with my general mental stability etc, I decided to learn about IBM mainframes, so got one running.. Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? Details: http://sampsa.com/2012/08/04/mvs-on-an-s390-because-openvms-is-just-too-eas… .

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by uusimaki＠exdecfinland.org

How about the SNA gateway, which DEC built just for that need? On 4.8.2012 13:38, Sampsa Laine wrote: For various reasons to do with my general mental stability etc, I decided to learn about IBM mainframes, so got one running.. Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? Details: http://sampsa.com/2012/08/04/mvs-on-an-s390-because-openvms-is-just-too-eas… .

13 years, 8 months

Managed to get an emulated S/390 with MVS up - any way we can get this beast onto HECnet?

by sampsa＠mac.com

For various reasons to do with my general mental stability etc, I decided to learn about IBM mainframes, so got one running.. Any way to connect this to DECnet? Maybe over over DECNet-OSI since the thing natively does VTAM? Details: http://sampsa.com/2012/08/04/mvs-on-an-s390-because-openvms-is-just-too-eas…

13 years, 8 months

HECNET accessible bulletin board

by sampsa＠mac.com

Guys, I've been reimplementing an old 80s BBS package called Waffle in Python (called Pyffle). Anyway, it's accessible over HECNET as the host name PYFFLE, log in as pyffle at the Unix prompt. Sampsa

13 years, 9 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet