DUMPSCAN Command

Purpose

Use DUMPSCAN for interactively analyzing and debugging problems in a dump. After you start a session, you can use the DUMPSCAN subcommands described in DUMPSCAN Subcommand Reference.

Operands

filename

is the file name of the CMS file containing a dump to be processed.

DUMPnnnn

is the file type of the dump to be processed. The file type must be eight characters long, consisting of the string DUMP and a four-digit number, nnnn. The default file type is DUMP0001.

*

fm

is the file mode of the dump file. If you do not specify the file mode, or if you specify an asterisk, DUMPSCAN uses the standard CMS search sequence.

Usage Notes

1. The DUMPSCAN session file has the same file name as the dump file. The file type is VIEWnnnn where nnnn is the number from the dump file type, DUMPnnnn.
2. DUMPSCAN modifies and re-records the symptom record to contain the dump name. Any modification made by the guest through user exits is also recorded.
3. If the dump is in one of the supported formats and the corresponding extraction routine is available, DUMPSCAN runs the routine to update information in the dump's symptom record and information record. See Using Attachment Interfaces for information about exit routines and supported dump types.
4. If you enter DUMPSCAN without operands, you are prompted for the dump file name, file type, and file mode.
5. The dump viewing session can be filed on your A-disk with the XEDIT FILE subcommand. When you view the same dump later, the saved file is reactivated and the new session is appended to the dumpname DUMPnnnn file containing the previous sessions.

Messages/Return Codes

Return Code

Explanation

0

Successful completion

20

Invalid file ID

24

Command line error

28

Nonexistent CMS file

32

Invalid data in file

36

Disk not accessed

41

Insufficient storage

50

CP dumps are not supported. Use VM Dump Tool

100

FSREAD/PRINTL error

104

Internal processing error