Conversation Security Mechanisms

In addition to LU security mechanisms, for APPC applications whose security type is SAME or PGM (for which a user ID is passed on the allocate request), APPC/MVS provides the following conversation security mechanisms as well:

Establishing a TP security environment on MVS
Controlling user access to LUs
Controlling user access from LUs
Controlling user access to TP profiles and side information, and tailoring TP work attributes
Controlling the ability to collect API trace data for conversations
Persistent verification (PV)

For more information about these conversation security mechanisms, see Conversation Security: Protecting APPC/MVS TPs.

Remember, the APPC/MVS security mechanisms primarily protect MVS and the TPs that run on it. Other operating systems that support APPC, such as Microsoft Windows, Sun Solaris, AIX®, OS/400®, OS/2, and VM, generally offer their own security mechanisms to protect TPs at their end of a conversation. If your cooperative processing applications include TPs on systems other than MVS, consult that system's documentation for information on protecting those TPs.