|
Yes, I thought about such procedures. But for a some small arrays this seems to me a little bit oversized. In between I've found a better solution and it works: d #ds ds d #value1 like(#array) overlay(#ds) inz('Val1') d #value2 like(#array) overlay(#ds:*next) inz('Val2') d #value3 like(#array) overlay(#ds:*next) inz('Val3') d #array 4 dim(3) overlay(#ds) Titus "Fisher, Don" <dfisher@xxxxxxxxxxxxx> schrieb im Newsbeitrag news:9C0D76BA2F7AD411953000805F85414707C03726@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > I believe your problem lies with the LIKE keyword. You're defining each > #value field as being the same as #array, which is a three occurrence array. > > By the way, if this array is used in a lot of places, you might consider > writing some load and retrieval procedures and placing them in a service > program. > > Hope that helps. > > Donald R. Fisher, III > Project Manager > Roomstore Furniture Company > (804) 784-7600 extension 2124 > DFisher@xxxxxxxxxxxxx > > > <clip> > What is a good way to initialize an array with different values in the > D-Specs? I want to replace the old fashioned way with tables and constant > data at the end of the program. Another reason is placing the array in an > include-sourcefile. Here is my example. But it doesn't work: > > d ds > d #array 4 dim(3) > d #value1 like(#array) overlay(#array) inz('Val1') > d #value2 like(#array) overlay(#array:*next) inz('Val2') > d #value3 like(#array) overlay(#array:*next) inz('Val3') > <clip> > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > >
As an Amazon Associate we earn from qualifying purchases.
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.