The documentation portal is undergoing maintenance. During this period, you can't create any new user credentials. If you do, you'll need to recreate the user credential after the maintenance period ends.
The TCPIP_ACCEPT_NONBLOCK statement specifies whether the TCP/IP ports on which the PowerExchange Listener listens are blocking or nonblocking ports.
Define TCPIP_ACCEPT_NONBLOCK=Y if the following conditions apply:
You perform a security check by using a port scanner such as Nessus.
The PowerExchange Listener appears to hang indefinitely on the main Listener port or ignore commands.
A Listener port for a netport job is defined.
z/OS
No
TCPIP_ACCEPT_NONBLOCK={
N
|Y}
N
.
PowerExchange Listener listening ports are blocking ports. When a blocking port is accessed, it blocks other attempts to access the port.
Y.
PowerExchange Listener listening ports are nonblocking ports.
Default is N.
If you perform a security check by using a port scanner such as Nessus, the PowerExchange Listener might hang indefinitely on the main Listener port or ignore commands if a Listener port for a netport job is also defined. The problem occurs when a call to the TCPIP accept() function on the netport port is blocked until a connection is present. While the netport port is blocked, the main PowerExchange Listener port is never polled, so that non-netport requests appear to be hung. The Listener remains in this state until a subsequent netport request unblocks the netport port.
If this situation occurs, include the TCPIP_ACCEPT_NONBLOCK=Y statement in the DBMOVER configuration file on the Listener machine. This statement makes the PowerExchange Listener listening ports nonblocking, so that the accept() call can return a suitable status if it fails.