Hi Erich Steinb,
Thank you for your reply:
Hi Bertram, first opening your log file with
call stream Windower_Logs'\'logfile_name,'
C','OPEN READ SHARED'
might do what you want
I tested it using the following code with rexxtry:
fn = 'Ibhalliwell_2014.09.13.log';
call stream fn,'C','OPEN READ SHARED';
input_lines. = '';
do i = 1 to 999999999 while lines(fn);
input_line.i = linein(fn);
end;
input_lines.0 = i - 1;
do i = 1 to input_lines.0;
say i '-' length(input_lines.i) '-' input_lines.i;
end;
say input_lines.0;
What I got was an improvement, but ....
1 - 0 -
2 - 0 -
3 - 0 -
.
.
.
4451 - 0 -
4452 - 0 -
4452
........................................... rexxtry.rex on WindowsNT
Thus now the "lines(fn)" is working fine but the input lines are still null.
As the Windows commands type and copy are able to read the file, I know it
is possible, but how using ooREXX? My fear is that the existing methods
used by ooREXX with its I/O will preclude this from working UNTIL there is
a bug fix and/or feature enhancement.
Another QUESTION: Is a situation like this in the ooREXX test suite? (In
other words does the ooREXX test suite try to read an open file in a
read/only manner? If yes, I'd be happy to look at that code as an example
of a good way to accomplish this task. If no and it is valid to do as I
desire, adding this might be good for the test suite.
Again, Erich, thank you for your reply and positive step in the correct
direction.
Thanks,
Bert.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
