Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-20 Thread J. Leslie Turriff
To capture both stdout and stderr, bash provides the '2>&1|' and '|&' paradigms; from the bash info: "If '|&' is used, the standard error of COMMAND1 is connected to COMMAND2's standard input through the pipe; it is shorthand for '2>&1|'. This implicit redirection of the standard erro

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Dave Jones
s.sourceforge.net > Subject: Re: [Oorexx-devel] ooRexx and the mainframe... > > Hi, René. > > If you can get the runREXX framework to work, could you share your > experiences with the group. I'm trying to decide if this is a "big deal" > or not. > >

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Chip Davis
:-) Yeah, nothing like having to read the entire Unix file just to find out how many records are in it, then having to find the EOL character(s) to know how long each record is, to make you appreciate mainframe filesystems... -Chip- On 6/18/2015 11:48 AM, Dave Jones wrote: > Thanks, Ruurd. I

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Dave Jones
Thanks, Ruurd. I was just now trying to get that part of the code to work.:-) I *know* the cmd_out file had more than just one line in it. Have a good one, too. DJ On 06/18/2015 10:09 AM, Ruurd Idenburg wrote: > > Gotta use: > >lines('/temp/cmd_out',"C") > > on Linux to get the actual

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Dan Carter
Subject: Re: [Oorexx-devel] ooRexx and the mainframe... Hi, René. If you can get the runREXX framework to work, could you share your experiences with the group. I'm trying to decide if this is a "big deal" or not. I'm going to use your suggestion on how to capture Linux co

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Ruurd Idenburg
Gotta use: lines('/temp/cmd_out',"C") on Linux to get the actual lines in a file, default is to indicate if there is at least 1 more line. Ruurd On 18-6-2015 16:16, Dave Jones wrote: > Hi, René. > > If you can get the runREXX framework to work, could you share your > experiences with the g

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-18 Thread Dave Jones
Hi, René. If you can get the runREXX framework to work, could you share your experiences with the group. I'm trying to decide if this is a "big deal" or not. I'm going to use your suggestion on how to capture Linux command output; thanks for passing that on. I'm going to use simple Linux redirec

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-17 Thread Chip Davis
Very interesting, Dave. Too bad it arrived mere days before the VM Workshop; it would have made an excellent presentation. As soon as I get my current all-consuming project flying, I'll have a look at it. Not quite sure about your question; are you asking if issuing a Linux command with redir

Re: [Oorexx-devel] ooRexx and the mainframe...

2015-06-17 Thread René Jansen
Interesting and have it downloaded already. To capture output on Linux and other, I would normally rxqueue the command and loop through the queued lines. “ls | rxqueue" line.0 = queued() do l = 1 to line.0 parse pull line.l say line.l end There might be more sophisticated ways. bes