I've got a text file called "HECNODES2.TXT" which I think I must have acquired via this email list somehow, which is in the format that can be imported into decnet_register.

it starts out like this, so you could fairly easily make your own version from the basic nodenames file and a bit of scripting.

!
! DECnet/OSI node name export/import file      3-MAR-2022 12:49:39.21
!

=Type DECnet Node
=Version 1

=All        Address Prefix               49::

=DECdns     Name Template                ???:.???.*
=DECdns     Synonym Directory            ???:.???
=DECdns     Reverse Address Directory    ???:.???

=PhaseIV    Name Template                *

=LocalFile  Name Template                LOCAL:.*


ERNIE              ERNIE     {Tower=SC2/NSP/CLNS=1.2}
FNATTE              FNATTE     {Tower=SC2/NSP/CLNS=1.3}
GOBLIN              GOBLIN     {Tower=SC2/NSP/CLNS=1.4}


On Wed, 23 Jul 2025 at 07:18, Michael Brown <mbrown@b5.net> wrote:
I've had alot of progress with HECnet connection, I created another VM
to run linux and pydecnet then proceeded to activate the connection to
HECnet. It all works very well and I have full functioning access. Hit
me up with email to GUARD::MBROWN

There is only one problem I have left, how do I enter the details in
NODENAMES.DAT into the local name lookup. This will be one of those
Phase V problems as previousely griped about. Phase V uses mcr
decnet_register to enter host names and I have done that for a handfull
of commonly used hosts, but I have no Idea how I could do this with the
nodenames.dat file.

I wonder how you yourselves do this with Phase 4, I might be able to get
a clue if I knew how you did this trick in the first place.

Thank You.


_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se