Mass Cancel

, ,
1

Imported from previous forum

2

Hi,

Has anyone implemented “mass cancel” functionality using 4.2? I know 4.3 has a separate msgtype to handle this.

Thanks

3

Hi Chintan,

Because there is no standard FIX 4.2 message for “Mass Cancel” and due to some other architectural constraint if you cannot use FIX 4.3 and your business wants to get this “mass cancel” functionality, you can do it using one of the two approaches mentioned below ( Reference ‘fix-42-with_errata_20010501_pdf’ ) :-

I) Define a “Custom Message Type” : Tag 35 = U1, U2 etc. i.e. having a
“U” as the first character in the MsgType field.

II) Using “User Defined Fields” : Tag numbers 5000 to 9999 have been reserved for use with user defined fields, which are used as part of inter-firm communcation.

But this choice between “upgrading to a higher FIX version” versus using “custom message types” versus “user defined fields” is a wider debate : Read thru :-

http://www.fixprotocol.org/discuss/read/bdf97d6e

in response to

http://www.fixprotocol.org/discuss/read/bca23e05

Regards,
K. Mahesh

Hi,

Has anyone implemented “mass cancel” functionality using 4.2? I know 4.3
has a separate msgtype to handle this.

Thanks

4

[ original email was from Jim Northey - jnorthey@jandj.com ]
More reason to permit inclusion of multiple application messages over a single session to permit counterparty agreed mixing of messages without the need for a full upgrade.

Hi Chintan,

Because there is no standard FIX 4.2 message for “Mass Cancel” and due
to some other architectural constraint if you cannot use FIX 4.3 and
your business wants to get this “mass cancel” functionality, you can do
it using one of the two approaches mentioned below ( Reference ‘fix-42-
with_errata_20010501_pdf’ ) :-

I) Define a “Custom Message Type” : Tag 35 = U1, U2 etc. i.e. having a
“U” as the first character in the MsgType field.

II) Using “User Defined Fields” : Tag numbers 5000 to 9999 have been
reserved for use with user defined fields, which are used as part of
inter-firm communcation.

But this choice between “upgrading to a higher FIX version” versus using
“custom message types” versus “user defined fields” is a wider debate :
Read thru :-

http://www.fixprotocol.org/discuss/read/bdf97d6e

in response to

http://www.fixprotocol.org/discuss/read/bca23e05

Regards,
K. Mahesh

Hi,

Has anyone implemented “mass cancel” functionality using 4.2? I know
4.3 has a separate msgtype to handle this.

Thanks

5

Choices : Upgrading to higher FIX version -vs- Custom message types -vs- User defined fields -vs- Multipe sessions ( one per FIX version ) between same parties -vs- Mixing different FIX versions in same session

Please take a look at :-

http://www.fixprotocol.org/discuss/read/3a6cfd8f

Hi,

Has anyone implemented “mass cancel” functionality using 4.2? I know 4.3
has a separate msgtype to handle this.

Thanks

6

Hi,

Has anyone implemented “mass cancel” functionality using 4.2? I know 4.3
has a separate msgtype to handle this.

Thanks

Thanks All, this was excellent help. I will let the Bus. mgr make the decision.