On Sun, 28 Mar 2021 00:58:22 -0400 Gary Weinhold wrote:
:>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 p
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
S052-104
EXTERNAL EMAIL
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).
...
>
On Sun, 28 Mar 2021, at 05:58, Gary Weinhold wrote:
> ... According to
> the customer, this happens once in a while and rerunning the job works.
Does the customer have more than one initiator servicing whatever job
class the job required?
That is, how likely is it that the rerun jobs run in a d
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 ow
This abend is not about a separate started task that uses LXRES in its
creation of an XM environment, and then subsequent jobs or started tasks
"connect".
The description for this abend is this: LXRES is issued but a
cross-memory-resource-owning jobstep task has already terminated in the
home
have to be in LPA/common but could probably execute
exactly the same code as it does today.
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Gary Weinhold
Sent: 25 March 2021 18:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Abend S052-104
EXTERNAL EMAIL
We have a
We have a situation in a customer environment where they intermittently
get this abend when our product initializes in a jobstep. The S052
abend explanation:
A program incorrectly issued a macro to request processing by Program
Call/authorization (PC/AUTH) service routines.
Register 15 contains
