APPCDATA subcommand

The IPCS APPCDATA subcommand formats dump information within the APPC component. To request a particular report, specify the report type and a level of detail as parameters after the APPCDATA subcommand. If you do not specify parameters, you see a summary of all reports. For information about using IPCS and the syntax of the IPCS APPCDATA subcommand, see z/OS MVS IPCS Commands.

You can request the following report types:

Table 1. APPCDATA report types . Find the right APPC report using this table as a guide.
Report name: Report displays: See the topic about:
STATUS The overall status of the APPC component. APPCDATA STATUS subcommand output
CONFIGURATION The configuration of local logical units (LUs) in terms of their connections to partner LUs. APPCDATA CONFIGURATION subcommand output
CONVERSATIONS Each local transaction program (TP) and its conversations for a particular address space or all address spaces. If no address space identifier (ASID) is specified, information for every address space with a TP is displayed. APPCDATA CONVERSATIONS subcommand output
SERVERDATA Information about APPC/MVS servers and allocate queues. APPCDATA SERVERDATA subcommand output
FMH5MANAGER The number of TP FMH-5 attach requests that are waiting to be processed and information about the ones currently being processed. APPCDATA FMH5MANAGER subcommand output
CTRACE The status of component trace for APPC, trace options, and other trace-related information. APPCDATA CTRACE subcommand output

Each report comes in three levels of detail. If you do not request a level of detail, you see a summary of the report. You can request the following report levels:

Report level: Displays:
SUMMARY Summary information for the report type. If you do not request a level of detail, you will see the summary level of the report.
DETAIL Detailed information about from a specific report type.
EXCEPTION Inconsistencies detected in a specific report type. When there are no inconsistencies, the message “No exceptions detected” is displayed. Exception reports contain:
  • A message containing a reason code
  • A hexadecimal dump of damaged areas from the dump

IBM® might request this information for diagnosis.