Creating a Route Permission Table
You can create a route permission table with a standard text editor.
● You must create a separate route permission table for each SAProuter in your network.
● If no specific route permission table has been assigned to the SAProuter, ./saprouttab is used on UNIX and iSeries. The saprouttab file in the working directory of the SAProuter (<lwk>:\usr\sap\saprouter) is used on Windows. If this file is not available, SAProuter terminates with an appropriate message.
You can use generic entries ('*') in hosts, ports, and passwords.
You can use sub-networks in host routes. Examples:
156.56.*.* |
All host addresses beginning with 156.56 |
133.27.17.* |
All host addresses beginning with 133.27.17 |
133.27.16.0/24 |
All host addresses beginning with 133.27.16 (0/24 at the end means that the first 24 bits are relevant, that is, the first three blocks) |
156.56.1011xxxx.* |
All host addresses from 156.56.176.* to 156.56.191.*. (Binary interpretation of the third byte of the address. ‘x’ is a freely selectable binary value (1 or 0).) |
You can display an example of a route permission table on the screen. To do this, enter saprouter to call the SAProuter online help:
For examples of route permission tables, see:
Example of a Route Permission Table
Example of a Route Permission Table with SNC
More Information
Route String Entry for SAProuter
Route Connects (in the implementation part)