HECnet

hecnet@lists.dfupdate.se

15562 discussions

by sampsa＠mac.com

So any chance of uploading this image anywhere? Sampsa On 28 Oct 2012, at 15:48, Sampsa Laine wrote: On 27 Oct 2012, at 21:19, Cory Smelosky wrote: On Oct 27, 2012, at 2:06 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 10/27/2012 03:57 AM, Sampsa Laine wrote: That reminds me, if someone has a turnkey RSX or RSTS box around (that I could just plug in to SIMH and play with), ideally with DECNET support, please let me know. If you can't find one, I can make a RSTS image up for you. (I've never done DECnet under RSX, so that'd take me awhile to figure out) Which version of RSTS? I can give my disk image for my install of 10.1 if anyone wants to try and figure out what I did wrong or wants to make it in to a turnkey install it's pretty basic as i'm new to RSTS. (it has DECmail though) I'm cool with RSTS - whatever version is fine. Sampsa PS: I will plague people with noob questions..

12 years, 8 months

rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

by b4＠gewt.net

On Oct 29, 2012, at 12:03 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote: Al 29/10/12 13:08, En/na Cory Smelosky ha escrit: It works mostly "out of the box" with the Panda distribution. You have to fiddle a little bit with the configuration file but IIRC it is pretty straightforward. I'll check it when I get access to my machine. Or you can check it yourself SET HOSTing to BITXT2 in HECnet. Unknown node, what's its address? Could you explain what you did to configure it? I am not at home now, so I will probably forgert something. You must edit SYSTEM:7-1-CONFIG.CMD and add/modify the following lines: NODE <your_node> <area.address> DECNET ROUTER-ENDNODE ETHERNET 0 DECNET 29-Oct-2012 09:33:11 ***BUGCHK COMBNN*** Bad local node number Job: 0, User: OPERATOR [KNILDR: Loading microcode version 1(172) into Ethernet channel 0] TYPE SYSTEM:7-1-CONFIG.CMD shows: NODE MINDY 33.303 DECNET ROUTER-ENDNODE ETHERNET 0 DECNET Trying to enter opr so I can enter NCP and see if I can get more information but nothing happens when I type opr<ret> as operator. The system is not reachable via decnet. Did I forget a setting somewhere? By the way, the address of BITXT2 is 7.78; you can login using GUEST / GUEST. I have not tried to configure it as a router, so I can not tell if anything different of ROUTER-ENDNODE would work. By the way, there is no "permanent database" in TOPS-20 DECNET, so you have to define the nodes everytime. I made a command procedure to do that parsing the output of a LIST KNOWN NODES, but unfortunately I can't tell you how do I invoke that command procedure now (I just forgot that!). The tricky part was the host configuration. I was unable to share the ethernet card of the host, so I resorted to the (somehow convoluted) solution of running a minimal linux system inside a virtualbox vm with several ethernet adapters and then run KLT10 inside the VM, using one of the virtual ethernet devices. I have it attached to a bridge and it is reachable via TCP/IP, so networking works.

12 years, 8 months

rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

by jg＠jordi.guillaumes.name

Al 29/10/12 13:08, En/na Cory Smelosky ha escrit: It works mostly "out of the box" with the Panda distribution. You have to fiddle a little bit with the configuration file but IIRC it is pretty straightforward. I'll check it when I get access to my machine. Or you can check it yourself SET HOSTing to BITXT2 in HECnet. > Unknown node, what's its address? Could you explain what you did to configure it? I am not at home now, so I will probably forgert something. You must edit SYSTEM:7-1-CONFIG.CMD and add/modify the following lines: NODE <your_node> <area.address> DECNET ROUTER-ENDNODE ETHERNET 0 DECNET By the way, the address of BITXT2 is 7.78; you can login using GUEST / GUEST. I have not tried to configure it as a router, so I can not tell if anything different of ROUTER-ENDNODE would work. By the way, there is no "permanent database" in TOPS-20 DECNET, so you have to define the nodes everytime. I made a command procedure to do that parsing the output of a LIST KNOWN NODES, but unfortunately I can't tell you how do I invoke that command procedure now (I just forgot that!). The tricky part was the host configuration. I was unable to share the ethernet card of the host, so I resorted to the (somehow convoluted) solution of running a minimal linux system inside a virtualbox vm with several ethernet adapters and then run KLT10 inside the VM, using one of the virtual ethernet devices.

