The following trace points are generated in a Java™ environment and then mapped to the listed CICS® trace points. This approach means that any number of trace points can use each of the trace points in table Table 51. The interface defines 15 different trace types. It is also possible to determine whether the trace point is an entry or an exit, which gives a total of 16 different trace point IDs (RASITraceEvent types). Setting CICS trace at a particular level can generate several of these RASITraceEvent types. As is generally the case in CICS, these trace levels are exclusive, for example trace level 2 does not include trace level 1. These trace types and the corresponding CICS trace levels are explained in table Table 52.
The second data field is optional and can be omitted when it offers no additional information (such as on a TYPE_ENTRY_EXIT event, where the class and the method name are all that is needed). The remaining data passed on the call, which can vary at run time, is inserted into the remaining fields. In the event of a trace event having more than 6 objects to trace, it spills over to one or more additional trace points where the second and subsequent trace points have a sequence number in parentheses appended to the class and method names, for example (2), (3), and so on.
Point ID | Class | Lvl | RASITraceEvent type | Data |
---|---|---|---|---|
AP 1800 | CICSTraceService.class | AP 1 | TYPE_API |
|
AP 1801 | CICSTraceService.class | AP 2 | TYPE_CALLBACK |
|
AP 1802 | CICSTraceService.class | AP 1 | TYPE_ENTRY_EXIT (Entry) |
|
AP 1803 | CICSTraceService.class | AP Exc | TYPE_ERROR_EXC |
|
AP 1804 | CICSTraceService.class | AP 2 | TYPE_MISC_DATA |
|
AP 1805 | CICSTraceService.class | AP 2 | TYPE_OBJ_CREATE |
|
AP 1806 | CICSTraceService.class | AP 2 | TYPE_OBJ_DELETE |
|
AP 1807 | CICSTraceService.class | AP 2 | TYPE_PRIVATE |
|
AP 1808 | CICSTraceService.class | AP 2 | TYPE_PUBLIC |
|
AP 1809 | CICSTraceService.class | AP 2 | TYPE_STATIC |
|
AP 180A | CICSTraceService.class | AP 2 | TYPE_SVC |
|
AP 180B | CICSTraceService.class | AP 1 | TYPE_LEVEL1 |
|
AP 180C | CICSTraceService.class | AP 2 | TYPE_LEVEL2 |
|
AP 180D | CICSTraceService.class | AP 3 | TYPE_LEVEL3 |
|
AP 180E | CICSTraceService.class | AP 2 | TYPE_PERF |
|
AP 180F | CICSTraceService.class | AP 1 | TYPE_ENTRY_EXIT (Exit) |
|
RASITraceEvent type | CICS trace level | Meaning |
---|---|---|
TYPE_API | 1 | Defines an application programming interface (API) trace point. |
TYPE_CALLBACK | 2 | Defines a callback method trace point |
TYPE_ENTRY_EXIT | 1 | Defines method entry and exit trace points |
TYPE_ERROR_EXC | off | Defines an error or exception condition trace point |
TYPE_MISC_DATA | 2 | Defines a miscellaneous data trace point |
TYPE_OBJ_CREATE | 2 | Defines an object creation (constructor) trace point |
TYPE_OBJ_DELETE | 2 | Defines an object deletion trace point |
TYPE_PRIVATE | 2 | Defines a private method trace point |
TYPE_PUBLIC | 2 | Defines a public method trace point. (This typically includes package and protected scope, as all of these methods may be used by other classes.) |
TYPE_STATIC | 2 | Defines a static method trace point |
TYPE_SVC | 2 | Defines a service code trace point. Service code is generally "low-level" code which provides commonly used services to other classes |
TYPE_LEVEL1 | 1 | Defines a "low-detail" trace point |
TYPE_LEVEL2 | 2 | Defines a "medium-detail" trace point |
TYPE_LEVEL3 | 3 | Defines a "high-detail" trace point |
TYPE_PERF | 2 | Defines a performance-monitoring trace point |