|
|
|
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.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |