IPCS Concepts

Figure 1 gives an overview of how IPCS works.

Figure 1. Overview of IPCS
Overview of IPCS

IPCS accepts unformatted dumps and traces as input. It uses members of parmlib to locate control block models and exit routines. The models and routines allow IPCS to format and analyze the contents of the dump or trace data set. IPCS produces three types of output: symptom strings placed in the headers of dump data sets, control block symbols and mappings of storage saved in a dump directory, and formatted reports that the user can view at a terminal or print.

The data sets that can be directly accessed by IPCS are shown to the left and below the IPCS box in Figure 1. As of z/OS® V1R11, all these data sets are supported in cylinder-managed space. The following table gives more details.
Data sets that can be accessed by IPCS directly Comments, regarding placement in cylinder-managed space
TRACE data set TRACE data sets for wrap-type traces stored in non-VSAM data sets must be initially recorded in track-managed space. IPCS, however, supports the use of COPYTRC to transcribe completed traces of this type into data sets in cylinder-managed space.
SVC dump data set  
Abend dump data set  
Stand-alone dump data set DASD data sets directly used by SADMP must initially reside in track-managed space. IPCS, however, supports the use of COPYDUMP to transcribe stand-alone dumps.
Dump directory (VSAM data set)  
IPCSTOC and IPCSPRNT In addition to DASD and tape storage devices, IPCSTOC and IPCSPRNT files can be directed to hardcopy printed destinations.