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



Would this be useful for you?

DINDICATORS ds
D exit 1n overlay(INDICATORS: 3)
D cancel 1n overlay(INDICATORS: 12)
DNamedInd ds 99
D Errors 3 overlay(NamedInd: 30)inz('111')
D IN30 1 overlay(NamedInd: 30)
D IN31 1 overlay(NamedInd: 31)
D IN32 1 overlay(NamedInd: 32)
...
INDICATORS = NamedInd;

I made a web page showing the whole code. The program works, but it may not be useful for you.

http://www.martinvt.com/Code_Samples/Setting_Indicators/setting_indicators.html



On 1/15/2013 2:39 PM, Buzz Fenner wrote:
On Tue, 15 Jan 2013 10:24:36, Stuart Rowe wrote:

Luis, while syntactically valid, that code would not set on any
indicators. You'd need to base that IndArray on the actual indicator
array's address.

This alternative would work:

%subarr( *IN: 30: 3) = *on;

Stu

This is the sort of thing I was looking for. Just couldn't imagine how to
map the program indicators to the BIF. Appreciate the discussion from you,
Luis, et. al.

However, in the code I'm dealing with, it needs to be function in this
manner:

%subarr(*in:30:3) = '010';

Which the compiler -still- does not like (I apologize for the previous
overly-simplistic example). Unfortunately, when trying to navigate to Jon's
article, Chrome crashes with a Reader Subscription error!!!

BTW, let's say that such use of indicator(s) processing is mainly to - keep
the peace!

"Small steps, Elle. Small steps." Contact

Buzz





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.