I would use CALL. Implies that you want to return to the caller. Works in all environments.
Most of my REXX code can then be ported to REXX/CICS without major rewrites. Another plus of CALL is that the called routine can be internal or external to the mainline code. On Tue, Mar 29, 2016 at 11:56 AM, Charles Mills <[email protected]> wrote: > Ah, you are right. I do in fact pass what I think of as multiple > arguments, as in the example below. But in SECOND I have to sort them out > with Parse Arg. > > FWIW Phil did not mention arguments, not one, not more. > > Charles > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Monday, March 28, 2016 5:46 PM > To: [email protected] > Subject: Re: Dumb TSO Rexx question > > On Mon, 28 Mar 2016 16:54:58 -0700, Charles Mills wrote: > > >I don't even use CALL. > > > >Given TSO and > > > >Address TSO "ALTLIB ACTIVATE DATASET(MYLIB.CLIST) APP(CLIST)" > > > >then with MYLIB.CLIST containing SECOND then in CALLER I can just do > > > >"SECOND arg1 arg2 arg33" > > > Depends. The command as you wrote it allows you to pass only one argument. > Scott's CALL allows passing multiple arguments. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