12 years, 8 months

DECnet VMS <-> RSTS/E

by bqt＠softjar.se

On 2012-10-29 15:01, Paul_Koning at Dell.com wrote: On Oct 29, 2012, at 3:26 AM, Jordi Guillaumes i Pons wrote: Jordi Guillaumes i Pons Barcelona - Catalunya - Europa El 29/10/2012, a les 8:07, Dave McGuire <mcguire at neurotica.com> va escriure: Going from RSTS/E to VMS via "SET HOST 61.2" gives me this: --------------------------------------------- $ set host 61.2 Connection Established to VAX/VMS Node 61.2 ?Unsupported Virtual Terminal Protocol. I don't think you can use RTERM as an incoming protocol. And since you can't use it outgoing (from the Alpha) I guess it has been removed from Alpha VMS too... There are two generations of terminal protocol (not counting LAT). The newer of the two is Cterm, which is very large and very complicated. VMS supports it, RSTS doesn't. (I forgot if RSX does.) RSX do. But there are issues, but mostly it works well enough to be at least usable... The earlier one doesn't have a name as far as I remember. Also, it isn't one protocol; instead, it's a separate protocol for each destination OS type. The VMS and RSX flavors roughly correspond to the terminal QIO operations, you could think of them as a sort of RPC. The RSTS one is a bit like telnet in that it comes with a simple line mode and a raw character mode. The TOPS-20 one is just raw character mode. All of these use the same DECnet object number, the distinction between the different protocols is made when you connect. Right. The RSX flavor is rather weird in that the I/O is done locally as whole I/O operations. Comparing it with RPC is probably a good way to explain it, as far as I can tell. RSX have separate application for connecting to RSTS/E (RRS), TOPS-20 (HOST) and RSX (RMT), but they are all in the "unsupported tasks" category. Also, the application installed on RSTS by default for Set Host ("net") is the RSTS-only subject of the older protocol. The message you see comes from that application. You need to install the "unsupported" multi-OS version ("netuns"). With that in place, it should be able to talk to any OS. If VMS didn't have the older protocol listener in place, you'd get a different error message: a failure to connect due to the DECnet object not being defined at the destination. "Unknown object" or something similar, I would think. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

12 years, 8 months

rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

by Paul_Koning＠Dell.com

On Oct 28, 2012, at 7:34 PM, Dave McGuire wrote: On 10/28/2012 07:31 PM, Cory Smelosky wrote: Got it reinstalled it still doesn't work the way you said to do it, but doing it through @[0,1]instal works so i'll just use that route any time I need to build a monitor Urr? You did a CLEAN install on a blank destination disk? From the tape image that I gave you? I just did it that way.. How might I go about adding "users" in RSTS/E? $ CREATE/ACCOUNT (see "help create /account") Note: An "account" under RSTS/E can mean a "user account" that gets logged into, or just a "directory". That can be confusing. Just bear that in mind as you read. Originally, there wasn't any such thing as a directory (on the system disk, that is) that wasn't available for login. So it was called an "account". Somewhere around V8 or V9, the notion of a "no-user account" was added, which is somewhat like you find on Unix when the password is set to "*" -- you have a directory and possibly some other attributes like a name, but no password and no other user-related attributes like quotas, so you can't log in. There's "create/account" and "create/account/nouser". If you create an "account" on a non-system disk, it's no-user by default. Also, accounts with group number 0 -- like [0,200] -- are always no-user; group 0 is restricted that way. paul

12 years, 8 months

DECnet VMS <-> RSTS/E

by Paul_Koning＠Dell.com

