Re: _cipher API vs Qc3Encrypt/Qc3DecryptData vs SQL

Depends on what the point is in encrypting, and data protected from whom. Obviously that does not prevent *ALLOBJ users from seeing the decrypted data, when the VIEW decrypts implicitly; i.e. if the password is in the VIEW or application. The password should probably come from someplace other than stored in the application or the VIEW [key store?], and for an SQL VIEW, be set for the session that reads the VIEW.

I provided some input to a relatively new Redbooks document; I do not recall the document id.... and I have not searched for it.

Regards, Chuck