|
Well, you can use array elements in the O-specs. Perhaps a phased disign implementation of the qualified DS. Why not simply remove the qualified and the based DS and create a noncontagious array using OVERLAY? Like
d Stats ds d Array 44 DIM(2) d Ord 11 2 OVERLAY(array:1) inz(*zero) d Lns 11 2 OVERLAY(array:*NEXT)
inz(*zero)
d GSls 11 2 OVERLAY(array:*NEXT)
inz(*zero)
d NSls 11 2 OVERLAY(array:*NEXT)inz(*zero)
Then reference the ord array element (without using a qualified name). If the array is only used once in the programme, why qualify or base a DS on such a DS array? Just the way I would try to do it. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 3-1-2007 at 12:29 rob@xxxxxxxxx wrote:
I am not so sure that it is the qualification that is a problem. I think
it is more the fact that you are trying to use an array element. Do a
little testing and see. Submit a DCR to get them to allow this.
https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change?Ope nForm
Here's one possible solution: PrintDetail(Sfy(1).ord : Sfy(2).ord); P PrintDetail B D PrintDetail PI D Col1 like(something) const D Col2 like(something) const and put Col1 and Col2 on your O specs. >Benefit is that PrintDetail can
also do the worrying about checking for page overflow, etc.
Rob Berendt A co-worker has asked why he cannot specify a qualified DS array element
on an O-spec. I scanned the ILE RPG reference, but did not see anything
helpful. Can anyone shed some light on this restriction? Here's a little snippet to explain the issue... d Sfy ds likeds(Stats) dim(2) d Stats ds qualified d Ord 11 2 inz(*zero) d Lns 11 2 inz(*zero) d GSls 11 2 inz(*zero) d NSls 11 2 inz(*zero) o e PrintLine 1 o 11 '# Of Orders' o Sfy(1).ord j 30 o Sfy(2).ord j 50
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.