RE: Array overlay -- 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.

Subject: RE: Array overlay
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Wed, 21 Jul 2004 18:13:31 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Mel's answer works, but I would suggest that an easier and less error prone
approach is to use a group field - i.e. do not define a length for MaxPtyA -
it is not needed. Like so:

D  MaxPtyA
D  MaxPty1                      10i 0 Overlay(MaxPtyA)
D  MaxPty2                      10i 0 Overlay(MaxPtyA:*next)
D  MaxPty3                      10i 0 Overlay(MaxPtyA:*next)
etc. etc.

The compiler will work out the size of MaxPtyA - you don't need to.

Jon Paris
Partner400
www.Partner400.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Array overlay , Barbara Morris
RE: Array overlay , rob

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.