I hope that nowadays you use ESPIE instead of SPIE...
A big disadvantage of SPIE/ESPIE is that it cannot be used in supervisor state.
So you have to use ESTAE even if you know that you want to quickly recover with
no dump, LOGREC, etc., from PIC-4/10/11 (such as when chasing system control
blocks unlocked) or to catch arithmetic errors (divide by zero and the like)
and continue on.
And how do you pronounce SPIE: SPY or SPEE? (Please don't take this as a
request for a long winded discussion on how we pronounce certain acronyms. It's
just an observation about how individually we all are in our vocalizations of
"non-words".)
Keith Moe
BMC Software
On Thursday, January 30, 2020, 12:17:47 PM PST, Seymour J Metz
<[email protected]> wrote:
There's a reason that I never had a job as a typist. You're right, of course,
that I meant S0C1.
I used to use SPIE to distinguish between a S/360 and a S/370 by having the
SPIE exit test whether a privileged instruction gave an 0001 or 0002; a friend
had a PIH front end that simulated S/370 instructions and my code failed
spectacularly. :-(
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Assembler List <[email protected]> on behalf
of Keith Moe <[email protected]>
Sent: Thursday, January 30, 2020 3:01 PM
To: [email protected]
Subject: Re: Does S0C5 still exist ?
S001 (from System Codes):
An I/O error condition was encountered during BDAM, BISAM, BPAM, BSAM, QISAM,
or QSAM processing.
The completion code can be issued if CLOSE processing called end-of-volume
(EOV), and EOV processing detected an out-of-space condition. See the
explanation of message IEC020I in z/OS MVS System Messages, Vol 7 (IEB-IEE) for
information about the task that was ended.
S001 and S0C1 have nothing to do with each other.
Keith Moe
BMC Software
On Thursday, January 30, 2020, 11:38:53 AM PST, Seymour J Metz
<[email protected]> wrote:
Not quite; ABEND S001 indicates an operation exception that *WAS NOT HANDLED
BY A SPIE OR SPIE EXIT*. Read my message again. I am prepared to defend what I
wrote in this universe, not what I might have written in some alternate
universe, and I never denied that a PIC 0001 was an operations exception.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Assembler List <[email protected]> on behalf
of Dan Greiner <[email protected]>
Sent: Thursday, January 30, 2020 2:34 PM
To: [email protected]
Subject: Re: Does S0C5 still exist ?
Hold the phone!
See "z/OS MVS System Codes" (SA22-7626-25 ... dunno if this is the latest rev),
page 106 or thereabouts. System completion code 0C1 (S0C1) indicates an
operation exception (which, last time I checked the PoO, is most definitely a
program interruption code 0001 [PIC-0001].
