Imported from previous forum
I’m having some trouble understanding how I should be using Category and CategoryAbbrev attributes for fields. I understand that when this field appears in a message that belongs to the Category specified here, I should use the CategoryAbbrev as the attribute name. For all other messages I should use QualifiedAbbrev.
-
How do I know what category a message belongs to? I could use the name of the file the message is defined in, but the names don’t exactly match the categories defined in the fields base file… For example, there is no file for “Indications” (note the ‘s’), or “SingleGeneralOrderHandling”. Ideally, I expected a message to have a Category attribute…
-
How do I use BaseCatagory ? If I understand this right, this indicates that the attribute name as specified in the complex type should be used for attributes of this type.
My apologies if these questions have already been answered or if the documentation addresses them already.
Thanks.
If you refer to the table of contents in the FIX 4.4 Protocol specification, you will see which messages fall under which message categories.
I’m having some trouble understanding how I should be using Category and
CategoryAbbrev attributes for fields. I understand that when this field
appears in a message that belongs to the Category specified here, I
should use the CategoryAbbrev as the attribute name. For all other
messages I should use QualifiedAbbrev.
How do I know what category a message belongs to? I could use the name
of the file the message is defined in, but the names don’t exactly
match the categories defined in the fields base file… For example,
there is no file for “Indications” (note the ‘s’), or
“SingleGeneralOrderHandling”. Ideally, I expected a message to have a
Category attribute…How do I use BaseCatagory ? If I understand this right, this
indicates that the attribute name as specified in the complex type
should be used for attributes of this type.My apologies if these questions have already been answered or if the
documentation addresses them already.Thanks.