The confirm action requests the partner to confirm receipt of the prior data.

The confirmed action returns the confirm request.

The connect action connects to the server or queue. The connect action must have a Connection Specification as a parameter to define what to connect to.

The destroyPart action destroys the part and its children, and releases all associated resources. You can use this action for both visual and nonvisual parts. All connections to the destroyed part are removed.

The disconnect action disconnects from the current server or queue.

The receive action receives one complete send from the partner.

If the local buffer is smaller than the total amount of data sent in one send command from the partner TP, then the receive command will read multiple times to read all the data from that one send. If partner TP does multiple sends, then local TP must do an equal number of receives to match.

The receive action ends whenever the server disconnects.

The receiveBuffer action receives a single buffer.

The receiveWithLengthInData action receives the record with the length of the record already initialized.

The sendBuffer action sends the buffer to the server.

The sendErrorDirectionReceived action sends a message specifying where the error occurred, either when the message was received or after the message was processed.

The sendIncorporatingLength action sends the data with four bytes prefixing the data. The four byte prefix contains the length of the data.

The sendRecord action sends the record to the server after converting it to a buffer.

The sendString action sends a string to the server after converting it to a buffer.

The sendStringAsLLAsciiZ action sends the given string after first appending a one-byte length at the front and appending a zero at the end.