Re: Removing blanks from a varning length field. -- RPG400-L

ideally result should have come like below :-

Display Report
Report width . . .
Position to line . . . . . Shift to column . . .
Line ....+....1....+....2....+....3....+....4....+....5....+.
TESTFILE
000001 707fbe32-0dbc-41e0-888f-5bc40de8c20d2P9AMPCTQ4CZ
****** ******** End of report ********

But when my program runs it ends up giving below result which is ideally
not correct due to those unwanted values after this value '
*707fbe32-0dbc-41e0-888f-5bc40de8c20d2P9AMPCTQ4CZ*'

So my program gives below result of :-
runqry () rishi/test file

Display Report

Report width . . . . . :
500
Position to line . . . . . Shift to column . . . . . .

Line
....+....1....+....2....+....3....+....4....+....5....+....6....+....7
TESTFILE

000001 707fbe32-0dbc-41e0-888f-5bc40de8c20d2P9AMPCTQ4CZ****************

****** ******** End of report ********

so these stars **** coming after Z (after decrypted value are unwanted ones
for me so I want to remove them withing my program itself but some how
unable to remove them)

Thanks

On Tue, Nov 19, 2019 at 11:52 AM Rishi Seth <rishiseth99@xxxxxxxxx> wrote:

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 could you please refer
below link to advise for this program code to resolve this issue.

*https://code.midrange.com/abc9f7368e.html
<https://code.midrange.com/abc9f7368e.html>*

Thanks

On Mon, Nov 18, 2019 at 11:29 PM Bruce Vining <bruce.vining@xxxxxxxxx>
wrote:

From an earlier posting:

-- From your code, the following does you no good because the
target
--variable is not variable-length.

--eval pos1= %scan(' ':encodedExchangeToken);
--eval encodedExchangeToken = %subst(encodedExchangeToken:1:POS1-1);

-- If you change the target variable to variable length then you
only
--have to do the following -- no scan required (this sets the prefix
length
--correctly):

Just pointing out that not only is the %scan not required, it's flat out
wrong if there happens to be an embedded blank (x'40') in
encodeExchangeToken.

As pointed out by many, %trimr is a proper way to handle trailing blanks
being found in a varying field (though that's also assuming that there are
not one or more significant blanks (x'40's) in the last byte positions of
the varying field). When variable value length is important using fixed
length fields just introduces unnecessary risk.

On Mon, Nov 18, 2019 at 12:48 PM <dlclark@xxxxxxxxxxxxxxxx> wrote:

From your code, the following does you no good because the

target

variable is not variable-length.

eval pos1= %scan(' ':encodedExchangeToken);
eval encodedExchangeToken = %subst(encodedExchangeToken:1:POS1-1);

If you change the target variable to variable length then you

only

have to do the following -- no scan required (this sets the prefix

length

correctly):

eval encodedExchangeToken = %trimr(encodedExchangeToken);

Then the following will work without any additional changes
required (RPG is smart enough to use only the prefix length and ignore

the

rest):

cmd = 'echo ' + '''' + encodedExchangeToken + ''' ! openssl +
enc -d -aes-128-ecb -K 363631653237354f494d31554c594c4a +
-nopad -nosalt -base64 -A';

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

--
Thanks and Regards,
Bruce
931-505-1915
--
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