I suspect that the S0C4 is reason code 4 and is a key 8 versus key 9 issue. But, as you noted, the OP has not provided details.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Peter Relson [[email protected]] Sent: Thursday, March 4, 2021 8:32 AM To: [email protected] Subject: Re: Acquire Storage While I'm sure all of the responses have been on target, none have discussed the actual problem. The OP should provide basic debugging information. What is it actually 0C4 and if so with what reason code? What was the user's PSW key? Depending on CICS configuration this could be key 8 or key 9. What subpool was being requested? While presumably it is true that a program is exposed if it does not use CICS services to acquire storage, and in particular if it is redispatched on a different task, that doesn't mean that you would blow up referencing the storage that was just obtained, unless the acquiring task terminated (and not necessarily even then, depending on subpool sharing characteristics). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
