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




On 08/11/2006, at 10:08 AM, Brian Lewis wrote:

I created a message file and added a message description to it like
MSG('&1 is an invalid value.') FMT((*QTDCHAR 15))

15 is the maximum length this field can take on, but it could be
anything from 0 to 15 in length.

I want the message to appear like
'BLAH' is an invalid value.

But it actually appears like
'BLAH           ' is an invalid value.

I'm sending it with QMHSNDPM. %trimr()ing the message data field doesn't
seem to matter. Setting the message data length field to
%len(%trimr(field)) doesn't seem to matter, either.

Not an RPG question but if you use VARYING data type then just maybe allowed.

Use a VARYING variable and define the message substitution value as *VARY also.
        FMT((*QTDCHAR *VARY 2))

Better to rephrase the message text too:
        Value &1 is not valid.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.