Re: One function to Trim and Edit a number.

Look at IBM's. They define one for every error plus the generics. I used to
define an error message for each error unless I had something that I could
use a reason code but have not lazy in the last few years and just CPF9898
for most things. I always defined second level help but I don't think anyone
ever looked at it.

On Tue, Jul 14, 2009 at 3:59 PM, John Rusling
<jrusling@xxxxxxxxxxxxxxxxxxx>wrote:

That'd work too but I often throw these into a log file as well.

And, to be honest, I've seen message files so overdone at my previous
employers, I grown an aversion to them.

I mean, I wrote a program to track their useage and found that
over 1/2 of them, and there were 1000+ of them, were used in only
1 or 2 places.

John B.

from: CRPence <CRPbottle@xxxxxxxxx>
subject: Re: One function to Trim and Edit a number.

Since sending a message, why not stop using dynamic\impromptu
message [text], and just let the message handler feature replace the
string variable TRIMmed into a message string defined with a
specific message identifier? ADDMSGD MSGID(XYZABCD)
MSGFILE(MyMsgFile) MSG('Customer &1 not found.') VAR((*CHAR 14))
[cmd syntax is suspect\un-verified] and then send the
edited\character result as the replacement variable for send message
and retrieve message.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.