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



Ignoring the temptation to tell you to stop it because it will make you go blind ... <grin>

I hate that technique and since the introduction of named indicators have exclusively used DS mapping to indicator structures to replace it.

First choice is to use INDDS and then (assuming for example that these are say print control indicators) code it something like this:

D printCtrl ds
D showBal_60 n Overlay(printCtrl: 60)
D highlight_61 n Overlay(printCtrl: 61)
D lineControls 2a Overlay(printCtrl: 60)

D clearControls c '00'

/Free
lineControls = clearControls;
// Or
reset lineControls;

There are better ways of coding that DS if doing the whole thing but you get the idea.

If INDDS is not desirable simply use the same technique and add Based(pIndicators) to the DS definition and add the D spec:

D pIndicators s * Inz(%Addr(*In))

And with that I'll stop and refer any further discussion to RPG400


On 2012-06-29, at 11:24 AM, wdsci-l-request@xxxxxxxxxxxx wrote:

Indicators also do not show up in Outline view when referenced as:

C movea '0000000' *in(60)

might anyone suggest a better coding technique? I like this because it's
short.



Also having an issue with indicators defined in the DSPF not showing in
Outline view for the RPGLE. They are showing in 8.0.3 as unreferenced.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.