On Oct 29, 2012, at 3:26 AM, Jordi Guillaumes i Pons wrote: Jordi Guillaumes i Pons Barcelona - Catalunya - Europa El 29/10/2012, a les 8:07, Dave McGuire <mcguire at neurotica.com> va escriure: Going from RSTS/E to VMS via "SET HOST 61.2" gives me this: --------------------------------------------- $ set host 61.2 Connection Established to VAX/VMS Node 61.2 ?Unsupported Virtual Terminal Protocol. I don't think you can use RTERM as an incoming protocol. And since you can't use it outgoing (from the Alpha) I guess it has been removed from Alpha VMS too... There are two generations of terminal protocol (not counting LAT). The newer of the two is Cterm, which is very large and very complicated. VMS supports it, RSTS doesn't. (I forgot if RSX does.) The earlier one doesn't have a name as far as I remember. Also, it isn't one protocol; instead, it's a separate protocol for each destination OS type. The VMS and RSX flavors roughly correspond to the terminal QIO operations, you could think of them as a sort of RPC. The RSTS one is a bit like telnet in that it comes with a simple line mode and a raw character mode. The TOPS-20 one is just raw character mode. All of these use the same DECnet object number, the distinction between the different protocols is made when you connect. Also, the application installed on RSTS by default for Set Host ("net") is the RSTS-only subject of the older protocol. The message you see comes from that application. You need to install the "unsupported" multi-OS version ("netuns"). With that in place, it should be able to talk to any OS. If VMS didn't have the older protocol listener in place, you'd get a different error message: a failure to connect due to the DECnet object not being defined at the destination. paul

12 years, 8 months

rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

by b4＠gewt.net

On 29 Oct 2012, at 03:30, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote: Jordi Guillaumes i Pons Barcelona - Catalunya - Europa El 29/10/2012, a les 1:38, Cory Smelosky <b4 at gewt.net> va escriure: As that could take some time, have any experience with DECnet and TOPS-20 in klh10? I read the documentation for it but it wasn't particularly helpful with regards to the networking "fronted" klh10 emulates, and I can't exactly load the executor config stuff to bring the node and circuit online. It works mostly "out of the box" with the Panda distribution. You have to fiddle a little bit with the configuration file but IIRC it is pretty straightforward. I'll check it when I get access to my machine. Or you can check it yourself SET HOSTing to BITXT2 in HECnet. Unknown node, what's its address? Could you explain what you did to configure it?

12 years, 8 months

DECnet VMS <-> RSTS/E

by mcguire＠neurotica.com

On 10/29/2012 03:26 AM, Jordi Guillaumes i Pons wrote: Going from RSTS/E to VMS via "SET HOST 61.2" gives me this: --------------------------------------------- $ set host 61.2 Connection Established to VAX/VMS Node 61.2 ?Unsupported Virtual Terminal Protocol. I don't think you can use RTERM as an incoming protocol. And since you can't use it outgoing (from the Alpha) I guess it has been removed from Alpha VMS too... I don't think it has been removed...it seems to be just plain crashing. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 8 months

rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

by jg＠jordi.guillaumes.name

Jordi Guillaumes i Pons Barcelona - Catalunya - Europa El 29/10/2012, a les 1:38, Cory Smelosky <b4 at gewt.net> va escriure: As that could take some time, have any experience with DECnet and TOPS-20 in klh10? I read the documentation for it but it wasn't particularly helpful with regards to the networking "fronted" klh10 emulates, and I can't exactly load the executor config stuff to bring the node and circuit online. It works mostly "out of the box" with the Panda distribution. You have to fiddle a little bit with the configuration file but IIRC it is pretty straightforward. I'll check it when I get access to my machine. Or you can check it yourself SET HOSTing to BITXT2 in HECnet.

12 years, 8 months

DECnet VMS <-> RSTS/E

by jg＠jordi.guillaumes.name

Jordi Guillaumes i Pons Barcelona - Catalunya - Europa El 29/10/2012, a les 8:07, Dave McGuire <mcguire at neurotica.com> va escriure: Going from RSTS/E to VMS via "SET HOST 61.2" gives me this: --------------------------------------------- $ set host 61.2 Connection Established to VAX/VMS Node 61.2 ?Unsupported Virtual Terminal Protocol. I don't think you can use RTERM as an incoming protocol. And since you can't use it outgoing (from the Alpha) I guess it has been removed from Alpha VMS too... The only "solution" I can think about is to use a simulated VAX to SET HOST into the RSTS machine, or to stick to LAT. But that would work just in one direction.

12 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet