Right. That was my point. I was agreeing with you, or amplifying what you had said.
I guess about the only oops would be a naïve or under-skilled programmer who did not realize the impact of some privileged instruction. Who had some legitimate task to accomplish, looked in the POps, and said "aha! Set Clock will do what I want ..." Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Binyamin Dissen Sent: Monday, July 13, 2015 11:43 PM To: [email protected] Subject: Re: SYSTEM KEY Programming Was: IVSK and SPKA On Mon, 13 Jul 2015 15:46:08 -0700 Charles Mills <[email protected]> wrote: :>Probably more likely to do inadvertent "storage" damage with Key 0 ("oops, I :>forgot that subroutine destroys R2") than to do inadvertent "you shouldn't :>use that op code" damage with supervisor state. If you were going to SPKA in APF code, you would MODESET anyway. :>I think inadvertent "oops's" are the issue here. If you are malicious, then :>if you have APF authorization all bets are off. What kind of oops would supervisor state alone allow? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
