>If you can provide the PTF level of nucleus module IEAVESPI, we could set a SLIP SET,IF,N=IEAVESPI,xxx,xxx) in it at some offset where it has decided that it will be invoking an ESPIE exit.
I may consider this and will come back to you in that case. Thanks. >SLIP gets called from RTM. Of course, now that you remind me. How could I forget about this :-( I assume this is true only for error type SLIPs, other SLIPs are recognized in other parts of processing. PER type SLIPs are probably handled by PGM check FLIH, since A PER event is a PGM check event. RTM is not invoked for those; they are not errors. Message ID traps are maybe handled in WTO processing. I may as well be completely wrong with this. SLIP command description has the following note for the COMP= operand: Note: 1. The SLIP action is not taken when the abend completion code is originally a program check (code 0C4) that the system converts to a new value. The following abend completion codes may be originally a program check and converted ones: 11A, 12E, 15D, 15F, 200, 212, 25F, 279, 282, 42A, 430, 57D, 700, 72A, A00, B00, and E00. This is not all too clear for me. Firstly, why is there the text "(code 0C4)" in the first sentence? Is this meant as an example, or is it meant to say the note only applies to 0C4s? Secondly, is the list of abend codes in the second sentence the complete list of completion codes which fall into this category? If so notge 1 would not apply to a PGM check 4 which was percolated and finally lead to an S0C4-4 abend so the abend would be trapped. The same would apply to an PGM 11 converted to a S0C4-11. Can you clarify, please, Jim? >I have not found any such documentation. There is probably room for some documentation improvements in that area. Shall I open an RCF? If so what manual for? -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
