On Sun, 23 Apr 2017 08:28:49 -0400 Peter Relson <[email protected]> wrote:
:>SETRP, IIRC, always "returns to the next sequential instruction" unless
:>you specify the REGS parameter.
:>One thing that I think you can't do is to set the "DUMP = Yes" option (or
:>any other option for that matter) without also setting the "return code",
:>as all the expansions set that, and the return code setting defaults to
:>"continue with termination" (i.e., percolate). Thus it is often a good
:>idea to set all the options (in one or more invocations) and then request
:>retry last, to avoid resetting the return code from "retry" to
:>"percolate".
Yes, there are many settings that you cannot set individually.even though
there are separate bits for them. To allow an FRR to sometimes return in
amode31 and other times in amode64 (but other similar options) requires (if
one wants to be clean and use SETRP rather than bits) two full SETRP
statements.
It would be nice if one could
IF condition1
SETRP to return 64
if condition2
free local lock
if condition3
set retry addr1
IF condition4
set retry addr2
BR R14
--
Binyamin Dissen <[email protected]>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.
I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
