[HECnet] RSTS/E started emitting "?EVTLOG (BLDNIC) -- %Integer error" messages

[Keith Halewood]

Netupdatev3.com on DUNE does some checking for ‘your’ range of nodes in an area and outputs a slightly more optimal set of commands for NCP. It also throws out a pydecnet node list too.

Keith 

> On 11 Nov 2021, at 12:14, Steve Davidson <steve at davidson.net> wrote:
> 
> NETUPDATE.COM  (VMS only) checks two things:  first it checks the record against the current node name and if equal skips the record.  Second, if the database is being run against a cluster then it additionally ignores all of the nodes in that area.  This way all of the Satellite information is not altered thus rendering satellite boot non functional.
> 
> Similar behavior for the first case could probably be applied in most of the command line interpreters. 
> 
> -Steve
> 
> SF:IP2
> 
>> On Nov 11, 2021, at 06:30, Johnny Billquist <bqt at softjar.se> wrote:
>> 
>> Tony,
>> 
>>>> On 2021-11-11 10:30, Tony Nicholson wrote:
>>> Johnny,
>>> Under RSTS/E I’ve found I can use FIX.CMD, but I have to comment the definition for the current node and add a missing definition for MIM.  
>> 
>> Ah. Yes, similar "problem" as with RSX in that the own node won't work. That's the reason MIM is not in there. I should create a different one for others. FIX.CMD is where I started, and it is very tailored to my own use.
>> 
>>> Then duplicate the definitions changing the ‘def nod’ to ‘set nod’ and feed it into NCP.
>> 
>> Maybe you should look at FIX.COM?
>> 
>>> When I update pydecnet using a new nodenames.dat I also use
>>> $ ncp copy known nodes from TNRTR to both
>>> (TNRTR Is my pydecnet router)
>> 
>> That definitely works in VMS. Does that also work in RSTS/E?
>> 
>> With that said, while generated command files are all nice and good, for at least VMS and RSX, I would actually recommend people use the provided DECnet tools instead.
>> 
>> 
>> In RSX:
>> 
>>> RUN LB:[5,54]NNCFSL
>> 
>> and collect the nodes from MIM, and then:
>> 
>> SCP STOP
>> SCP START
>> 
>> and you have the new nodenames in there.
>> 
>> 
>> In VMS (as mentioned above):
>> 
>> $ NCP COPY KNOWN NODES FROM MIM TO BOTH
>> 
>> If the VMS solution also works in RSTS/E that is really nice.
>> 
>> Johnny
>> 
>>> Tony
>>>> On Thu, 11 Nov 2021 at 19:54, Johnny Billquist <bqt at softjar.se <mailto:bqt at softjar.se>> 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.
>>>   At the moment, the following files are created:
>>>   FIX.T20 (for TOPS-20)
>>>   FIX.COM <http://FIX.COM> (for VMS)
>>>   HECNET.PY (for PyDECnet)
>>>   FIX.CMD (for RSX)
>>>   All can be found at MIM::HECNET:
>>>       Johnny
>>> -- 
>>> Tony Nicholson <tony.nicholson at computer.org <mailto:tony.nicholson at computer.org>>
>> 
>> -- 
>> 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