¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Latest version of Review ABENDs


 

Greg,

I tried running RFE under TEST and got some different results than what you show in that graphic.
READY
test 'sys2.cmdlib(rfe)' cp
ENTER COMMAND FOR CP
rfe
TEST
go
RFE ENDED DUE TO ERROR+
TEST
?
SYSTEM ABEND CODE 0C1 REASON CODE 001
TEST
where
FCD28. LOCATED AT +578 IN RFE .REVPROF UNDER TCB LOCATED AT 9A64D8.
TEST
l fcd28. l(16)
0FCD28. F0F1F2F3 F4F5F6F7 F8F9C1C2 C3C4C5C6
TEST
Offset +578 looks like an EBCDIC character string, '0123456789ABCDEF', not code. So, it looks like the 0C1 was caused by an errant branch to the wrong address.

I tried running that AMASPZAP job step and now RFE works! It's good to have RFE running again. Thanks for the quick response and fix.

Charles Bailey

On 2021-01-01 22:30, Greg Price wrote:
On 2021-01-02 9:31 AM, Charles Bailey wrote:
READY
rfe
RFE ENDED DUE TO ERROR+
READY
?
SYSTEM ABEND CODE 0C1 REASON CODE 001
READY
The next thing to enter here is
TEST
then issue WHERE at the TEST prompt. END will exit TEST back to READY.

Attached is a screen shot of a TEST session I did to produce the sort of information that may assist diagnosis.

Of course, I could not reproduce the error on my TK-based system because I was running "380" to debug some glitch to placate the demands for XA compliance from a certain quarter. Anyway, a testing mod remained in the code base which resulted in the S0C1 on strictly 370 "hardware".

A S0C1 abend is an operation exception. The first thing to find out is whether there is an unsupported instruction in the code stream, or if there has been a wild branch to an incorrect location. The attached screen shot shows it was the former. Of course, the clearly superior way to capture the circumstances of the abend would be to use MVSDDT. Unfortunately, in my z/OS-based job I don't have MVSDDT so I continue to reinforce my habit of using TEST. (Naughty Greg!) And naturally IPCS comes in for a fair bit of use on z/OS as well.

Still, that's not why you called...

Here is a job step you can tailor to apply a fix:

//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DISP=SHR,DSN=SYS2.CMDLIB
//SYSIN DD *
NAME REVIEW REVIEW
IDRDATA S0C1-FIX
VER 02C8 4700
REP 02C8 47B0
/*

Cheers,
Greg




Join [email protected] to automatically receive all group messages.