Gary 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). Admittedly this is rare as LXRES-issuing code normally runs as a started task.
One possibility that could explain the situation : (1) A prior batch job established a non-resuable System-LX PC-ss and then terminated cleanly (including a successful LXFRE) (2) At this point PCAUTH still has the initiator ASID in the “memory delete queue” and has marked the ASID as non-reusable. (3) Your code is then scheduled to run in this initiator (same ASID as the init has not restarted) (4) When you issue the LXRES you will get the S052-104 (5) If the initiator was stopped prior to your code executing, I would expect a IEF352I message (due to (1) and (2)) Without testing, I am unsure if the prior code was changed to use REUSABLE=YES if this would prevent the problem you are seeing, however this is moot as the prior job code is not under your control. 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. Rob Scott Rocket Software From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Gary Weinhold Sent: 25 March 2021 18:05 To: [email protected] Subject: Abend S052-104 EXTERNAL EMAIL 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 a hexadecimal reason code in the form xxyy, where x identifies the macro that was issued, and yy identifies the error. See the system programmer response for an explanation of these reason codes. *Code** Explanation* 01yy The program issued an LXRES macro. 0104 A job step attempted to issue the LXRES macro, but a prior job step owned space-switch entry tables. (Subsequent job steps are not permitted to issue PC/AUTH macros.) Before applications using our product are started, our product initializes an non-terminating address space in which we set up a system non-space-switching PC. This PC is executed when our product is initialized in a job step. The function of the PC is to create a non-space-switching non-system PC in our address-space with our "user" PC for several supervisor state routines we need to invoke. We also set up an MVS RESMGR exit to allow us to cleanup at termination (which includes an LXFRE). So there is no doubt that we executed an LXRES. But to me this abend indicates that some prior step (could it perhaps not even be in this job, but in some job that previously ran in this address space?) created a space-switching PC and the address space is still is supporting it and will not allow another LXRES. So to prevent this error from occurring, is there something we can do in our code, or should the submitter of the job ensure that it runs in a different address space or should whatever created the space-switching PC clean it up? Or do I entirely misunderstand the meaning of this abend code? Gary Weinhold Senior Application Architect DATAKINETICS | Data Performance & Optimization Phone:+1.613.523.5500 x216 Email: [email protected]<mailto:[email protected]> Visit us online at www.DKL.com<http://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 [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
