@Seymour: The two TCBs have different functions and I got a dump which shows when the AS created by TCB1 terminates, the exit from TCB2 got driven, leading to an 0C4 because the input requirements are different.
@Rob: Thanks for the detailed reply, I will reply to each of your points: (o): Each ASCRE is issued from a different TCB that have their own work storage obtained. (o): The ODAs are as expected, I use the returned ECBs to coordinate with an AS initialisation module. The RC is zero. (o): See above about ECBs. I started up a transaction with TCB1 which completes after creating a new AS. I then do a transaction with TCB2 and it creates a new AS. I then do another transaction with TCB1 and when its AS terminates I get an abend 0C4 in the exit in the code running under TCB2. This gives the impression that TCB1's exit has been replaced by TCB2's. (o): The code containing the two exits is all still in memory. I too doubt there is a problem with ASCRE but was wondering if there is a system limitation that one AS can only have one ASCRE termination exit active at one time. Where does the TRMEXIT address get saved? At TCB or ASCB level? Anyway, though an interesting problem, I need this to work and the obvious solution is to code one independent exit that will work with both types of transaction. Thanks to all who replied. 😊 Robin -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Rob Scott Sent: 22 April 2021 22:59 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ASCRE termination exits: how many? The address of the TRMEXIT is stored in the ASCRE parameter list prior to the PC routine that invokes the ASCRE service. If the newborn ASID-1 runs TRMEXIT-2, I would imagine that either the parmlist for ASCRE-1 is the same as the one for ASCRE-2 or the TRMEXIT-1 address is in fact TRMEXIT-2. To debug, I would consider the following : (o) : Are you using the same storage area for the MF=L form for both invocations of ASCRE? If so, what happens when you use different ones? (o) : What are the contents of the ODA after both ASCREs have been issued and what are the RC+RSN codes for both services? (o) : The creating TCB could wait on an ECB that will be POSTed by the newborn ASID-1 jobstep code when it starts and then only perform ASCRE-2 for ASID-2 afterwards. (o) : Is the storage containing TRMEXIT-1 and TRMEXIT-2 as expected and not released or re-used when ASID-2 terminates. It is unlikely that there is a problem with ASCRE. Rob Scott Rocket Software From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Robin Atwood Sent: 22 April 2021 14:15 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ASCRE termination exits: how many? EXTERNAL EMAIL I disagree. It says the termination routine is run under the creating TCB, it doesn't say what happens if another ASCRE has been issued with a different exit. I have a dump of an abend in one of the exits which has the right parameter list and TCB but the code is the wrong exit. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Binyamin Dissen Sent: 22 April 2021 19:40 To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: ASCRE termination exits: how many? The manual documents otherwise: "Specifies the address of the termination routine that gets control when the new address space terminates. The routine receives control in 31-bit addressing mode as an asynchronous exit in the creator's address space under the creator's TCB." I would suggest that you display your parameter lists and verify that you are requesting what you expect. And validate which TCB is running the exit. On Thu, 22 Apr 2021 18:26:38 +0700 Robin Atwood <abend...@gmail.com<mailto:abend...@gmail.com>> wrote: :>I issue an ASCRE macro with TRMEXIT specified and a new AS is started. Then :>from another TCB I issue an ASCRE with TRMEXIT :> :>specifying a different exit routine and a second AS is started. When the :>first created AS terminates which TRMEXIT gets driven? I :> :>had assumed that the TRMEXIT would be associated with the TCB that owned the :>new AS and you could have different exit :> :>routines for different TCBs, but testing seems to show that the last :>specified TRMEXIT gets called. So is it correct to say that you :> :>can only have one TRMEXIT routine per address space? :> :> :> :>Thanks :> :>Robin :> :> :> :> :> :> :>---------------------------------------------------------------------- :>For IBM-MAIN subscribe / signoff / archive access instructions, :>send email to lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN -- Binyamin Dissen <bdis...@dissensoftware.com<mailto:bdis...@dissensoftware.com>> http://www.dissensoftware.com<http://www.dissensoftware.com> Director, Dissen Software, Bar & Grill - Israel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu<mailto: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<mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- 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
