'OPER' is just the TSO command, which can be embedded in a REXX. The SLIP subcommand will send a prompt back to the user but not as a WTOR. On the screen:
IEE725I SLIP PARAMETERS ARE- PER-IF,ENABLED ACTION=SVCD,SET BY xxxxxx,PRCNTLIM=10,00,MATCHLIM=1,0 IEE726D ENTER ADDITIONAL SLIP PARAMETERS, 'END', OR 'CANCEL' (me) CANCEL In the log: +IKJ000I SL SET,IF SL SET,IF SEND 'IEE756I SLIP COMMAND CANCELED BY OPERATOR', USER=(xxxxxx),LOGON Since there's no actual WTOR, I cannot invoke a second REXX to continue the conversation. Yes, an IEASLPxx member in PARMLIB would seem to be the solution. Thanks for the clarification. . . . 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 jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Saturday, December 13, 2014 9:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Setting a lonnnnng SLIP trap No operator command, under any circumstance, under any way of entering it, can exceed 126 characters. So if "lonnnnng" means > 126, then your only choices are to enter it with some on the SLIP SET and the rest in response to the "give me more" WTORs, or with parmlib. I don't know what REXX "OPER" gives you access to in terms of responding to WTORs (which the "give me more" request is), but if it does let you see and respond to the WTOR, then you could do that. SLIP doesn't care how many responses it took to enter the whole trap. But if it's really lonnnng and has to be entered in multiple pieces, I couldn't imagine doing anything other than parmlib because it would be such a pain to re-enter if you've made some mistake that cannot be overcome. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
