Outsort Assignment

The outsort assignment follows the primary endpoint assignment. It is recommended for the functionality to be contained in a node. This section describes an example of using an esort node to contain the tables that perform the look ups.

The example node XML stanza shows outsorting based on a combination of the routing transit and account fields and a combination of the routing transit and auxiliary fields:

<?xml version="1.0"?>
<nodeDescriptor name="OutsortNode" type="ESORT">
  <tasks>
    <task name="OutsortRtAccTask"/>
    <task name="OutsortRtAuxTask"/>
  </tasks>
  <connections>
    <connection srcName="OutsortRtAccTask" dstName="OutsortRtAuxTask" 
                results="FAILURE"/>
  </connections>
</nodeDescriptor>

One of the XML stanzas for the table would be:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dataDescriptor name="OutsortRtAccTask" type="TABLE" ignoreBadKey="true">
  <viewName>OutsortRtAccTask</viewName>
  <fileName>OutsortRtAccTable.tbl</fileName>
  <record>
    <field datatype="byte" length="2"  name="ibmValOutsortPrefix" type="key"/>
    <field datatype="char" length="9"  name="ibmNprRT"            type="key"/>
    <field datatype="char" length="20" name="ibmNprAccount"       type="key"/>
    <field datatype="char" length="10" name="ibmNprEndpoint"      type="payload"/>
  </record>
</dataDescriptor>

The OutsortNode receives the outsort prefix as read by the endpoint assignment node. It first executes the routing transit and account look up. If the look up is successful, the endpoint is reassigned and the node exits. If the look up fails, the second table is used to try to reassign the endpoint. If both look ups fail, the node exits without changes to the endpoint.

Note: The table headings in gray are key fields.

Table 1. Example Table for Routing Transit and Account
Outsort Prefix	Routing Transit	Account Start	Account End	Endpoint
3	555555555	0000001	9999999	02127265
3	555555555	00000001	99999999	02800030
3	555555555	000000001	999999999	02800030

Table 2. Example Table for Routing Transit and Auxiliary
Outsort Prefix	Routing Transit	Aux Start	Aux End	Endpoint
7	555555555	1000	9999	02127265
7	555555555	100000	999999	02800030
8	666666666	1234	1234	02800030

When configuring multiple tables for field combinations, the order of the tables can impact the endpoint that is assigned. If one table does routing transit and account as a direct look up and the other does it as a range, both tables contain the same prefix and routing transit values.

The result the user wants in this scenario is to assign 11111111 for account 0000002. If the second table is configured to be called first, 22222222 is assigned.

Table 3. Example Table for Routing Transit and Account
Outsort Prefix	Routing Transit	Account	Endpoint
1	555555555	0000002	11111111

Table 4. Example Table for Routing Transit and Account
Outsort Prefix	Routing Transit	Account Start	Account End	Endpoint
1	555555555	0000001	9999999	22222222