On Mon, 20 May 2013, Johnny Billquist wrote:
On 2013-05-20 17:01, G. wrote:
Now that there is a TOPS-10 host on HECnet, can some people try at least to
trace on which versions it works and on which it does not?
Thanks to everyone! :)
Hum...
..set /host=marley
NCT -- Connection rejected, Node unreachable
NCT -- Control returned to node "MIM "
..ncp tell marley sho exec
NCP -- Show failed, Listener connect failed, node unreachable
..
Johnny
I'm seeing tha two...expect I can ping it from my area router and I can SET HOST from VAX/VMS 7.3
I am...very confused.
--
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
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Mon, 20 May 2013, Brian Schenkenberger, VAXman- wrote:
G. <gerry77 at mail.com> writes:
Hello all!
Let's try to summarize the problem.
RTPAD.EXE is the executable image behind SET HOST and SET HOST/APP=3DR on=
VMS,
and it can use both CTERM and RTERM protocols to connect to remote =
systems.
Some older OSes, notably TOPS-10 and RSTS (and others, I suppose), do =
either
behave badly when accessed with the newer CTERM protocol, mainly because =
it's
too VMS-centric, or do not work at all because they do not suppport it. =
To
connect to them, the solution is to always use the older RTERM protocol.
RTPAD.EXE on OpenVMS V8.3 for both Alpha and Itanium (IIRC) has some =
serious
bug that prevents it from connecting to such older OSes using the old =
RTERM
protocol: actually it ACCVIOs before doing any useful work.
The RTERM protocol can be used to connect to VMS too, and when connecting=
to
another VMS node using RTERM, the V8.3 RTPAD.EXE works as expected. So, =
either
some older OSes are sending out-of-standard packets (and the older =
RTPAD.EXE
were more forgiving), or the new RTPAD.EXE cannot understand all the =
protocol
variants and intricacies (as the older versions did).
I tried exchanging V8.3 RTPAD.EXE (ident X-10) with a couple of older =
versions
(idents X-8, X-9) and even with the V8.4 one (ident X-10 too, so should =
be the
same as V8.3), to no avail: every one of them ACCVIOs as well. The oldest=
I
tried (X-8) comes from plain vanilla V7.2 (and does not work), but I'm =
almost
sure (I cannot swear on it, though) that RTERM worked fine in V7.2, so =
I'm
stuck: the same image (X-8) was working on V7.2 but it's not in V8.3.
I know that testing by exchanging images among different VMS versions is =
not
bulletproof, but considering that I didn't get any error like SHRIDMISMAT=
and
such, I feel confident about thinking that they are compatible. So maybe =
the
problem is somewhere else, probably in some shared library.
What else can I do? Is there anyone with the right knowledge (I'm =
thinking to
e.g. Brian Schenkenberger) that can try to track down the bug and at =
least
identify in which part of VMS lies the problem? Or give me some =
suggestions...
This is what happens:
| $ set host/app=3Dr xxxxxx
| %REM-I-CONNECTION, connection made using RTERM protocol
|=A0%SYSTEM-F-ACCVIO,=A0access=A0violation,=A0reason=A0mask=3D00,=A0virtu=
al=A0address=3D000052D800008AA4,=A0PC=3D000052D800008AA4,=A0PS=3D0000001B
|=20
| Improperly handled condition, image exit forced.
| Signal arguments: Number =3D 0000000000000005
| Name =3D 000000000000000C
| 0000000000010000
| 000052D800008AA4
------------------------------------^v^v^v^v^v^v^v^v
| 000052D800008AA4
| 000000000000001B
This looks bad. I can tell you that it's not very likely a problem VMS address
which RTPAD is operating in. I suspect that 0000000000008AA4 would be close to
the PC in the RTPAD image or 0000000000052D8. I would guess that some improper
stack manipulation is the cause for this error.
If this stack dump came from V8.3, I'll take a look in the source to see if the
addresses yield anything. Please confirm that the above was from the Alpha V8.3
RTPAD.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
I was going to grab the stack dump from 8.4...but there's a completely different issue there.
$ set host/app=rterm marley
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
$ set host marley
*INTERRUPT*
$
$ set host/lat marley
%LAT-S-CONNECTED, session to MARLEY established
Can anyone else reach MARLEY? DECnet is up...I cam reach it from 7.2 on simh and my area router can ping it.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
G. <gerry77 at mail.com> writes:
On Mon, 20 May 2013 11:51:56 -0400, Brian Schenkenberger, VAXman- wrote:
Were you attempting to RTERM to a TOPS20 system???
=20
That's where that stack dumps seems to be taking me.
No, TOPS-10.
Well, there's no specific TOPS-10 module. I'll assume that the TOPS20 is
also for use when the target is TOPS10.
Wait, when connecting to RSTS/E it changes...
Hmm. Very peculiar.
000052D800008AA4
0000517000008AA4
OK. I have some other work to address but I'll try to look into this some
more later.
If you can go back to plain-vanilla V8.3 (ie. sans any update patches), see
if it occurs there. If it does not, one of the updates has introduced some
incompatibility. It will be much easier to trace down if you can prove and
or disprove this.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On May 20, 2013, at 11:38 AM, G. wrote:
On Mon, 20 May 2013 15:07:28 +0000, <Paul_Koning at Dell.com> wrote:
Port the Linux one to VMS?
Linux speaks RTERM, not only CTERM?! :o
That would be an interesting solution. I didn't know at all that dnprogs now
support RTERM too, and I see that the author is you... :)
Yes, or more precisely, I supplied some of the variants -- RSTS and perhaps one or two others, it's been long enough that I no longer remember.
The comment about ending up in the rtpad RSTS code makes sense. TOPS-10 terminal behavior is quite similar to RSTS, so the same protocol is apparently used by both. The other three flavors are (a) VMS, (b) RSX, and (c) TOPS-20. I forgot what Ultrix used, or Linux when in rtpad mode.
sethost.c, I suppose. At first sight the new dnlogin program appears not to
support RTERM. Am I right?
I don't remember. Perhaps a built option?
paul
On Mon, 20 May 2013 11:51:56 -0400, Brian Schenkenberger, VAXman- wrote:
Were you attempting to RTERM to a TOPS20 system???
That's where that stack dumps seems to be taking me.
I can SET PROC/DUMP and do something with ANA/PROC if needed...
G.
G. <gerry77 at mail.com> writes:
On Mon, 20 May 2013 11:29:28 -0400, Brian Schenkenberger, VAXman- wrote:
For what it's worth, both of the addresses I previously identified =
fell,
according to the RTPAD.MAP, in the CODE and DATA PSECTs of module =
RSTSRT.
So it's not a shared library issue? Anyway, I wonder what got changed in =
such
an old and perhaps not-so-much-used-today module...
Were you attempting to RTERM to a TOPS20 system???
That's where that stack dumps seems to be taking me.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On 2013-05-20 17:43, G. wrote:
On Mon, 20 May 2013 11:29:28 -0400, Brian Schenkenberger, VAXman- wrote:
For what it's worth, both of the addresses I previously identified fell,
according to the RTPAD.MAP, in the CODE and DATA PSECTs of module RSTSRT.
So it's not a shared library issue? Anyway, I wonder what got changed in such
an old and perhaps not-so-much-used-today module...
I would be very surprised if that code have been touched in many years. More likely some corruption of the stack or some data structure. If the same code previously worked, then I'd still start by pointing at some shared library, but there might also be common data with other parts of RTPAD, which have been changed, while the RSTSRT piece was not.
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
On Mon, 20 May 2013 11:41:07 -0400, Brian Schenkenberger, VAXman- wrote:
image name: "RTPAD"
image file identification: "X-10"
image file build identification: "XBC4-0080060000"
link date/time: 29-JUN-2006 18:18:54.69
linker identification: "A13-03"
Excellent. This is unscathed (ie. no patchin). The link date in the source
listing is: 29-JUN-2006 18:18
The only recent patch to RTPAD was in V7.3 for an unrelated problem.
BTW, I tried both 7.3 images too, and they do not work...
G.
On Mon, 20 May 2013 11:29:28 -0400, Brian Schenkenberger, VAXman- wrote:
For what it's worth, both of the addresses I previously identified fell,
according to the RTPAD.MAP, in the CODE and DATA PSECTs of module RSTSRT.
So it's not a shared library issue? Anyway, I wonder what got changed in such
an old and perhaps not-so-much-used-today module...
G.
