Right on Walt. But I swore decades ago never to write a new CLIST. I’m too old to change. ;-)))
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Walt Farrell Sent: Sunday, December 14, 2014 7:01 AM To: [email protected] Subject: Re: Setting a lonnnnng SLIP trap On Sat, 13 Dec 2014 23:33:12 -0500, Shmuel Metz (Seymour J.) <[email protected]> wrote: >In ><cy1pr0101mb076351ce69bc7140c03659c2ce...@cy1pr0101mb0763.prod.exchange >labs.com>, >on 12/13/2014 > at 06:53 PM, J O Skip Robinson <[email protected]> said: > >>Since there's no actual WTOR, I cannot invoke a second REXX to >>continue the conversation. > >What are you trying to say? If you can invoke a REPLY command then you >can invoke a SLIP command, authorization permitting. From what he showed, it appears that in TSO/E OPER, the SLIP subcommand simply prompts for additional operands. At that point, if he were writing in CLIST rather than REXX he could examine the prompt, and respond with something generated by the CLIST. However, writing in REXX I don't think he can respond. (As I remember, it is possible to stack/queue additional responses, which the system would then read when the REXX exec ends. But I don't think REXX provides a way to issue them while the exec continues to run. But those are old memories, at this point.) I think (but cannot test) that his choices are to use CLIST, or to avoid using OPER within his REXX exec and use the more modern (but more complex) CONSOLE function instead. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
