Re: Removing blanks from a varning length field.

Hi

It's called AES decryption thing also that encoded exchang token is not
fixed wil keep on varying as it comes from other channel so i have not kept
it as a fixed length secondly after use of % trimr so far it seems to be
picking up correct value ignoring those junk values after reading relevant
value from input XML file but when i tried to use these fields as a stand
alone fields then i get these errors:-


Msg id Sv Number Message text

*RNF7031 00 37 The name or indicator is not referenced.

*RNF7016 20 1 Display Length is greater than maximum allowed.

*RNF5191 30 2 The Result-Field is not a data structure when Factor 2
is a
file name.



Please refer below ink in which i tried no to use
DS but to use them as a big stand alone fields.

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

Thanks

On Tue, Nov 19, 2019 at 3:55 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Why are they DS fields? You are not really defining data structures -
just big fields. Also they only seem to be being used for printing and you
could use most anything for that - your real program assumedly doesn't
print anything.

I think it might be useful for you to backtrack and lay out for us what
you are trying to do.

For example - in my experience things like your exchange token are
usually encoded for a fixed length - yet you seem to be dealing with a
variable length field.

In other words I'm not convinced that we are helping you solve the real
problem - rather we are dealing with problems caused by your attempts to
debug the real problems.

On Nov 19, 2019, at 5: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>

<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

<mailto: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 <mailto:

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 <mailto:

RPG400-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l <

https://lists.midrange.com/mailman/listinfo/rpg400-l>

or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx <mailto:

RPG400-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l <

https://archive.midrange.com/rpg400-l>.

Please contact support@xxxxxxxxxxxx <mailto:support@xxxxxxxxxxxx> for

any subscription related

questions.

Help support midrange.com <http://midrange.com/> by shopping at

amazon.com <http://amazon.com/> with our affiliate

link: https://amazon.midrange.com <https://amazon.midrange.com/>

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx <mailto:

RPG400-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l <

https://lists.midrange.com/mailman/listinfo/rpg400-l>

or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx <mailto:

RPG400-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l <

https://archive.midrange.com/rpg400-l>.

Please contact support@xxxxxxxxxxxx <mailto:support@xxxxxxxxxxxx> for

any subscription related questions.

Help support midrange.com <http://midrange.com/> by shopping at

amazon.com <http://amazon.com/> with our affiliate link:
https://amazon.midrange.com <https://amazon.midrange.com/>
--
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