Re: SQL encryption v5r4 error

[CRPence <CRPbottle@xxxxxxxxx>]

  Not to imply one should be [a]shamed for asking.... but IMO, the 
syntax diagrams and explanations for each element should be sufficient 
enough that one should not need not call for support.  From the docs, it 
seems obvious to me that argument-01, being the "encrypted-date" as the 
first element after the opening parenthesis, needs to be declared as binary:

     >>-+-DECRYPT_CHAR----+--(--encrypted-data--...

_encrypted-data_
    An expression that must be a string expression that returns a 
complete, encrypted data value of a CHAR FOR BIT DATA, VARCHAR FOR BIT 
DATA, BINARY, VARBINARY, or BLOB built-in data type. The data string 
must have been encrypted using the ENCRYPT_RC2 or ENCRYPT_TDES function.

  If there is something about the documentation for which the 
requirement is unclear, there is a _Send feedback_ link at the top of 
almost every page within InfoCenter whereby suggestions on improvements 
can easily be made.  The procedures at the receiving end, include a 
reply\response to the submitted feedback.

Regards, Chuck

On 27 Apr 2012 11:57, Chris Bipes wrote:
> I get the same results on our system at V6R1.  Google and digging found this:
>
> http://www.code400.com/forum/showthread.php/1111-Decryption?highlight=encrypt
>
>
> "I tried what you did and got the same error. I called IBM Software
> support and was told that you have to use CHAR FOR BIT DATA, VARCHAR
> FOR BIT DATA, BINARY, VARBINARY or BLOB fields rather than a simple
> CHAR field. <<SNIP>>