Hi, Dan.
I'm glad I shared that with the list, then.I almost decided not to,
since the tool is aimed at Rexx developers working on the mainframe. If
it can help you with ooRexx development, then that's great to hear.
DJ
On 06/18/2015 10:06 AM, Dan Carter wrote:
> Dave, it might be a big deal
:-)
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
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
Dave, it might be a big deal for me! I use Eclipse as my workbench for
everything from Java to COBOL. Adding ooRexx would be a strong plus.
-Original Message-
From: Dave Jones [mailto:d...@vsoft-software.com]
Sent: Thursday, June 18, 2015 08:16
To: oorexx-devel@lists.sourceforge.net
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
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
