Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!NIHCU!RAF From: RAF@NIHCU.BITNET (Roger Fajman) Newsgroups: bit.listserv.nodmgt-l Subject: Re: :routtab tableformat for NJEF Message-ID: Date: 10 Feb 90 01:46:32 GMT Sender: Node Management Discussion Reply-To: Node Management Discussion Lines: 55 Approved: NETNEWS@PSUVM Gateway Comments: To: MAINTCMS@PUCC.BITNET, NODMGT-L@BITNIC.BITNET > In the same vein of removing local info from the :routtab tag, Mike > Gettes and I have talked a little about the O= value for JES2 systems. > I'm not familiar with how the routing tables for JES2 works. Is there > any reason a generic table couldn't be created (with the node number > in the appropriate field but without the offset applied) and then post > process this table to add the local offset value? Would some JES2 > folk post how those numbers are used? Here's a sample from NIHCU's January 1990 routing table, created by GENROUTS: N0200 NAME=CUNYVM,NONETATH,NODEVATH,NOJOBATH,NOSYSATH,SNA CONNECT NODEA=0200,MEMBA=1,NODEB=1852,MEMBB=1,REST=2 /* -> CUNYVMV2 */ N0201 NAME=AKRON,NONETATH,NODEVATH,NOJOBATH,NOSYSATH,SNA CONNECT NODEA=0201,MEMBA=1,NODEB=0227,MEMBB=1,REST=2 /* -> CSUOHIO */ N0202 NAME=ANLCHM,NONETATH,NODEVATH,NOJOBATH,NOSYSATH,SNA CONNECT NODEA=0202,MEMBA=1,NODEB=0207,MEMBB=1,REST=2 /* -> ANLOS */ The Nnnnn statements are defining the node numbers and names, plus other attributes of the nodes. We use a starting node number of 200 (O=199). The CONNECT statements are defining the connections between the nodes. NODEA and NODEB are specifying the node numbers of the two ends of the connection. MEMBA and MEMBB are specifying particular machines in a loosely coupled complex. "/* whatever */" is a comment. We run JES2 2.2.0. Other versions use somewhat different formats, but the information is the same. JES2 uses the CONNECT statements to figure out what link it needs to send a particular file on. If the Network Path Manager is used, then the CONNECT statements are omitted and JES2 figures out for itself dynamically what is connected to what. Information is passed around the network for this purpose. Currently only JES2 has a Network Path Manager, so all BITNET nodes are defined with CONNECT statements. By the way, it is possible to define multiple connections, loops, etc. JES2 will use resistances to figure out with path to use. The BITNET tables to do make use of this capability because other NJE software does not support it. To answer the question, yes, it would be possible to post process a routing table to add in the offset. Why that would make sense is a lot less clear to me. If you are going to do that, you might as well run some program to generate your own routing table from scratch (GENROUTS or a replacement for it). GENROUTS and GR do run on MVS. I don't know about Pathalias/Fastrout. I've been using GENROUTS for several years and am quite satisfied. Before that my routing table got lost in transit more than once.