The Initialize_Conversation call (function name cminit) is issued by the invoking program to obtain an 8-byte conversation identifier and to set the initial values for the conversation's characteristics.
CM_ENTRY Initialize_Conversation(
unsigned char FAR *conversation_ID,
unsigned char FAR *sym_dest_name,
CM_INT32 FAR *return_code
);
This parameter is an 8-byte ASCII character string. The allowed characters are as follows:
This parameter can also be set to eight spaces. In this case, the invoking program must issue the following calls before issuing Allocate:
The conversation is in RESET state.
If the return_code is cm_ok, the conversation changes to INITIALIZE state. For other return codes, the conversation state remains unchanged.
The initial values are CPI-C defaults or are derived from side information associated with the symbolic destination name. For more information about initial values and side information, see Initial Conversation Characteristics and Side Information.
Initial values can be changed by the Set_ calls.
If the side information contains an invalid value or a Set_ call sets a conversation characteristic to an invalid value, the error is returned on the Allocate call.
If a CPIC application attempts to invoke more than one concurrent conversation, only a single Local APPC LU is used by all conversations. This prevents concurrent conversations across two or more dependent LU6.2 LU's, causing subsequent Initialize_Conversation (CMALLC)calls to wait for the first conversation to be deallocated.
If the CPIC application needs to invoke more than one concurrent conversation, independent LU6.2 must be used between Microsoft® SNA Server and the remote system.
Upon successful execution of this call, CPI-C generates a conversation identifier. This identifier is a required parameter for all other CPI-C calls issued for this conversation by the invoking program.