CICS® dump allows you to specify areas of main storage to be dumped, by means of the DUMP TRANSACTION , onto a sequential data set, which can be either on disk or tape.
The PERFORM DUMP command allows you to request a system dump. See the CICS System Programming Reference manual for programming information about PERFORM DUMP.
You can format the contents of the dump data set and you can print them offline using the CICS dump utility program (DFHDU640) for transaction dumps or the interactive problem control system (IPCS) for system dumps. Instructions on using these programs are given in the CICS Operations and Utilities Guide.
Only one dump control command is processed at a time. If you issue additional dump control commands, while another task is taking a transaction dump, activity within the tasks associated with those commands is suspended until the dump is completed. Remaining dump commands are processed in the order in which they are made. Using the DUMP TRANSACTION command causes some fields (for example, EIBFN and EIBRCODE) in the EIB and the TCA to be overwritten.See the CICS Application Programming Reference manual for programming information about DUMP TRANSACTION.
Options on the DUMP TRANSACTION command allow you to dump the following areas of main storage in various combinations:
A dump of these tables is typically the first dump taken in a test in which the base of the test must be established; subsequent dumps are usually of the task-related storage type.
Program storage is not dumped for programs defined with the attribute RELOAD(YES).
You also get a list of the CICS nucleus modules and active PPT programs, indexed by address, at the end of the printed dump.
[[ Contents Previous Page | Next Page Index ]]