On Wed, 3 Jun 2020 09:32:27 -0700, Charles Mills wrote: >You are a bad boy! >You failed to ask if it can be a ZFS path, and if not, why not? Perhaps an RFE >is in order? > Maybe next time. I'm pessimistic. Meanwhile, IBM says (but as a Rexx user I'm uncomfortable with: EXEC 'USERID.MYREXX.EXEC(TEST4) 'EXEC I'd prefer: EXEC 'USERID.MYREXX.EXEC(TEST4)' EXEC ... with the space outside the '...'. I suppose the TMP likes it.):
Hello. I am the writer for the z/OS TSO/E REXX Reference and have received your comments below. I contacted development, and there will be an update to the book. The paragraph is rewritten to correct and clarify. Thank you for letting us know. Running an exec in the TSO/E address space You can invoke a REXX exec in the TSO/E address space in several ways. To invoke an exec in TSO/E foreground, use the TSO/E EXEC command processor to either implicitly or explicitly invoke the exec. To invoke an exec explicitly, use the EXEC command, specifying the name of the data set and member to be executed. For example: EXEC 'USERID.MYREXX.EXEC(TEST4)'EXEC To invoke an exec implicitly by just specifying the member name of an exec, place the exec in a data set allocated to your SYSEXEC DD or SYSPROC DD. SYSEXEC contains only REXX execs, but SYSPROC can contain both REXX execs and CLISTs. To distinguish REXX execs from CLISTs, execs that are placed in SYSPROC should always start with a comment with the word "REXX" in line one, such as : /* REXX */. So if TEST1 is a REXX exec in a SYSEXEC or SYSPROC data set, you might invoke it implicitly with: %TEST1 For more information about how to invoke an exec in TSO/E foreground, see z/OS TSO/E REXX User's Guide. From: Paul Gilmartin <[email protected]> To: [email protected] Date: 06/03/2020 12:13 PM Subject: GRXBIMG TSO/E REXX Reference Hello, MHVRCFs, In: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ikja300/tsorun.htm • /OS 2.2.0 • z/OS TSO/E • z/OS TSO/E REXX Reference • Using REXX in different address spaces I read: "... you must have ddname GRXBIMG allocated." I'm curious. Does: //GRXBIMG DD DUMMY suffice, or must it be a PDS(E)? What error is reported if the programmer fails to allocate GRXBIMG? Is this covered in M&C? Thanks, gil [redacted:] z Systems Content Design and Dev, z/OS Core JES2, JES3, MVS, TSO/E IBM Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
