| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4645.1 | Follow-up questions | TOOK::MINTZ | Erik Mintz | Thu Mar 11 1993 11:23 | 4 |
| Which version? T1.3.1? VMS or ULTRIX? Are you using FCL or the map?
Also, please post the exact syntax that you are using to specify the time.
-- Erik
|
| 4645.2 | More Information... | TRIGG::TRIGG::CLAYTON | Merlin Clayton DTN 445-7217 | Thu Mar 11 1993 12:27 | 36 |
|
I'm running V T1.3.1 on a VS4000/90 with VMS 5.5-2.
I'm trying to do this from the map.
I've tried various time syntax such as:
1. START TIME 18:00
END TIME 23:00
2. START TIME 18:00:00
END TIME 23:00:00
3. START TIME 10-MAR-1993 18:00:00
END TIME 10-MAR-1993 23:00:00
4. START TIME 10-MAR-1993 18:00
END TIME 10-MAR-1993 23:00
5. START TIME <default>
END TIME 10-MAR-1993 23:00:00
6. START TIME 10-MAR-1993 18:00:00
END TIME <default>
All of the above result in an error stating
"illegal scheduling time specification"
When I use the following syntax, it works OK:
3. START TIME 18:00
END TIME <default>
Merlin
|
| 4645.3 | Same Behavior on SSB Kit | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Mon Mar 15 1993 09:43 | 13 |
|
I've installed the SSB kit of EMS 2.3 and I see the same behavior discussed
in .0 and .2.
Has anyone else experienced similar problems with the time format on a VMS
system?
Is there potentially any operating system related settings I should be looking
at?
Mgc
|
| 4645.4 | Use "FOR" instead of "AT"? | TOOK::T_HUPPER | The rest, as they say, is history. | Mon Mar 15 1993 18:17 | 14 |
| It sounds as though a "schedule" time is being input for the OCCURS
rule instead of a "scope of interest". For "schedule" time, any "END"
time is illegal, and you will see the error mentioned.
Check that the OCCURS rule uses the "FOR" time clause (scope of
interest) instead of the "AT" time clause (schedule). Something like:
FOR START 18:00:00 END 23:00:00
instead of:
AT START 18:00:00 END 23:00:00
Ted
|
| 4645.5 | Looks Like Schedule Time Format | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Tue Mar 16 1993 15:31 | 19 |
| When looking at the rule expression for a rule that created successfully
using the format...
START TIME 11:10
END TIME <default>
the rule expression looks as follows:
Expression = (OCCURS (Node4 LGRANG Any Events),
for start=(11:10))
Category = "Fault Masnagement"
Severity = Warning
Probable Cause = Unknown
Is this what you would expect to see for a "schedule" time?
Merlin
|
| 4645.6 | It's a "scope of interest" time | TOOK::T_HUPPER | The rest, as they say, is history. | Wed Mar 17 1993 16:12 | 4 |
| It looks like a proper "scope of interest" time clause (using "for
start"), so I don't see where the problem is. Anyone else have a clue?
Ted
|