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



So why not, assuming it's conditioning a PC attribute on MYFLD, embed
the indicator 
number in the name, and call it something like "PCMYFLD40" or
"I40PCMYFLD" or "PC40MYFLD"?

Right, here's what we do.

     FDspF      CF   E             WorkStn IndDS( DspfInd ) 

      //  Display File Indicator Data Structure.
     D DspFInd         DS
     D  PCFld1                40     40n   Inz( *Off ) 


Kurt Anderson
Application Developer
Highsmith Inc

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert
Sent: Monday, December 11, 2006 12:19 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Does anyone use indicators anymore?

"Raby, Steve" <agnictsr@xxxxxxxxxxxxx> wrote:
But talking about readibility then doesn't that get confusing if you 
want to do a PC and in the display file it is set using 40 and in the 
program its called something else?

So why not, assuming it's conditioning a PC attribute on MYFLD, embed
the indicator number in the name, and call it something like "PCMYFLD40"
or "I40PCMYFLD" or "PC40MYFLD"?

That same basic idea could also be used for an indicator used to
condition statements or store flags raised by calculations.

I'm not directly familiar with overlaying names on the general
indicators. What release did it come in at, and can more than one name
be overlaid on an indicator that's used for more than one purpose?

--
JHHL

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.