On 29 Nov 2012 09:47, Lim Hock-Chai wrote:
Did encounter a strange behavior:

The statement below works fine in STRSQL. But if I put that
statement in a Source file and run it with RUNSQLSTM, it failed.
Weird. But no big deal. <<SNIP>>

create or replace variable pa1234.pinewEncPwd Binary(256) default 'TEST124 '

Simply stating that the request "failed" is not very descriptive :-( If there is a reason to expect that the function is supported, e.g. the /failure/ was *not* SQL0084 [although the documentation gives no indication that would be the case], then probably that is an indication that the /strange behavior/ should be reported as a probable defect.? Hopefully whatever the failure was, was not merely due to a missing semicolon, as required by the script processor [at least for lack of an EOF in its place].

IBM i 7.1 Information Center -> Database -> Reference -> SQL reference -> Statements
"The CREATE VARIABLE statement defines a global variable at the application server.


This statement can be embedded in an application program or issued interactively. It is an executable statement that can be dynamically prepared.

This thread ...

Return to Archive home page | Return to MIDRANGE.COM home page