Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!QUEENSU!ANDREW.S.HOOPER From: Andrew.S.Hooper@QUEENSU.CA Newsgroups: bit.listserv.nodmgt-l Subject: Differences between Chris Thomas RSCS tables and NETSERV tables Message-ID: <14471*Andrew.S.Hooper@QueensU.CA> Date: 2 Feb 90 23:13:18 GMT Sender: Node Management Discussion Reply-To: Node Management Discussion Lines: 24 Approved: NETNEWS@PSUVM Gateway P1-Message-Id: CA**QueensU.CA;QueensU:MxPGO0RK X400-Trace: CA**QueensU.CA; arrival Fri, 2 Feb 90 17:13-0500 action Relayed Comments: To: Lance Wilkinson This is really getting a little tedious. Perhaps you should have read the specifications for the the RSCS routing tables before writing your code. Both GENROUTS and Chris Thomas' tables conform to the specifications. To quote from the IBM RSCS manual SH24-5005: "RSCS directory control statements must be in the following formats, with one or more blanks as operand delimiters. All operands are positional from left to right. ... Operands may be entered in columns 1 through 71. All data entered to the right of column 71, and all data entered to the right of the last possible operand are ignored. No continuation of RSCS directory control statements is provided. RSCS ignores completely blank records and records having an asterisk (*) in column 1, allowing these lines to be used for comments and print formatting. ... ROUTE locid linkid locid is the one- to eight-character location identifier of the remote location that is being defined for indirect communication. linkid is the one- to eight-character link identifier of the link on which transmissions destined for the remote location are to be made. This link must have been defined by a preceding LINK statement. ----- Andy Hooper Queen's Univ. Computing Services Bitnet: HOOPER@QUCDN Kingston, Ontario, Canada Telephone: +1 613 545 2019