Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.





Binary Type

Binary Length





The unique identifier of the Party Details Definition Request Acknowledgment associated with this message; this is the value submitted on the inbound message.

For pre-registered messages:

  • Unique ID from Party Details Definition Request Acknowledgment message
  • PartyDetailsListRequestID≠0.

For on-demand messages:

  • If not registered beforehand through iLink then Party Details Definition Request Ack message will be sent along with the business message and will immediately precede it
  • PartyDetailsListRequestID=0.
Unique ID of a Security Definition Request.
  • 0=Automated
  • 1=Manual
Indicates if the message was initially received manually.
Sequence number assigned to this message.

For futures and options markets:

Operator ID.

Should be unique per Firm ID.

Assigned value used to identify specific message originator.

Represents last individual or team responsible for the system that modifies the order prior to submission to CME Globex.

For fixed income markets: represents the Entering Trader.

  • SecurityRequestType=1

Type of Security Definition Request.

Constant value.

Time when the message is sent. 64-bit integer expressing the number of nanoseconds since midnight January 1, 1970.
  • REPO

Identifies specific type of UDS; valid values are COMBO, COVERED, and REPO.

Text describing sender's location (i.e. geographic location and/or desk).
Start date of a financing deal, i.e. the date the buyer pays the seller cash and takes control of the collateral.
End date of a financing deal, i.e. the date the seller reimburses the buyer and takes back control of the collateral.
The expiration date of the series to use for the TM template.

Max number of substitutions allowed. The value of 0 indicates that substitutions are not allowed.

Applicable for US Repos.

Represents the source Repo instrument on which the new Repo should be modeled.
  • minValue=2
  • maxValue=40

Up to 26 legs (i.e., repeating groups) supported for UDS for options. Up to 40 legs (i.e. repeating groups) supported for UDS for futures.

  • An iLink Security Definition Request (tag 35-MsgType=c) is rejected as "'Too Many Legs forcombo: <option/future leg count> Max: <max option/future leg>" due to Tag 555 is more than 40
  • An iLink Security Definition Request (tag 35-MsgType=c) is rejected as "'Not Enough Legs: <leg count> Min: 2'" due to Tag 555 is less than 2

  • LegSecurityIDSource=8 (exchange symbol)

Identifies class or source of the tag 602-LegSecurityID.

Constant value.

Price of the futures contract as part of UDS Covered
ISIN code, this is the primary tag used to identify the contract and it must be populated with the corresponding tag 48-SecurityID value from the market data 35=d Security Definition message.

Delta used to calculate the quantity of futures used to cover the option or option strategy.

  • For a covered option outright instrument, must be between +0.01 and +1.00.
  • For a covered option spread instrument, must be between +0.01 and +40.00.
  • LegSide=1 (Buy)
  • LegSide=2 (Sell)

For Covereds, must be present for option repeating group and must = 1 (buy).

For Covereds, must be present for future repeating group as well.

For Combos, the first instrument in the repeating group must = 1 (buy).

All UDS contracts are defined from the buy side perspective (i.e. buying the spread).

  • minValue=1
  • maxValue=20

Specifies ratio for the instrument defined in this repeating group.

Required for any UDS options leg.
Optional for Covereds leg.