(zos)

Bind-specific support for TCP/IP resources on z/OS

Bind-specific support enables you to control the use of the product TCP/IP resources.

This support allows you to have the Application Server ORB and other products and applications on the same z/OS system without requiring the client code to configure unique ports. In other words, this support allows use of port 2809 by the Application Server and other products and applications on the same system. This support allows the utilization of multiple TCP/IP stacks (Common INET) by the product ORB and the use of multiple IP addresses on the same TCP/IP stack.

To use bind-specific support, use the ORB_LISTENER_ADDRESS end point, which specifies the IP address in dotted decimal format. The application servers listen for client connection requests on this IP address.

Restriction: DNS host names are not supported for the ORB_LISTENER_ADDRESS end point value.

Because a given IP address is associated with a given TCP/IP stack, we can specify the ORB_LISTENER_ADDRESS endpoint so that the applications servers use a specific TCP/IP stack.

In addition, because we can define multiple IP addresses for a given TCP/IP stack, the Application Server port 2809 servers could share the same TCP/IP stack with other products and applications requiring port 2809, because you made their IP addresses unique with the ORB_LISTENER_ADDRESS end point.

Alternatively, we can, without the use of bind-specific support, define alternate ports for port 2809 and the location service daemon, which are the only values defined by the CORBA standard. However it is not clear that all client ORBs will easily support configuring the Application Server port to something other than 2809. Configure the ports for the location service daemon and node by specifying port numbers on the z/OS location service daemon settings page in the console.

For more information about multiple TCP/IP stacks (Common INET), see z/OS UNIX System Services Planning. For more information about multiple IP addresses on the same TCP/IP stack, see z/OS Communications Server: IP Configuration Reference.


Related tasks

  • WebSphere variables

  • Ports settings