×
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.
On 27 Apr 2012 12:32, Stone, Joel wrote:
How do you guys know all this stuff?? Very impressive.
I found several articles on Iseries SQL encryption, but nothing
about "for bit data".
I have Conte's SQL/400 book and also Howard Arners - nothing about
this (probably because ENCRYPT wasn't supported when published no
doubt).
The Iseries SQL error description didn't help much.
I feel like I should be paying tuition on this list!!
When BookMgr documents were available, I often had a book open for
the function\feature I was working with. After great improvements were
made to InfoCenter, I finally move there. I am rarely ever able to
recall the specific rules for arguments in SQL scalar functions, so for
that I consult the docs for almost every function I would not use "every
day". Even with those functions I use pervasively, there are nuances
that I need to [or at least should] review. For example, SUBSTR() seems
simple enough, but unless I am only working with SBCS EBCDIC, I visit
the docs to know what are the caveats or alternatives.
Since I will surely never memorize the rules for bounds allocation
for encrypted data, I always have to look those up; different for
whether a HINT is coded versus not. Thus, knowing that a 20-byte CHAR
needs to have a 40-byte CHAR FOR BIT DATA is from looking that up in the
docs, not from memory; albeit an SQL FUNCTION to ask for the answer
would be pretty nice, but then I would have to recall that function name
too ;-)
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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.