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:[email protected]] On Behalf Of Joe Reichman Sent: Monday, January 8, 2018 3:55 PM To: [email protected] 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 [email protected] with the message: INFO IBM-MAIN
