Practically speaking however, starting a Rexx script under one of the z/OS Unix 
shell programs is pretty much the only way to get it done.  Although if you use 
the BPXWUNIX() function from a TSO Rexx  script to start another Rexx script 
stored in the z/OS Unix file system it might work.  I will have to try that 
path out.

I have recently done some experiments with Rexx scripts stored in the z/OS Unix 
file system encoded in ASCII and they will execute without a problem so long as 
the starting script file is properly tagged as ISO8859-1 text.  Untagged Rexx 
script files started from any z/OS Unix shell do have to be encoded in EBCDIC 
though.

Peter

From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jon 
Perryman
Sent: Monday, April 22, 2024 12:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX vs other languages -- EXECIO intuitiveness


On Sun, 21 Apr 2024 22:54:15 +0000, Seymour J Metz 
<sme...@gmu.edu<mailto:sme...@gmu.edu>> wrote:



>>Wait, what?  Are you saying TSO-REXXhaas LINEIN, CHAROUT and so on?



>Only in a EUnix environment. I don't know if syscalls is enough or if you 
>actually have t be running under the shell.



Syscalls does not setup a full z/OS Unix environment and in environments like 
TSO would only cause dubbing.



I've never tried it but a shell should not be required to automatically 
integrate REXX & UNIX as long as you start REXX using z/OS Unix facilities in a 
Unix address space. Technically, shells are not required by Unix but I doubt 
that it has been tested much for obscure requirements.

--



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to