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



That the best approach when designing a new app. But if you are dealing with an existing app then, unless the display file was created with INDARA specified (and most were not), you've also go to consider changing the display file and checking the program to make sure there is no impact when switching to INDARA.

The other issue with using INDDS is that it does not map to the regular *IN indicators and therefor any O-spec output - of which sadly there is far too much - cannot share the display indictors thereby requiring additional logic to copy any common indicators.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 11, 2019, at 3:58 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

I don't understand all this pointers to indicators stuff. I just do the
following.

dcl-f PLBG01_D01 WorkStn InfDs(gFileInfo)
InDDS(gIndicators)
Include(RD01_02: SFMSG_CTL)
UsrOpn;

dcl-ds gIndicators Len(99);
InvalidFrontierManaged Ind Pos(53);
InvalidErrorDescription Ind Pos(56);
ServiceOrderMode Ind Pos(81);
EditRecordMode Ind Pos(82);
DisplayRecordMode Ind Pos(83);
DisplaySubfileEndOnSubfileMessageQueue Ind Pos(95);
end-ds;





On Thu, Jul 11, 2019 at 12:38 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Easiest way is to use either group fields like this:

d IndicatorPtr2 s * Inz(%Addr(*In))
d ds_indics ds Based(IndicatorPtr2)
d s2_errors Overlay(ds_s2Errors:51);
d s2_descriptionError...
d 1n Overlay(s2Errors)
d s2_investorsError...
d 1n Overlay(s2Errors:*Next)
d s2_statesError...
d 1n Overlay(s2Errors:*Next)

Alternatively you can just use POS and forget the overlay stuff. This is
the way I would do it today e.g.

dcl-ds ds_indics Based(IndicatorPtr2);
d s2_errors char(3) Pos(51);
d s2_descriptionError ind Pos(51);
d s2_investorsError ind Pos(52);
d s2_statesErro ind P{os(53);


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 11, 2019, at 12:20 PM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

i have the below code in my pgm...

d IndicatorPtr s * Inz(%Addr(*In))
d Indicators ds Based(IndicatorPtr)
d sf1_clear 1n Overlay(Indicators:80)
d sf1_#records 1n Overlay(Indicators:81)
d sf1_SflEnd 1n Overlay(Indicators:88)
d ws1_clear 1n Overlay(Indicators:90)
d ws1_#records 1n Overlay(Indicators:91)
d ws1_SflEnd 1n Overlay(Indicators:98)
d s2_error...
d n
d s2_Inquiry_Protect...
d 1n Overlay(Indicators:35)
d s2_protectOnEdit...
d 1n Overlay(Indicators:36)
d s3_error...
d n
d n

d IndicatorPtr2 s * Inz(%Addr(*In))
d ds_s2Errors ds Based(IndicatorPtr2)
d s2_descriptionError...
d 1n Overlay(ds_s2Errors:51)
d s2_investorsError...
d 1n Overlay(ds_s2Errors:52)
d s2_statesError...
d 1n Overlay(ds_s2Errors:53)


I am wanting to simply set off all error indicators by doing...

clear ds_s2Errors

this works but it clears ALL indicators in the %Addr(*In)) pointer...

How can I set a range of indicators off (or accomplish what I'm trying to
do)... in this scenario?
Hoping for a low impact change to %addr(*In) where I can specify an
indicator range.

tia

jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.