Unless there’s a concurrent PER and Monitor event indicated*;
then it wouldn’t be a typo, but that’s just what it was. Thank you for reading
my post and commenting on my mistake. Maybe I should pay more attention to my
posts like when I use Ditto to edit a VVDS (has anybody else done that, btw?).
* I know that’s not going to happen.
On Mon, Aug 6, 2018 at 2:19 PM -0500, "Seymour J Metz" <sme...@gmu.edu> wrote:
No, you get a program interrupt 003; you only get an ABEND S0C3 if the program
interrupt is not handled by a SPIE/ESPIE exit. There's actually software that
uses EX 0,* as a control structure. I don't recall whether it was a debugger, a
profiler or "E none of the above".
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Assembler List on behalf of Keven
Sent: Monday, August 6, 2018 11:23 AM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: EX
Ditto for
EX R0,*
except that you get a 0C3 program interrupt instead, which is usually a sign of
code scuttling itself and can be treated as such in recovery routines.
On Mon, Aug 6, 2018 at 9:36 AM -0500, "Ed Jaffe" wrote:
We use 'Jxx *+2' which disturbs no registers and is guaranteed to fail
with an 0C1.
On 8/6/2018 3:10 AM, Jonathan Scott wrote:
> J *+1 isn't even possible, as the hardware offset for relative
> addressing is in halfwords.
>
> For many years I have been using a conditional TRAP macro which
> is equivalent to
> BC cond,*+1
> but which is coded using LA with an ORG back to change the
> opcode, to avoid getting an error message. This avoids a branch
> in the normal case. It is primarily used for integrity and
> consistency checks, and my recovery routine recognizes this
> convention and reports it as "TRAP occurred at offset &1 in &2".
>
> Martin Ward writes:
>> On 06/08/2018 02:30, Robin Vowels wrote:
>>> And anyway, why would you want to EX an EX?
>> To cause an ABEND after an error, of course!
>> I have seen "EX 0,*" in production code to do this
>> (along with "J *+1")
> Jonathan Scott, HLASM
> IBM Hursley, UK
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
