No, the barn door is the specific REXX code, not the command to invoke it. BTW, where is the TSO environment documented for System Rexx? The authorized Services manual lists supported environments for TSO=NO but not for TSO=YES. And, yes, "environment" is another overloaded term; it has at least two relevant meanings in that section :-(
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Sunday, May 7, 2023 8:54 AM To: [email protected] Subject: Re: TSO command System Rexx On Sun, 7 May 2023 04:43:27 -0500, Willy Jensen wrote: >This will issue any TSO command, but security-wise I think it opens a barn >door. > Why is that not cause for an integrity APAR? Wasn't the "barn door" already open? >Save it as member TSOCMD in your SYSREXX lib. > >/* general TSO command rexx */ > address tso arg(1) > Exit 0 > >Sample use (@ is my SYSREXX command char): > >@TSOCMD LISTCAT ENT(SYS1.HELP) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
