Enhancements to BusinessMessageReject ^35=j^

, ,
1

Imported from previous forum

2

I would recommend that the following enhancements be made to BusinessMessageReject ^35=j^

  1. More enumeration values for Tag 380 BusinessRejectReason

Conflicting Tags specified (examples both 126 UTCTimestamp and 432 LocalMktDate specified/ both 38 OrderQty and 152 CashOrderQty specified)

Throttle limit exceeded (http://fixprotocol.org/discuss/read/09dce4b4)

Invalid value specified for this tag (tag number would be specified in 371)

I am leaving out the enumeration numbers because that would be assigned in sequence (that still does not explain why we have 18 after 7 for 380 / gap of 9 to 17 for 380)

  1. Add Tag 371 RefTagID to BusinessMessageReject ^35=j^ so that if an invalid value is specified for a Tag, then there is a field to indicate which Tag had invalid value (presently Tag 371 is present in Session Level Reject)

I would prefer that only one field “Reject reason” be used in place of 373 (SessionRejectReason) and 380 (BusinessRejectReason) and this field have values from both of these fields.