Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!ig!agate!ucbvax!VENUS.YCC.YALE.EDU!LEICHTER From: LEICHTER@VENUS.YCC.YALE.EDU ("Jerry Leichter ", LEICHTER-JERRY@CS.YALE.EDU) Newsgroups: comp.os.vms Subject: re: DECnet Object Number vs. Network Name Message-ID: <8807060002.AA16893@ucbvax.Berkeley.EDU> Date: 4 Jul 88 04:37:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 20 I wonder if anybody could explain to me the practical differences between DECnet 'network name' and 'object number'. Using $QIO with the ACPCONTROL function I can assign either a name or a number to my task, but I cannot seem to find any information in the 'Guide to Networking on VAX/VMS' about why I should choose one over the other. (I'm wondering about this because I'm making a server which accepts multiple inbound connections....) Object numbers are intended for a small set of "well-known", standardized network objects. The set HAS to be small, since an object number is just a single byte! I suppose very simple-minded DECnet implementations might understand a couple of the standard numbers but not have the smarts to interpret an object name. Can't say I've ever heard of such an implementation, but it's possible.... I'd use an object name. -- Jerry