Re: Line-ending for IFS test stream file -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

No, the LF characters are missing (removed) at the end of every line. So
if there's 15 lines of data, the file is shortened an extra 15 bytes and
all the <CRLF> end-of-record delimiters are now simply <CR>. Strange, eh?

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 06/03/2015
04:29:06 PM:

----- Message from John Yeung <gallium.arsenide@xxxxxxxxx> on Wed, 3
Jun 2015 15:22:14 -0400 -----

To:

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

Subject:

Re: Line-ending for IFS test stream file

On Wed, Jun 3, 2015 at 2:41 PM, <MichaelQuigley@xxxxxxxxxx> wrote:

The PC process which later uses the data doesn't interpret these as

blank

fields.

Generally speaking, I find processing stream files on the PC much
easier than processing them on the i, so if I control both ends, I do
the "simplest possible thing" on the i, and delegate the rest to the
PC. But that's neither here nor there.

I call the write API using my revised data. Then I have to use
the ftruncate() API to shorten the file to its new length.

Well, the point of ftruncate() is to set the new size, so could it be
that you've specified a size that is one byte too small?

John Y.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.