[HECnet] My RSTS/E system...

[Keith Halewood]

When I use set host on vms to login to the little rsts/e box, I have to:

Set host/app=rt

To connect to rterm and not cterm. It works quite well.

> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
> 
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se> wrote:
>>> 
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at softjar.se> wrote:
>>>>> 
>>>>> Hi.
>>>>> 
>>>>>> ...
>>>>> 
>>>>> By exploring adjacent nodes and known circuits, you'd get a more complete picture, as it will also show you connections which are not the lowest cost paths.
>>>>> 
>>>>> However, as I said, it will only give a partial picture anyway. I also found out the other day that it don't seem like RSTS/E implements it either, or maybe it depends on version and maybe it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning (i.e., from when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>> However, it need not be enabled as a known object.  And if enabled, it may or may not accept connections without access control variables (PPN/password).  If not, you'll get a reject indicating either no such object or bad access control.  However, if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node you're talking to is an endnode it will only tell you who the adjacent designated router is (or the adjacent nodes, on point to point circuits).
>>> 
>>> In this case not enabled then, I think. Thanks for clarifying that it exists. I only did a reflection based on trying to look at an RSTS/E node just the other day that did not give me anything.
>>> 
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error.  Network resources is a bit odd.  Possibly there is a default account defined but that account doesn't exist, or is configured as "no network connections allowed".
> 
> Agreed that it's a bit surprising error. I have not tried looking deeper into it. Maybe I should. Do you have any RSTS/E system online I can try talking to just to make sure it's nothing more general?
> 
>>> And I did verify that it's an up and running RSTS/E system. V9.6 according to information I have.
>>> 
>>> Might also be some other kind of problem somewhere that I haven't figured out. System also isn't talking CTERM, but did answer when I tried some RSTS/E specific terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol.  That doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
> 
> The RSTS/E specific remote terminal application under RSX have some bug, though. When it finishes, it crashes the RSX system. Definitely a problem I need to fix.
> 
>  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