Thanks Elvis,

Looks like it is also in _RFILE.buf_length.

I'll use that one, otherwise I have to figure out how to get/use the
feedback info. <grin>

I've got those two manuals open, but IMHO they are not organized real
well. In fact, I did find a description of _RFILE and _RIOFB_T. But
the description only cover a few of the subfields not all of them. In
particular, _RFILE.buf_len is not mentioned.

Thanks again,

On Wed, Sep 24, 2008 at 12:26 PM, Elvis Budimlic
<ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
(_Ropnfbk(openFile))->pgm_record_len will give you the record length for the
_RFILE * open file handle (pOpenFile in my example).

As for more info, check out the following manuals:

"ILE C/C++ Run-Time Library Functions"
"ILE C/C++ Programmer's Guide" -- for some reason IBM puts it under
Websphere Development Studio category

There are other manuals I use, but these should suffice I think.


Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and

-----Original Message-----
Subject: Re: [C400-L] Question about _Rreadn C function

How do you know what the record length is?

I don't know ahead of time what file I'll be opening. I suppose I
could use an API call to determine what the record length is, but is
it already there somewhere?

Perhaps in _RIOFB_T or _RFILE?

Speaking of _RIOFB_T and _RFILE. Is there anyplace in the manual that
gives more info on what is contained in these two structures? The
names of the subfields just don't seem to be enough in some cases.


This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by 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.