Adaptive Server is IPv6-unaware, by default. To make Adaptive Server IPv6-aware, you must start Adaptive Server with trace flag 7841. This causes Adaptive Server to determine IPv6 availability and makes Adaptive Server IPv6-aware.
See your Network or IT specialist to configure your platforms and Network Infrastructure correctly for IPv6 support.
A second trace flag, 7815 can be set when you start Adaptive Server which captures and logs address connection requests and host / name lookups.
The IPv6 Adaptive Server traceflags:
T7841 – Enable Adaptive Server IPv6-awareness
T7815 – Report all Adaptive Server IPv4 & IPv6 Client address connect requests
Before starting Adaptive Server for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, an IPv6 connection handler can be configured and enabled. Configuring and enabling the IPv6 connection handler requires adding an additional DCL entry. A single Adaptive Server configuration can typically carry up to 32 connection handler assignments within the DCL.
For example if you have a Site-local setup with two domains administrated under the name server setup:
sybase.com - being responsible for all IPv4 networking applications v6.sybase.com - being responsible for all IPv6 networking applications
The DCL entry for Adaptive Server to start named “SYBASE” on the host “revival” for port 17100 would typically look like:
SYBASE master tcp ether revival.sybase.com 17100 query tcp ether revival.sybase.com 17100 master tcp ether revival.v6.sybase.com 17100 query tcp ether revival.v6.sybase.com 17100
In the above example, when Adaptive Server is started with IPv6-awareness it creates two connection handlers. One listens on port 17100 for incoming IPv4 Clients connection requests, and the other listens on port 17100 for incoming IPv6 Clients connection requests.
