× 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.



Bill

When you say "instance", do you really mean "element"?

To work with a particular element, you just put the array index in parentheses after the array name. That's just as you said below.

But what you have as the DS declaration might not be valid - the DIM() keyword has to be on the dcl-ds - not on the subfiled, Group.

And I have no idea, without trying it, where your Fld1 and Fld2 fields end up - and Group is not defined here - what is its data type and length? Does it come from an F-spec?

You say you are on 6.1 - I suggest that you use the fixed-format D-specs, not the free-form, which your 6.1 compiler will not understand - RDi DOES understand it, but not the compiler.

HTH
Vern

On 11/6/2014 11:36 AM, Bill Howie wrote:
Jon,

Thanks for the info. In this scenario:

dcl-ds MyDS;
Group Dim(99);
Fld1 char(4) Overlay(Group);
Fld2 char(20) Overlay(Group: *Next);
end-ds;

index <http://archive.midrange.com/rpg400-l/201411/msg00008.html#> -
%LookUp( searchText: Fld2); // This should do it.

how then would I be able to refer to an individual instance of the array?
I'm trying different options and having some difficulty. So say I wanted
to load up the first instance of the array, both fields Fld1 and Fld2, with
data - how would I refer to them?

Fld1(someindexvalue) = data?


Thanks!

Bill


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.