I guess you're trimming one character off that request? Looked at my
DECnet receive processing, and it takes all the characters returned by
the receive, and don't trim anything off.
Happy to help dig more into this if you want me to. Let me know what I
can help with...
Also, is this how it's supposed to look like?
.fin dune::
[DUNE::]
OpenVMS V7.3 on node DUNE 25-JAN-2026 03:30:29.55 Uptime 41 13:03:12
SYSTEM, SYSTEM MANAGER, no plan, on:
14-DEC 19:46 OPA0:
EFRICHA, Eric F Richards, no plan, on:
26-DEC 16:10 RTA1: (BUZZEL::EFRICHA)
.
(Several newlines still in there.)
Also, it seems to pass through finger requests fine to other nodes. So
that seems to work right.
Johnny
On 2026-01-24 18:53, Keith Halewood wrote:
It's all pure $QIO and non-transparent now, on
DUNE:: and BUZZEL::
A decnet finger to MIM::DUNE:: seems to work except that I have to add a character
otherwise MIM seems to think it's MIM::DUNE:
resulting in no such user DUNE:
so MIM::DUNE::: works.
K
-----Original Message-----
From: Johnny Billquist [mailto:bqt@softjar.se]
Sent: 23 January 2026 16:37
To: hecnet(a)lists.dfupdate.se
Subject: [HECnet] Re: DECnet Finger Specification (Possible re-post) and Tops-20 Finger
Setup Documentation (New)
More feedback then...
On 23/01/2026 17.30, Keith Halewood wrote:
There are now CRLFs on outbound lines, one record
per line, one message per line.
Uh... Well...
.fin dune::
[DUNE::]
OpenVMS V7.3 on node DUNE 23-JAN-2026 16:34:56.34 Uptime 40 02:07:39
SYSTEM, SYS
TEM MANAGER, no plan, on:
14-DEC 19:46 OPA0:
EFRICHA, Eric F Richards, no plan,
on:
26-DEC 16:10 RTA1: (BUZZEL::EFRICHA)
SQKEITH, Keith Halewood,
unread mail,
no plan, on:
18-JAN 22:53 NTY144: (merdwyn.pitbulluk.local)
22-JAN
20:04 NT
Y160: (merdwyn.pitbulluk.local), running:
DUNE$DUA0:[SYS0.SYSCOMMON.][SYSEX
E]TPU.EXE
MALCOLMB, Malcolm Blunden, no plan, on:
23-JAN 13:33 NTY163:
(host86-
181-206-156.range86-181.btcentralplus.com)
23-JAN 13:33 (subprocess)
.
May I suggest you log into MIM, and try it yourself until it works... ;-)
By interoperate, I meant that @host might signal
a tcp/ip finger call to host whereas host:: would be decnet.
Ah. Well, yes. That is what I do, and what I would recommend. But others
might be doing things in different ways...
Note also the placement of the user:
user@host
vs.
host::user
Johnny
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol