× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.





Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)

"If you think education is expensive, try ignorance." (Derek Bok)

"What is worse than training your staff and losing them? Not training them
and keeping them!"


Why does the :Input variable need to be cast as a 5000 byte character
filed for bit data to make this work?

Because it's implemented in this way!

From the SQL Reference:
Function: DECRYPT_CHAR
DataType of first argument: CHAR FOR BIT DATA, VARCHAR FOR BIT DATA,
BINARY, or VARBINARY
BLOB
Actual Data Type of Encrypted Data: Character string, Unicode String
Result: VARCHAR
CLOB

Does it really work to use a host variable named RESULT?
I'm wondering because Result is a reserved word in SQL and normally cannot
be used (without double quotes around) as variable name.

Birgitta

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Mike Cunningham
Gesendet: Wednesday, March 26, 2008 21:44
An: 'RPG programming on the AS400 / iSeries'
Betreff: SQL question


My code is working but I do not understand why.

This works...

EXEC SQL SET :Result = DECRYPT_CHAR(cast(:Input as char(5000) for bit data),
:pw);

This does not.
EXEC SQL SET :Result = DECRYPT_CHAR(:Input, :pw);

:pw has the password that field was encrypted with
:Input and :result are 5000 byte character fields

D Input S 5000
D Result S 5000

Why does the :Input variable need to be cast as a 5000 byte character filed
for bit data to make this work?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.