Re: eval-corr with record format as source

That is why I stuck. How do I load the record into a fresh copy of a qualified DS? I need this fresh copy of qualified DS to contain values that has already been changed by all sort of business logics that this program has done, but has not yet updated the file.


"Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx> wrote in message news:<mailman.14549.1360343272.10847.rpg400-l@xxxxxxxxxxxx>...

I don't understand why you can't load the record into a fresh copy of
the DS (a qualified copy local to a subprocedure, not used anywhere
else) and then EVAL-CORR it into your target DS?



On 2/8/2013 8:48 AM, Lim Hock-Chai wrote:

I'm. Populating values into the qualified DS is actually what I'm trying to do. I've an export procedure in a service program that takes the DS of the file layout (extname) as parameter. I need to change the program I mentioned in the OP to call this export procedure. I know read/chain opcode will allow me to directly read/chain record into the qualified DS. But it will not work for me. This is because this is a very big on-line program, it has code all over the program that changes values of those fields in the file. There are also several fields in the files that are directly defined in the DSPF. I've to call this export procedure before this on-line program update the record into the file. So, chain/read directly into the qualified DS won't work in this situation.


PS: I attended your "Building Mobile Apps with Profound UI and PhoneGap" webinar". Awesome.


"Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx> wrote in message news:<mailman.14515.1360331936.10847.rpg400-l@xxxxxxxxxxxx>...

You could, of course, use qualified data structures.

On 2/8/2013 7:48 AM, Hockchai Lim wrote:

It seems like eval-corr does not allow using record format name as the
source. I've a program where several fields in a record format have already
been defined as subfields in several different DS. So, using extname to
define this record format name and use it in eval-corr is not an option.
Other than eval one field at a time, Is there any other work around?