The system dump table
Table 1 shows two examples of the sort of information that might be maintained in the system dump table for different system dump codes.
| Type of information | Example 1 | Example 2 |
|---|---|---|
| System dump code | SYDMP001 | MT0001 |
| Take a system dump? | YES | YES |
| Take system dumps on related systems? | YES | NO |
| Is the dump eligible for DAE? | YES | NO |
| Shut down CICS? | YES | NO |
| Maximum times action can be taken | (default) | 999 |
| Times action already taken | 0 | 79 |
| System dumps taken | 0 | 79 |
| System dumps suppressed | 0 | 0 |
The sort of information kept in the system dump table
is similar to that kept in the transaction dump table (see Table 1).
- Example 1 shows a system dump table entry for system dump code SYDMP001, a user-supplied system dump code, specified using EXEC CICS PERFORM DUMP. System dumps on related systems are to be taken. Dumps duplicate of this one are to be suppressed by DAE. The table entry shows that no dumps have yet been taken. However, if one were taken, CICS would be shut down. If global suppression of system dumping was in effect, no dump would be taken but CICS would be shut down if this dump code were referenced.
- Example 2 shows the system dump table entry for system dump code MT0001, the CICS-supplied dump code for system dumps requested from the main terminal, with CEMT PERFORM DUMP or CEMT PERFORM SNAP. CICS is not shut down when a dump is taken for this dump code. Also, the value of 999 for “maximum times action can be taken” shows that an unlimited number of dumps can be taken for this dump code. The current count (“times action already taken”) shows that to date, 79 dumps have been requested using CEMT.