RE: Interesting subfile feature

I didn't expect output-only fields to be returned from a subfile because
they are not returned from a non-subfile.  Non-subfile records do not return
output-only fields in the input buffer.  Subfile records do.  My original
post simply pointed out the discrepancy and wondered why it was so.  I was
further confused by the fact that the output-only fields do not show an
input buffer position when the display file is viewed using the DSPFFD
command.

Your reply does little to resolve my question, except to note that the word
"subfile" includes the word "file".  Since "display file" also contains the
word "file", I don't see that your response particularly addresses the
issue.  On the other hand, Buck's post, and the specific quote from the
Application Display Manual, does indeed answer the question.  It still does
not resolve the DSPFFD issue, but that's likely just a programming oversight
in the DSPFFD command.

Thanks for your response.

Joe


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Reeve Fritchman
> Sent: Thursday, July 26, 2001 9:24 AM
> To: MIDRANGE-L@midrange. com
> Subject: Interesting subfile feature
>
>
> It's called a "file".  You "write", "read", "chain", and "update" records.
> Why wouldn't you expect such a construct to return values in an individual
> record when you read or chain?

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---