PREFERENCE

Required? Yes
Keyword Type Enumerated
Default USE_DEFAULT_PREFERENCE
Multiples Allowed? No, only one for each PARTNER_LU keyword
   PREFERENCE = (
      @TYPE = ENUMKEYWORD
        @ENUM_LIST = (
         NATIVE = 0
         NONNATIVE = 1
         NATIVE_THEN_NONNATIVE = 2
         NONNATIVE_THEN_NATIVE = 3
         USE_DEFAULT_PREFERENCE = 255
      )
      @REQUIRED = 1
      @DEFAULT = USE_DEFAULT_PREFERENCE
    )
The PREFERENCE parameter specifies the type of routing that you want the node to use by default. Valid values are:
NATIVE
Use native (APPN®) routing protocols only.
NONNATIVE
Use nonnative (AnyNet®) protocols only.
Note:
This value is only meaningful when an AnyNet® DLC is available to the Node Operator Facility, and there is an AnyNet® link station defined. (See LINK_STATION).
NATIVE_THEN_NONNATIVE
Try native (APPN®) protocols, and if the partner LU can not be located, retry session activation using nonnative (AnyNet®) protocols.
Note:
This value is only meaningful when an AnyNet® DLC is available to the Node Operator Facility, and there is an AnyNet® link station defined. (See LINK_STATION).
NONNATIVE_THEN_NATIVE
Try nonnative (AnyNet®) protocols, and if the partner LU can not be located, retry session activation using native (APPN®) protocols.
Note:
This value is only meaningful when an AnyNet® DLC is available to the Node Operator Facility, and there is an AnyNet® link station defined. (See LINK_STATION).
USE_DEFAULT_PREFERENCE
Use the default preference defined when the node was started. (This can be recalled by QUERY_NODE.)

This parameter is required. The default is USE_DEFAULT_PREFERENCE.

Note:
The PREFERENCE parameter cannot be set using the SNA Node Configuration application.