I used to do this by having the rexx exec call a small (assembler) program which issued the WTO. It wasn't 'sent to NetView' as such, but the message automation table in NetView then had an entry added to run a NV rexx exec when the WTO was seen. Typically we used this to let TSO/ISPF users...
Fifteen years ago when I last used TSO and ISPF, I always put edit macros, whether written in CLIST or REXX, into the SYSPROC concatenation, rather than SYSEXEC. I don't know if that matters.
A related point is if you store, say date() values in one column and want to be able to sort on date. I used to do that by also having columns that I'd never display to a user, and keep a date("B") value in those. To sort by date I sorted the latter column.
The drawback with entering '=x' repeatedly (which can be done with a macro in a 3270 emulator) is that not all ispf apps will stop. If I remember correctly '=X' issues END commands repeatedly. An app that's active might see END and then display a 'are you sure you want to end' screen (if eg...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.