11 Nov
2021
11 Nov
'21
10:10 p.m.
It had occurred to me that ordering the node file by area and then node
within area might make it more directly useful to someone looking at it
while trouble-shooting a local area, but I've never felt strongly enough
about the matter to come down on it one way or the other.
Besides, my SETNODE rewrite will display them in either other, an example:
@g sn:setnD2.EXE.0
@start
% Insufficient capabilities for INSERT command
SETNODE>GET (binary node definition file) SYSTEM:NODE-DATA.BIN
/no-ACCESS /pagE-MAP /unrESTRICTED-READ /prelOAD
Mapped 4 pages, 1830 Words, 915 Nodes.
SETNODE>RECONSTRUCT (node keyword tables from binary table) /silENT
[Closed log file: NUL:]
SETNODE>SHOW (node table) aREA (number to filter by) 30
[Area 30]
FRODO????? 1??? MV80?????? 2??? RD73?????? 3??? YODA 4??? IMAC?????? 5
RD83?????? 6??? LTC??????? 7??? DFRPI????? 8??? LAN40A 10???
RDP1????? 11
RDP2????? 12??? RDP3????? 13??? RDP4????? 14??? CBVRP3 15???
RD84????? 16
LAN40B??? 17??? BLISH???? 18??? NICHTS??? 60??? MALCOM 70
Total nodes in area 30: 19
SETNODE>SHOW (node table) SAME (node) /arEA 30
[Area 30]
BLISH???? 18??? CBVRP3??? 15??? DFRPI????? 8??? FRODO 1??? IMAC?????? 5
LAN40A??? 10??? LAN40B??? 17??? LTC??????? 7??? MALCOM 70???
MV80?????? 2
NICHTS??? 60??? RD73?????? 3??? RD83?????? 6??? RD84 16??? RDP1????? 11
RDP2????? 12??? RDP3????? 13??? RDP4????? 14??? YODA 4
Total nodes in table: 915; area 30: 19 nodes
SETNODE>
The former SHOW is DEC SETNOD compatible syntax.? The latter parse is a
result of the multi-section keyword tables I build for COMND%. This also
allows question mark and escape recognition, which is kind of whizzy,
yet useless for programming and probably NFT.
------------------------------------------------------------------------
On 11/11/21 9:51 AM, Johnny Billquist wrote:
On 2021-11-11 15:17, Supratim Sanyal wrote:
On 11/11/21 8:50 AM, Johnny Billquist wrote:
It is sorted. Currently by name.
Do you want it sorted some other way?
It's just one more line of Datatrieve, so it's super trivial.
? Johnny
Surpatim, check out MIM::HECNET:FIX.RST if it
looks good.
Looks good. Just to pick your noodle, maybe filter it through sort
first, equivalent of *sort -V -t " " -k 4* ? (I'm also open for another name of the file,
if wanted...)
? Johnny
On 2021-11-11 14:36, Supratim Sanyal wrote:
-- On 11/11/21 3:53 AM, Johnny Billquist wrote:
> If a specific format is needed for RSTS/E nodes, I can create that
> format file whenever the nodename database is updated. Just let me
> know what the format should be.
>
$ type defnod.cmd
*SET VER**
**SET NOON**
**NCP DEFINE NODE 1.1 NAME MAGICA**
**NCP DEFINE NODE 1.2 NAME ERNIE**
**NCP DEFINE NODE 1.3 NAME FNATTE**
**...**
**...**
**NCP DEFINE NODE 62.637 NAME CTAKAH**
**NCP SET NODE 1.1 NAME MAGICA**
**NCP SET NODE 1.2 NAME ERNIE**
**NCP SET NODE 1.3 NAME FNATTE**
**...**
**...**
**NCP SET NODE 62.637 NAME CTAKAH*
> At the moment, the following files are created:
>
> FIX.T20 (for TOPS-20)
> FIX.COM (for VMS)
> HECNET.PY (for PyDECnet)
> FIX.CMD (for RSX)
>
> All can be found at MIM::HECNET:
>
> ? Johnny
>
> On 2021-11-11 02:20, Supratim Sanyal wrote:
>> Maybe helpful to someone, the latest node database can now be
>> synced up on RSTS/E using RST101::DEFNOD.CMD
>>
>> RST101 is at 31.28
>>
>> best,
>> /s.
>>
>> On 11/10/21 7:42 PM, Tony Nicholson wrote:
>>>
>>>
>>> On Thu, 11 Nov 2021 at 11:31, Supratim Sanyal
>>> <supratim at riseup.net> wrote:
>>>
>>> ??? Copied from GALAH, the copy at DINGO doesn't have read
>>> permission.
>>>
>>>
>>> Fixed permissions - I thought I had protected them against
>>> writing/not reading. Blame finger memory not engaging with my
>>> brain.
>>>
>>> Tony
>>>
>>> --
>>> Tony Nicholson <tony.nicholson at computer.org>
>> --
>
--