SSH Reference Manual

?TACL MACRO
#OUTPUT Macro %0% started with parameters: >%*%<
That macro could be started, for example, using the command below:
ssh usr@host ci -c $TEMP.TEMP.MYMACRO
The TACL process that gets started will display something like the following:
…
$TEMP.TEMP.MYMACRO abc def 123
Macro $TEMP.TEMP.MYMACRO started with parameters: >abc def 123<
It is also possible to set CI-COMMAND to “$TEMP.TEMP.MYMACRO abc def 123” to avoid the requirement to
specify the macro name on the client side. In this case the client command for executing the macro with fixed parameters
“abc def 123” would just be as shown below:
ssh usr@host ci
In cases where a TACL macro should be started but some input from the client side is needed, then it is possible to
access the command specified on the client side. If CI-COMMAND is configured, then the specified client side
command will not be executed but the command in CI-COMMAND. The command specified on the client side is put
into PARAM SSH-ORIGINAL-COMMAND and can be accessed by the TACL macro.
Example content of a macro making use of that PARAM:
?TACL MACRO
#OUTPUT Macro %0% started with parameters: >%*%<
#OUTPUT SSH-ORIGINAL-COMMAND was: >[#PARAM SSH-ORIGINAL-COMMAND]<
If the command ‘test data’ is specified as in:
ssh usr@host ci -c some data from client
then the output would be similar to:
…
$TEMP.TEMP.MYMACRO abc def 123
Macro $TEMP.TEMP.MYMACRO started with parameters: >abc def 123<
SSH-ORIGINAL-COMMAND was: >ci -c some data from client<
Please remember that through this section the assumption is that a 6530 terminal is on the client side.
146 • Configuring and Running SSH2 HP NonStop SSH Reference Manual