× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 24-Feb-2015 05:04 -0600, Anil Kumar wrote:
<<SNIP>>

When we are trying the see decrypted value of a field then Decryption
API returning the garbage value at 16th position character and rest
of decrypted character value's are correct .

<<SNIP>>

value should be return as: 1222222222222222222
but API return garbage value at 16th position
i.e. the VALUE returns as: 122222222222222u222

<<SNIP>>

CALL 'QC3DECDT' USING IN-CIPHER-DATA
LENGTH-CIPHER-DATA
ALGO
ALGO-FMT-NAME
KEYD
KEYD-FMT-NAME
CRYPTO-SP
CRPTO-DEVICE
OUT-DECRYPTED-VALUE
LOA-DECRYPTED-VALUE
LENGTH-DECRYPTED-VALUE
ERR.

<<SNIP>>

Any inputs/insights will really help us.


Use debug to review all of the inputs and the declared lengths of the storage areas before the CALL and then review the outputs for all of the in/out and output parameters on the CALL. Most notably, refer to my comments in reply to the same message posted on c.s.i.a.m:
<https://groups.google.com/d/msg/comp.sys.ibm.as400.misc/sEyHdtf-d_Q/NHwWb1woRJkJ>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.