I don't know why you are checking the key on the client side, but your PC routine cannot really count on the filtering by the client side - if it will be setting a client passed protected storage location or accessing something that the client could not directly access it will need to validate the callers key itself.
On Sat, 28 Dec 2013 15:35:33 -0500 zMan <zedgarhoo...@gmail.com> wrote: :>This is the client side of an API which is going to do a PC to a started :>task. It can be called from "plain" code, or on occasion from a DB2 user :>exit. I want to know if it's a user exit, hence I'm testing the key. If :>"non-system key" is the real answer, then yeah, the IPK approach looks a :>bit better. :> :> :>On Sat, Dec 28, 2013 at 12:03 PM, Binyamin Dissen < :>bdis...@dissensoftware.com> wrote: :> :>> On Fri, 27 Dec 2013 18:31:17 -0500 zMan <zedgarhoo...@gmail.com> wrote: :>> :>> :>Is there a simpler way to see whether we were called in key 8 (not that :>> :>this is that complicated): :>> :>> :> EPSW R14,R0 Extract PSW :>> :> SLL R14,8 Get key bits in left-most nibble :>> :> SRL R14,28 Now isolate in bottom nibble :>> :> CFI R14,8 Are we in key 8?? :>> :>> What is being called? PC? SVC? Simple subroutine? -- Binyamin Dissen <bdis...@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
