Conversation Security for an Outgoing Allocation Request

A remotely started transaction program (one started by another transaction program) can validate a user ID and password before it allocates a conversation to a third transaction program. In such a case, the security(SAME) parameter in the [MC_]ALLOCATE and [MC_]SEND_CONVERSATION verbs can indicate that the conversation security is already verified. The second Attach automatically gets the user ID from the first Attach, that started the first conversation.

APPC can obtain the current user ID and send it, with an indicator that the user ID was validated. In the Attach for a locally started transaction program that uses the security(SAME) parameter in either the [MC_]ALLOCATE or the [MC_]SEND_CONVERSATION verb, the partner must be able to accept the already validated indication.

Refer to System Management Programming for more information about using the user ID and password.