Using integrated Xsockets

Follow these instructions to use the Xsockets tool on an integrated client.

  1. From a command line, add the library in which the Xsockets tool exists to your library list by issuing this command:
    ADDLIBLE <library-name>
    where the <library-name> is the name of the library you created during integrated Xsockets configuration. For example, if the name of the library is MYXSOCKET, then enter:
    ADDLIBLE MYXSOCKET
  2. On a command line interface, enter:
     CALL TSOXSOCK
  3. From the Xsocket window that is shown, you can access all socket routines through its menu bar and selection field. This window is always shown after you choose a socket API. You can use this interface to select socket programs that already exist. To work with a new socket, follow these steps:
    1. In the list of socket APIs, select socket and press Enter.
    2. In the socket() prompt window that displays, select the appropriate Address Family, Socket Type, and Protocol for the socket, and press Enter.
    3. Select Descriptor and select Select descriptor.
      Note: If other socket descriptors already exist, this displays a list of active socket descriptors.
    4. From the list that displays, select the socket descriptor that you created.
      Note: If other socket descriptors exist, the tool automatically applies a socket API to the latest socket descriptor.
  4. From the list of socket APIs, select a socket API with which you want to work, whatever socket descriptor you chose in step 3c is used on that socket API. As soon as you select a socket API, a series of windows are displayed where you can provide specific information about the socket API. For example, if you select connect(), you need to provide the address length, address family, and address data in the resulting windows. The socket API chosen is then called with this information that you provided. Any errors that occur on a socket API are displayed back to the user as an errno.
Notes:
  1. The Xsockets tool uses the graphical support for DDS. Thus, how data is entered and how selections are made from the windows you see depend on whether you are using a graphical display station or a nongraphical display station. For example, on a graphical display station, you can see the selection field for the socket APIs as a check box; otherwise, you might see a single field.
  2. Be aware that there are ioctl() requests that are available on a socket which have not been implemented in the tool.