The transaction dump table

Table 1 shows some examples of the sort of information that might be maintained in the transaction dump table for different transaction dump codes.
Table 1. Examples of transaction dump table entries
Type of information Example 1 Example 2 Example 3
Transaction dump code MYAB ASRA AKC3
Take a transaction dump? YES NO NO
Take a system dump? YES YES NO
Take system dumps on related systems? NO YES NO
Shut down CICS? NO NO NO
Maximum times dump code action can be taken 50 30 999
Times dump code action already taken (current count) 0 30 37
Transaction dumps taken 0 0 0
Transaction dumps suppressed 0 30 37
System dumps taken 0 30 0
System dumps suppressed 0 0 37
  • Example 1 shows a transaction dump table entry for transaction dump code MYAB. This is a user-supplied dump code, specified either on an EXEC CICS DUMP TRANSACTION command, or as a transaction abend code on an EXEC CICS ABEND command.

    The table entry shows that when this dump code is invoked, both a transaction dump and a system dump are to be taken, and CICS is not to be terminated. System dumps on related systems are not to be taken. The dump code action can be taken a maximum of 50 times, but the action for this dump code has not been taken since CICS was started or since the current count (“times dump action taken”) was reset.

  • Example 2 shows a transaction dump table entry for transaction dump code ASRA. This is a CICS transaction abend code, and this dump table entry is referred to every time a transaction abends ASRA. The entry shows that a system dump only is to be taken for an ASRA abend, and that CICS is not to be terminated. System dumps on related systems are to be taken. It also shows that the action for this abend code has already been taken the maximum number of times, so no action is taken when another ASRA abend occur. However, the current count could be reset to 0 dynamically using either a CEMT transaction or a system programming command (SET TRANDUMPCODE or SET SYSDUMPCODE). More system dumps would then be taken for subsequent ASRA abends.
  • Example 3 shows a transaction dump table entry for transaction dump code AKC3. This is a CICS transaction abend, and this dump table entry is referenced every time a transaction abends AKC3 - that is, whenever the master terminal operator purges a task.

    The entry shows that no action at all is to be taken in the event of such an abend. System dumps on related systems are not to be taken. The maximum number of times the dump code action can be taken is given as 999, meaning that there is no limit to the number of times the specified action is taken. The dump code action has been taken 37 times, but each time both the transaction dump and the system dump were suppressed.

Table 2 shows how the transaction dump table entry for transaction dump code MYAB would be updated with and without global suppression of system dumping. Only the updated fields are shown.
Table 2. Effect of global suppression of system dumping on transaction dump table update
Type of information Before update System dumping enabled System dumping suppressed
Transaction dump code MYAB    
Take a transaction dump? YES    
Take a system dump? YES    
Take system dumps on related systems? NO    
Shut down CICS? NO    
Maximum times action can be taken 50    
Times action already taken 0 1 1
Transaction dumps taken 0 1 1
Transaction dumps suppressed 0 0 0
System dumps taken 0 1 0
System dumps suppressed 0 0 1
The statistics show that a system dump was taken when system dumping was enabled, but not when system dumping was suppressed.
There is a further effect. CICS maintains a record of the current dump ID, which is the number of the most recent dump to be taken. This is printed at the start of the dump, together with the appropriate dump code. It is concatenated with the CICS run number, which indicates the number of times that CICS has been brought up since the global catalog was created, to provide a unique ID for the dump.
Note: This does not apply to SDUMPs taken by the kernel; these always have a dump ID of 0/0000.
For example, for the ninth dump to be taken during the eleventh run of CICS, if the dump code were TD01, this is what you would see:
    CODE=TD01 ID=11/0009
If system dumping is enabled for the dump code, the same dump ID is given to both the transaction dump and the system dump.


dfhs1lf.html | Timestamp icon Last updated: Monday, 5 June 2017