--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
From: Joe Reichman [mailto:reichman...@gmail.com]
Sent: Tuesday, January 9, 2018 2:44 PM
To: 'IBM Mainframe Discussion List'
Subject:
This is the program that is causing the abend
TESTRCOV AMODE 31
TESTRCOV RMODE ANY
YREGS
AR0 EQU 0
AR1 EQU 1
AR2 EQU
osed to do and I can continue executing
> :>
> :>-Original Message-
> :>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Wayne Driscoll
> :>Sent: Monday, January 8, 2018 9:20 PM
> :>To: IBM-MAIN@LISTSERV.UA.EDU
> :>Subject: Re: PC rtn AK
IN@LISTSERV.UA.EDU
:>Subject: Re: PC rtn AKM=(0:15) Getting S0C2 REASON 002
:>
:>Are you sure the 0C2 is occurring at the PC instruction, not because your
program is in problem state when issuing the ETDEF or ETCON macros? I would run
outside of TESTAUTH, so I could get a dump and then look a
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Wayne Driscoll
Sent: Monday, January 8, 2018 9:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PC rtn AKM=(0:15) Getting S0C2 REASON 002
Are you sure the 0C2 is occurring at the PC instruction, not because your
program is in problem state when issuing the
ubject: 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
-
ERV.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
-
ssion 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,
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