Peter/Clark, Since we are a ISV, we try to intervene ourselves. My issue was on how to do it. I know LE but I am faced with we cant just convert to pure HLASM or even threaded C or C++ . So i have to come up with an alternative solution that works. We have been using Subpool 231 and it works fine except when an Operator becomes impatient and cancels the STC. I agree we use the PPT to enforce no cancel that would prevent one issue. But since we capture security (RACF, ACF2 and Top-Secret) events with exits and use SP231 as a place to store them, we have to think about data integrity and recovery. My thoughts thanks to Allan and the rest of you guys is maybe a DataSpace might be what we want to do.
Scott On Thu, May 16, 2019 at 7:39 AM Peter Relson <[email protected]> wrote: > The choices are between saving the data yourself as you go, such as by > some sort of checkpoint or other method, or saving the data yourself after > the cancel (for which some sort of TERM=YES ESTAE-type recovery is > necessary) or not allowing the CANCEL (whether by intercepting CANCEL or > making the job non-cancelable). > > There are PPT attributes pertaining to whether or not a job can be > canceled. I think that applies both to a job and to a started task. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- *IDMWORKS * Scott Ford z/OS Dev. “By elevating a friend or Collegue you elevate yourself, by demeaning a friend or collegue you demean yourself” www.idmworks.com [email protected] Blog: www.idmworks.com/blog *The information contained in this email message and any attachment may be privileged, confidential, proprietary or otherwise protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
