Imported from previous forum
Could I suggest a special "unknown" value for TradSesStatus - possibly 0.
Apart from being generally useful to have a null or “don’t know” value, it will be especially necessary when the TradSesStatusRejReason field is added as suggested in the Fix 4.3 draft.
When a trading session status request is rejected, this field will be present in the Trading Session Status reply. However, TradSesStatus is still a required field, so what value should it take? My proposed “unknown” would be the natural value to take in a reject.
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
This makes sense to add the Unknown enumeration as you described. I think it makes sense to keep the TradSesStatus value as required, as what would be the point of a trading session status message if you had to test for the existence of a TradSesStatus tag upon each receipt. Seems like there could be anciliary usage for an Unknown Status enum - besides reporting reject.
> Could I suggest a special “unknown” value for TradSesStatus - possibly 0.
>
> Apart from being generally useful to have a null or “don’t know” value, it will be especially necessary when the TradSesStatusRejReason field is added as suggested in the Fix 4.3 draft.
> When a trading session status request is rejected, this field will be present in the Trading Session Status reply. However, TradSesStatus is still a required field, so what value should it take? My proposed “unknown” would be the natural value to take in a reject.
>
Upon review we currently (as of 4.3 Draft #2) have:
- TradSesStatus (340) as Req’d with values: Halted, Open, Closed, Pre-Open, Pre-Close
- TradSesRejReason (567 new to 4.3) as Optional with value: "Unknown or invalid TradingSessionID"
There does not seem to me to be a way to express that a Trading Session Status Request has been rejected other than the presence of the single value TradSesRejReason. Should TradSesStatus have a value of "Request Rejected" for the reject case? Regardless, is there still a need for the "ancilary usage" of "Unknown"?
> This makes sense to add the Unknown enumeration as you described. I think it makes sense to keep the TradSesStatus value as required, as what would be the point of a trading session status message if you had to test for the existence of a TradSesStatus tag upon each receipt. Seems like there could be anciliary usage for an Unknown Status enum - besides reporting reject.
> > Could I suggest a special “unknown” value for TradSesStatus - possibly 0.
> >
> > Apart from being generally useful to have a null or “don’t know” value, it will be especially necessary when the TradSesStatusRejReason field is added as suggested in the Fix 4.3 draft.
> > When a trading session status request is rejected, this field will be present in the Trading Session Status reply. However, TradSesStatus is still a required field, so what value should it take? My proposed “unknown” would be the natural value to take in a reject.
> >
>
This has been addressed for FIX 4.3 Draft #3. Added "0 = Unknown" and "6 = Request Rejected" values to TradSesStatus field. TradSesStatusRejReason is applicable if TradSesStatus = "Request Rejected" [PC20010718_2]
> Upon review we currently (as of 4.3 Draft #2) have:
> 1) TradSesStatus (340) as Req’d with values: Halted, Open, Closed, Pre-Open, Pre-Close
> 2) TradSesStatusRejReason (567 new to 4.3) as Optional with value: “Unknown or invalid TradingSessionID”
>
> There does not seem to me to be a way to express that a Trading Session Status Request has been rejected other than the presence of the single value TradSesStatusRejReason. Should TradSesStatus have a value of “Request Rejected” for the reject case? Regardless, is there still a need for the “ancilary usage” of “Unknown”?
>
> > This makes sense to add the Unknown enumeration as you described. I think it makes sense to keep the TradSesStatus value as required, as what would be the point of a trading session status message if you had to test for the existence of a TradSesStatus tag upon each receipt. Seems like there could be anciliary usage for an Unknown Status enum - besides reporting reject.
> > > Could I suggest a special “unknown” value for TradSesStatus - possibly 0.
> > >
> > > Apart from being generally useful to have a null or “don’t know” value, it will be especially necessary when the TradSesStatusRejReason field is added as suggested in the Fix 4.3 draft.
> > > When a trading session status request is rejected, this field will be present in the Trading Session Status reply. However, TradSesStatus is still a required field, so what value should it take? My proposed “unknown” would be the natural value to take in a reject.
> > >
> >
>