"IBM Mainframe Assembler List" <[email protected]> wrote on
01/26/2022 11:34:49 AM:
> This url
>
> https://urldefense.com/v3/__https://share.confex.com/share/115/
> webprogram/Handout/Session7691/S7691bla.pdf__;!!E0nbmg29qrX0lQ!
> OTvai-wmEzcCFWsNro1rC88rNvJOY67W-amGAHrjZnfKs7FbEDv72AmM27K7LmwYQxY$
>
> Contains what I want to do it says how to write
> The program if the program is extensive
> You have to debug it
>
> The only way to get the Rexx environment
> Block
There are two situations in which an assembler program can execute
as it relates to REXX. (1) I didn't read it in its entirety, but the PDF
seems to describe an assembler program that creates the REXX environment.
(2) The other situation is to have the REXX environment passed to your
assembler program. It is easy to debug the first situation and very
difficult to debug the second situation.
> Address tso
> “Call ‘myloadlib(myprog) passenvb’
> Passenvb populates register 0 with the address of the envblock
>
> How would I debug this program
The above demonstrates an assembler program executing in the
second situation I mentioned above.
> It tried test ‘mylosdlib(myprog)’ cp
> And used ECTENVBK but now I am getting
>
> A return code invalid language environment
The above demonstrates an assembler program executing in the first
situation I mentioned above -- and that is why you are getting an error
because it appears your assembler program is expecting the REXX
environment to be passed to it but you didn't actually pass a REXX
environment (i.e., you faked it).
Sincerely,
Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
