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



Thanks for the clarification, Barbara...  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Wednesday, January 03, 2007 6:13 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Output a Qualified DS array element


"DeLong, Eric" wrote:

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?
...
     o                       Sfy(1).ord    j     30

O specs only support "simple qualified names", names in the form DS.SUBF
or DS.ARR(x).  Anything with more than 2 dots, or with an array index
not at the end is a "complex qualified name".  The same is true of D
spec keywords, I specs and C spec factor 1, factor 2, and result.

The limitation is mainly due to compiler-development resource; it would
take a boatload of time to rejig the parsing of those entries to support
complex qualified names.  And partly due to the fact that 14 characters
doesn't give much room to specify a complex qualified name, so the
feature would be of limited use.  The second reason doesn't apply to D
spec keywords, but the first one does ...

To input or output complex qualified names, you have to code some other
temp field on the I or O spec.  (Someone already suggested this.)
    read file;
    Sfy(1).ord = ordtemp;

    ordtemp = Sfy(1).ord;
    except whatever;


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.