HECnet

hecnet@lists.dfupdate.se

2 participants
15583 discussions

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.

13 years

DECnet VMS <-> RSTS/E

by mcguire＠neurotica.com

Hi guys. I fired up a (real hardware) PDP-11 tonight and did some DECnet testing between it and my up-24/7 Alpha. The systems are a DS10L running VMS v8.3 node 61.2 (AXPEE), and a PDP-11/53 running RSTS/E v10.1 and DECnet/E v4.1, node 61.4 (MECCA). Going from VMS to RSTS/E via "SET HOST/APP=RTERM 61.4" gives me the same crash as was reported earlier. 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. Control returned to node MECCA --------------------------------------------- Note: File operations work bidirectionally without difficulty. I log into the PDP-11 from my desktop via LAT using the "llogin" command, as I have LAT running on the PDP-11. I can also reach the Alpha via LAT. I don't know how to establish an outbound LAT connection in RSTS/E (and it's getting late) so I haven't tried that. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by mcguire＠neurotica.com

On 10/28/2012 08:57 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 On that note...are you sure that you set the logicals that I told you about in my first message about this? $ assign/system sy:[0,12] sysgen$$ $ assign/system sy:[0,1] system$$ After assigning the logicals it works fine. Seems I forgot to set them last time I tried. Oops. Ahh ok. Mystery solved. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by b4＠gewt.net

On Oct 28, 2012, at 8:53 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 10/28/2012 08:22 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 On that note...are you sure that you set the logicals that I told you about in my first message about this? $ assign/system sy:[0,12] sysgen$$ $ assign/system sy:[0,1] system$$ After assigning the logicals it works fine. Seems I forgot to set them last time I tried. Oops. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by mcguire＠neurotica.com

On 10/28/2012 08:22 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 On that note...are you sure that you set the logicals that I told you about in my first message about this? $ assign/system sy:[0,12] sysgen$$ $ assign/system sy:[0,1] system$$ -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by mcguire＠neurotica.com

On 10/28/2012 08:38 PM, Cory Smelosky wrote: Ok. I'll bring up a RSTS/E system and run some tests here. This will involve real hardware; none of my emulated systems are networked right now. I may get to this later tonight. You have a lot of real DEC hardware, don't you? ;) Yep. I would estimate about 45-50, not including destkop machines. Including desktop machines...it's...um, a LOT. And I wouldn't live any other way. As that could take some time, have any experience with DECnet and TOPS-20 in klh10? With DECnet on that platform, none at all. Sorry. :-( 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. If Peter is around, he's your man here, I think. Two things I can tell you is that I can easily reach a RSTS/E system from a Linux system via LAT, and also file operations work between that pair. File operations also work between the RSTS/E system and an Alpha running VMS. (all real hardware) I've probably misconfigured something obvious. Could be. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by b4＠gewt.net

On Oct 28, 2012, at 8:27 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 10/28/2012 08:22 PM, Cory Smelosky wrote: What's up with your DECnet installation, again? It's connected to the network, yet it can't reach any other nodes. Adjacency notices between nodes are seen, but they cannot communicate. Alpha to RSTS/E resulted in $ set host/app=rterm 33.301 %REM-I-CONNECTION, connection made using RTERM protocol %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000517000008AA4, PC=0000517000008AA4, PS=0000001B Improperly handled condition, image exit forced. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000000 0000517000008AA4 0000517000008AA4 000000000000001B Register dump: R0 = 0000000000000003 R1 = 0000000000008F50 R2 = 0000000000008134 R3 = 0000000000034804 R4 = 000000007FFCF814 R5 = 0000000000009AEF R6 = 0000000000000000 R7 = 0000000000000001 R8 = 000000000003481D R9 = 000000007FF9DDF0 R10 = 000000007FFA4F28 R11 = 000000007FFCDC18 R12 = 000000007FFCDA98 R13 = 0000000000005170 R14 = 0000000000008E28 R15 = 0000000000008E28 R16 = 0000000002A83089 R17 = 0000000000200000 R18 = FFFFFFFF809043A0 R19 = FFFFFFFF816367D0 R20 = 0000000000000002 R21 = 0000000000000000 R22 = 000000007AE4BA54 R23 = FFFFFFFF80190A50 R24 = 0000000000000001 R25 = 0000000000000003 R26 = FFFFFFFF80190A8C R27 = 000000007AE4BA54 R28 = 0000000000000006 R29 = 000000007AE4BA60 SP = 000000007AE4BA30 PC = 0000517000008AA4 PS = 300000000000001B $ And VAX to RSTS/E just results in a timeout. Attempting to dir from an Alpha results in the request being seen on RSTS/E, but it fails. RSTS/E to Alpha results in $ set host 33.302 Connection Established to VAX/VMS Node 33.302 ?Unsupported Virtual Terminal Protocol. Control returned to node MINDY So, I don't know what I misconfigured. Ok. I'll bring up a RSTS/E system and run some tests here. This will involve real hardware; none of my emulated systems are networked right now. I may get to this later tonight. You have a lot of real DEC hardware, don't you? ;) 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. Two things I can tell you is that I can easily reach a RSTS/E system from a Linux system via LAT, and also file operations work between that pair. File operations also work between the RSTS/E system and an Alpha running VMS. (all real hardware) I've probably misconfigured something obvious. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by mcguire＠neurotica.com

