Hello Rick
> Generally, it is impossible to answer questions
> like this without seeing exactly what you are
> doing. I can't speak for others, but I won't even
> attempt to answer the "is this a bug" type
> questions until I have an open bug report and
> am able to reproduce the problem myself.
You are correct. I posted an example of the code several digests back.
Here it is again:
This is a snippet of code:
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 -
.
.
.
1498 - 0 -
In this case the program "Windower4.exe" (http://www.windower.net) is the
one creating / writing the file Ibhalliwell_2014.09.13.log.
Both of the Microsoft Windows (7 / XP x32 & x64) "type" and "copy" commands
(cmd.exe) successfully read and process the file
Ibhalliwell_2014.09.13.log. They provide the actual lines in the file,
while the above Rexx code sees the number of lines in the file, but returns
a null line.
Bert.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
