z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Managing APPC Work in the System

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

Managing any work in the system requires a set of performance objectives in terms of resources used, response goals, and service requirements. To achieve these objectives, an installation monitors how work is running in the system and then tunes the system to try to meet the performance objectives.

Incorporating new work, such as APPC, into a tuned system can affect system performance. The purpose of this chapter is to provide guidance to help you get the best performance possible for APPC work without upsetting the balance of existing work in the system.

The steps for measuring the effect of APPC work in your system and for tuning the system are listed below. Each step is described in more detail in the sections that follow.

  1. Consider the storage requirements of APPC/MVS
  2. Monitor APPC performance
    1. If resources used by TPs are charged to accounts, use SMF to audit APPC work.
    2. Use RMF reports to measure the performance of APPC as a whole, by class, by account number, or by single transaction program.
    3. Use the DISPLAY APPC and DISPLAY ASCH operator commands to take a "snapshot" of APPC work in the system.
  3. Improve performance by program design and administration
    1. Make efficient use of callable services.
    2. Be aware of keywords that cause performance degradation in the TP profile's JCL.
    3. Consider using multi-trans scheduling to enhance performance.
    4. Define classes for APPC work with appropriate response time goals.
    5. Put each multi-trans TP in its own class.
    6. Associate TPs to LUs with the appropriate level of access to eliminate unnecessary searching.
    7. Eliminate unnecessary use of the TP message log.
  4. Improve performance through system changes
    1. Consider the amount of buffer storage needed for received data.
    2. Improve verification performance of RACF® by using VLF. For complete information, see z/OS Security Server RACF System Programmer's Guide.
    3. Eliminate unnecessary SMF recording.
    4. Improve network performance.
    5. Minimize use of APPC component tracing.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014