CALL Command loses parms when prompted

[dickdonohue]

With this existing line of code, press F4. The prompt only picks up the first parm. The other parms are lost:

CALL       PGM(MYPGM) PARM( (&PARM1) (&PARM2) (&PARM3) )

It doesn't matter if there are spaces between the parentheses and variables.
Also, the same issue happens with this line of code (it does compile even though technically, it is not formatted "correctly")

CALL       PGM(MYPGM) PARM(  &PARM1  &PARM2  &PARM3 )

[bobcozzi]

The formatting doesn't matter to the prompter; valid syntax is all that matters. Since I haven't used the "new" CL CALL syntax since they enhanced it to support parameter definitions, I likely did not create a test scenario to verify we had it working.
I just checked and yes, I am on V7R3 and that feature didn't appear until V7R4. So I'll have to find a V7R4 box to connect to and verify. I can possibly do that on Pub400.com I will keep you posted.

[bobcozzi]

I've detected the issue. I signed onto Pub400.com and testing the VSCODE CL Prompter. The new PARM parameter is an ELEM that contains sub-ELEMs and we had not yet implemented that level of nesting. Even the RUNIQRY or CPYF CL commands didn't have that type of nesting. So this is "new to us".
GIve me a few days to implement it and test it.
Thanks!