Re: Removing blanks from a varning length field.

[Bruce Vining <bruce.vining@xxxxxxxxx>]

> 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