|
|
|
|
|
The main purpose of scanit is to scan for tokens in the application source. The tool is designed to scan the source code of custom user-written applications and look for things not supported in Avaya IR.
scanit does not take any command-line parameters. It prompts interactively for the user to enter a directory from which to search for source files. It also allows the user to supply an input file. The user must provide an input file or specify the directory to search.
The following example shows the format of an input file for the scanit tool. The input file includes a list of specific files the tool should scan.
TYPE t
/test/your.t
/tools/my.t
TYPE c
/tools/test/my.c
TYPE sh
/tools/test/hirunner
Note:
You must list all files of the same type after the TYPE declaration. Valid types are c, t, sh, nam, and prg. These types correspond to C source/IRAPI, TAS, shell, screen capture, and Script Builder program file, respectively.
Listing specific files has an advantage over searching directories for unspecified files because, with specific listing, the tool is explicitly told the type for each file. With the directory search option, the tool can determine the file type only through the file extension. For example, if the tool is given only a directory to search and this directory contains extensionless shell files, those shell files, without the .sh extension, will not be discovered and will be ignored by the tool. If the specific shell files are listed in an input file, the shell files will be examined by the tool.
