×
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.
Mike Cunningham wrote:
Not sure why exactly the cast needs to be done as it is on the decrypt but it's the only code that works.
Mike:
From how I understand what happens (or more accurately 'how little
I understand' and trying to keep even that small amount simplified) --
When accessing [BIT DATA], you still get the bytes but there is
apparently no chance of it running through some CCSID conversion
when the bytes/characters arrive in the job.
For encrypted bytes, you definitely want to avoid CCSID differences.
By using [BIT DATA], the bytes/characters are handled as CCSID 65535
and no conversion/translation mucks it up. If it was handled as
basic [CHARACTER] data, a change in job CCSID might give different
results to different users. This would seriously disrupt decryption.
So, I'd say that it was just a safeguard in SQL. Perhaps someday it
won't be needed.
Tom Liotta
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.
midrange.com
