APPC Management Tasks

The management tasks required to support APPC/MVS fall into four categories:

Program Management: After an installation has coded or acquired APPC applications, a programmer defines scheduling classes for the TPs and uses the administration utility or dialog to define TP profiles and side information.
Session Management: To enable TPs to communicate over the network, an installation must plan each LU 6.2 it needs and the characteristics of sessions that connect the LU to LU 6.2s on other systems. Each LU 6.2 is defined to APPC/MVS as a local LU, and to VTAM® in an APPL statement. Session definitions are determined by logon mode names that must first be defined in VTAM and must correspond to session characteristics defined on the partner system.
Security Management: Security of APPC/MVS can be controlled on the LU-to-LU level, LU-to-TP level, TP-to-TP level, LU-to-user level, and TP-to-user level. Some specific ways of controlling access are through defining TPs as RACF® resources, which controls access to TPs, and defining a pair of LUs as a RACF resource, which allows specific levels of conversation security.
System Management: To operate APPC/MVS, use various MVS system commands such as START, DISPLAY, SET, STOP, and CANCEL. To control how APPC work performs in relation to other z/OS work, create an SRM performance group for TPs scheduled by the APPC/MVS transaction scheduler and a second SRM performance group for any transactions processed by APPC/MVS servers. You can also use SMF records to audit TPs.

The remainder of this document is organized into four parts based on these management categories. The way the tasks are ordered is not, of course, the only way to order them; and the processes described are not performed only when APPC is first introduced on an z/OS system. The tasks and processes are ongoing. As an installation acquires more TPs, for example, those TPs must be defined, possibly creating the need to add an LU or change an existing LU.