Use the BLDDUMP BUILD command to define the protection scheme for a dump file when you create it. The PROTECT command enables you to change the protection scheme of an existing dump file. You can either protect a dump file from overwrites by subsequent dumps-to-disk or leave it unprotected.
Protected dump files |
 |
The BLDDUMP utility enables you to protect valuable dump information from accidental overwrites by subsequent dumps. If a protected dump file is empty, however, it is available for a subsequent dump.
If you have only one dump file configured on your system, you must check its status regularly and minimize the amount of time that it is unavailable for subsequent dumps.
Unprotected dump files |
|
If you choose to have a dump file unprotected, the system can write to it repeatedly; however, each time that the system writes to an unprotected dump file, any previous dump information in that file is lost.
Protection scheme alternatives |
|
If you configure only one dump file for AutoRestart/iX, you should protect it. You must also regularly monitor dump-to-disk activity, so that you can analyze dump information quickly and reset the dump file (empty the contents). If you configure two or more dump files, protect the first file shown by the LIST command.
While you analyze the information in your first (protected) file, the system writes any subsequent dumps to the additional dump file. When you finish analyzing the protected file, you can store it to tape (if necessary) before you use the RESET command to set the file content status to zero.
