A pointer would be a dynamic memory address (based upon the address of *IN in this case) and therefore would not be known at compile time. I wouldn't think it could be made as a constant?
Daron
-----Original Message-----
From: Anderson, Kurt [mailto:KAnderson@xxxxxxxxxxxx]
Sent: Wednesday, October 03, 2012 10:22 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] To be under Indicators or not to be
Can you make the pointer a constant instead of a variable? (Note: your message said 'static' but I read it as 'constant')
-Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Daron Whitehouse
Sent: Tuesday, October 02, 2012 12:37 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] To be under Indicators or not to be
Hi Barbara,
Agreed. I suspected such an explanation would prevent the concept from being feasible. Too bad the address couldn't be made static such that the pointer could not be changed during runtime.
Thanks for the feedback.
Daron
Daron Whitehouse
Systems and Programming Manager
Madico Inc
64 Industrial Parkway
Woburn,MA 01801
781-935-7850 X-196
dwhitehouse@xxxxxxxxxx
www.madico.com
Notice of Confidentiality
This e-mail and any attachments thereto are intended only for use by the addressee(s) named herein and may be proprietary and/or legally privileged. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, without the prior written permission of the sender is strictly prohibited. If you receive this email in error, please immediately telephone or email the sender and permanently delete the original copy and any copy of this mail, and any printout thereof.
The contents of an attachment to this email may contain software viruses that could damage your own computer system. While Madico has taken every reasonable precaution to minimize this risk, we cannot accept liability for any damage that you sustain as a result of software viruses. You should carry out your own virus checks before opening any attachment.
-----Original Message-----
From: Barbara Morris [mailto:bmorris@xxxxxxxxxx]
Sent: Monday, October 01, 2012 8:05 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] To be under Indicators or not to be
On 2012/10/1 3:30 PM, Daron Whitehouse wrote:
The following snippet is a mapped named indicator example (there are other methods):
// named indicators
D p_Indicators S * Inz(%Addr(*In))
D indicators DS Based(p_Indicators)
D In01thru65 65A Overlay(indicators)
D inputUL 1N Overlay(indicators: *Next)
Daron, your indicators DS isn't necessarily always mapped to the *IN indicators. Your p_Indicators pointer could be set to point to some other storage.
Any human can tell that the "indicators" DS is mapped over *IN, but it's not _officially_ mapped over *IN.
So unfortunately, the concept of a mapped named indicator doesn't really exist.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
