×
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.
Take a look in the manual:
http://tinyurl.com/dspatr-pfields
Note that it says DSPATR P-field does not support MDT, OID, PC or SP
attributes.
It makes sense if you think about it. DSPATR is "Display Attribute",
it's supposed to define the attributes of how something is displayed --
i.e. what it looks like.
So reverse image, high intensity, underscore, blink, and colors all make
perfect sense. But "position cursor"? (As well as those other things)
really doesn't make sense as a display attribute.
I wonder what the history is here? How did those come to be specified
as display attributes? Why didn't they create a separate, more
appropriate keyword for this?
In the underlying 5250 code, all of the hex codes correspond directly to
field display attributes that have the exact same hex codes -- with the
exception of the 4 unsupported ones, and also PR=protect.
Anyway, it is possible to control the cursor position with hex codes --
but not in the same way, and not with the DSPATR keyword. You'd need to
send the 5250 Insert Cursor or Move Cursor orders, instead. This is
what the DDS compiler will generate, under the covers, for DSPATR(PC).
On 1/14/2015 8: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....
Any helpful pointer would be appreciated.
Dutch
midrange.com
