TIDM

1
TIDM
2
What is TIDM?

• TIDM is the Tradable Instrument Display Mnemonic
• It is a 4-character field used by participants
  for ease of use to intuitively identify a
  security e.g. ABI AMBIENT in the UK
• It is a system-wide field, as opposed to segment
  specific
• It is comparable in use, to an extent, to the JSE
  instrument alpha code, but presents the following
  issues
• 4-char limit vs 6-char JSE alpha code
• Duplicate values exist between JSE LSE (e.g.
  ABI Amalgamated Beverage Industries in SA)
• Need to separate exchange specific securities
  (Which ABI refers to which?)
• We recommend that users do not to rely on the
  TIDM for unique translation as it only appears on
  some of the messages and should be looked up
  using a combination of the following four fields
• Segment
• ISIN (tradable instrument)
• Country of Register
• Currency

3
JSE Alpha Code and TIDM

• Sequence master data can be classified in two
  forms, system wide and segment specific.

Instrument Definitions
TIDM is unique at this level
System Wide
Segment (Exchange) Specific
Instrument to Segment Mapping
Segment Definitions
The JSE Alpha code will be stored on this table
in the TISGC field
In addition to using TIDM, JSE instrument alpha
codes will be used as part of the Tradable
Instrument Symbol Group Code (TISGC), which is
stored at a segment level.
4
What is the TISGC field?

• The TISGC field contains symbol group codes which
  relate to the Daily Official List published in
  the UK
• It is a 45 character field, structured to contain
  15 x 3 char symbol group codes, as follows
• Code 1 Code 2 Code 3
• . . . .
• Where for example,
• 001 REDEEMABLE AT GOVERNMENT OPTION
• 022 CO. NOT RECD UNDER SS 86,87,88 FSA
• 023 CONVERSION RIGHTS HAVE EXPIRED
• A maximum number of 5 symbol group codes have
  been used in the past for any particular security

0
0
1
0
2
2
0
2
3
5
JSE Alpha Code in TISGC

• The JSE will auto generate TIDM codes for SA
  SADC region exchange securities segments (e.g.
  NSX)
• LSE securities and securities which are primary
  listed on LSE and secondary listed on the JSE
  will have the LSE TIDM code (e.g. SAB)
• The JSE will populate part of the TISGC field,
  positions 37 to 42
• Users systems will need to read the TISGC field
  and parse the JSE Alpha Code from it for
  inclusion in their reference data
• Users systems will need to translate from the
  alpha code to the ISIN and vice versa for trading
  and processing messages. This will require a
  translation table of some sort.

LSE Reserved
JSE Alpha Code
Reserved for 12 x 3 symbol group codes
Positions 1 to 36
37 to 42
43 to 45
6
TIDM code generation

• The algorithm will be an alpha numeric starting
  with the numbers prefixes 1 and 2 and
  increment as follows
• 1st TIDM code 1000
• 2nd TIDM code 1001
• 10th TIDM code 1009
• 11th TIDM code 100A
• 35th TIDM code 100Z
• 36th TIDM code 1010
• 46656th TIDM code 1ZZZ
• 93312th TIDM code 2ZZZ
• The following JSE-LSE dual-listed securities will
  not have these generated TIDM codes for example
• SAB
• DDT
• Etc . . .

7
Building Instrument Reference Data
Instrument to Segment Mapping
Instrument Master Data
50A Instrument Reference Data Message
ZAE00123451
NEDCOR INVESTMENT BANK
10ZZ
INSTRUMENT MASTER TABLE
8
Building Instrument Reference Data
Instrument to Segment Mapping
Instrument Master Data
50B Instrument in Segment Reference Data Message
ZA01
10ZZ
ZA
ZAR
----------------------------NIB-------
NIB
ZAE00123451
LOOKUP TABLE
9
Trading Alpha Code to ISIN
ZA01
ZAE00123451
NIB
NEDCOR INV BANK
ZAE00123451
Segment ZA01 Instrument NIB
NIB
ZAE00123451
LOOKUP TABLE
10
Processing Public Data Messages
Incoming Message
ZA01
NIB
10ZZ
UDATE VALUE
It may be desirable to display both the TIDM and
Alpha Code
RECORD MATCH
ZAE00123451
ZA01
ZA
ZAR
NIB
LOOKUP TABLE
11
Use of Generic Fields
12
JSE use of generic fields

• Two generic fields on the Enter Order Message
  5EO are used for specific purposes when trading
  on JSE or NSX segments
• Participant Order Reference contains dealer code
  and institution identifier
• Client Reference contains clients BDA account
  number and the CX flag

Institution ID Bytes 8-10 char
1
2
3
4
5
X
X
X
Dealer Code Bytes 1-5 num
CX Flag Byte 15 value Y or N
1
2
3
4
5
6
7
X
BDA account Bytes 1-7 num
13
GENERAL
14
JSE use of generic fields

• Two generic fields on the Enter Order Message
  5EO are used for specific purposes when trading
  on JSE or NSX segments
• Participant Order Reference contains dealer code
  and institution identifier
• Client Reference contains clients BDA account
  number and the CX flag

Institution ID Bytes 8-10 char
1
2
3
4
5
X
X
X
Dealer Code Bytes 1-5 num
CX Flag Byte 15 value Y or N
1
2
3
4
5
6
7
X
BDA account Bytes 1-7 num
15
General

• Differences between JSE SETS and LSE SETS
• Timestamps
• Dual-sided trade report
• Client order modification
• JSE calendar
• JSE TIDM
• Use of generic fields

16
General

• Approved Software Providers
• Accreditation
• Provisional list and approved list
• Test scripts
• Notice for changes
• JSE Front End
• Depth of the order book

17
Communications
Email JSESpec_at_jse.co.za Web www.jse.co.za /
jse initiatives
18
Questions