Re: routing entries

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

>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



When your job enters the subsystem it is 'routed.'  The subsystem uses the
compare value of each routing entry to see if the job matches the specified
condition.  If it matches, then that routing entry is used.

The routing entries are evaluated in numerical order.

If you had the following:

        200     compare 'qcmdb'
        300     compare 'qcmd'

then jobs with 'qcmdb' would be processed by #200.  'qcmda' and 'qcmdc'
thru 'qcmdz' would 'fall through' #200 and would be caught by #300.

That's why you have to be careful when you add new entries-- you have to
watch out for duplicate conditions.

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| 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
+---