EXECCALL can help there too: SET PF10 EXECCALL .EXEC mainexec 2010/7/6 Rob van der Heij <rvdh...@gmail.com>
> 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 changed), > and > > press PF10 (PF10 is assigned to EXECCALL). EXECCALL will SAVE the file > (if > > it was modified), start the exec passing what I entered in XEDIT's cmd > area > > or the parameters defined on EXECCALL. > > Most of the cases I'm not working on the main EXEC that can be > invoked, but on one of the REXX stages that it uses. With CMS > Pipelines stages you often can set up some test data and run the stage > on the command line of the editor. > > In my 25+ years of XEDIT, I came up with some macros that keep the > location and cursor position when I exit XEDIT through PF3 (for each > of the files I'm working on). So when I invoke XEDIT for that file, I > get back to where I was before (normally near the place where I need > to be now). Amd my PF3 outside XEDIT is set to edit the last file > again. This means going to CMS line mode to try something does not > disturb the process. > > Rob > -- Kris Buelens, IBM Belgium, VM customer support
