I have an OLD ESA/390 Pops book I am quoting from "if the current PSW specifies problem state the current PSW-key mask in control register 3 is tested against the AKM and PSW key mask are anded and if the result I zero a privilege operation is recognized"
So If I am in problem state the AKM field which I specified as everything 0 - 15 determines if the PC is a privileged operation -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Monday, January 8, 2018 7:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PC rtn AKM=(0:15) Getting S0C2 REASON 002 S0C2 is not a key problem, it is a state problem. Does your S0C2 PSW show supervisor state? Is there any possible cause for S0C2 *other* than "you tried a privileged op code but you were not in supervisor state"? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joe Reichman Sent: Monday, January 8, 2018 3:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PC rtn AKM=(0:15) Getting S0C2 REASON 002 Hi I have a PC rtn defined in the following way with AKM=(0:15) meaning all keys can access ETDEF TYPE=SET,ETEADR=ETD,ROUTINE=(R2),SSWITCH=YES, X STATE=SUPERVISOR,AKM=(0:15),EKM=0,PC=STACKING And yet while running under TESTAUTH I get the following ABEND IKJ56641I TESTPRGK ENDED DUE TO ERROR IKJ56640I SYSTEM ABEND CODE 0C2 REASON CODE 00000002 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
