That sounds like yet another reason for TSO/E to steal GLOBALV from CMS.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Farley, Peter x23353 [0000031df298a9da-dmarc-requ...@listserv.ua.edu] Sent: Monday, August 29, 2022 2:07 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to use LISTDSI from Rexx under Unix shell? Apologies for not responding sooner, but I will reply with working example soon, have been busy on other things. However, I can report that the OUTTRAP works from shell-initiated Rexx because the "address tso" fork inherits FD's 0, 1, 2 and OUTTRAP captures FD 1 (SYSTSPRT from the TSO fork) with no problem. This is documented behavior. Rexx variables like SYSREASON, etc., set by LISTDSI in the TSO fork do not get set in the OMVS address space, which is also documented behavior. The TSO fork has to output values needed in the OMVS address space to SYSTSPRT (or maybe to the stack, still testing to see if that works or not). STEMPUSH/STEMPULL may also work as a communication path if the stack survives the TSO fork. Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Sunday, August 28, 2022 7:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to use LISTDSI from Rexx under Unix shell? On Fri, 26 Aug 2022 00:21:06 -0500, Hank Oerlemans wrote: >See >https://secure-web.cisco.com/1M_xTFEwsPu00bvTEXVoZ6ceCVLecodh0nIoNgvwQ18pdzx6Vy7o2y-zaArhM5Kcw80Kv1AzhsQIJ5rbf5CaaTGcAE_BDI3enwZVMjuoyG1RJrKXP_V22QV6pK3uG-icphKU0bvNN0x5tl9yquz-Pxa5CvY1bIhWICpX2twXGc9pfrcewAtYJd6DKevKpbzVfon6i6VL4NroShKAP9ocRM66WPaaD7Ebf_GViqw8qt_MmxSQXxT74GyvUjcpTwp7NdtHsBMXSzgBDPofOz-w4csC1sInaplpul3MyOl_eGtPZOJclcZdnvjMPMOiaAlraVsQiGnhSo-QaRshj4_duZfr4eDu-VzxmJY9vmNmFMjSjEY8nV9nHapNI4MFsRtLGiD8EesULn3_4lJyZr4z3F2Lj-yITmMIONMfALQ--fpi_bHLjTmMysQNupDBw43G-0xisxRNl1THXjgI78wpc1w/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.ibm.com%2Fdocs%2Fen%2Fzos%2F2.4.0%3Ftopic%3Denvironment-examples__%3B%21%21Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg%21KesIc3TuKFptIfS99HLPkItYC57T3-XBb_a8ys87AZ1h99dzxzncHglIwjzi5SNqrng0k3qbkEbI7zpOrBXnbR7m58EpuMzuNMVK5iI1%24 > >Use your OMVS Rexx to Address TSO 'exec (mydsi)' your working code and outtrap >to work with the results. > I suspect that outtrap will take effect in the TMP fork, not in the OMVS fork. You might use a POSIX pipe (address syscall pipe p.), details left as an exercise for the student. -- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
