Most of my execs do indeed not send their messages to XEDIT (I've got got less than 10 EXECs that do), for exactly the reasons you mention. My former IBM colleague who also worked years for my famous ex-customer, he though had a SUBCOM XEDIT test in his standard REXX skeleton, much to my regrets...
2009/3/16 Rob van der Heij <rvdh...@gmail.com>: > On Mon, Mar 16, 2009 at 8:41 AM, Kris Buelens <kris.buel...@gmail.com> wrote: > >> You got me... almost exactly one year ago I updated all my EXECs to become >> 'RTNSTATE DMSINXED' >> if Rc<>0 then do; 'SUBCOM XEDIT' ; Xedit=(rc=0); end >> else do; call csl 'DMSINXED RETC REAS T'; Xedit=(reas=0 & t=0) ; end >> But, this SIGNAL SAMPEXEC didn't have filetype EXEC (nor XEDIT, nor >> REXX), hence I missed it. > > So we can conclude that you have not written any new REXX code since a > year or don't use your own standards ;-) > > I really hate the approach to show CMS error messages as XEDIT MSG > (even when the EXEC was invoked directly from the command line). I've > often stared at the line mode output in "HOLDING" to see why it did > not behave correct, only to get the VMLINK message after you get back > in FILELIST. Weird enough the CP errors don't follow that path. > For XEDIT macros its different since they are meant to do things with > your editor. But for EXEC it is often less helpful. > > Rob > -- Kris Buelens, IBM Belgium, VM customer support
