I have as many problems with T24 design as everyone else but the 'ugly' structure ensures performance in exceptionally high transaction volume sites.
The key is designed to give a good distribution for transactions whilst ensuring commonality (each component is a transaction characteristic) and minimal locking; the use of these consolidated entries reduces the COB time by ensuring fewer records have to be processed. The unconsolidated version of the ID is simply day / port / time / sequence so is equally meaningless for investigation purposes. John. On Apr 24, 4:26 pm, Vlad <[email protected]> wrote: > I'm wondering who invented those netted postings. Probably it was > really a bad day for those who decided to make such an ugly structure > of the ID. Instead of standard "150810001139384.00" style, now > RE.CONSOL.SPEC.ENTRY file has this "R!LD.1.TR.BHD.21071.1002.BH.5Y.... > 1200.3..17.LIVEDB.20100308!DR!BHD!LD!CNW!20090308!!!1!!!20090308!17! > 21071". Obviously, Temenos has to hire some good architects. > --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
