RE: routing entries

System checks for matching routing data starting at sequence 1.  Usually
you have a sequence 9999 catch-all entry of *ANY.
This allows sort of generic matching on routing data.  For example:

Seq #           Routing Data

50      DEPT5
51      DEPT50
52      DEPT501
53      DEPT502
54      DEPT503

Etc.

... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


        -----Original Message-----
        From:   Paul Ellison [SMTP:ellison@harolds.net]
        Sent:   Tuesday, February 03, 1998 3:01 PM
        To:     'Midrange ListServ'
        Subject:        routing entries

        I appreciate the answers to my last question very much!  It's
nice to have this resource out there.  Another question please:

        What exactly does the sequence # in the routing entries display
have to do with adding new entries.  Such as:

        seq nbr 200     compare 'QCMDB'
                9999    compare *any

        If I add an entry should it be above or below the QCMDB in the
sequence?  It's a live sbs and not too much experimental ability on the
system.  

        Thanks much in advance,



        Paul Ellison
        Technical Analyst
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---