You can use dot commands in the Command field of a step. They provide access to special capabilities and functions within the system.
You can mix dot commands with ordinary commands in a step and you can have multiple dot commands in a single step. Do not use more than one .scan command in a single step, however, as the system cannot accurately report the command's results if you do.
There is a separate list of dot commands for use with environment variables. See Using dot commands in variables.
Syntax specifications: each dot command description includes a syntax specification, using the following notation:
You can use environment variables for command parameters except where specifically noted.
If a dot command accepts environment variables for parameters, you can also use:
Consider the following .set example:
.set envgroupname "FOO[1,3-5]=`cat foofile`"
In this case, the agent runs cat foofile, which lists the contents of foofile. Using range notation, lines 1 and 3 through 5 are extracted. The .set command then uses those lines to update the existing variable 'FOO' within the environment group named envgroupname.