Supervisor state, AR mode and key 0 don't affect execution of an ESTAE. If as you say (ESTAE is set and you BALR to another routine), then your ESTAE will be called. Either you are not telling us everything we need to know or you are telling us something that is wrong. This is why we the source would be extremely helpful because we are just guessing.
If you are telling us everything, then the only possibility is that your ESTAE routine is also abending with a S0C4. Did you analyze the dump? Try changing your ESTAE program so that DC X'FFFF' ABEND is the first statement. This will cause a S0C1 to be displayed if your ESTAE get's control. Your ESTAE may be running in the wrong key to analyze the abend. Jon Perryman On Friday, August 29, 2014 8:19 AM, MichealButz <[email protected]> wrote: I do establish the estaex in the cmdproc the authorized program at the time it is in problem state ASC primary I load a program BALR to it at the time of the abend Iam in Supervisor state ASC AR storage key 0 does that matter. For my recovery routine to get control > >What I wll do under TESTAUTH is do a LISTTCB at the time I establish the >esate(x) and another LISTTCB when I am in ASC AR supervisor state storage key >0 and see it thr TCB is the same > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
