× 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.


  • Subject: Re: Colored Break Messages
  • From: John P Carr <jpcarr@xxxxxxxxxxxx>
  • Date: Tue, 18 Jan 2000 20:01:52 -0500


Use the same hex codes for the attributes that have been discussed here
for Source File highlighting(for red, blinking, etc)

In a CL program RTVMSGD of the message id that you want,  
change it with the CHGVAR command (*BCAT, *CAT, etc of 
your hex characters).

Then do a CHGMSGD with the changed message string.
Remember to put a hex 20 at the end of the highlighting to 
return the rest of the message back to normal.

Did these tricks in '85 on a SYS/38

John Carr

Janet Nelson wrote:
> 
> Does anyone know how to send a "colored" break message?
> In the past, I have received critical error messages
> (i.e. disk failures) in red text.  I am familar with
> the hexidecimal codes used for coloring screen text.
> I have successfully used these hex codes in DDS and
> within source members.  However, if I try to use
> these hex codes as part of a string for a break message,
> it is unsuccessful.  Any ideas?
> 
> Thanks.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.