Here is a link to "DDS for display files":
Here is a link to "Application Display Programming":
To supplement what Vern suggested, you might want to pay particular
attention to Part 3: Programming Application Displays using Panel
Groups. This section of the manual describes how to use the User
Interface Manager (UIM) -- this is what IBM uses internally for many of
the display and "work with" panels you see in OS/400 or IBM i. It is a
very different way to develop a user interface, compared with DDS
display files. The screen layout is described with a "tagged" language,
and it has sections that can be %included -- so this may be more to your
liking, as you can develop your own "in house" standards, etc.
In addition to the above reference, I suggest you try to find a (used)
copy of the book "Unleash the power of UIM" by Richard Schaler, (c) 1994
by MC Press. -- this has been "out of print" for some time and is hard
to find, but perhaps you might get lucky and find a copy in a local
library, or try using "inter-library loan"? It is written in more of a
tutorial style, compared with the "reference manual" above.
Also, search for magazine articles by Carsten Flensburg and others, who
have published various tools and utilities that use the UIM, as it
really helps to have a "working example" to learn from, when learning to
The way your program(s) will interact with UIM is closer to the way a
web application interacts with a browser e.g. via a CGI interface, at
least, conceptually. With UIM, you populate a number of "variables" in
a "variable pool" and then you ask UIM to display a panel, and if the
panel contains any "substitution variables" (it almost always does), it
fetches the values of those "variables" from that dialog manager
(If you have ever worked on IBM mainframes and used ISPF/PDF, then this
concept should sound rather familiar.)
I hope this helps,
Mark S. Waterbury
> On 1/29/2014 6:27 PM, Vernon Hamberg wrote:
Sarah - have you seen the "Application Display Programming" manual from
IBM? It would answer most of what you are asking, although it might take
you a while to get to each area.
But there are examples there of doing various things that might help you.
You are going from web to 5250 - the usual thing today is from 5250 to
web, and often parts of the 5250 screen are parceled out to index tabs,
say, to give better landscape.
Now it is possible to have windows overlay a screen, and those windows
can have the smaller bits or the things you would have had in tabs -
maybe that's a way to go - take your tabs and make DSPF windows of
those, then assign F-keys to make them be displayed over the main screen.
On 1/29/2014 5:05 PM, Sarah Kemp wrote:
Thanks for the explanation. In this scenario, is there a way to set the file-level keywords and available function keys in one file and use them across the whole application, or do their definitions need to be present in each display file? Is there some way to set these with RPG or do they have to be compiled in with the DDS?