|
Unfortunately, a question asked a different way still has the same answer -- NO. :( Had there been an RPG-compiler designed user interface to arrays for any of the other types of indicators, I would have included those types as well. Only the 99 numerical indicators are candidate for the technique. Gary Guthrie > That article as well as the code below are fine if you want to assign the > *INK(x) indicator to one of the numeric valued, (01-99), indicators via DSPF > defined indicator keywords. I believe the question can be expanded upon by > asking the following; > > Is there a similar type of array for the *INK(x) indicators as there is *IN > or is *INK(x) a portion of *IN array that is addressable via Named > Indicators fashion? > > Regards, > Jon A. Erickson > > From: Gary Guthrie > > > > You must use CFxx(yy) type nomenclature to use named indicators in the > > fashion you describe. > > > Gary Guthrie > > Technical Editor, NEWS/400 and author of "Use Named Indicators with RPG > > IV" (February 1997) > > > -----Original Message----- > > > Indicators can be Redefined as something easier to > > > understand. Like.. example(s). > > > > > > Ex 1) > > > > > > D IndPtr * INZ(%ADDR(*IN)) > > > D DS BASED(IndPtr) > > > D F03Key 3 3 > > > D F05Key 5 5 > > > > > > or > > > > > > Ex 2) > > > > > > D F03Key c 3 > > > D F05Key c 5 > > > > > > My question is ...... > > > > > > What about the *INKx used in an RPG Program? > > > > > > The DDS is defined as > > > A CF03 > > > not like.. > > > A CF03(03) +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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 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.