You must define listening sockets and ports, as described in Define listening sockets/ports (required).
Rule: If you use a unique application-instance
DVIPA for the Advisor in a CINET environment, all TCP/IP stacks on
that system must code the VIPARANGE statement for that DVIPA. Alternatively,
and less desirably, you can establish stack affinity to one of the
TCP/IP stacks that are coded with the VIPARANGE statement for that
DVIPA, if you do not have VIPARANGE coded for that DVIPA on all of
the TCP/IP stacks on that system. This alternative, of course, does
not enable the Advisor to be moved to another TCP/IP stack in the
event of failure, unless you are able to restart the Advisor with
a different start procedure that can establish stack affinity to another
TCP/IP stack that has the DVIPA defined in a VIPARANGE statement.
For information on the use of the _BPXK_SETIBMOPT_TRANSPORT environment
variable that can be used to establish stack affinity, see
Generic server versus server with affinity for a specific transport provider.
The lb_connection_v6 statement does for IPv6 what the lb_connection_v4
statement does for IPv4. You can specify either or both of these statements.
If you run the Advisor on a CINET system, be aware that the address
or addresses you choose for these statements tie the Advisor to the
stack owning those addresses. Consequently, termination of that stack
results in termination of the Advisor.