Advanced Program-to-Program Communication Extensions › Client/Server Connection Mode

Client/Server Connection Mode

During server process creation and initialization, all client connection requests that target the process remain pending until the server declares its operational mode for client connection. It can choose to automatically accept new connections, request notification before accepting connections, or reject connections.

Connections only apply to new conversations targeting an active process such as:

• Any standard transaction where the TCT entry indicated a server name as target, and the server is active
• Any ATTACH transaction that targets a server name, and the server is active
• Any CONNECT transaction that always targets an active NCL process

However an explicit conversation transfer request, resulting from an &APPC TRANSFER operation, is not considered a connection request and its mode of operation is unchanged.

The connection mode chosen by the server depends upon whether it intends to serialize connection processing, or operate multiple conversations concurrently. It can also depend on whether the server makes any use of the PIP data sometimes present with new conversations.