Page tree
Skip to end of metadata
Go to start of metadata

The following diagrams present basic message processing for rejected RFC orders. An RFC order message can be rejected in two ways:

  1. Message Rejected -  occurs when the New Order Cross (tag 35-MsgType=s) message violates iLink message validation; CME Globex rejects the message with a Business Level Reject (tag 35-MsgType=j),  or
  2. Sides Rejected - occurs when the New Order Cross (tag 35-MsgType=s) message violates CME Globex business rules; CME Globex rejects the message with two Execution Reports, one sent for each side .
RFC Message Rejected

If the RFC message submitted by the client fails CME Globex message validation, CME Globex sends a single Business Level Reject (tag 35-MsgType=j) message with the appropriate value in tag 380-BusinessRejectReason and explanation for the rejection in tag 58-Text.

RFC Sides Rejected

Two Execution Report -- Reject (tag 35-MsgType=8) messages, one for each side, are generated when an inbound RFC message fails the CME Globex business rules.

  • No labels