Correct, that pointer technique does require a DS to be defined base on
the file. Am I correct to say that your techinque, once used in the
program, will restrict the program from being able to to define a file
DS from then on? Another word, you can't do something like below
(Assuming that ALLOWANCPF file contains all those 5 allowance fields):
d ds
d allowances
D allowance1
D allowance2
D allowance3
D allowance4
D allowance5
d FileDS e ds extname(ALLOWANCPF)
I would expect above to get compile error. File DS sometime is quite
useful, becuase it gives us the ability to pass the entire record to
another program or save it for later comparison.
Jon Wrote:
<clip>
This is a very dangerous practice for reasons I have outlined here and
elsewhere before. Even if the fields remain contiguous in the record,
unless there is a DS based on that record defined there is NO guarantee
that the compiler and/or optimizing translator will keep them that way.
It might work today and then break tomorrow with a simple re-compile.
This article explain a technique that is guaranteed to always work.
http://www.ibmsystemsmag.com/ibmi/february03/enewsletterexclusive/8073p3
.aspx
</clip>
midrange.com