On 10/28/2012 08:22 PM, Cory Smelosky wrote: What's up with your DECnet installation, again? It's connected to the network, yet it can't reach any other nodes. Adjacency notices between nodes are seen, but they cannot communicate. Alpha to RSTS/E resulted in $ set host/app=rterm 33.301 %REM-I-CONNECTION, connection made using RTERM protocol %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000517000008AA4, PC=0000517000008AA4, PS=0000001B Improperly handled condition, image exit forced. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000000 0000517000008AA4 0000517000008AA4 000000000000001B Register dump: R0 = 0000000000000003 R1 = 0000000000008F50 R2 = 0000000000008134 R3 = 0000000000034804 R4 = 000000007FFCF814 R5 = 0000000000009AEF R6 = 0000000000000000 R7 = 0000000000000001 R8 = 000000000003481D R9 = 000000007FF9DDF0 R10 = 000000007FFA4F28 R11 = 000000007FFCDC18 R12 = 000000007FFCDA98 R13 = 0000000000005170 R14 = 0000000000008E28 R15 = 0000000000008E28 R16 = 0000000002A83089 R17 = 0000000000200000 R18 = FFFFFFFF809043A0 R19 = FFFFFFFF816367D0 R20 = 0000000000000002 R21 = 0000000000000000 R22 = 000000007AE4BA54 R23 = FFFFFFFF80190A50 R24 = 0000000000000001 R25 = 0000000000000003 R26 = FFFFFFFF80190A8C R27 = 000000007AE4BA54 R28 = 0000000000000006 R29 = 000000007AE4BA60 SP = 000000007AE4BA30 PC = 0000517000008AA4 PS = 300000000000001B $ And VAX to RSTS/E just results in a timeout. Attempting to dir from an Alpha results in the request being seen on RSTS/E, but it fails. RSTS/E to Alpha results in $ set host 33.302 Connection Established to VAX/VMS Node 33.302 ?Unsupported Virtual Terminal Protocol. Control returned to node MINDY So, I don't know what I misconfigured. Ok. I'll bring up a RSTS/E system and run some tests here. This will involve real hardware; none of my emulated systems are networked right now. I may get to this later tonight. Two things I can tell you is that I can easily reach a RSTS/E system from a Linux system via LAT, and also file operations work between that pair. File operations also work between the RSTS/E system and an Alpha running VMS. (all real hardware) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by b4＠gewt.net

On Oct 28, 2012, at 8:19 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 10/28/2012 07:36 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.. Well it wasn't blank, but I did choose "erase", so maybe that was my mistake. Regardless, I know what to do next time I need to install RSTS/E just need to fix the DECnet issues. Hmm. Ok. That's still a bit fishy, but at least we know why you couldn't run a sysgen. What's up with your DECnet installation, again? It's connected to the network, yet it can't reach any other nodes. Adjacency notices between nodes are seen, but they cannot communicate. Alpha to RSTS/E resulted in $ set host/app=rterm 33.301 %REM-I-CONNECTION, connection made using RTERM protocol %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000517000008AA4, PC=0000517000008AA4, PS=0000001B Improperly handled condition, image exit forced. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000000 0000517000008AA4 0000517000008AA4 000000000000001B Register dump: R0 = 0000000000000003 R1 = 0000000000008F50 R2 = 0000000000008134 R3 = 0000000000034804 R4 = 000000007FFCF814 R5 = 0000000000009AEF R6 = 0000000000000000 R7 = 0000000000000001 R8 = 000000000003481D R9 = 000000007FF9DDF0 R10 = 000000007FFA4F28 R11 = 000000007FFCDC18 R12 = 000000007FFCDA98 R13 = 0000000000005170 R14 = 0000000000008E28 R15 = 0000000000008E28 R16 = 0000000002A83089 R17 = 0000000000200000 R18 = FFFFFFFF809043A0 R19 = FFFFFFFF816367D0 R20 = 0000000000000002 R21 = 0000000000000000 R22 = 000000007AE4BA54 R23 = FFFFFFFF80190A50 R24 = 0000000000000001 R25 = 0000000000000003 R26 = FFFFFFFF80190A8C R27 = 000000007AE4BA54 R28 = 0000000000000006 R29 = 000000007AE4BA60 SP = 000000007AE4BA30 PC = 0000517000008AA4 PS = 300000000000001B $ And VAX to RSTS/E just results in a timeout. Attempting to dir from an Alpha results in the request being seen on RSTS/E, but it fails. RSTS/E to Alpha results in $ set host 33.302 Connection Established to VAX/VMS Node 33.302 ?Unsupported Virtual Terminal Protocol. Control returned to node MINDY So, I don't know what I misconfigured. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

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

by mcguire＠neurotica.com

On 10/28/2012 07:36 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.. Well it wasn't blank, but I did choose "erase", so maybe that was my mistake. Regardless, I know what to do next time I need to install RSTS/E just need to fix the DECnet issues. Hmm. Ok. That's still a bit fishy, but at least we know why you couldn't run a sysgen. What's up with your DECnet installation, again? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet