We've exactly the same problem with tools that send commands to our
RxServer based servers.
I found you always end in trouble when you write the options for the
command sender at the end. Sooner or later you will want to send a
command that includes your special delimiter. I had to change one of our
execs due to such problems.
Write the local option in front, just like PIPE. This way it is easily
parsed too.
PIPE (pipe options) pipstages and options
RO (options for RO) comands
Parsing:
if left(word(arg(1),1),1)='(' then parse upper arg '(' options')'
commandstosend
else parse upper arg commandstosend '' options
Kris,
IBM Belgium, VM customer support
> I wrote a command that sends commands on to another system for
> processing. This command is named (for historical and compatibility
> reasons) "RO".
> The "other system's" command may have its own imbedded parenthesis.
> Meanwhile, "RO" has its own options.
>
> Typical VM commands have options following an open parenthesis. Up
> until now I've been using double close-parentheses, such as:
>
> RO some other system command operands ( some other system
> command options )) RO's own options
>
> That DOES work, but looks rather "inelegant" to my eyes. Perhaps
> someone having experience with other systems might have a more
> elegant solution?
> Obviously, a vertical bar (Pipe's default stage separator) is a
nonstarter.
>
> TIA,
> Mike Walter
