Signing On to the API
The communication address used to establish a connection to IBM® Connect:Direct® is determined by the TRANSPORT parameter defined in the SIGNON command. The default for the TRANSPORT parameter is NET (NETMAP) which means that the protocol defined in the NETMAP Adjacent node entry is used. For more information, see Adjacent Node Definition Examples.
Parameter Value | Description |
---|---|
TRANSPORT = NET | Default. When TRANSPORT is defined as NET, the sign on process retrieves the Adjacent node entry to determine if the TCPAPI parameter has been defined. If TCPAPI exists, then a TCP connection is attempted using the communication address defined. The communication port number is obtained from the TCPAPI parameter, and if the IP address exists in the TCPAPI parameter, it is also used. If the IP address does not exist in the TCPAPI parameter, it must be obtained from either the Adjacent node or the LDNS parameter. If the TCPAPI does not exist, the APPLID parameter is retrieved and SNA is used as the protocol. |
TRANSPORT = SNA | When TRANSPORT is defined as SNA, the sign on process retrieves the Adjacent node entry to determine the APPLID parameter, and SNA is used as the protocol. If the APPLID parameter does not exist, then an ESF SIGNON is performed. |
TRANSPORT = TCP | When the TRANSPORT is defined as TCP, the communication address must be specified on the SIGNON command. For more information, go to the IBM Sterling Connect:Direct for z/OS® Administration Guide and search for Initializing IBM Connect:Direct without SNA Support. |
Adjacent Node Definition Examples
To only allow SNA API signons:
|
To only allow TCP API signons using an IPv4 address:
|
To only allow TCP API signons using an IPv6 address:
|
To only allow TCP API signons using the LDNS parameter:
|
To allow both SNA and TCP API signons:
|