|
Michael, Also, if you don't want ro recompile your file (eg., if you are not sure if the source corresponds with your object), you can simply do a DSPFFD display_file and will get a list of the indicators used by the display file. Regards, Luis Rodriguez > > ------------------------------ > > message: 5 > date: Tue, 4 Apr 2006 11:08:29 -0400 > from: Michael_Schutte@xxxxxxxxxxxx > subject: Re: Indicators in a DSPF > > Sorry, answered my own question. Did a compile of the display file with > the option of *LIST in "source listing options". > > Michael Schutte > Work 614-492-7419 > email michael_schutte@xxxxxxxxxxxx > > > > Michael_Schutte@b > obevans.com > Sent by: > To > midrange-l-bounce midrange-l@xxxxxxxxxxxx > s+michael_schutte > cc > =bobevans.com@mid > range.com > Subject > Indicators in a DSPF > > 04/04/2006 11:05 > AM > > > I just came across a display file that has a bunch of indicators in use > with no logical reasoning behind the use of each. For example, I tend > to > use *In01 thru *In10 as error indicators for the first screen 11 thru 20 > on > screen two. It appears that this display file has just been picking and > choosing for error indicators. What I'd like to know is what indicators > are currently in use. I tried recompiling the source of the RPGLE, but > it > didn't list all of the indicators, some that I know that are being used > were not listing in the RPGLE compile listing. Does anyone know how to > determine this with maybe a CL command, or compile listing option? > > Thanks to all. > > Michael Schutte > Work 614-492-7419 > email michael_schutte@xxxxxxxxxxxx > ---------------------------- Luis Rodriguez IBM Certified Systems Expert eServer i5 iSeries Technical Solutions Caracas, Venezuela
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.