Point ID | Module | Lvl | Type | Data |
---|---|---|---|---|
|
||||
AP E110 | DFHEISR | AP 2 | Entry |
|
AP E111 | DFHEISR | AP 2 | Exit |
|
AP E112 | DFHEISR | Exc | Recovery |
|
AP E113 | DFHEISR | Exc | Storage not within DSA |
|
AP E114 | DFHEISR | Exc | INQUIRE_ACCESS request failed |
|
AP E115 | DFHEISR | Exc | Invalid function |
|
AP E116 | DFHEISR | Exc | GETMAIN request failed |
|
AP E117 | DFHEISR | Exc | Invalid data length |
|
AP E118 | DFHETC | Exc | LENGERR |
|
AP E119 | DFHEIQVT | Exc | Invalid response from ZOPA |
|
AP E11A | DFHEKC | Exc | WAIT EVENT bad ECB address |
|
AP E11B | DFHEIQSK | Exc | WAIT CICS® bad ECB address |
|
AP E11C | DFHEIQSK | Exc | WAIT EXTERNAL bad ECB address |
|
AP E120 | DFHSAIQ | AP 1 | Entry |
|
AP E121 | DFHSAIQ | AP 1 | Exit |
|
AP E122 | DFHSAIQ | Exc | Recovery |
|
AP E130 | DFHEISP | AP 2 | Entry |
|
AP E131 | DFHEISP | AP 2 | Exit |
|
AP E133 | DFHEISP | Exc | Invalid EIEI function |
|
AP E134 | DFHEISP | Exc | Recovery |
|
AP E135 | DFHINDSP | EI 1 | Entry |
|
AP E136 | DFHINDSP | EI 1 | Exit |
|
AP E137 | DFHINDSP | Exc | Recovery |
|
AP E138 | DFHINDSP | Exc | Invalid format |
|
AP E13A | DFHINTRU | Exc | RMLN add link failed |
|
AP E13B | DFHINDT | Exc | RMLN start link browse failed |
|
AP E13C | DFHINDT | Exc | RMLN getnext link failed |
|
AP E13D | DFHINDT | Exc | RMLN end link browse failed |
|
AP E13E | DFHINDT | Exc | RMUW inq unit of work failed |
|
AP E13F | DFHINDT | Exc | RMLN Unexpected reason |
|
AP E140 | DFHINDT | Exc | RMLN init recovery failed |
|
AP E141 | DFHINDT | Exc | RMLN set recovery status failed |
|
AP E142 | DFHINDT | Exc | RMLN term recovery failed |
|
AP E150 | DFHEIP | AP 2 | Entry GETMAIN/FREEMAIN subroutines |
|
AP E151 | DFHEIP | AP 2 | Exit GETMAIN/FREEMAIN subroutines |
|
AP E160 | DFHEISR | AP 2 | Entry |
|
AP E161 | DFHEISR | AP 2 | Exit |
|
Note:
The entries AP E160 and
AP E161 trace the interface between an application and CICS. The entries represent
the command and its parameters as passed to CICS and as returned to the application. The interpreted data from the data 1 field is shown in the interpretation string. The uninterpreted form of this data (in the data 1 field) is laid out as follows:
The first command and parameter data after the length bytes (bytes 1 and 2 of data 1) represent the values in arg0. Thereafter, they represent the application program commands. The interpretation string, in addition to containing the formatted data 1 information, tells you:
It is advised that traces containing entries AP 150, AP 151, AP 160, and AP 161 be formatted with the FULL trace control statement. Using the ABBREV trace control statement results in interpretation strings which do not give the same level of information. |