Thank you Jon, I do like the INDDS as well. Lets me say things like
when F3_Exit
... some code
etc.
Alas, neither method results in the indicators showing up in Outline view.
Wasn't there something in Ferris Bueller's Day Off about "Eschew Unnamed
Indicators" ? or maybe I'm mis-remembering.
Karleen Bushard || IBM i Software Devloper || HOM Furniture, Inc ||
763.767.3777 || VM1777 || kbushard@xxxxxxxxxxxxxxxx
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx,
Date: 06/29/2012 11:02 AM
Subject: Re: [WDSCI-L] RDP 8.5 Open Service Requests
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
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
midrange.com
