Script Initiated Aborts

Top Previous Next

The scripts have multiple checks that are performed while being run. If any of these checks fail, the script will exit before completion. Below is a list of these possible errors:

•	Command line has a missing required argument

•	Filename following the –sf argument does not exist or is not readable

•	Username or password is not entered within 30 seconds

If any of the above conditions occur, an error message should be displayed which identifies the problem. Below shows a sample error message where the –rf argument was omitted from the command line:

[allan@localhost tcl]$ config_devices -cf cmd_list

ERROR3 Loop NA: Missing required command line argument <-rf>
ERROR3 Loop NA: Aborting Script

[asilver@localhost tcl]$

Another possible reason for the script aborting is there is an error with one of the input files. The input files could be one of the following: setup.var file, the login/password file, or a file used with the –sf argument. The most common example of this would be if the user removes or puts in an extra double quote (“) when editing one of the variables. If this type of error occurs, there will not be a “clean” error message. It will most likely look like a “strange” TCL error message. Below shows an example of one of those variables defined in the setup.var file.

set SCRIPT_HOME [file nativename "/home/allan/net-scripts"]