|
Isn't it always true, you fix one thing and someone wants another....
The enumeration problems from not 513.6 and 7 have been corrected,
but...the V1.1 kit does not handle event report arguments from the
notification services (when requested using the NOTIFY command), though
you shouldn't have a problem with the GETEVENT command. The NOTIFY
command problem (we simply didn't write the code to accept arguments)
has now been corrected and should be available in the next major
baselevel.
jill
|
| I'm using the GETEVENT directive, and I get this:
>>>>>>>>>>>>>>>
CVR returned:
%MCC-S-RESPONSE, success with response reply
ILV dump of OUT_P:
[ 1 ] (
[ 1 ] (
[ 69 ] (
[ 0 ] 09
)
)
)
AES dump of ENTITY OUT:
depth=2 class code= 1001 instance = �class code= 1017 instance = equipe_line
CMEAGT NMF_NS:.mistral TESTOBJ "equipe_line"
AT 16-MAY-1991 13:25:22 FRANCOIS EVENTS
Successfully received events: !<GetEvent Response>
%MCC-E-NOENTITY, no corresponding entity instance exists
MCC>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I don't get the ACCESS VIOLATION, as in note 513 but I must be missing
something somewhere...
Here is my MS code...
TYPE totrigEnum = 10190 (addvalue = 1,
attributeChange = 2,
enrolObject = 3,
environmentalAlarm = 4,
equipmentAlarm = 5,
deenrolObject = 6,
processingAlarm = 7,
removeValue = 8,
serviceAlarm = 9,
transmissionAlarm = 10);
EVENT PARTITION FRANCOIS EVENTS = 15 :
SYMBOL = PRT_FRANCOIS_EVENTS,
EVENT Bip = 69 :
DISPLAY = TRUE,
SYMBOL = CMEAGT_BIP,
TEXT = " BIP Event Argument: !<Trigger Param>. ",
ARGUMENT Trigger Param = 01 : totrigEnum
DISPLAY = TRUE,
SYMBOL = BIP_EVENT_ARG
END ARGUMENT Trigger Param;
END EVENT Bip;
.........
DIRECTIVE GetEvent = 65 :
DIRECTIVE-TYPE = EVENT,
DISPLAY = TRUE,
SYMBOL = GETEVENT_DIRECTIVE,
CATEGORIES = (ALL),
REQUEST
ARGUMENT Events Wanted = 01 : EventIdList
ECHO = TRUE,
DISPLAY = TRUE,
REQUIRED = TRUE,
DEFAULT = NO DEFAULT,
SYMBOL = ARG_GETEVENT_LIST
END ARGUMENT Events Wanted;
END REQUEST;
RESPONSE GetEvent Success = 01 :
SYMBOL = EVENT_RECEIVED,
TEXT = " Successfully received events: !<GetEvent Response>",
ARGUMENT GetEvent Response = 01 : Event_report
DISPLAY = TRUE,
SYMBOL = ARG_EVENT_REPORT
END ARGUMENT;
END RESPONSE GetEvent Success;
..............................
|
|
ILV dump of OUT_P:
[ 1 ] (
[ 1 ] (
[ 69 ] (
[ 0 ] 09
)
)
EVENT PARTITION FRANCOIS EVENTS = 15 :
SYMBOL = PRT_FRANCOIS_EVENTS,
EVENT Bip = 69 :
DISPLAY = TRUE,
SYMBOL = CMEAGT_BIP,
TEXT = " BIP Event Argument: !<Trigger Param>. ",
ARGUMENT Trigger Param = 01 : totrigEnum
DISPLAY = TRUE,
SYMBOL = BIP_EVENT_ARG
END ARGUMENT Trigger Param;
END EVENT Bip;
You will notice in the ilv encoding that [0] is supplied for the argument
to the event report (code 69), and that "Trigger Param" is defined as
code 1. My guess at looking at this is that that is what is causing your
problem.
The only other question I have is why did you make the event report an FAO type
argument on the getevent response? Chapter 15 (SRM pg 884) gives the architected
(generic) way in which the common directives should be modeled. The SRM shows
the response as having no reply text, with a single argument of datatype
event_report.
jill
|
| Jill,
I have just changed my code following what you told me in the first part of
note .3, and I got this...
May be that the MCC I'm using is not the good one. This V1.1.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
ILV dump of OUT_P:
[ 1 ] (
[ 1 ] (
[ 69 ] (
[ 1 ] 09
)
)
)
AES dump of ENTITY OUT:
depth=2 class code= 1001 instance = �class code= 1017 instance = equipe_line
CMEAGT NMF_NS:.mistral TESTOBJ "equipe_line"
AT 16-MAY-1991 15:41:31 FRANCOIS EVENTS
Successfully received events: !<GetEvent Response>
%MCC-E-DATATYPE_NOT_SU, data type is not supported
MCC>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
About FAO type argument in the getevent response:
I followed the MSL examples given in the SRM page 156. I'll try again without
this FAO type argument...
I'll let you know.
Francois.
|