Well there are probably circumstances where 16 bytes may well expand to more than 50. Assuming that normal compression techniques are in play then (say) 60 blanks if included in the encrypted string would probably compress down to 3 or 4 bytes.

Why not make the field bigger and see what you get?


On 2013-11-21, at 9:50 AM, Jon S <rvrratjon@xxxxxxxxxxx> wrote:

I am trying to use QC3DECDT to decrypt an encrypted field which was also encrypted with QC3DECDT. Sometimes (6 out of 2381 records ) I am getting CPF9DD6 which is "Length of area provided for output data is too small.". I have my clear data output length set to 50 which should be plenty big, as the first one I am getting an error on is only 16 characters encrypted. Can anyone help?

Thanks, Jon

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.