Re: QUSLFLD

It was an ODBC job that failed on these files prompting a RCLSTG and
indirectly my comments.

Again I re-iterate: the API is designed specifically for the purpose of
returning the field information in a guaranteed format, the other file also
happens to contain the data. This is the undocumented/informal aspect of
using this file that I was alluding to, not to any lack of documentation
regarding the existence of this table.

In terms of ODBC (which actually doesn't seem applicable to the original
question as I remember it, or to RPG although I might be missing something)
I agree that this cross reference is probably tied to the ODBC driver.
However, my experience suggests that if the field/table reference columns
get out of whack - and they can because I have seen it happen - ODBC breaks
until a RCLSTG DBXREF is performed.

Pick which ever solution is as robust as you need - I was merely offering
another perspective :)

Regards
Evan Harris


>Maybe you're just not looking at the right place for this being documented.
>Do you suppose that someone doing a client server package calls that API
>and processes the user space?  No, there are some SQL calls that will
>return the structure of a table.  Granted I don't know all of this.  Maybe
>our visual basic odbc brethern are better versed - but then again maybe
>it's buried in the ODBC driver itself.
>
>Rob Berendt
>--
>"They that can give up essential liberty to obtain a little temporary
>safety deserve neither liberty nor safety."
>Benjamin Franklin