Previous Topic: IntroductionNext Topic: Viewing Dumps from TSO/ISPF


Customizing Dump Capture

When dump capture is initialized on a system, a copy of the options table (CADVTABL) is loaded into resident storage in the common system area. These options remain in effect until dump capture is refreshed or until an IPL, both of which reload the options table. During dump capture, options are never retrieved from disk, only from the resident copy of CADVTABL.

You must customize your options table, CADVTABL, to control dump capture at your site before initializing dump capture. It is shipped with default settings that must be modified before initializing the dump captures facility. The following sections briefly describe each of the customizations you can perform. Before customizing your options table, see the Installation Guide for detailed instructions.

This section contains the following topics:

Selecting Dumps for Capture

Selecting a Dump Index File

Allocating Dump Data Sets

Selecting Diagnostic Reports

Initializing Dump Capture

Selecting Dumps for Capture

You add the inclusion and exclusion criteria to the options table (CADVTABL) to control which system dumps are captured. Every time a system dump occurs, CA SymDump System compares the dump capture inclusion and exclusion entries in the CADVTABL to the user ID, the jobname, and the abend or error code associated with the dump. Before a dump is captured, at least one of the defined inclusion criteria must be met. If any of the exclusion criteria are met, the capture is suppressed.

Even when a dump satisfies the selection criteria, you can exclude the dump from capture by including the following DD statement in the JCL for the abending step:

//CADVSTOP DD DUMMY

For more information, see the appendix “Special DD Statements.”

For details about specifying the inclusion and exclusion criteria, see the appendix “Customizing Options Using CADVTABL” in the Installation Guide.

User exit CADVUSR1 permits more complex determination to be controlled at your site. For more information about the user exit, see the appendix “User Exits.” The options table also contains a duplication limit to prevent excessive captures for duplicate dumps.

Selecting a Dump Index File

The options table contains the name of your currently active dump index file. You can use one dump index file for your entire site or you can use multiple index files for multiple systems. Either way, dump viewers can access any existing dump index file at any time.

To use a single dump index for all of your systems, simply define that index in the options table. For multiple index data sets, you must maintain multiple copies of the options table.

Allocating Dump Data Sets

Each dump capture consists of two separate dump data sets. The smaller of the two, typically referred to as the reports data set, contains all of the reports produced during the dump capture. The reports data set also contains a storage index used to map the contents of the larger data set—the storage data set. The storage data set is populated by an SDUMP and is compatible with IBM's IPCS product. The storage data set is typically the same size as most SVC dumps.

The options table contains a single high-level qualifier that must be used when dynamically allocating both dump data sets during capture. The two lowest-level qualifiers of each data set name are constructed dynamically to maintain uniqueness.

The options table also contains two separate sets of values that control the space allocations and destination of each dump data set. Therefore, it is possible for the larger storage data sets to be cataloged on a different volume than the smaller reports data sets, if you want.

When defining the destination of the dump data sets, you can either use a specific UNIT and VOLUME name or allow the data set to be managed by SMS by specifying a management, storage or data class name.

Regardless of how your dump data sets are defined, it is never necessary for any end user to know the name or location of a dump data set. All captured dumps are logged in the dump index, and the dump viewer displays the list using dump attributes and data set names. For example, when selecting a dump for viewing, an end user might select the dump from a S0C4 in job PAYROLLA that occurred on June 23, 2009 at 11:33am.

Selecting Diagnostic Reports

When a dump is captured, the reports data set is populated with information about your system and the dumping address space as defined by your installation. CA SYSVIEW (or Server) produces most report information but some reports are provided exclusively for CA SymDump System users.

Report generation during dump capture is controlled using a list of commands located in the OPTLIB control file. The OPTLIB members are distributed with CA SymDump System, but are customized and maintained outside the control of SMP/E. Within each OPTLIB member is a list of commands used to control report generation during dump capture. Report production during a dump capture is determined primarily by which OPTLIB member is selected at the time of the dump.

During a dump capture, the OPTLIB member is selected as follows:

Within each member, control statements must begin in position one with each statement having the following syntax:

<title>command

title is optional and, if present, defines the report title, as it appears in the dump viewer when the report is displayed. title must be enclosed in less than and greater than signs (< >) and must start in position one.

Note: Reports having a title starting with an exclamation point (!) appear in the Favorites folder during dump viewing. For more information about the Favorites folder, see the chapter "Viewing Dumps from TSO/ISPF."

command refers to any CA SYSVIEW (or Server) command (or command list). These commands are described in the CA SYSVIEW Administration Guide.

Additionally, command can refer to any of the following CA SymDump System commands:

These commands and the reports they produce are described in the appendix "CA SymDump System Reports."

An asterisk (*) in position one denotes a comment and is ignored during dump capture.

Initializing Dump Capture

Dump capture can be initialized or terminated on any system using the Resource Initialization Manager (CAIRIM), a component of CA Common Services for z/OS as described in the Installation Guide. This process should occur automatically at every IPL on systems where dumps are captured.

For more information on initializing and disabling dump capture, see the installation step Activate the Dump Capture Facility in the Installation Guide.