Re: Removing blanks from a varning length field.

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 11/19/2019
05:52:38 AM:

ok,thanks all for your help and detailed explanation but considering my
scenario as these record and outrec are data structure fields so can't

use

varying keyword so unable to use %trimr properly and program keeps

writing

so called junk values after decrypted value so what can i do neither can
use them as stand alone fields nor could use varying keyword and end

result

is getting those junk values written in my flat file

A data structure can contain a varying length field. But that is
not going to change the amount of storage required for the varying length
field. Then, writing that variable-length data to a file presents a
problem unless the file is to contain nothing by the varying-length data.
If that is the case, then you must write only the valid data to the file.
But, if that file is on the IBM i, then the file is still going to have to
have room to allow for the *MAX length of the varying length field --
unless you define the file on the fly and give it a record length which
matches the length of the valid data in the varying length field. So,
unless the processes you are passing the data to will also accept a length
parameter to define the amount of valid data -- then you're stuck.


Sincerely,

Dave Clark