Yes they will stay defined. If you define an ESTAE at the beginning of a program, outside of a linkage stack entry, you can create and delete all the linkage stack entries you want and it will still be there.
You could create a linkage stack entry on entry to your program rather than chaining save areas, create an ESTAE, and have stack entries below it and the ESTAE will be there until you do your final PC back to the system, not that I would recommend doing that. Chris Blaicher Technical Architect Mainframe Development P: 201-930-8234 | M: 512-627-3803 E: [email protected] Syncsort Incorporated 2 Blue Hill Plaza #1563 Pearl River, NY 10965 www.syncsort.com Data quality leader Trillium Software is now a part of Syncsort. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Joseph Reichman Sent: Tuesday, June 13, 2017 8:50 AM To: [email protected] Subject: Re: Estae and the Linkage Stack Will the ESTAE remain active if declared outside of the BAKR/PR pair David from you description it should > On Jun 13, 2017, at 3:55 AM, David Cole <[email protected]> wrote: > > BAKRs do not create or cancel ESTAEs. > > PRs do automagically cancel all ESTAEs created since the matching BAKR. There > is a bit (in the BAKR's stack entry I think. I forget which and where.) that, > when set on, causes an interrupt to occur when the PR is issued. This is how > z/OS gains control so that it can do the purge of the appropriate SCB[s]. > > I remember how surprised I was to discover this some years ago when I was > writing z/XDC's linkage stack support. > > Dave Cole > ColeSoft Marketing > 414 Third Street, NE > Charlottesville, VA 22902 > EADDRESS: [email protected] > > Home page: www.colesoft.com > LinkedIn: www.xdc.com > Facebook: www.facebook.com/colesoftware > YouTube: www.youtube.com/user/colesoftware > > > > > > > At 6/12/2017 06:24 PM, Joseph Reichman wrote: >> Hi >> >> I thought for the longest time that an ESTAE was associated with a Task. >> Then I saw a thread with Chris Blaicher where the upshot as that a >> BAKR would deactivate it >> >> I did a search on the archives but didn't come up with anything. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ________________________________ ATTENTION: ----- The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
