LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Doron Shikmoni <P85025@BARILVM>
Thu, 24 Mar 88 09:44:05 P
text/plain (22 lines)
>> One quick question....it appears that it is possible to have
>> a bitnet nodename that has a dash in it, like BU-ACC. Can anyone
>> think of a reason why I could not use this as a nodename?
>> I don't see any. (FYI: there is no rscs nodename with a '-' in it now).
>>             - Michael Gettes, Boston University
>
>I looked in the JES2 manuals and the NJE Protocol Handbook to see
>what characters are allowed in a node name.  I couldn't find any
>clear statement of it.  I think, given all the different software
>out there, that there is bound to be some packages that don't expect
>dashes in NJE node names.
 
Yep, Roger, and you'll find one like this close enuf... JES2; it will
not accept a dash in a node name (unless you make a mod - very trivial
one, but still you have to *do* something or the node tables will be
rejected).  And BTW, the same "parameter parsing" rule (SCANTAB)
requires the first byte of a nodename to be alphabetic or "special
national" ($@#), so an all-numeric nodename won't work either on
the vanilla system.
 
Doron

ATOM RSS1 RSS2