M
Marian Edu
Guest
Hey Fernando, the fact that you don't support it is understandable as long as there is no way to have a CLOB variable... for me a buffer field handle is well, a HANDLE 
Anyway, just said will make it for a nice feature and doubt it's that hard to have it added... as long as you guys figure it out how to set the value for primitive data types in a buffer field handle I have all the faith in the world you could do the same for longchar(clob)/memptr(blob). Meanwhile will be nice to have a note in documentation to clear things out. parameter-value An expression whose type is compatible with data-type. If iomode is "OUTPUT" or "INPUT-OUTPUT", each of the following must be true: parameter-value must represent a program variable or a NO-UNDO TEMP-TABLE field (perhaps with an array reference). parameter-value must still be in scope and must still be valid when the dynamic invoke is executed. If the output value from the called procedure does not have a data type that matches the data type passed, the output value will be converted to the data type passed.
Continue reading...
Anyway, just said will make it for a nice feature and doubt it's that hard to have it added... as long as you guys figure it out how to set the value for primitive data types in a buffer field handle I have all the faith in the world you could do the same for longchar(clob)/memptr(blob). Meanwhile will be nice to have a note in documentation to clear things out. parameter-value An expression whose type is compatible with data-type. If iomode is "OUTPUT" or "INPUT-OUTPUT", each of the following must be true: parameter-value must represent a program variable or a NO-UNDO TEMP-TABLE field (perhaps with an array reference). parameter-value must still be in scope and must still be valid when the dynamic invoke is executed. If the output value from the called procedure does not have a data type that matches the data type passed, the output value will be converted to the data type passed.Continue reading...