Macro> command can't take a Let variable?

[support]

Actually, annoyingly, there does appear to be a problem. It does seem to be the case that only the first variable is being passed successfully into the macro. Another bug to fix!

A workaround until then:

Let>RP_WAIT=1
Run>c:\blablabla\msched.exe c:\blablabla\somescript.scp /var1=something /var2=somethingelse /var3=another

Apologies for this, we'll fix it and release a patch asap.

[support]

Another workaround:

Macro>%SCRIPT_DIR%\MacroB.scp /vars=fred;sally;beatrice

MacroB:
Separate>vars,;fields

Now you have fields_1, fields_2 and fields_3 containing fred, sally and beatrice respectively.

[Bob Hansen]

Macro>%SCRIPT_DIR%\MacroB.scp /vars=fred;sally;beatrice

MacroB:
Separate>vars,;fields

Now you have fields_1, fields_2 and fields_3 containing fred, sally and beatrice respectively.

Confused about this. If MacroB.scp has more than three variables, then which ones of them pick up fred;sally;beatirice? The first three in the script? Are these first three variables always named fields_1, etc.?

The first workaround you noted seems more correct.
-----------------------------------------------------------------

Hmmm....nevermind confusion above......I see you are using Separate. So now I would take original variable1 and make it equal to field_1, etc.

Neat....., but need to modify to add missing comma:
Separate>vars,;,fields