Closing the SSCP Connection

To close the system services control point (SSCP) connection, an application sends a Close(SSCP) Request to the local node, which responds with a Close(SSCP) Response. The Close(SSCP) Request is unconditional. The Close(SSCP) Response always reports that the connection was successfully closed. The Close(SSCP) Response is provided so that applications can determine when outstanding data and status messages on the session have been delivered.

If the logical unit (LU) is bound, the local node sends a TERM-SELF message to the SSCP on behalf of the application to elicit an UNBIND. An application that needs to be unbound can issue Close(PLU). (For more information, see Closing the PLU Connection.) Normally, the SSCP connection can be maintained while the application task is active, even if it is idle.

Closing the connection invalidates the locality, partner, index (LPI) pair for the connection, but does not alter the state of the SSCP session. The following figure shows the message flow.

Message flow for closing a connection

See Also

Opening the SSCP Connection
SSCP Session
RTM Parameters]
3270 User Alerts