home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!lll-winken!ptavv.llnl.gov!oberman
- From: oberman@ptavv.llnl.gov
- Newsgroups: comp.os.vms
- Subject: Re: Nodename 15 chars??
- Message-ID: <1992Aug26.170703.1@ptavv.llnl.gov>
- Date: 27 Aug 92 01:07:03 GMT
- References: <1992Aug21.145443.8936@bsu-ucs.uucp> <2314.2a9b5b3b@decus.ch>
- Sender: usenet@lll-winken.LLNL.GOV
- Lines: 23
- Nntp-Posting-Host: ptavv.llnl.gov
-
- In article <2314.2a9b5b3b@decus.ch>, b_sanderson@decus.ch (Bruce Sanderson ABB Process Automation) writes:
- > In article <1992Aug21.145443.8936@bsu-ucs.uucp>, 00mjstum@bsu-ucs.uucp (Matthew J. Stum) writes:
- >> This may sound like a stupid question, but why does $GETSYI's SYI$_NODENAME
- >> return up to _15_ characters? I was under the impression that nodenames
- >> were restricted to 6 characters.
- >>
-
- > PROBABLY DUE TO THE FACT THAT SOON DECNET PHASE 5 WILL BE OUT (OSI CONVENTIONS)
- > (EQUIVALENT OF NODENAMES WILL BE LONGER)
-
- If you check the Phase V planning docs you will see that 15 won't come close to
- a full name. Maybe 1024? But this is the SCSNODE, not the DECnet node. I don't
- know of any reason that it should be limited to 6 characters except the sanity
- of having the DECnet node name and the SCSNODE agree. But Phase V will make
- that obsolete.
-
- I imagine it was a semi-arbitrary decision, in reality.
-
- R. Kevin Oberman Lawrence Livermore National Laboratory
- Internet: koberman@llnl.gov (510) 422-6955
-
- Disclaimer: Don't take this too seriously. I just like to improve my typing
- and probably don't really know anything useful about anything.
-