| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Running VMS T1.2.7
I'm sure someone else must have seen this, but I can't see anything in the Notes
file since 1.2.7 was released.
I have set up an alarm which should mail me when it fires. When the alarm fires
notification displays it correctly, but no mail is sent. Checking the log file
it would appear that the description is being used as the personal name.
MCC 0 ALARMS RULE link_down
AT 13-MAY-1992 13:10:44 Characteristics
Examination of attributes shows:
Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.
COM;8
Exception Handler = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPT
ION.COM;8
Description = ".reo.reotn1 link is down"
Category = "HDLC"
Queue = "mcc_alarms"
Parameter = "rdgeng::pratt"
Expression = (OCCURS (Node DEC:.reo.reotn1 HDLC
Link syn-0-0 Link Down))
Perceived Severity = Critical
Probable Cause = Unknown
Part of .log file - I can mail the entire log if it is required.
$ !
$ ! Mail the alarm.
$ ! RULE = the rule name, TIME = the time of detection, PARAMETER = the dist
ribution
$
$ personal_name = F$EDIT (F$EXTRACT (0, 25, " .reo.reotn1 link is down"),
"COMPRESS,TRIM")
$ mail/subj="Notification of alarm "" MCC 0 ALARMS RULE link_down 13-MAY-
1992 12:38:19.34"""/pers=".reo.reotn1 link is down" mail_alarm_00000A45.tmp " rd
geng::pratt"
%MAIL-E-ILLPERNAM, .reo.reotn1 link is down is an illegal personal name
$ !++
$ ! Delete the data file
$ !-
Ian Pratt
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2990.1 | work around mail's limitations.... | DADA::DITMARS | Pete | Wed May 13 1992 11:08 | 18 |
Now that you know that the description field is going to be used as a personal name for VMS mail, re-create the rule using a description that will be a valid VMS mail personal name. Experiment. I think it doesn't like the leading "." Mcc1� mail/perso=".reo.reotn1 link is down" nl: ditmars %MAIL-E-ILLPERNAM, .reo.reotn1 link is down is an illegal personal name Mcc1� mail/perso="reo.reotn1 link is down" nl: ditmars New mail on node MCC1 from MCC1::DITMARS "reo.reotn1 link is down" (10:08:11) p.s. I've QAR'd this against alarms, but I doubt we'll be able to address it by the ship date. We could probably attempt to mangle the description to ensure it was a valid personal name. | |||||
| 2990.2 | Start your description field with alpha. | TOOK::NAVKAL | Wed May 13 1992 16:43 | 32 | |
To expand on what Pete said in .1, the personal_name
field in mail requires first character to be alpha!
Even white space is not accepted! Sorry we didn't catch
this earlier.
- Anil
<<< Note 2990.1 by DADA::DITMARS "Pete" >>>
-< work around mail's limitations.... >-
Now that you know that the description field is going to be used as a
personal name for VMS mail, re-create the rule using a description that
will be a valid VMS mail personal name.
Experiment. I think it doesn't like the leading "."
Mcc1� mail/perso=".reo.reotn1 link is down" nl: ditmars
%MAIL-E-ILLPERNAM, .reo.reotn1 link is down is an illegal personal name
Mcc1� mail/perso="reo.reotn1 link is down" nl: ditmars
New mail on node MCC1 from MCC1::DITMARS "reo.reotn1 link is down" (10:08:11)
p.s.
I've QAR'd this against alarms, but I doubt we'll be able to address it by
the ship date. We could probably attempt to mangle the description to ensure
it was a valid personal name.
| |||||