×
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 22-May-2016 06:28 -0500, Birgitta Hauser wrote:
I'd open a PMR - seems to be a bug.
I am not a customer, so I can not; I am merely a concerned iCitizen.
Because DB2 LUW 11 has the same restriction documented for use in a
routine-body [procedure, function, or trigger (trigger-body)], while not
having any explicit note about [dis]allowance in
dynamic-compound-statements [that I could find], by having opened the
topic, I was mostly /wondering aloud/ if that statement really is
allowed there; probably not many LUW DB2 lurkers here though. But if
allowed in that other DB2 variant, in a d-c-s, then someone who is a DB2
for IBM i customer, and who might eventually want the capability, such a
person might want to pursue the issue as a defect.
I did consider submitting a doc comment [probably just as good as a
PMR, and something I can do, with just an IBM ID], but figured I would
await followups to this topic; though I will probably forget soon, that
I ever wrote any of this :-Q I will probably only remember when I ever
again try to use that statement again in a d-c-s; and recall easily
enough that I can just do the EXECUTE IMMEDIATE [no matter how daft] to
circumvent, if ever I want.
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
