Avaya Writing Technician Interface Scripts Instrukcja Użytkownika Pobierz pdf (Strona 29)

Creating a Script File

308660-14.00 Rev 00

1-13

Inserting Comments

You can insert comments into the script file. 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 file, 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 file 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 file, use the

save env

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

following command:

save env test

To read and execute the commands in a Technician Interface script file, 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 file 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

command and then use the

source env

command. The Technician Interface displays each line from the file 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 ... 24 25 26 27 28 29 30 31 32 33 34 ... 115 116

Komentarze do niniejszej Instrukcji

Brak uwag

Avaya Writing Technician Interface Scripts Instrukcja Użytkownika Strona 29

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Oprogramowanie Avaya Writing Technician Interface Scripts