Imported from previous forum
[ original email was from Ryan Pierce - rpierce@taltrade.com ]
I’m working on an options FIX interface and noticed that one field I need, 77 (OpenClose) does not have a defined enumeration.
That field has been in the spec for a while, so I’m wondering if a de-facto enumeration exists. I would assume, since the field is type char, that the most logical choice is ‘O’ for Open and ‘C’ for close; is this what most people are using?
[ original email was from Will Walter - will_walter@dbna.com ]
I don’t believe that there are many people using these fields yet. I agree with your decision, however, to use ‘O’ and ‘C’. Most api’s to exchanges and f&o systems use a type char field and use these values.
> I’m working on an options FIX interface and noticed that one field I need, 77 (OpenClose) does not have a defined enumeration.
>
> That field has been in the spec for a while, so I’m wondering if a de-facto enumeration exists. I would assume, since the field is type char, that the most logical choice is ‘O’ for Open and ‘C’ for close; is this what most people are using?
>
>
[ original email was from Jim Northey - jorthey@up.net ]
Sounds like a sensible idea. How does this get added to the documentation?
> I’m working on an options FIX interface and noticed that one field I need, 77 (OpenClose) does not have a defined enumeration.
>
> That field has been in the spec for a while, so I’m wondering if a de-facto enumeration exists. I would assume, since the field is type char, that the most logical choice is ‘O’ for Open and ‘C’ for close; is this what most people are using?
>
>
[ original email was from John Armstrong - johna@ms.com ]
In keeping with the other options related fields
(e.g. CoveredUnCovered, CustomerFirm),
the enumerations would be 0(Open) and 1(Closed).
Another thing missing is the BrokerDealer indicator. Instead of adding another field, we
could add enumeration 2(Dealer) to the CustomerOrFirm field.
> I’m working on an options FIX interface and noticed that one field I need, 77 (OpenClose) does not have a defined enumeration.
>
> That field has been in the spec for a while, so I’m wondering if a de-facto enumeration exists. I would assume, since the field is type char, that the most logical choice is ‘O’ for Open and ‘C’ for close; is this what most people are using?
>
>
[ original email was from Koji Kubota - koji.kubota@gs.com ]
> In keeping with the other options related fields
> (e.g. CoveredUnCovered, CustomerFirm),
> the enumerations would be 0(Open) and 1(Closed).
>
In Japan Extension Working Group, this
was brought up as well.
Wouldn’t it be more natural to use characters for char fields? In this case, “O” and “C”? CoveredUnCovered and CustomerFirm are int
fields.