Re: Issue with Decryption API-QC3DECDT

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>

I am resending this message mostly because I need to test my re-subscription per my prior attempts at replying-to or posting a new message [via NNTP], and even contacting the administrator of the list have all failed. As I recall the OP followed-up in the thread on c.s.i.a.m reporting some sort of resolution.