Here’s the URL to the API finder: http://publib.boulder.ibm.com/iseries/v5r3/ic2924/info/apis/apifinder.htm
In the ‘Search by descriptive name’ field, type ‘encrypt’. One of the APIs listed will be ‘… QC3ENCDT, Qc3EncryptData)’.
I uploaded a trivial working example of Qc3EncryptData and Qc3DecryptData in the <a href=”http://itknowledgeexchange.techtarget.com/itanswers/using-encrpt-data-api/”>Using Encrpt Data API</a> thread. It uses the Triple-DES algorithm to encrypt and then decrypt a simple text variable, with a definitely unsecret ‘secret’ key.
If you test the APIs a couple times, they’re really not that big of a deal.
The problem comes when you try to figure out what to do with encrypted data.
For example, surely you wouldn’t be expecting ever to use those numbers as part of an index key, right? No sorting, no random retrieval — that kind of stuff? Once encrypted, the only thing they’ll ever be good for is decrypting. (Once decrypted, of course, your programs can do anything they want. But while encrypted, they’re useless.)