I also ran into the same issue the other day. When DESCRIPTION is followed by more than one value, it produces all sorts of errors.
resorting to creating the text, as in the first example works, but it's messy and defeats a lot of the "neat" reasons for using RAISE as extoled in the doc.
Discovered today that using a variable following DESCRIPTION does not work at all, the variable name is made uppercase, and that becomes the description.
Using more than one word in the description causes errors, have to wrap them in quotes.
Don't know if this is the way it's supposed to work, but having a rexx variable for the DESCRIPTION value would be very nice. (example two)
So in Michael's original post, BOTH variations won't work, but at least the first one doens't cause RPC errors.
搜索
论坛
Home
回顶部
1. Bug in RAISE ?
g.yi.org Hits:0
