I think "percolate" simply means to pass back control to whatever comes next. It could be another ESTAE, or it could be back to the SLIH.
Lennie -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Charles Mills Sent: 08 March 2022 16:58 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESTAE and IEBCOPY What happens when IEBCOPY cancels its ESTAE which is earlier in the chain than the ESTAE hypothetically established in the exit? Is it an error to cancel a "middle" ESTAE, or does z/OS gracefully remove it from the middle of the chain? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lennie Dymoke-Bradshaw Sent: Tuesday, March 8, 2022 8:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESTAE and IEBCOPY Untried suggestion. Since the error is passed to the latest ESTAE created, you may be able to get control at an exit point in IEBCOPY that is taken *after* IEBCOPY's ESTAE is established. You would need to establish code which takes the details you need and then allow the error to percolate to the next ESTAE, which would be IEBCOPY's ESTAE. The description of exit points in IEBCOPY is in the manual, but it may take you some trial and error to determine whether IEBCOPY has already established his ESTAE. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
