Starting a Conversation

To start a conversation with a partner TP, a local TP calls the Allocate service. On the call to Allocate, specify the conversation type (basic or mapped) and the destination (a symbolic destination name or explicit values for the partner TP name, LU name, and session mode). Also specify whether or not the conversation will include confirmation requests (a sync_level of none or confirm).

To protect against unauthorized conversations, Allocate must include the security information that the partner expects. Specify which of the following levels of security information you are providing:

Security_none: Specifies that no user ID, password, or profile (RACF group name) is passed for verification.
Security_same: Specifies that the same user ID and possible profile name that were used to allocate the local program are being passed on the current allocate call.
Security_pgm: Specifies that a user ID, password, and profile name are being provided for the partner LU to verify. If surrogate authorization is used, only the user ID is required. For more information, see z/OS MVS Planning: APPC/MVS Management.