>> The "special" cases, especially when R14 is loaded up separatelyWould you
>> being reached by a BAL consider a special case? L 15,whereverI.e.
>> BAL 14,12(,15) go to write handlerMartinVon einem Smartphone gedendet.
-------- Ursprüngliche Nachricht --------Von: Steve Smith <[email protected]>
Datum: 15.08.20 18:43 (GMT+01:00) An: [email protected]
Betreff: Re: how to return? Let's see how good you are. Given those
requirements, the only thing your subroutine needs to do isreturn with BSM
0,R14. It will do the right thing in every case youmentioned.As you didn't
originally specify much of this, we had to qualify answerswith various unlikely
scenarios. Fact is, BSM 0,R14 works correctly forany call by BASSM, BSM, BASR,
BAS, JAS (BRAS), JASL (BRASL), BALR, and BAL(BAL only in 31-bit mode).The
"special" cases, especially when R14 is loaded up separately, areunpredictable.
Fortunately, those are rare, and slightly rarer codedincompetently, such that
R14 has the wrong AMODE indicator. Your list ofrequirements do not say you need
to support any of those.Furthermore, your program can switch AMODE all it
likes. The BSM 0,R14will restore the correct AMODE on return to the caller.
And I don't seethat LE is relevant.Seems like a case of over-thinking and
under-learning.sasOn Fri, Aug 14, 2020 at 6:23 PM Tony Thigpen
<[email protected]> wrote:> I have been reading all the "that is not a good way
to do it" posts, so> here it the challenge to all those nay-sayers.>> It's time
to 'put-up' or 'shut-up'.>>
