Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!UCONNVM.BITNET!ART From: ART@UCONNVM.BITNET ("Arthur Radcliffe Jr.") Newsgroups: comp.protocols.ibm Subject: (none) Message-ID: <8901071746.AA18422@jade.berkeley.edu> Date: 6 Jan 89 17:37:40 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: "Arthur Radcliffe Jr." Organization: The Internet Lines: 18 We are beginning to migrate our network from non-SNA to an SNA implementation. I have seen IBM references concerning naming conventions for SNA resources. I am not sure how good their suggestions are. In particular, the naming convention for terminals. In the Publications I have looked at, they suggest Tssliapt, where "T" is for (remote) terminal, "ss" is for owning Subarea, "lia" is for the line address in the 37xx, "p" is for the PU sequence, and "t" is for LU sequence. For local terminals they recommend Hsscuutt. In this case they allow 2 bytes for the LU sequence. Might it be better to drop the H and T from the LUNAME's thereby allowing 2 bytes for the remote LU sequence? Since we will be tagging Devices with the LUNAME, I would like to come up with a decent naming convention that will handle growth later on. I would appreciate hearing from people who have an SNA network and wouldn't mind sharing some of their ideas about resource naming conventions. Are IBM's from the ADVANCED COMMUNICATIONS FUNCTION PRODUCTS INSTALLATION GUIDE GG24-1557 good ones? Thanks, Art.