Skip to content
All library documents

Mapping Zhengzhou Commodity Exchange Symbols to CTP Contract Names

Article vn.py community
Read the original

Summary

This short forum exchange explains why a Zhengzhou Commodity Exchange contract may show a successful market data subscription but deliver no ticks through a CTP connection. The example uses soda ash: a trading screen displays SA2601, while the CTP interface expects SA601. Subscribing with the interface-specific contract symbol resolves the missing data in the reported case.

The exchange also explains how to identify the correct symbol: use the platform’s contract query feature, which displays the live contract symbols returned by the connected trading interface. The discussion is a practical integration note, not a general specification for all Zhengzhou contracts or all interfaces. It offers one reported example and does not describe a broader diagnosis process or explain why the trading screen and CTP use different naming conventions.

Key ideas

  • A successful subscription message does not guarantee that the contract symbol matches the CTP interface.
  • The reported soda ash example receives market data when subscribed under SA601 rather than SA2601.
  • Use the platform’s contract query feature to find symbols returned by the connected interface.
  • The exchange provides an example, not a comprehensive mapping for Zhengzhou contracts.

Tags

FuturesMarket microstructure

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.