Does RSX-11S actually send a different code tham -M ?  Or is that a distinction the DAP
spec made that isn't valid in the real world?
It's not surprising the table would use the -M code since that would be the original
common one.  I don't know that DECnet on 11D was real, and it seem D wasn't
anywhere near as popular as M for a number of good reasons.
	paul
  On Oct 20, 2022, at 2:10 PM, Johnny Billquist
<bqt(a)softjar.se> wrote:
 
 Yes. RSX-11M and RSX-11M-PLUS have different IDs, and yes, MIM is M+, and thus sends
13(8).
 
  Johnny
 
 On 2022-10-20 03:05, Thomas DeBellis wrote:
  I recently had a number of connectivity issues
that caused me to review my DECnet related batch jobs.  The following is a snippet from
the log file of GETNOD, which is the weekly batch job that fetches the latest HECnet node
list from MIM::.  I had updated it in part because of trouble-shooting, but the change
isn't dramatic--it's rather more of a 'buff and polish'.  The items in red
are of note:
    20:31:21 MONTR   $@NFT
    20:31:21 USER   NFT>*SET DEFAULTS MIM:: /USER:
    20:31:21 USER   NFT>*SET DEFAULTS MIM:: /PASSWORD:
    20:31:21 USER   NFT>*SET DEFAULTS MIM:: /ACCOUNT:
    20:31:21 USER   NFT>*SET DEFAULTS MIM:: /OSTYPE:RSX11  ;<-- NEW
    20:31:21 USER   NFT>*DIR MIM::FIX.T20;0
    20:31:21 USER
    20:31:21 USER   [Fork NFT opening DCN:MIM-FAL for reading, writing]
    20:31:23 USER %Remote OS type /different/ from that specified with
    SET DEFAULT
    20:31:23 USER
    20:31:23 USER     MIM::DU1:[DECNET]
    20:31:23 USER   FIX.T20;161;P775656             18 35840(8)
    18-Oct-2022 09:59:43
 There is nothing fatal about the message, but it was surprising. Investigating the parse
table for OSTYPE in NFT.MAC shows:
    OSTTBL: XWD OSTSIZ,OSTSIZ               ;ARGUMENTS FOR /OSTYPE
             T (IAS,.OSIAS)                  ;Operating system type
    ;       T (OS-8,.OSOS8)
             T (RSTS,.OSRST)
             T (RSX11,.OSRXM)
             T (RT11,.OSRT)
             T (TOPS10,.OSTP10)
             T (TOPS20,.OSTP20)
             T (VMS,.OSVAX)
 So the above shows only a single RSX parse item and I had wondered about that, given all
the various flavors of RSX. Further investigation into DAPSYM.MAC shows what Tops-20 DAP
actually knows about (in octal).
         .OSRT==1        ;RT-11
         .OSRST==2       ;RSTS/E
         .OSRXS==3       ;RSX-11S
         .OSRXM==4       ;RSX-11M
         .OSRXD==5       ;RSX-11D
         .OSIAS==6       ;IAS
         .OSVAX==7       ;VAX/VMS
         .OSTP20==10     ;TOPS-20
         .OSTP10==11     ;TOPS-10
         .OSOS8==12      ;OS-8
         .OSRXP==13      ;RSX11-M PLUS
 That's more like it, I would assume.  So I guess the fix here is to put a few more
entries into the NFT parse table.
 Johnny, which one of the above is MIM:: reporting?  I guess 13? 
 
 -- 
 Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
 email: bqt(a)softjar.se <mailto:bqt@softjar.se>             ||  Reading murder books
 pdp is alive!                     ||  tryin' to stay hip" - B. Idol
 _______________________________________________
 HECnet mailing list -- hecnet(a)lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se>
 To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
<mailto:hecnet-leave@lists.dfupdate.se>