I don't know if this ancient history will be of any use in your
case Binyamin:
In the early 1990s, I was working on IBM Prolog for 370 (MVS). I
was asked to help the VM group migrate their code to MVS and they
explained their issues with Stack/Heap. We discussed storage keys
and what they were using and why.
So it was decided to use KEY9 and I think we also used KEY15
(long time ago, and I have forgotten some details).
I wrote the SVC for PROLOG and was in the middle of testing when
we were informed that CICS was going to use KEY9 and a system
change (forgot the name of this) was being done for them. So I
had to find another key.
Just thought you might need to make sure you will not create or
incur some problem in using Key9 with CICS (and since the changes
to CSA, this may well be obsolete).
Regards,
Steve Thompson
On 7/14/2023 10:41 AM, Farley, Peter wrote:
Binyamin,
Is this desire perhaps for use in a CICS "threadsafe" or "open" TCB? If so,
doesn't CICS itself provide some CICS-unique storage facilities to LE programs, and are those not
sufficient to your needs?
As many others have mentioned, the LE Vendor Interfaces manual has information
on heap routine replacement. I suspect you are SOL for redirecting STACK
storage though. The LE start and stop macro generated code doesn't look to me
to be very amenable to replacing the stack allocation/free subroutines, unless
maybe after setting up an enclave with CEEPIPI you change storage routine
addresses in the CAA (and possibly elsewhere?), but that sounds like a heavy
lift to test for RAS integrity.
Peter
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Binyamin Dissen
Sent: Thursday, July 13, 2023 6:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Change how LE allocates storage (subpool,key)
I would like to have LE use SP=132 KEY=9 for its STACK and HEAP.
I obviously could screw with CEEINT, but I don't know if that will affect
other storage requests.
Is there some explicit getmain routine that I can play with?
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
