Re: Data Structures for IO (Re: overlaying arrays in v5r1) -- 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.

Not sure if this is the issue, but I find I generally need 3 DSs for a record. #1DS is the original data, populated with the first, unlocked, read. #2DS is the new, updated data from the user workstation, and #3DS is the data in the original record when I go back to get the record for the update. At update time I compare #1DS and #3DS to be sure they are still identical. If not identical, then the record has been updated in the meantime by another workstation. If they are identical then I need #2DS to populate the record word with the new, updated data.

On 1/21/2014 5:55 PM, Sam_L wrote:

On 1/21/2014 11:33 AM, Joe Pluta wrote:

Ugh. I've just had to rip data structures out of a whole bunch of
programs. It's not that I'm against the idea in and of itself, it's
just that it's not a wholesale rip and replace, for several reasons.
Here are two of the biggest:

1. You need different data structures for the input and output.

I'm also somewhat annoyed by this. If I have a physical file with a
single format, can someone explain why I need to have both an *INPUT and
an *OUTPUT DS? There must be something that I'm missing and I'd like to
know...

Sam

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.