| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1619.1 | The argument to a GETEVENT directive is an EventIdList | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Oct 09 1991 13:05 | 23 |
| > According the SRM the request argument of a GETEVENT is an
> EventIdList , which is a construction of event NAMES (in
> Latin1String). This is clearly shown in the example page 156.
The MSL code-segment is correct. The 'Which Events' argument *is* an
"EventIdList". What seems to be incorrect, however, is the
"REQUIRED=TRUE" line. The 'Which Events' is optional, and if not
present in the request indicates *all* events (ie, a wildcard).
You are probably getting confused by the BNF information for EvnetIDList
On page 264 (section 9.3.8 Event ID List), the SRM says:
<EventIDList> ::= <Event-Name> { "," <Event-Name> }
<Event-Name> ::= <Latin1Char> { <Latin1Char> }
An Event Id List, INTERNALLY, is a setof Unsigned32 values - each value is an
Event Id for the target Entity of the GETEVENT directive.
EXTERNALLY, the Event Id List is a list of Event Names. I think the
Event-Name should have been <Latin1String> instead of <Latin1Char>, but
I'm not a BNF expert.
|
| 1619.2 | | TOOK::STRUTT | Management - the one word oxymoron | Thu Oct 10 1991 14:36 | 9 |
| I hate to be picky, but:
.1> The 'Which Events' is optional, and if not
.1> present in the request indicates *all* events (ie, a wildcard).
If Which Events argument is missing, it indicates that *any* event
may be returned.
Colin
|
| 1619.3 | Ok - *any* event, not *all* events | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Oct 10 1991 14:57 | 10 |
|
Ok - *any* event, not *all* events,
that makes sense - sorry if I confused anyone.
.1>
But - As far as the "REQURIED=TRUE" statement in the MSL for
the Getevent directive argument 'Which Event' .. which is it?
Should it be True, or False ??
/keith
|
| 1619.4 | Recommend you use REQUIRED=FALSE for GetEvent arg | TOOK::STRUTT | Management - the one word oxymoron | Tue Oct 15 1991 11:56 | 7 |
| re: .3
The standardised directive in chapter 15 shows the request argument
Events Wanted as optional.
The example MSL does not adhere to the standardised directive - this is
clearly an oversight - QAR #1012 has been entered.
Colin
|
| 1619.5 | | TOOK::STRUTT | Management - the one word oxymoron | Tue Oct 15 1991 12:01 | 3 |
| Oh, and isn't it good timing - Keith is the new owner of SRM chapter 7.
:-}
|
| 1619.6 | Great timing - | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Tue Oct 15 1991 15:13 | 5 |
| >> Oh, and isn't it good timing - Keith is the new owner of SRM chapter 7
I couldn't have planned it better myself
8)
|
| 1619.7 | ECO 111 - getevent definition changing | TOOK::CALLANDER | MCC = My Constant Companion | Wed Oct 23 1991 20:54 | 11 |
| Just be warned...ECO 111 which should be out for full MRG review any
moment now (MASG has the updated copy ready for distribution to the
masses), modifies the GETEVENT directive to support the added value
functions of the V1.2 notification FM. So if you are just adding in
support for the GETEVENT directive you will want to get a copy of
the eco when distributed. The ECO does *NOT* change the calling
arguments or response codes, but addes new arguments and exceptions
to allow more information to be returned, including OSI compliant
events.
jill
|