I had played around with this once before. Support for attribute bytes in a message is variable, depending on what is displaying the message. <p>It works with status messages. <p>Messages sent to IBM functions (such as the *ESCAPE example), depend on the program. While testing I found that PDM shows the attributes, but a menu (such as MAIN), does not. <p>Sending to a queue, and then DSPMSG, also doesn't work. DSPMSG replaces the attribute bytes with RI blocks, and it all shows up as normal (green). <p>On the positive side, the list of attribute values is documented in the DDS Reference: Display Files, under the DSPATR keyword. <p>Use the table for nonprotected fields (x'20' through x'3F'). The other table gets converted to displayable characters; e.g., x'A0' is ~ (tilde), and x'A1' is µ (LC mu).

I have had this posted on my bulletin board for some time: <p>Color Code Attributes For 5250 Displays <p>Green 20,21,24,25 <BR>
White 22,23,26 <BR>
Red 28,2E <BR>
Turquoise 30,31,34,35 <BR>
Yellow 32,33,36 <BR>
Pink 38,39,3C,3D <BR>
Blue 3A,3B,3E <p><!--mccodelink_begin--> <BR>
<!-- do not remove --> <BR>
<hr width=50 align=left><small><a href='http://www.mcpressonline.com/mc/showcode@@.6b21101a/1' target='_blank'>Code</a></small> <BR>
<!--mccodelink_end-->

I started using this back in 1986 or so when Greg Veal published an article on doing this in "Q38 Technical Journal". <p>It is interesting that IBM hasn't done much with it todate. <p>The courious thing to me, however is that the author of this TNT article uses the BLINK attribute in the example--the very thing user interface designers say not to use. Oh well, doesn't matter as blink is converted into RED on most display nowadays anway. <p>Fun article!

Here's where different size fonts become useful in 5250 land. For instance you could send a message that says: <p><big><big><big><big>Are you going to blow it</big></big></big></big><tt>again?</tt> <p>Dave

I hesitate to use explicit colors in code. With users constantly changing their screen colors, important messages with explicit colors may be hard to read, or even indistinguishable from the background.

John Driscoll said: "I hesitate to use explicit colors in code. With users constantly changing their screen colors, important messages with explicit colors may be hard to read, or even indistinguishable from the background." <p><troll>That's why we should get rid of PCs and go back to the old 5250 dumb terminals. That way they CAN'T change the colors.</troll> <p>-dan

<i>Daniel Stephens wrote: That's why we should get rid of PCs and go back to the old 5250 dumb terminals.</i> <p>Welllll, , , , at least it would prevent the users "X"ing out of their sessions. <p>Dave

This is a discussion about <B>TechTip: Messages with Pizzazz!</b>.<p align='center'><a href=http://www.mcpressonline.com/mc? This e-mail address is being protected from spam bots, you need JavaScript enabled to view it @.6b1ba9da>Click here for the article</a>.</p>

I used colored messages for some time prior to posting codes on: <p><a href="/mc? This e-mail address is being protected from spam bots, you need JavaScript enabled to view it @.6ae42d49/2">ukpi1b "Add color to messages" 10/23/02 11:44am</a> <BR>
<a href="/mc? This e-mail address is being protected from spam bots, you need JavaScript enabled to view it @.6ae51fa2">Issak Brender "TechTip: Same Screen, New Colors" 12/13/02 9:35am</a> <BR>
&nbsp;While it brings some excitement to programmers, it is less appreciated by most users and management. <p> For expended list of hex values check <BR>
&nbsp;<a href="http://www.as400pro.com/servlet/sql.tipView?key=682&category=RPG">http://www.as400pro.com/servlet/sql.tipView?key=682&category=RPG</a>