
|
If you were logged in you would be able to see more operations.
|
|
|
HermesJMS
Created: 16/May/08 09:44 AM
Updated: 16/Jun/08 09:50 AM
|
|
| Component/s: |
GUI
|
| Affects Version/s: |
1.13
|
| Fix Version/s: |
1.13
|
|
|
Environment:
|
w32, probably all
|
|
|
The "text" view of the parsed FIX messages in hermes v1.13 and others is most useful when there's a need to copy and paste FIX messages into emails, for example. It would be even more useful if you could order, space, and line-break the display. Example of a current display:
ROYB -> PORT: BeginString<8>=FIX.4.2 BodyLength<9>=286 MsgSeqNum<34>=48 MsgType<35>=8<ExecutionReport>
PossDupFlag<43>=N<ORIGINAL_TRANSMISSION> SenderCompID<49>=ROYB SendingTime<52>=20080516-10:22:52.217
TargetCompID<56>=PORT TargetSubID<57>=ws OnBehalfOfCompID<115>=ODDOC DeliverToCompID<128>=JPMF
Account<1>=A1 AvgPx<6>=20.520000 ClOrdID<11>=5435002 CumQty<14>=50 Currency<15>=EUR
ExecID<17>=OS119f1404f0d-000 ExecTransType<20>=1<CANCEL> IDSource<22>=4<ISIN_NUMBER>
LastMkt<30>=PA LastPx<31>=0 LastShares<32>=0 OrderID<37>=OS119f13286f9-000 OrderQty<38>=200
OrdStatus<39>=1<PARTIALLY_FILLED> OrdType<40>=2<LIMIT> Price<44>=20.520000 SecurityID<48>=FR0000133308
Side<54>=1<BUY> Symbol<55>=FTE.PA TimeInForce<59>=0<DAY> TransactTime<60>=20080516-10:22:52
LeavesQty<151>=150 CheckSum<10>=021
Here is how I would change it:
a) TargetCompID<56>=PORT becomes TargetCompID <56> = PORT (note the spaces)
b) Tags and values are one each for every line
c) Tags remain sorted numerically small to large, within header, body, trailer of the message.
Is this something you can / would do?
--ws
|
|
Description
|
The "text" view of the parsed FIX messages in hermes v1.13 and others is most useful when there's a need to copy and paste FIX messages into emails, for example. It would be even more useful if you could order, space, and line-break the display. Example of a current display:
ROYB -> PORT: BeginString<8>=FIX.4.2 BodyLength<9>=286 MsgSeqNum<34>=48 MsgType<35>=8<ExecutionReport>
PossDupFlag<43>=N<ORIGINAL_TRANSMISSION> SenderCompID<49>=ROYB SendingTime<52>=20080516-10:22:52.217
TargetCompID<56>=PORT TargetSubID<57>=ws OnBehalfOfCompID<115>=ODDOC DeliverToCompID<128>=JPMF
Account<1>=A1 AvgPx<6>=20.520000 ClOrdID<11>=5435002 CumQty<14>=50 Currency<15>=EUR
ExecID<17>=OS119f1404f0d-000 ExecTransType<20>=1<CANCEL> IDSource<22>=4<ISIN_NUMBER>
LastMkt<30>=PA LastPx<31>=0 LastShares<32>=0 OrderID<37>=OS119f13286f9-000 OrderQty<38>=200
OrdStatus<39>=1<PARTIALLY_FILLED> OrdType<40>=2<LIMIT> Price<44>=20.520000 SecurityID<48>=FR0000133308
Side<54>=1<BUY> Symbol<55>=FTE.PA TimeInForce<59>=0<DAY> TransactTime<60>=20080516-10:22:52
LeavesQty<151>=150 CheckSum<10>=021
Here is how I would change it:
a) TargetCompID<56>=PORT becomes TargetCompID <56> = PORT (note the spaces)
b) Tags and values are one each for every line
c) Tags remain sorted numerically small to large, within header, body, trailer of the message.
Is this something you can / would do?
--ws |
Show » |
|
|
As for sorting, some users like to see message tag ordering as per the message in the text so you can see if something is out of order (and this can cause problems with some FIX engines I have heard).
I have no problem with alternative text representations. I'd just need to think of a way to easily support several and let users select their preferred.