unavailable RIC in chain list for corn future

xuquan

Hi,

I'm trying to subscribe all RICs for cbot corn future. While the chain RIC 0#C: as following contains RICs like CN0 (contract month Dec of 2020) that not listed yet on CME website at 20170727, http://www.cmegroup.com/trading/agricultural/grain-and-oilseed/corn.html. The refresh message for CZ0 also contains invalid data like 0 price tick. My question is how can I tell these 'unavailable' RICs from the normal ones.

0#C:

PROD_PERM (1):       91
RDNDISPLAY (2):      208
DSPLY_NAME (3):      CORN
RDN_EXCHID (4):      23
CURRENCY (15):       841
NEWS (28):           YYYY
NEWS_TIME (29):      5:26:35:0
REF_COUNT (239):     14
LINK_1 (240):        <CU7>
LINK_2 (241):        <CZ7>
LINK_3 (242):        <CH8>
LINK_4 (243):        <CK8>
LINK_5 (244):        <CN8>
LINK_6 (245):        <CU8>
LINK_7 (246):        <CZ8>
LINK_8 (247):        <CH9>
LINK_9 (248):        <CK9>
LINK_10 (249):       <CN9>
LINK_11 (250):       <CU9>
LINK_12 (251):       <CZ9>
LINK_13 (252):       <CN0>
LINK_14 (253):       <CZ0>

CZ0:

PROD_PERM (1):       91
RDNDISPLAY (2):      77
DSPLY_NAME (3):      CORN DEC0
RDN_EXCHID (4):      23
CURRENCY (15):       2009
NEWS (28):           YYYY
NEWS_TIME (29):      6:25:31:0
CONTR_MNTH (41):     DEC0
OPNRNGTP (49):       2
CLSRNGTP (52):       3
LOTSZUNITS (54):     21
LOT_SIZE (55):       5000.0
EXPIR_DATE (67):     14 / 12 / 2020
LOT_SIZE_A (198):    5000.0
RECORDTYPE (259):    194
IRGCOND (374):       0
INSCOND (378):       0
BCAST_REF (728):     GRA
CROSS_SC (825):      0
SEQNUM (1021):       0.0
CONV_FAC (1078):     56.0
PREF_DISP (1080):    5216
RDN_EXCHD2 (1709):   23
PREV_DISP (3263):    0
CONTEXT_ID (5357):   2533.0
PRC_TICK (6210):     0.0
DDS_DSO_ID (6401):   8221
SPS_SP_RIC (6480):   .[SPSCB1L1
SETL_TYPE (6513):    0
CAN_COND (6585):     0
BLKTRDVOL (6908):    0
TICK_VAL (7480):     1250.0
CRT_MNTH (8512):     DEC20
RCS_AS_CL2 (8635):   0
RIC_TYPE (12785):    3
LOTSZUNIT2 (13416):  21

Jirapongse

@xuquan

Please contact our Data Content experts at Contact Us to verify RICs in 0#C:

Make
sure you mention that it is a Data / Content question (rather than an API
question) to ensure your query is directed to the correct team.