Filter
Top Products
A Summary of Commands mkAlerter
UCS 1000 R4.2 Administration 585-313-507 Issue 3 April 2000 531
pieces, one containing main () and the other containing everything else. The
source file containing main () ends in “Main.c” with truncation as necessary.
Once produced, this file, like the make file, is be overwritten. If you want to
produce your own initialization, you can use the -M option and then make
your changes to the “*Main.c” file.
Normally, the make file specifies that the executable to be produced by this
alerter description is the same as the name of the alerter description minus
the “.A” extension. The -o option allows you to specify an alternate
executable name. This is used when the make file is generated.
The code template files are normally expected to exist either in the current
directory or in /usr/lib/alerter. If the templates are not found in either of these
places, mkAlerter uses its own internal copies, but also reports the fact. If
the templates exist elsewhere, an alternate path can be specified with the -p
option. Each directory that should be searched is separated by a colon (:), the
same as a normal UNIX description.
To get the initial template files, the user can specify the -t option. This causes
mkAlerter to create each of the required template files using its internal
copies. At this point each site may, if desired, alter these templates to
produce alerter code appropriate for its needs. By itself the -t flag does
overwrite existing template files. The -f flag causes the new templates to
overwrite existing ones.