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: 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
