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


Tracking Changes to the APPC/MVS Configuration and Workload

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

During APPC/MVS initialization and processing, the system issues ASBxxx and ATBxxx messages to the master console, or a console with master authority. These messages primarily report only errors, or status changes that might require operator intervention. Messages that report successful processing generally are routed to hardcopy, thus reducing message traffic on the console. z/OS MVS System Messages, Vol 3 (ASB-BPX) describes the ASBxxx and ATBxxx messages.

This message design, along with the cumulative effects of parmlib members and possible command processing delays, might require you to rely on the DISPLAY command to obtain current, detailed information about the APPC/MVS configuration and workload. To tailor information to your specific needs, enter the DISPLAY APPC and DISPLAY ASCH commands, as shown in summary tables beginning with Displaying TP Status, with operands that filter the information returned to the console. The underlined keywords are defaults; you can omit them when you issue the command.

To monitor SET command changes to APPC/MVS parmlib members, you can also review the contents of SMF type 90 records. Every time a SET command is issued, SMF records the parmlib information associated with the SET. The SMF type 90 record is useful for tracking changes to the APPC configuration. z/OS MVS System Management Facilities (SMF) describes the format and contents of type 90 records.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014