In <[EMAIL PROTECTED]>, on
04/21/2008
at 07:56 AM, "McKown, John" <[EMAIL PROTECTED]> said:
>IIRC, IBM has stated that an opcode of x'00' will __never__ be valid and
>will __always__ produce a program check interrupt code 1 (S0C1 in
>MVS-speak).
S0C1 is S0C1 in MVS speak; program check interrupt code 1 is not. There's
lots of code that would break if it got an ABEND when it was expecting a
program check.
>However, I had a friend at another shop do this.
>He got a royal dressing down by the lead sysprog because he (the
>sysprog) had decided that the S0C3 abend was his alone and had placed a
>SLIP in COMMNDnn to take SVC dumps on every S0C3 to debug __his__
>programs.
And didn't document it because?
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
