| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4600.1 | the Alarms .DAT files is a superset of arguments p1 - p7 | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Thu Feb 25 1993 10:47 | 15 |
| DaN,
If memory serves me correctly, no promises 8), the Alarms Data file
is named by Argument P8 .. and contains the values of arguments
P1 to p7 plus other information; like Event Arguments. If what you
need is in p1 - p7, then have your script or .EXE work them.
If you what you need is in the data file (p8), the script or .EXE must
open and read the file.
The Data File is written to disk before your Script is executed.
Check with the Alarms Use Manual for the exact definition of the arguments.
/keith
|
| 4600.2 | What's the mechanism that produces the p8-datafile? | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Feb 26 1993 01:15 | 9 |
| Keith,
What I really mean to ask:
How does the ALARMS FM write the data to the log file?
Is there a way to pass the data directly to a program or procedure
without plopping it in a log file first?
-Dan
|
| 4600.3 | Thats easy ... No | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Fri Feb 26 1993 12:48 | 17 |
| >How does the ALARMS FM write the data to the log file?
>Is there a way to pass the data directly to a program or procedure
>without plopping it in a log file first?
Oh - thats easy - No. Alarms creates the data file then starts the
Alarms Security Procedures .. which then calls your procedure .. which
can then execute your .EXE program.
If the information you need is in p1-p7, then you don't have to read
the data file .. But, the data file contains additional information;
like event arguments. It had to be this way because DCL only allows
256 characters per "P" argument...and the event report information
could get very large. Also, There are only 8 "P" arguments, so using
the data file makes the mechanims extensible.
/keith
|