Avaya Writing Technician Interface Scripts Manuel d'utilisateur télécharger pdf (Page 27)

Creating a Script File

117382-A Rev. A 1-13

Inserting Comments

You can insert comments into the script ﬁle. Comments begin with a pound sign

(#) in column 1, as shown in the following example:

# The 'echo' command is used to

# output messages to the user’s console.

When you execute a script ﬁle, the system does not display the comments on the

user’s console.

Debugging a Script File

To enable the debug trace facility, use the verbose command. When you enable

the trace facility, the Technician Interface displays each command read from the

script ﬁle before and after its variables have been expanded. For instructions on

using the

verbose command, see Chapter 2.

Saving and Restoring Variables

To save the current list of local and global variables to a ﬁle, use the save env

command. For example, to save the variables to a ﬁle named test, enter the

following command:

save env test

To read and execute the commands in a Technician Interface script ﬁle, and to

ensure that the router saves (restores) all local variables when the script ends, use

the

source env command.

For example, to run the script ﬁle test on volume 2, and to restore upon

completion all local variables saved previously to test, enter the following

command:

source env 2:test

To locate script errors, use the verbose on command and then use the source env

command. The Technician Interface displays each line from the ﬁle before it

executes the line, enabling you to easily locate errors.

For more information about the

save env and source env commands, see

Chapter 2.

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 115 116

Pas de commentaire

Avaya Writing Technician Interface Scripts Manuel d'utilisateur Page 27