Re: Question on how Date parameter in sql procedure is handled by RPG.

I attempted to duplicate this over the weekend defining the sql procedure and test program similar to the full fledged version. My result was as expected and passing an illegal date caused an error.

The original program validate the passed date so I'm not concerned. It must have been my testing causing strange results.

Rob


On 1/7/2016 10:04 AM, CRPence wrote:

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.