Re-sent considerably trimmed due to IBM-MAIN restriction of 250 lines per reply.
-----Original Message----- From: Farley, Peter x23353 Sent: Tuesday, December 7, 2021 6:36 PM To: IBM Mainframe Assembler List <[email protected]> Subject: RE: Is it possible to update CSA from an unauthorized user-key program? Responses inline below. Peter -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Seymour J Metz Sent: Tuesday, December 7, 2021 6:09 PM To: [email protected] Subject: Re: Is it possible to update CSA from an unauthorized user-key program? A few points: 1. As Peter Relson has noted, the shared storage should not be in CSA/ECSA. Somewhat agreed. I was thinking more along the lines of 64-bit user storage for the bulk of the data, accessed via the defined interface. Slightly longer path length than direct memory access, but better RAS and security. (Does C library shmem() supply any RAS or security?) 2. If, e.g., an ISV, does it on their own, the code is likely to be tied to their own needs. Very likely, but it is at least possible for something more general to come out of such an ISV effort, FSVO possible. 3. The best option if there is a business is for IBM to do it. Agreed, but then again they might over-complicate it just because that's what they often do. Making a business case is difficult at best, and may be impossible given IBM's diminished knowledgeable technical head count in recent years (not counting the PFCSK's). 4. If an RFE would take too long, then ther best option is an open source project. Agreed, assuming an RFE wasn't rejected out of hand for no or insufficient business case. 5. Is corporate sponsorship for such a project likely? Is it needed? -- 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.
