[WDSCI-L] CL prompter bug in 5.1.0.3 (5.1.2?)

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

I've found another bug in the CL prompter in WDSC 5.1.0.3 - it is probably 
in 5.1.2, as well. I'm not attached to an IBM customer at this time, so I'm 
reporting it here. (I'm using a timeshare iSeries.)

If I enter

if &error (goto endpgm)

and prompt it, I get an error "Command (GOTO in library *LIBL not found." 
The prompter adds extra parentheses in the command string:

IF COND(&ERROR) THEN((GOTO ENDPGM))

which is bogus.

SEU handles this syntax just fine - in fact, putting parentheses on is a 
time-honored way to isolate a (positional) parameter.

BTW, both of the following are handled correctly:

if &error then(goto endpgm)

if &error goto endpgm

The latter one surprised me, but it also works in SEU. Even in that 
context, this is not normal command parameter processing as I understand 
it, where each unquoted token separated by spaces is a new parameter. 
Unless it has always been the case that the last parameter does not need to 
be quoted if it has more than one word?