Re: Saving in memory data in case of operator cancel was Re: LE question

2019-05-16 Thread scott Ford
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

Re: Saving in memory data in case of operator cancel was Re: LE question

2019-05-16 Thread Peter Relson
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

Saving in memory data in case of operator cancel was Re: LE question

2019-05-15 Thread Clark Morris
[Default] On 14 May 2019 11:23:01 -0700, in bit.listserv.ibm-main idfli...@gmail.com (scott Ford) wrote: >All: > >I need to do some research on how job is cancelled via the Operator , Abend >S222. I read through some of the Boston share doc of some time ago by Ed, >Sam and Skip. Its great. >I