
Writing Technician Interface Scripts
1-14 117382-A Rev. A
Running a Script File
To read and execute the commands in a Technician Interface script file, and to
ensure that the router deletes all local variables when the script ends, use the
run
command.
For example, to run the script file test on volume 2, deleting upon script
completion all local variables saved previously to test, enter the following
command:
run 2:test
To locate script errors, use the verbose on command and then use the run
command. The Technician Interface displays each line from the file before it
executes the line, enabling you to locate errors easily.
You can use the
run command with the -s flag to prevent the system from
returning an error message if the
run command cannot locate the specified script
file. The following example shows the
run command with the -s flag:
run -s install.bat
For more information about the run command, see Chapter 2.
Creating Menus
The menu utility allows you to edit existing script menus and to create your own
menus. For instructions on using the menu utility, refer to Using Technician
Interface Scripts.
You can also edit a script menu by directly editing the appropriate .mnu file.
Appendix A shows examples of a script menu and a script.
Note: The run command automatically appends the .bat suffix to the end of
the script file name you specify. If you issue the command
run install, the
system first looks for a file named install. If it cannot find this file, it looks for
a file named install.bat.
Commentaires sur ces manuels