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



Jon Paris wrote:

On 9-Jan-08, at 12:52 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

> If I define a field as follow:

> D FOOT_NOTES_FIELD...
> D S 65535A INZ(*BLANKS)
>
> DOW NOT %EOF(RFQFOOTNPF);
>
> FOOT_NOTES_FIELD = %TRIM(FOOT_NOTES_FIELD) + %TRIM(FOTNOTE) + '|';
> READE (RFQ# : QSTRAT_ITEM_NUMBER) RFQFOOTNPF;
>
> ENDDO;

1) Given the current field definition, the second %TRIM is a waste of time and the spaces removed will immediately be reinserted when the resulting string is shorter than the max length.

I think both trims might be required, but it depends on whether or not the trailing blanks are important in the target file format.

Suppose the file is looks like
RFQ# ITEMNUMBER FOTNOTE
1 1 'A '
1 1 'BC'
1 1 'D '

If RFQ# = (ITEMNUMBER = 1), with second %TRIM() we'd have FOOT_NOTES_FIELD = 'A|BC|D ... ', but without the second %TRIM(), we'd have FOOT_NOTES_FIELD = 'A |BC|D ... ' (where ... represents a whole lot of blank spaces).

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.