Re: read/chain/write/update with *input/*output/*all DS -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Well, Jon, There lies the problem: To do what you suggested, that means
each time the program performs chain/update/write/read, I've to do
remember to do eval-corr to make sure all version of qualified DS
contains the same data. The best choice seems to be to not use
result-field DS (fall back to global). But this has its own problem
also.

"Jon Paris" <jon.paris@xxxxxxxxxxxxxx> wrote in message
news:<mailman.3088.1282055610.2619.rpg400-l@xxxxxxxxxxxx>...

On Aug 17, 2010, at 1:38 AM, rpg400-l-request@xxxxxxxxxxxx wrote:

This is because RPG requires the result-field DS to match the record

format
of the file that the IO code is executing on and for the write
opcode, the
result-field DS must be of a *output type. Below is how I normally

handle
this type of situation. Is there a better way than this?

Well I would use EVAL-CORR for this - that's what it was designed for.

The *ALL option is now available, but I think only for EXFMT.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.