×
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 05-Jan-2016 12:24 -0700, Robert Rogerson wrote:
<<SNIP>>
Can anyone explain this behavior.
Perhaps provide an end-to-end re-create exhibiting the issue; a
simple RPGLE source, the compile command for that source, a SQL CREATE
PROCEDURE source, and the source for the example invocations.? Note
also the release [and TR] being used, so as to compare to what is
exhibited for others.
Note: The SQL would have the ability only to set a valid value for a
Date typed RPG variable, and the current date may be the default; refer
to the associated indicator variable first, to determine if the value
for the variable can be /trusted/. From the OP, [beyond not knowing how
the procedure was defined] how the procedure was even invoked is unclear
[e.g. a DATE typed variable has no /blank/ nor /zero/ value] but
possibly, apparently, the invocation were with literal\constant values
for which I believe the expected error is the SQL0180 [for blank] and
the sqlstate=07006 with SQL0301 for a zero value, issued before [and
thus failing before] the procedure is even invoked.
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
