MessageEventSource missing?

, ,
1

Imported from previous forum

2

[ original email was from Jim Northey - jnorthey@jandj.com ]
The MessageEventSource field does not appear to be part of the current FIA Extensions Schema. Is it okay to add it with an abbreviated name of MsgEvntSrc? type of string?

3

[ original email was from Niranjana Sharma - nsharma@cme.com ]
> The MessageEventSource field does not appear to be part of the current

FIA Extensions Schema. Is it okay to add it with an abbreviated name of
MsgEvntSrc? type of string?
The field is defined in the fields-impl. Type - MsgEventSource_t. The datatype is String.
Definition -
MessageEventSource used to identify the event or source which gave rise to a message. “MQM” (originated at Firm Back Office), “Clear” (originated in Clearing System), “Reg” (static data generated via Register request), “ETC” (Order Routing).

4

[ original email was from Jim Northey - jnorthey@jandj.com ]
Niranjana,

It looks like the name is MsgEvtSrc. Are these enumerations or can we add additional values - we would like to use it to name the source.

The MessageEventSource field does not appear to be part of the current
FIA Extensions Schema. Is it okay to add it with an abbreviated name
of MsgEvntSrc? type of string?
The field is defined in the fields-impl. Type - MsgEventSource_t. The
datatype is String. Definition - MessageEventSource used to identify the
event or source which gave rise to a message. “MQM” (originated at Firm
Back Office), “Clear” (originated in Clearing System), “Reg” (static
data generated via Register request), “ETC” (Order Routing).

5

[ original email was from Niranjana Sharma - nsharma@cme.com ]
> Niranjana,

It looks like the name is MsgEvtSrc. Are these enumerations or can we
add additional values - we would like to use it to name the source.

The MessageEventSource field does not appear to be part of the
current FIA Extensions Schema. Is it okay to add it with an
abbreviated name of MsgEvntSrc? type of string?
The field is defined in the fields-impl. Type - MsgEventSource_t. The
datatype is String. Definition - MessageEventSource used to identify
the event or source which gave rise to a message. “MQM” (originated at
Firm Back Office), “Clear” (originated in Clearing System), “Reg”
(static data generated via Register request), “ETC” (Order Routing).
The value that we have defined so far are
MQM - Originated at Firm Back Office
Clear - Originated in Clearing
ETC - HandHeld
STP - Order Routing
TOPS - TOPS
UI - User Interface
CMESys - CME System
REG - Static data generated via Register request
We haven’t used a restriction on the enumerations. So we could add more user defined values.