On Tue, Jul 6, 2010 at 8:28 AM, Kris Buelens kris.buel...@gmail.com wrote:
What do I often see: the user XEDITs the exec, searches the area to change,
issues FILE, starts the exec from CMS Ready and that over and over again...
What do I do: I stay in XEDIT (at the place of the code just
On Tue, Jul 6, 2010 at 8:59 AM, Kris Buelens kris.buel...@gmail.com wrote:
EXECCALL can help there too:
SET PF10 EXECCALL .EXEC mainexec
But I rarely have an exec that does not require arguments, so I would
need XEDIT to remember that too...
Rob
Before I retired we had a module from YKT that would execute the EXEC being
edited FROM STORAGE, w/o having to Save it. Don't know if it ever was put in the
VM Download Library but it was *very* handy for tweaking or experimenting with
code! I wrote a RUN macro to invoke it and pass parms,
In REXX programs you may use PIPE with direct access to 3270 devices with
specified dev address.
Piotr
-Wiadomość oryginalna-
Od: The IBM z/VM Operating System w imieniu Florian Bilek
Wysłano: Pn 2010-07-05 19:14
Do: IBMVM@LISTSERV.UARK.EDU
Temat: Second screen in a z/VM CMS session
There isn't any way to modify a running REXX EXEC, if that is what you wa
nt to do.
CMS Multitasking is very limited. It is really multithreading. All CMS co
mmands must run in the
base thread, so you cannot run two commands such as XEDIT and the EXEC at
the same time in
different threads --
Thank you for this clarification about multitasking in CMS.
Maybe I was not precise enough.
I would like to avoid always invoking XEDIT in order to change some line
of
code in the REXX exec during debugging. The idea was to have the file ope
ned
in XEDIT, save it and then run it on a second
