One thing I will add from actual testing I have done with ZOAU facilities -- 
they are HORRIBLY slow.  Yes, you can run them from off-platform - that was 
their intended raison d'etre - and the fact that you even CAN do that if you 
really, really need it is a Good Thing (tm).

But I found that using them from the z/OS Unix command line embedded in a 
python script just as in the article link is a performance nightmare.  
Definitely NOT ready for production use.  The idea is good but the 
implementation is awful.  Take a close look at the implementation of the ZOAU 
dataset-read function for an example of what I saw.  Substantially better 
performance can be had by using the python subprocess.run() function to execute 
the "cat" shell command to capture the z/OS dataset file contents you need in a 
python list (assuming your file contents will fit in available memory, of 
course; if not use "head" instead to read in chunks at a time).  Or even use 
David's pyzfile facility, assuming you can get it installed at your shop.

I suppose one could put ZOAU in the class of development tool that is "OK to 
use once or twice a day" but not something you want to use more often than that 
in our CPU-constrained-for-cost environments, at least not until the underlying 
implementation improves dramatically.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jay 
Maynard
Sent: Thursday, March 2, 2023 7:57 AM
To: [email protected]
Subject: Re: Mainframe REXX (Re: Badmouthing Rexx and ooRexx - again (Re: zOSMF 
and zOWE for non-mainframers

I haven't tried to write anything in Rexx, let alone a TCP server. I'd probably 
be inclined to use Go for that, though.

JCL to Python:
https://medium.com/theropod/the-journey-from-jcl-to-python-so-easy-even-an-old-mainframer-can-do-it-f088cc49366a
 

--

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 [email protected] with the message: INFO IBM-MAIN

Reply via email to