Compaq GS320 - Manual (Page 274)

D-2 SMC Installation and User's Guide
All events listed in Table D–1 have a priority of 50 and a severity of critical.
Note that event GS_PCI_PBM_SYSEVENT can be triggered by any of three
subevents. These are defined and recognized in the Perl script, as described in
Section D.2.
D.1.1 Loading
SCM.PORT is imported with the import_pcm utility. To do this, open a Comand
Prompt window, change the directory to C:\Cwks, and type the command
import_pcm c:\cwks\port\scm.port .
The PC will need to be restarted after this is done.
D.1.2 Contents
The content of the SCM.PORT file is included in Section D.4. It is supplied for
reference purposes; it is useful for verification and testing (Section D.3).
D.2 MAIL.BAT and MAIL.PL
ConsoleWorks invokes the command script MAIL.BAT when an event is
triggered. MAIL.BAT, in turn, invokes the Perl interpreter, passing the Perl
code filename (MAIL.PL) and the command arguments automatically supplied
to it by ConsoleWorks.
Technical Note: ConsoleWorks requires the intermediate step of executing a
.BAT file, which then executes the Perl script.
These are the arguments that ConsoleWorks automatically supplies to the
MAIL.PL script:
$ARGV[0] Console name
$ARGV[1] Event name
$ARGV[2] Event sequence number
$ARGV[3] Name of event context file
$ARGV[4] Contact name (comma delimited if more than one)
$ARGV[5] User supplied parameter
The contact name field is based on the information provided during setup. It
should be the fully qualified mail addresses of the users who are to be notified
during an event action.
A current limitation of ConsoleWorks is the inability to set up a trigger based on
patterns that span more than one line. When the event
GS_PCI_PBM_SYSEVENT occurs, MAIL.PL parses the resultant context file,