Dump Creation
The z/OS® MVS™ System Commands reference (SA22-7627-xx) contains the most up-to-date information about using the DUMP command and this should ultimately be your source of information for taking dumps of z/OS address spaces.
For convenience however, here are the proper commands and format for capturing a dump of an OMEGAMON® address space at the time of this writing:
DUMP COMM=’...arbitrary dump title...’
The system will respond with a WTOR message like this:
*8297 IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND
You should reply:
R 8297,JOBNAME=stc_name,SDATA=(ALLNUC,CSA,LPA,PSA,RGN,SQA,SUM,TRT),END
Where stc_name is the name of the started task you are attempting to dump.
Some product components use data spaces as repositories for collected data. If your problem involves one of these components that you should use dump parameters that will cause the data space(s) to be included in the dump. The syntax for including the data space looks like the following:
R 8297,JOBNAME=stc_name,SDATA=(ALLNUC,CSA,LPA,PSA,RGN,SQA,SUM,TRT), DSPNAME=(’stc_name’.dspname,...),END
Use the following table to find the value for dspname:
| Component | Where to find it in the RKLVLOG |
|---|---|
| Dataset-level I/O statistics collector | The names are not in the log but they are 00001CND and 00002CND. |
| HSM Log Analyzer | Obtain from RKLVLOG msg KDFS210I |
| SMS MCDS Analyzer | Obtain from RKLVLOG msg KDFS208I |
| Dataset Groups | Obtain from RKLVLOG msg KS3G031I |
| RMM collector | Obtain from RKLVLOG msg KS3R204I |
| Dataset Attributes Database | Obtain from RKLVLOG msg KS3A000D |