Re: Removing blanks from a varning length field.

sorry i did not understand what you mean but let me explain somethings
clearly:-

1) decrypted output of this AES128 algorithm is uncertain.
2) Encodedexchangetoken field is also uncertain.
3)Output i receive is in record field
4) Record field even though i tried to define both as a data structure and
as a stand alone fields and did %trimr to both of them individually in
different attempts it keeps generating those junk values after decrypted
value
so how can i get rid off these junk values coming after my decrypted value.
so this all above what i had to say in simple language but i am struggling
with code attempts shared in previous mail links and they are ending up
writing junk values after my decrypted value.

So any help which could tell me where i should correct or what should i
correct in my code so that it should only write correct decrypted value in
my testfile not those junk values coming after decrypted value would be
much appreciated.

Thanks much..

On Tue, Nov 19, 2019 at 4:44 PM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331





*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com