RUCSA was (reluctantly) designed to allow a particular set of customers to move to z/OS 2.4 while continuing to run a mission critical application for which the source code has been lost. RUCSA is not intended to be a model for future application development.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <[email protected]> wrote on 09/10/2019 04:05:07 AM: > From: "Vernooij, Kees (ITOP NM) - KLM" <[email protected]> > To: [email protected] > Date: 09/10/2019 09:00 AM > Subject: Re: APAR OA56180 / RUCSA > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > Compared to what was, access is now limited to the members of a > restricted club, accessing a restricted part of CSA. > The club administration can select trusted members for the club. I > think this is quite acceptable. > > Kees. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Martin Packer > > Sent: 10 September, 2019 9:55 > > To: [email protected] > > Subject: Re: APAR OA56180 / RUCSA > > > > Up to a point: > > > > If you are enabled to use User-Key CSA via RUCSA I believe you "have a > > ticket to THE party", the ONE AND ONLY party. Meaning you can access other > > users' allocations of User Key CSA. > > > > Someone correct me if I've got this wrong. > > > > If I'm right auditors might not be quite so happy. > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
