That's a great idea! Thanks a bunch! The JS can actually attach both the ORIGINAL and the SERVICE tasks, thus easily fixing the issue at once =================================== In the OP's case, he does not get control in order to issue the DETACH - the DETACH is issued by the system when the JS ends.
Also, the DB2 messages are not issued by an ESTAE - it is by the DB2 RTM. It would be quite tricky to get DB2 to skip the RTM routine. It appears that there are two issues - (1) to prevent the JS from the X03 abend (2) to avoid the messages from the subtask There is the requirement that the JS black box not be altered One option would be to replace the JS in the JCL to attach a new task that attaches the original JS task and ends when it does. Then the service subroutine can run in the new JS task and will clean up when the original JS ends. Even a LINK may be adequate. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
