Change an entry in the transaction dump table.
SET TRANDUMPCODE >>-SET TRANDUMPCODE(data-value)--+--------------+---------------> +-ACTION(cvda)-+ +-ADD----------+ +-REMOVE-------+ '-RESET--------' >--+-----------------+--+---------------------+-----------------> +-DUMPSCOPE(cvda)-+ '-MAXIMUM(data-value)-' +-LOCAL-----------+ '-RELATED---------' >--+------------------+--+------------------+-------------------> +-SHUTOPTION(cvda)-+ +-SYSDUMPING(cvda)-+ +-NOSHUTDOWN-------+ +-NOSYSDUMP--------+ '-SHUTDOWN---------' '-SYSDUMP----------' >--+-------------------+--------------------------------------->< +-TRANDUMPING(cvda)-+ +-NOTRANDUMP--------+ '-TRANDUMP----------'
Conditions: DUPREC, INVREQ, IOERR, NOSPACE,
NOTAUTH,
NOTFND
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The SET TRANDUMPCODE command allows you to change the transaction dump table entry for a particular dump code, to add a new dump code to the table, or to delete one.
The table entry tells CICS the actions to take when a transaction dump request with this code is received. Possible actions include taking a transaction dump, taking a system dump (an MVS SDUMP), initiating requests for SDUMPs of related CICS regions, and shutting down CICS. The table entry also indicates how many times this set of actions is to be taken (the MAXIMUM value); after the maximum is reached, requests are counted but otherwise ignored.
Table updates are recorded in the CICS global catalog and preserved over executions of CICS until an initial or cold start occurs, except in the case of temporary table entries. CICS creates a temporary entry when it receives a dump request with a code for which there is no table entry; these entries, and any changes to them, last only for the current execution of CICS. If you want preserve changes to a temporary entry over restarts, you need to remove the dump code from the table and then add it back.
For information about transaction dumps, see the CICS® Problem Determination Guide.
A related CICS region is one in the same sysplex, connected by MRO/XCF and doing work on behalf of the task that caused the dump request----specifically, a region that has a task doing work under the same APPC token as this task.
This propagation of SDUMP requests occurs only when the table entry for this code also specifies a SYSDUMPING value of SYSDUMP, and only in a sysplex environment executing under MVS/ESA 5.1 and the MVS workload manager. In other systems, specifying RELATED causes an exception condition.
CVDA values are:
LOCAL is the default for entries you add, if you do not specify a DUMPSCOPE value.
If this option is omitted from an ADD request, NOSHUTDOWN is assumed.
If this option is omitted from an ADD request, NOSYSDUMP is assumed.
If this option is omitted from an ADD request, TRANDUMP is assumed.