On Fri, 26 Jan 2018 01:43:25 -0600, Andrew Metcalfe <[email protected]> wrote:
>If you have a moment please review my RFE for ISPF's ISRDDN/DDLIST function >below. > >In summary it asks for SAF protection for some of the sub-functions such as >APF/DISASM etc. > > >If you think it is a valid request please vote. > As others have said, the information is available to anyone through other means, and therefore simply protecting one method of displaying it is, indeed, silly. And you should explain that to your auditors. Binyamin suggested asking, instead, for a way to truly protect the names of the APF data sets, and I agree that that could make sense. Protecting the disassembly functions: As anyone can read the code of the SVC from storage, and anyone can hand-disassemble the code by reference to the Principles of Operation, there's no good purpose to protecting the disassembly function. The only solution I can think of at the moment is to convert your user SVCs into space-switching PC routines, so they are hidden from prying eyes. That, of course, is something you need to discuss with the developers of those SVCs. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
