Comments on: RPGLE

By: teandy

teandy — Mon, 26 Oct 2009 16:18:35 +0000

Something else you can do is create your own indicator. For example:

D VALID_FIELD S N INZ(*OFF)

By: aceofdelts

aceofdelts — Fri, 23 Oct 2009 21:25:08 +0000

A technique I’ve used on occaision uses no indicators at all.

Define a text field to the length of your text (so 16 is fine for your example). Reset it to blanks and then fill it with “F19 …” if your history criteria is met (before rendering the screen, of course).

Downside is it might not support use as a hot key (all of my iSeries users do this via an “F” key anyway).

Mike L.

By: tomliotta

tomliotta — Wed, 14 Oct 2009 23:13:43 +0000

…i tried to use H and U indicators in display file to make the field ND…

Review a DDS manual for display files for the DSPATR keyword. In particular, look at the DSPATR(&program-to-system-field) option. You don’t need an indicator to condition non-display (nor most other attributes). You define a hidden program-to-system field and put the hex attribute value into it when you write the display. For non-display, the P-field value is given as x’27′ in the DDS manual. No indicator needed.

Alternatively, you simply pass the text to the display in an output field. When you want it to show up, you put the text in the field. When you don’t want it to show up, put blanks in the field.

Tom

By: nutangujar

nutangujar — Wed, 14 Oct 2009 21:57:41 +0000

Thank you so much guys…

I’was trying to add new funtionality in existing huge program…
i identified some existing chain operations in the program where i can replace indicators with %found()

plus i tried to use H and U indicators in display file to make the field ND but AS400 didnt like it so i cudnt…

I’m really afraid of doing surgery to that existing huge and infamous program so
next I’m planning to try some non-indicator logic which I’m totally unaware of…

Thanks once again!!!
-NG

By: splat

splat — Wed, 14 Oct 2009 20:23:55 +0000

Don’t use indicators for your function keys, use the AID field in the DSPF INFDS.

By: yorkshireman

yorkshireman — Wed, 14 Oct 2009 13:14:42 +0000

Sheesh – I once had a programmer ‘who ran out of indicators’

your logic generally only needs one, file and diplay conditions a few more

time to do surgery on the program.

By: tomliotta

tomliotta — Tue, 13 Oct 2009 22:25:27 +0000

The only indicator that seems to be needed is one that enables the CA19 or CF19 F-key in the record format. Since the conditions already seem to be known in the program, any conditioning indicator(s) also would be known already. What do you need to use an indicator for? You don’t need one to display the [F19=View History] text — that can be done simply by populating a field with either blanks or the text, or perhaps with DSPATR(&P-field).

Or do you need to come up with a new set of resulting indicators in the program?

The real answer is to start getting rid of any indicators going to the screen and being used in the program. Except for a few subfile keywords, no other indicators are required. And numbered indicators in the program can be mostly eliminated, either by using %bifs or by substituting named indicator fields.

Surely you can find a couple indicators that are used in only a couple program instructions and eliminate them. Once replaced by code that doesn’t need a resulting/conditioning indicator, the previously used indicator can be used for your CA19 conditioning.

Tom