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


  • Subject: RE: what is unclear about 01 02 03 -Reply
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Thu, 7 May 1998 20:28:18 -0600

Hey Simon !
I wrote a program back in the 70's that used all indicators 01-99 - and
I was DAMN proud of it at the time too !    :-), so then you move on to
KA-KY, U1-U8, OA, OF, OV, etc. etc. - then you start saving them in one
byte fields and restoring them for subroutines !
I think I ran into a problem when I could only AND together 7 lines in
the calcs ! 
It was my first RPG program, and I'd taught myself how to wrote it
reading the manuals on the night shift while I was an operator.


Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Simon Coulter [SMTP:shc@flybynight.com.au]
> Sent: Thursday, May 07, 1998 6:07 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: what is unclear about 01 02 03 -Reply
> 
> At the risk of boring the enlightened and irritating the benighted ...
> 
> Comments should illuminate not reiterate.  Tell me WHY you did
> something not what you did.  The what should be 
> obvious from the code (although some of the examples posted here give
> the lie to that).  The why is rarely 
> obvious.
> 
> Anyone still using the *INKx indicators needs their head read.  Maybe
> the geezers instantly know which key 
> *INKP is but there are more obvious ways;  Assigning *IN01 to *IN24 to
> the function key is more obvious due the 
> mnemonic relationship between the key and the indicator.  Better yet
> is to use the AID byte from the feedback 
> area and avoid the indicators entirely.  Besides you simply don't need
> to use all those indicators.
> 
> Named indicators are already available in RPGIV with pointer support.
> Simply code the following:
> 
> D @Indicator        S                  *       INZ(%ADDR(*IN))
> D Indicators        DS                         BASED(@Indicator)
> D  SflInz                                51  51  
> D  SflClr                                52  52
> D  SflDsp                                53  53
> D  SflDspCtl                             54  54
> D  SflEnd                                55  55
> D  SflNxtChg                             56  56
> 
> Then you can do things like:
> 
> C                     IF      SflRRN > *ZERO
> C                     EVAL    SflDsp = *ON
> C                     ENDIF
> C                     EVAL    SflDspCtl = *ON
> 
> Regards,
> Simon Coulter.
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.