DFHTR0112 applid Bad data passed for tracing to module modname.
Explanation
Some data passed to the trace (TR) domain for addition to the internal trace table, auxiliary trace data set or GTF trace caused a program check when an attempt was made to access it.
This could either be as a result of a request made by CICS system code or a request made by a user program through the API or XPI.
If transaction isolation is active, this message can be issued if a transaction passes another transaction's storage to CICS. A program check occurs when CICS attempts to trace this storage because the storage is fetch protected.
System action
A system dump with dump code TR0112 is taken.
If the message was issued by DFHTRPT the dump contains an exception trace entry (point ID TR0102) that includes the erroneous parameter list passed to DFHTRPT.
If the message was issued by DFHTRFT the dump contains an exception trace entry (point ID TR0402) that includes the erroneous parameter list passed to DFHTRFT.
Message DFHME0116, which contains the symptom string for this problem, is produced.
User response
Examine the interpreted exception trace entry to determine the domain that issued the call and the ID of the entry. Then look at the specified addresses and lengths in the datan fields to see if they contain reasonable values. The fault is in the module that set up these fields for the trace call.
If transaction isolation is active, examine the calling domain's parameter list, data2, for storage that belongs to another transaction. Correct the offending application program. It should not be passing another transaction's storage. Alternatively, alter the definition of the application so that it can validly access another transaction's storage. See the Defining resources for more information on how to alter the definition.
Module
XMEOUT parameters/Message inserts
- applid
- modname
Destination
Console