IKJEFT1B is the batch TSO processor. It wants to set a return code so it has captured the 04C abend allowing it to set the return code. I don't think IKJEFT01 does that.
I suggest that you have a range of expected return codes that don't need recovery and anything else requires recovery. TSO and batch TSO intercept abends in many places (REXX, clist, command processors and ...), so there is no guarantee you will capture every abend you expect to capture. If you still insist on capturing abends, then rather than frontending TSO, you could have IKJEFT1B call your program (as a command processor) and your program would strip it's program name from the command and call IKJEFTSR to issue the original command. As I said before, it won't capture every abend but it will allow the MVS return code to be set where as IKJEFT01 won't give you the return code. Regards, Jon Perryman. ----- Original Message ---- From: Phil <[email protected]> u I'm trying to front-end some existing IKJEFT1B job steps to do some setup & checking before and cleanup after. In my testing, any abend generates an 04C, which is fine, however my ESTAI routine does not seem to get control in this case for me do the cleanup (which could be disastrous). Anyone have experiences with this? I suppose I could go back to IKJEFT01. :(
