If a memory dump is to be sent to your customer support center for analysis, you must first run DUMPANALYZER on the dump and use the SAVE command. In general, use the SAVE command if you are saving the dump for analysis at a later date, when the dumping MCP code file might not be available.

The SAVE command creates a saved dump, which contains the memory image from the original dump together with relevant data from the dumping MCP code file. The saved dump is usually an extremely large file and is often stored on tape. Do not label-equate MCPCODEFILE when you create a saved memory dump.

When you run DUMPANALYZER to analyze a saved dump file, file-equate the file TAPEIN to the saved dump file. You do not have to file-equate the MCPCODEFILE, and the MCP code file that produced the dump does not need to be present.