.-ALIASRCH--=--YES-----. >>-+----------------------+------------------------------------>< | .-YES-. | '-ALIASRCH--=--+-----+-' '-NO--'
| statement: | ADJCP |
| dependencies: | BN=YES; APPN only |
- ALIASRCH=YES
- Specifies that inbound ALIAS searches from this adjacent control point (ADJCP) are allowed.
- ALIASRCH=NO
- Specifies that inbound ALIAS searches from this adjacent control point (ADJCP) are halted at the defining node. Code ALIASRCH=NO to configure border nodes so that they prevent unwanted ALIAS searches received from one or more adjacent non-native nodes from entering the native APPN network.
Tip: You can dynamically change the ALIASRCH value for one or more adjacent CP definitions without restarting VTAM®. If a definition for the adjacent CP to be changed has already been activated, then you must first deactivate the entire ADJCP major node containing that definition. (Deactivating a predefined ADJCP major node does not cause links or CP-CP sessions to stop. Rather, the adjacent CP definitions for nodes that currently have active connections to this node are moved to the dynamic ADJCP major node, ISTADJCP. During this process, the current ALIASRCH value in effect is preserved.) After you modify or create the necessary ADJCP minor node definitions, and you activate the ADJCP major node, VTAM updates these definitions immediately if the NETID operand is specified on the ADJCP minor node. If you do not specify the NETID operand on the ADJCP minor node, then you must stop (at the same time) all the links to this adjacent node and restart them for the updated definitions to be used.
Rule: The ALIASRCH operand can be specified only on ADJCP definitions that are activated on border nodes (BN=YES). The ALIASRCH operand is ignored and an error message is issued if the activating node is not a border node.