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


  1.  Home
  2. MIDRANGE-L
  3. September 2006

Re: Formatting non-program messages

Using externally defined messages in a message file is more about communications and ease of program maintenance than it is about re-use of message IDs. There are many advantages:
1) It makes it easier to monitor for different errors. (I hate it when commands and programs send CPF9898 escape messages.) 2) When retrieving messages it makes it easier to figure what's going on without having to programatically parse the message text. 3) To find which part of a program sent an error it's easier to searching for a unique message IDs in source is much easier than searching for text strings or for the dreaded CPF9898 message ID. 5) The text of the messages are stored externally, like file record formats, which makes life easier all around, so if you want to change the text of a message you can do so without re-compiling the program (or programs). 

There are probably many more that I can't think of right now.

[Can you tell that I'm a zealous message handling advocate?  ;-)  ]
IMHO all messages whether used once or many times should be defined in a message file. 

AGlauser@xxxxxxxxxxxx wrote:

Peter Levy wrote:
The solution is to not use impromptu messages by creating a message file, adding a message ID to it for you message with the formatting you want, and sending that in the QMHSNDM API call instead of the impromptu message.
I was afraid of that .... it always seems a bit strange to me to define a message ID for something specific to one program. I will give this a try though. 

Thanks for the help,
Adam


#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. 

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.