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



So, *IN27 is not the same as the "27" in my display file? Sheesh. But
the problem is that "27" didn't seem to be on in my display file, and
*IN27 was OFF - BUT - ExcludeSys was *ON... 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
AGlauser@xxxxxxxxxxxx
Sent: Wednesday, December 06, 2006 10:39 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Indicator Redux

Dave Turnidge wrote on 06/12/2006 11:26:28 AM:

Because on my display file, I am using "27" as a conditioning
indicator.
When I test it in debug, it doesn't come on, but ExcludeSys is *ON.
Therefore, the action that I am attempting to do on the display file 
isn't happening.

Okay, so you have something like this


     A            SCBRKRPROV     2A  B 18 76DSPATR(UL)
     A  27                                  DSPATR(PC)
     A  27                                  DSPATR(RI)

in your display file?

If that is the case, and you have INDARA/INDDS, your INDDS (the one
referenced on the F-spec), should have something like this:
     D indicators...
     D                 DS            99
     D   exit                  3      3N
     D   prompt                4      4N
     D   changeCusts           9      9N
     D   excludeSys...
     D                        27     27N

Then, in your RPG, you have to always use "excludeSys = *ON", _not_
"*IN27 = *ON".  In this case, *IN27 <> excludeSys.  If you really wanted
to, you might be able to define the indicators DS as BASED(&addr(*IN01))
or something, but IMHO that would be asking for trouble.  Personally, I
avoid the *IN indicators like the plague, because they are just too
difficult to read, and you never know when someone might accidentally
reuse one for another purpose.

So, if I wanted to set the excludeSys based on the result of a file
check, I'd do something like this:
/free
 chain (keys) file;
 excludeSys = %found();
/end-free

Then, excludeSys will be *ON if the record was found, *OFF otherwise.

HTH,
Adam

########################################################################
#############
Attention:
The above message and/or attachment(s) is private and confidential and
is intended only for the people for which it is addressed. If you are
not named in the address fields, ignore the contents and delete all the
material. Thank you. Have a nice day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
########################################################################
#############
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.



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.