Re: COMPILE ERROR RNF7595

I have no idea what is different. What is means is, don't use an *OUTPUT DS for CHAIN. It is clearly documented that you use *INPUT in certain cases and *OUTPUT in others. It might be of interest to look somewhere around page 440 in the ILE RPG Reference - 6.1 version, I think. That is in the File Operations section, and it is interesting that when data structures are used for all operations, that no I-specs or O-specs are generated. This might be a reason to use DS' for everything. Just a thought stemming from a previous thread you had about writing, where someone suggested just modifying the columns instead of using a DS.

Maybe Barbara will say something about this, but she doesn't have to, in my opinion. It's how it works, I simply think we need to accept what is documented.

There is no evident difference when I look at them in debug. And EVAL-CORR works fine between them - probably they ARE the same for data files. They could be different, I suppose, for display files. Maybe there is an internal flag that knows the difference. That's the kind of thing I love to know about, but in the end, it doesn't matter, eh?

HTH
Vern

On 1/28/2011 7:17 AM, David FOXWELL wrote:

I got this error because I used *OUTPUT on myds definition for a chain instead of *input.
The


RNF7595 20 1 The result data structure does not include a subfield in position 1 for a record format.


What does it actually mean and what are the physical differences between the DS coded with *input, *output and *all?