Introduction to T24 HANDOFF file.
The Handoff is a file populated by a core T24 program (EB.HANDOFF) . It is supposed to be the reflect of all financial transactions or financial events and thus contains all data needed to produce delivery messages. A delivery message can be a SWIFT / SIC / SIT SECOM / SEPA / or any other carrier message, a printed advice, etc… Each T24 application (FX, MM, SC, DX,…) is preparing the CALL EB.HANDOFF in order to populate proper information. Some applications provide flexibility in linking messages to events: This relates more to recent modules (Swaps, DX,…) and is known as “soft delivery” in T24 language.
- Structuration
Physical name of this handoff is F.DE.O.HANDOFF. Not really interesting to edit directly that file under DB. In some sites you can find a usefull enquiry “DE.HANDOFF.DETS” which is showing the file content and structuration. Under Jbase, you can also launch SEE.HANDOFF + <handoff key> to get the same result. The Handoff file is organised in 9 sections (records). Each section is dedicated to a specific topic of the application. Example for DX-Derivatives application:
REC1 ;*DX.TRANSACTION - LATEST VERSION REC2 ;*DX.TRANSACTION - LASAT VERSION REC3 ;*DX.TRADE (R.NEW) REC4 ;*DX.TRADE (R.OLD) REC5 ;*DX.CLOSEOUT REC6 ; *DX.OPTION.ACTION REC8 ;* HEADER INFO REC9 ;* RESERVED local use
Example for MG-Mortgages application:
REC1 - Delivery header info REC2 - Contract record from MG.MORTGAGE file REC3 - Balances record from the MG.BALANCES file. REC4 - REC5 - Main collateral record REC6 - Overdue/Penalty details REC7 - REC8 - REC9 - Reserved local use.
In each section you’ll find all data referenced as section nb.xxx, such as 3.41 orĀ 2.3, etc…
All sections are fed by the system and thus can not be altered. Section 9 is dedicated to local customization. Following chapter describes how to append extra information in T24 delivery messages using this section 9.
Altering the standard handoff
This can be done by writing a subroutine, and by attaching the routine in the related DE.MAPPING record, using the dedicated field 16 ROUTINE. To achieve this:
- minimum needed libraries are:
SUBROUTINE XXXXXX(MAT HANDOFF.REC, ERR.MSG) $INSERT I_COMMON $INSERT I_EQUATE $INSERT I_DEOCOM
- feed local used records using the following format:
HANDOFF.REC(9)<1,1> = "What you want"
will populate the record 9.1.1 with the what you want value.
- then in DE.MAPPING you can add a name to this 9.1.1 field:
5.xx INPUT.POSITION. 9.1.1 7.xx. 1 FIELD.DESCR. MY.FIRST.LOCAL.FIELD 8.xx FIELD.NAME..... MY.FIRST.LOCAL.FIELD