The primary output from a successful Receive_Allocate call is the conversation ID, which uniquely identifies the conversation that was received. A server uses the conversation ID to communicate with the transaction program that initiated the conversation (the client TP). The conversation ID is required as input to other APPC/MVS callable services, such as the LU 6.2 Send and the CPI-C Receive services. Once a server obtains the conversation ID, communications can proceed between the partner programs (client TP and server) until one partner ends the conversation.

For information about using APPC/MVS TP conversation services, see z/OS MVS Programming: Writing Transaction Programs for APPC/MVS.