×
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.
David,
INDARA in DDS (
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=/rzakc/rzakcmstdfindar.htm
) specifies that a 99-byte area is passed, containing all numbered
indicators (*IN01 - *IN99). If you don't use INDARA, only relevant
indicators are passed, as individual fields. With INDARA you can add,
remove or change indicators without having to recompile the RPG.
INDDS in RPG (
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=/rzasd/sc092508462.htm
) associates a 99-byte data structure with the INDARA-indicators. If you
don't specify INDDS, you end up using the normal numbered indicators of
RPG. If you do use INDDS, indicators 01 - 99 in DDS correspond with
positions 1 - 99 in the data structure. How you name these subfields is
entirely up to you (but you obviously can't use *IN-names).
Joep Beckeringh
David FOXWELL
Hi all,
I just found an answer to why my program was blowing up thanks to
this thread in the archives http://archive.midrange.com/rpg400-l/
200407/msg00168.html (thanks Eric!)
I made the following modifications: I needed to condition the
display of certain fields. The DSPF already had INDARA but the RPG
only used a ton of *inxx.
So, I added an INDDS and used a named indicator and I got the same
problem as the OP in the above thread.
I've temporarily replaced my named indicator with *in81 until I
understand what's goin' on.
So, do I have to have all named indicators or all *inxx? Can someone
explain how it all works?
Thanks.
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.