×
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.
On 1/14/2015 9:39 AM, rpglist@xxxxxxxxxxx wrote:
I have been trying to find the appropriate hex code for the following:
Reverse Image | Position Cursor.
I have a display file and I'm out of indicators so I'm trying to utilize
the P-fields but I see nothing on IBM's docs for position cursor....
So it turns out that the 5250 is only MOSTLY a dumb terminal. There is
a language used to talk to it (the 5250 protocol). Sample commands are
'field begin', 'field attribute', and 'position cursor'. The 'hex
codes' are field attributes like underline and reverse image. The DDS
compiler conveniently translated DSPATR(PC) to a 'position cursor'
command, but as the documentation says, DSPATR(&ATTR) does not support
PC.
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakc/rzakcmstdfdspat.htm
One way to go is to switch to INDDS / INDARA. This means that you're
going to have to tease out the places where disk I/O conditions screen
I/O. Not always the easiest of things to do, but once you've done it,
all of the display file indicators are isolated from the RPG indicators.
Jon Paris has an article describing this:
http://www.itjungle.com/fhg/fhg091912-story01.html
Another way to go is to use the display file keyword CSRLOC. It
specifies variables for row, column. Kind of messy, since the
row/columns need to be stored somewhere in your program and if you move
the fields on the display file, those row/column numbers need to be
recalculated. This is faster to do than INDDS, but it's always been a
temporary solution for me because someone always wants one more thing on
the display that needs a clump of indicators...
midrange.com
