Before a TP running on an z/OS system can use APPC/MVS to converse, system programmers must provide the information z/OS needs to support the TP's conversations. Communication requirements must be determined and translated into LUs and VTAM® session definitions. In addition, TPs must be defined to the system and grouped according to scheduling classes. If the conversations require security, RACF® provides various methods to secure all or part of the supporting APPC/MVS structure.

These considerations and many more fall under the category of APPC/MVS management, the topic of this document.