Because, sadly, I do not expect to live forever.

On Tue, 25 Apr 2017 13:30:23 -0400 Steve Smith <[email protected]> wrote:

:>Sometimes, I just get enough fed up with badly designed/written* macros
:>that I re-write them myself.  Or in SETRP's case, why not just code your
:>own flag settings?  The SDWA is well-documented, and has a complete
:>DSECT[s].
:>
:>sas
:>
:>* SETRP hasn't caused *me* any problem.  Many other IBM macros have, and
:>do, but they're off-topic for now.
:>
:>On Tue, Apr 25, 2017 at 11:39 AM, Charles Mills <[email protected]> wrote:
:>
:>> And an IMREALLYTRULYPOSITIVEABOUTWHATIAMDOING=NO(default)/YES keyword for
:>> the really risky options.
:>>
:>> Charles
:>>
:>> -----Original Message-----
:>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
:>> Behalf Of Binyamin Dissen
:>> Sent: Tuesday, April 25, 2017 8:05 AM
:>> To: [email protected]
:>> Subject: Re: SETRP with DUMP=YES
:>>
:>> On Tue, 25 Apr 2017 07:59:48 -0400 Peter Relson <[email protected]> wrote:
:>>
:>> :><snip>
:>> :>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
:>> :></snip>
:>>
:>> :>Why can't you? Although I assume you meant by "free local lock" instead
:>> :>"ask RTM via SETRP to free local lock upon return" (and be aware that
:>> that
:>> :>with FRLKRTY=YES it will not be freed upon retry). I'm not sure what
:>> :>"return 64" means or what you wrote a it earlier "return in AMODE31".
:>>
:>> :>The only thing anomalous I see in what you pose above is that if by "free
:>> :>local lock" you mean SETRP  FRELOCK=LOCAL, you have to be aware that that
:>> :>is equivalent to SETRP FRELOCK=LOCAL,RC=0
:>>
:>> :>It is true that some of the retry-oriented options (such as RETADDR)
:>> :>require that you specify RC=4. So if your "SETRP to return 64" meant
:>> :>including setting RC=4 (retry) then your "free local lock" would have
:>> :>reset it to 0 (percolate).
:>>
:>> That is what I mean. Let me specify only what I want - if necessary, add a
:>> IKNOWWHATIAMDOING=NO(default)/YES keyword which will avoid the checks.
:>>
:>> ----------------------------------------------------------------------
:>> For IBM-MAIN subscribe / signoff / archive access instructions,
:>> send email to [email protected] with the message: INFO IBM-MAIN
:>>

--
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

Reply via email to