Rob Scott wrote (snipped):
From the description of the abend, if your user code runs as a jobstep in something like a JES initiator, you will always be at risk from a prior batch job performing an LXRES for PC-ss (without an initiator restart).
...
Is there any reason why your user-ASID owned PC-cp cannot be owned by your server-ASID ? The load module would have to be in LPA/common but could probably execute exactly the same code as it does today.
and Peter Relson wrote (snipped):
One case would be a multi-step started task (or initiated job) where the first step did so, and there is a second step. Don't do that.
Thanks, Peter and Rob. This was a batch job and we do not know all the preceding job steps (we only know the prior step was IDCAMS). We know our product can be run in multiple steps in the same job. Your responses will enable us to help the customer research the preceding steps to the abend in the address space. The resolution may be as simple as changing the job class for this job (or the cross-memory job step). According to the customer, this happens once in a while and rerunning the job works. It was set up this way when we decided we had to add a PC to our product 20 years ago. I believe the programmer was afraid that a customer could accidentally cancel the server started task and cause all running instances of our product to abend (which could include CICS and IMS/TM regions, batch jobs and a shared dataspace). He figured this technique would only prevent new instances of our product from starting and wouldn't be as big a problem for the customer to recover from. Gary Gary Weinhold Senior Application Architect DATAKINETICS | Data Performance & Optimization Phone:+1.613.523.5500 x216 Email: weinh...@dkl.com Visit us online at www.DKL.com E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
