Data Migration Userguide

TEMENOS – PBG – Country Model Bank
Data Migration Tool

User Guide
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means, for any purpose,
without the express written permission of TEMENOS HEADQUARTERS SA.
COPYRIGHT 2007 - 2008 TEMENOS HEADQUARTERS SA. All rights reserved.

DM Tool – User Guide
Table of Contents
Table of Contents ...................................................................................................................... 1

Document History ...................................................................................................................... 4
Overview of this guide ............................................................................................................... 6
Assumptions .............................................................................................................................. 6
Document Support ................................................................................................................. 6
Abbreviations used in this Guide ........................................................................................... 6
T24 Modules Supported ............................................................................................................ 6
1. Introduction ......................................................................................................................... 7
2. Product Overview ............................................................................................................... 7
3. Workflow Diagram .............................................................................................................. 8
4. Template, Fields and Description ....................................................................................... 9
4.1. DM.INFORMATION ................................................................................................. 9
4.2. DM.DATA.TRANSLATION .................................................................................... 10
4.3. DM.PREREQUISITE ............................................................................................. 11
4.4. DATA.MAPPING.VERIFICATION ......................................................................... 12
4.5. DM.MAPPING.DEFINITION .................................................................................. 13
4.6. DM.SERVICE.CONTROL ...................................................................................... 16
4.7. DM.SERVICE.SCHEDULER ................................................................................. 17
4.8. DM.AA.MAPPING .................................................................................................. 18
4.9. DM.DATA.COMPARE ........................................................................................... 19
4.10. DM.EXTRACTOR .................................................................................................. 20
4.11. DM.MAPPING.EXTRACT ...................................................................................... 22
4.12. DM.AA.EXTRACT ................................................................................................. 23
4.13. T24.SAB.INFO ....................................................................................................... 23
5. Process workflow: ............................................................................................................ 25
5.1. Menus .................................................................................................................... 26
5.1.1 Migration Pre-Requisite Check .......................................................................... 26
5.1.1.1 Check Migration Table Record Count ............................................................ 28
5.1.2 Client System to T24 Migration .......................................................................... 31
5.1.2.1 T24 Data Loading ........................................................................................... 31
5.1.2.2 Data Migration Load Preparation ................................................................... 32
5.1.2.3 Data Mapping Definition ................................................................................. 44
5.1.2.4 Automatic creation of Versions & DMD’s: ...................................................... 70
5.1.2.5 DM Service Control ........................................................................................ 75
5.1.2.6 Service Control ............................................................................................... 88
5.1.2.7 Application backup ......................................................................................... 90
5.1.2.8 AA.MAPPING ................................................................................................. 96
2 GPACK
5.1.2.9 DM.PRE.PROCESS (Multi-Threading) .......................................................... 98

5.1.2.10 STP – Straight Through Processing workflow.............................................. 103
5.1.3 T24 Recon Data Extract................................................................................... 109
5.1.3.1 DM.PREREQUISITE .................................................................................... 110
5.1.3.2 T24 Data Extract for Reconciliation .............................................................. 114
5.1.4 T24 to T24 Migration ........................................................................................ 179
5.1.5 Data & Object Audit ......................................................................................... 179
5.1.5.1 DATA AUDIT BUILD .................................................................................... 179
5.1.5.2 OBJECT AUDIT BUILD ................................................................................ 218
a. DM Tool Additional Features .......................................................................................... 254
i. DM.REF.TABLE .................................................................................................. 254
ii. DM.AA.CUSTOMER.PROXY .............................................................................. 255
iii. T24.AA.INT.ACT.DEFAULT ................................................................................ 257
iv. DM.AA.CUSTOMER ............................................................................................ 260
v. T24.EB.EXT.ARR.ACT.DEFAULT ...................................................................... 262
vi. SC.PERF.DETAIL Load and SC.PERF.DETAIL.CONCAT updating .................. 265
vii. Data Compare ..................................................................................................... 272
viii. DM Scheduler ...................................................................................................... 281
ix. DM.DATA.TARNSLATION .................................................................................. 288
x. Handling BYTE Length in ORD ........................................................................... 291
xi. DM.AA.LENDING.BAL.EXTRACT ...................................................................... 293
xii. DM.AA.LENDING.SCHEDULE.EXTRACT .......................................................... 294
xiii. DM.DC.BATCH.UPDATE .................................................................................... 295
xiv. Mnemonic duplication: ......................................................................................... 296
xv. AA - Product Proofing and Publishing ................................................................. 298
xvi. TDM.DATA.STRUCTURE.EXTRACT ................................................................. 299
xvii. ENQUIRY DM.ENQ.ISSUE.LOG ........................................................................ 301
xviii. UTF8 conversion .............................................................................................. 301
xix. DM.CLEANUP ..................................................................................................... 304
6.Conclusions: ....................................................................................................................... 308
3 GPACK
Document History
Author Version Date
Gpack 1.0 11th April 2013
Gpack 2.0 5th August 2013
Data Migration 3.0 13th September 2013
Gpack 4.0 17th February 2016
Gpack 5.0 27th July 2016
Jeya Sudha.K 5.1 13 Mar 2017
R.Srisailesan 6.0 15 Mar 2017
B Srinivas Rao 6.1 Updateddesc of the DMD

record
K Jeya Sudha 7.0 Reviewed
B Srinivasarao 7.1 Updated the Description of the

@ID field in the
DM.DATA.TRANSLATION
application
K Jeya Sudha 8.0 Reviewed
Ragachandrika 8.1 Updated Error log id format
Sarath Balaji 8.2 New Field in

DM.SERVICE.SCHEDULER
Sarath Balaji 8.3 New Field in

DM.INFORMATION
Sarath B 8.4 New field introduced in

DM.SERVICE.CONTROL to
support straight through
processing.
Sarath B 8.5 OFS REPLACE functionality

covered.
Sarath B 8.6 New fields introduced in

DM.INFORMATION to support
the value of Delimiters in the
data records.
4 GPACK
Comments:
5 GPACK
Overview of this guide
This document is intended to be used as a reference guide for using DM Tool. The purpose of this
guide is to help the user to understand the various Templates and the fields in the Templates and
the crucial setup of any PARAMETER Files in the DM Tool.
Assumptions
This reference guide is prepared in different releases. Hence the screen shots will be in any
release. Wherever the release is mentioned, there are all the actual release is applicable.
Document Support
Any queries in any part of this document can be addressed to gpack@temenos.com.
Abbreviations used in this Guide
▪ S – Single Value Field

▪ M – Multi Value Field
▪ AMS – Associated Multi Value Starts Here
▪ AM – Member of Associated Multi Value
▪ AMC – Associated Multi Value Closes Here
▪ OFS – Open Financial Services
▪ TSM – Temenos Service Manager
▪ TSA – Temenos Service Agent
T24 Modules Supported
▪ CUSTOMER
▪ ACCOUNT
▪ COLLATERAL
▪ CURRENCY
▪ SECURITY.MASTER
▪ AA.ARRANGEMENT.ACTIVITY, etc
6 GPACK
1. Introduction
The T24 Data Migration tool was originally written using the EB.PHANTOM option. Phantom
processing in T24 is gradually moving from EB.PHANTOM to TSA.SERVICE. The Data
Migration tool too has been modified to be run as a Service. The original functionalities of
• Multi-threaded transaction takeover
• Takeover performance reporting, have been preserved in the latest version.
2. Product Overview
The T24™ Data Migration tool will be used during the pre-Live in any site implementations. It
basically covers the following functionalities.
• Used the Standard OFS module to perform the Load. The Option is given to
use either OFS or standard jBase WRITE function to perform the Load.
• Validations done on the data, prior to update.
• Accepts data in any layout and format, that includes double byte characters
(Provided the jBase used for the implementation is 4.1 or higher)
• Required less manual intervention during mapping of the incoming file to
T24™ applications, which is a onetime setup.
• Supports load of Local Tables too that are site specific
• Perform all standard T24™ validations and also includes any special cases to
perform local validations for the data being loaded.
• Supports scaling, using the multi-threading capabilities of TSA.SERVICE.
However, this is dependent more on the hardware capabilities.
• Stop/Resume options in case the Server/T24™/Database connectivity is lost
in the middle of the load. In this case, the operation will be resumed from
where it was paused. Standard TSA.SERVICE transaction management
capabilities are available.
• Exception Handling is done to report any erroneous data present in the Data
file. This report also includes detailed description of the error that is raised
during the load.
• Supports Sequential Load of Data in multithread. For example, In Drawings
Table, where data is to be loaded in sequence of the ID.
• Supports Read Replacement for Multi Company.
7 GPACK
3. Workflow Diagram
8 GPACK
4. Template, Fields and Description
4.1. DM.INFORMATION
Counting the number of records for every application, before and after migration, is a vital part
of Data Migration .The information of the number of counts per application is available in a
Live file DATA.MIG.COUNT. This application keeps track of the changes in the load count.
The entire operation can be successfully complete using the Browser
No. Field Name Description

@ID ID must be SYSTEM.
1.1 CLIENT.NAME The name of the client for which the migration is to be done
2.1 DESCRIPTION. The descriptions of your report set / interface.
The migration type that is going to be done (E.g. TM0, DR1,

3 MIG.TYPE LIVE)
This is an optional filed, where a valid &SAVEDLISTS& name
4 SELECT.LIST can be given.
5 MNEMONIC Specify the company Mnemonic

This is a multivalue set where we should provide the Application
6.1 APPLICATION Names for which the count is to be done
This is an associated multivalue set where the number of
7.1 LIVE.COUNT records in LIVE file will be populated.
8.1 NAU.COUNT records in NAU file will be populated.
9.1 HIS.COUNT records in HIS file will be populated.
10 OVERRIDE Overrides that are generated, if any.

If set to “Yes” then records are not overwritten and the same is
reported as exception in log file. Record check is applicable only
for load type “WRITE” in DMD record. Valid values are “Yes” or
11 RECORD.CHECK “No”. No and null are treated the same way.
If the FM delimiter ‘|’ defined in DM.MAPPING.DEFINITION is
part of migration data then the same has to be replace by
special characters defined in this field. Example: Let say the
delimiter used is | pipe symbol and if beneficiary name contains |
pipe symbol “John | Smith” then it has to be replaced by “John
12 FM.DELIM.REPLACE %$% Smith” for successful processing in Transact.
13 VM.DELIM.REPLACE Same as above
14 SM.DELIM.REPLACE Same as above
Table 1 – DM.INFORMATION
9 GPACK
4.2. DM.DATA.TRANSLATION
The data provided by the Client will contain values that correspond to the Legacy
Data Format which cannot be loaded into T24 without any TRANSLATION. Hence a valid
TRANSLATION must be done so that the Data is converted into a T24 Data format and can
be loaded. The application DM.DATA.TRANSLATION is used for converting legacy data into
T24 format.

The id should be the valid Directory inside the
DATA.IN directory. Creation of directory [DATA.IN] is
covered as part of Installation guide.The id allows 25
@ID characters long
1 APPLICATION The application for which the conversion carried out.
The source directory of the data file consisting of
2 SOURCE.DIR Legacy ID is provided in this field
3 SOURCE.FNAME The Data file name consisting of Legacy ID is given.
The name of the output directory where the
converted file will be available after the conversion is
over. Any error log generated will be available as
mentioned above.
By default DATA.IN can be provided or modified as
per the user.
4 TARGET.DIR
The name of the converted data file with T24 Ids
5 TARGET.FNAME must be given here.
The Field Marker that is used in the datafile to delimit
field values. By default ‘|’ is defaulted which can be
modified as per the user.
6 FM.DELIM
The Value Marker that is used in the datafile to
delimit field values. By default ‘::’ is defaulted which
can be modified as per the user.
7 VM.DELIM
The Sub Value Marker that is used in the datafile to
delimit field values. By default ‘!!’ is defaulted which
can be modified as per the user.
8 SM.DELIM
Any Concat file name that will be used for the
conversion can be provided in this field. This is a
multivalue field.
9.1 MAPPING.TABLE
The positions in the datafile where the conversion
has to be done and replaced with T24 Ids. This is a
10.1.1 POS.CONVERT sub value field associated with Mapping Table field.
The positions in the data file where the conversion

11.1.1 POS.VALUE values are defined .This is a sub value field
10 GPACK
associated field.
A subroutine can be attached to this field that will be

used for conversion logic. This is an associated sub
value set with Position Check field. This is a sub
12.1.1 POS.ROUTINE value field associated field.
The number of agents that will be required to run the
conversion can be mentioned in this field. Default
13 NO.OF.SERVICE value is 16
Table 2 – DM.DATA.TRANSLATION
4.3. DM.PREREQUISITE
This table is used to create folders and for copying of data files to the respective folders
and creating the DM.SERVICE.CONTROL (DSC) that are necessary for the load of Data to
T24. Using the application DM.PREREQUISITE we can create necessary folders and moves
the data files to their respective paths. We will also be able to create folders for placing
reconciliation extracts from T24.

A 3 digit number followed by an asterisk (*), followed
by a valid user name that must be present in the
@ID USER table
1 DESCRIPTION Free text Description.
The task that will be done when the application is
verified. Either creation of DSCs or Only creation of
2 PROCESS Directories or Both can be specified here.
3 RESERVED.5 Future Use
The directory name where the data files are stored
and under this directory will other folders get created
which will be used as Path Name in
DM.SERVICE.CONTROL. The value DATA.IN is
defaulted, which can be changed to any other
4 DIRECTORY.NAME directory as and when needed.
This is an optional filed, where a valid
5 SELECT.LIST &SAVEDLISTS& name can be given
This is an Associated Multivalue set which will hold
the DMD name for which the
DM.SERVICE.CONTROL will be created followed by
a dot (.) and a two digit sequence number. (The
format is mandatory). The folders that need to be
created for the data file will be based on the input to
6.1 DMD.NAME this field.
This is an Associated Multivalue set .The data file
that will be used for the load will be selected
automatically based on the input in the previous field.
The data file must be present in the Directory that
7.1 FILE.NAME has been specified in the field Directory Name. The
11 GPACK
format of the data file must be as follows.

<dmd.name>.<2 digit
number>.<yyyymmddhhmm>.TXT
E.g.: CUSTOM.01.201203031653.txt
We need to specify if Reconciliation Folders are to be

12 RECONCILIATION created or not. By default, the value “No” is defaulted.
The Directory name must be specified here where
the reconciliation folders will be created. By default
13 RECON.DIR RECON.OUT is populated in this field.
This is a multivalue field that is used to provide the
Names of the folders that need to be created under
the Directory specified in the field Recon Dir.
14.1 RECON.SPEC.NAME
This is a multivalue field that contains DM Extractor
Id. The value entered must exist in the
15.1 DM.EXTRACTOR.NAME DM.EXTRACTOR table
16 FILE.CONV.REQD File conversion will be done if this field is set to YES.
This field specifies whether the file load is from
17 FILE.LOAD.TYPE Server or Local host
Conversion type is specified here. Values entered
18 CONVERSION.TYPE here are NT or Unix
Table 3 – DM.PREREQUISITE
4.4. DATA.MAPPING.VERIFICATION
Verifying the correctness of the Data Mapping Table and the DM.MAPPING.DEFINITION is a
vital part of Data Migration, without which the data load, could go wrong.
DATA.MAPPING.VERIFICATION verifies, whether the Data Mapping Table and the
DM.MAPPING.DEFINITION are in synchronisation.
This application also produces an output file in the specified DMV directory with the status of
the Verification.

The id of this application is free format text, 12
characters long.
A meaningful ID, indicating the application name e.g.,

CUSTOMER should be provided.
CUSTOMER
MM.MONEY.MARKET
LIMIT
@ID
1 DESCRIPTION Free text Description.
12 GPACK
Name of the T24™ Table to which the Data is been

2 APPLICATION.NAME loaded.
3 DMD.NAME DMD Name to be specified.
The Directory name where the DMV status result will

4 DIRECTORY.NAME be stored.
This field gets updated on verification of the record
with PASS or FAIL status
If the fields in DMD and the one in save list are same
without any mismatch then it would be updated as
5 MAPPING.STATUS PASS.
This is the name of the file where the core fields are
given for comparison. This file is to be placed in
6 CORE.LIST DATA.IN.
This is the name of the file where the local fields if
any are given for comparison. This file is to be placed
7 LOCAL.LIST in DATA.IN.
This is an associated Multivalued field which gets
updated with the fields in the CORE.LIST i.e the Core
8.1 CORE.FIELDS fields upon verification.
The Delimiter used to identify each multi-value field in
the data. Value allowed only when IN.DATA.DEF is
9.1 CO.FIELD.STATUS set to DELIM. This is an associated Multivalued field
This is a Multivalue field which gets updated with the
fields in the LOCAL.LIST i.e the local fields upon
10.1 LOCAL.FIELDS verification
This field specifies the Data file name. The file has to
11 DATAFILE.NAME be placed in DMV directory.
This field becomes mandatory on providing value for
the field DATAFILE.NAME.Values allowed is
12 VERIFICATION.TYPE FIRST,POSITION,RANDOM.
This field becomes Mandatory on specifying
POSITION in VERIFICATION.TYPE.This field
specifies the position from where verification has to
13 FIRST.POSITION be done for the file.
This field becomes Mandatory on specifying
POSITION in VERIFICATION.TYPE.This field
specifies the position till where verification has to be
14 LAST.POSITION done for the file
The number of records in datafile will be updated
15 DATAFILE.COUNT here.
If there is any error then the error message will be
16 ERROR.DESC populated on verifying the record.
Table 4 – DATA.MAPPING.VERIFICATION
4.5. DM.MAPPING.DEFINITION
13 GPACK
This application allows the user to define the format of the data in the incoming tape. The
following provides the list of fields, positions and the associated description.

characters long.
A meaningful ID, indicating the application name e.g.

first six characters of the application name,
CUSTOMER and the Load process, should be
provided.
V.CUSTOM
A.CUSTOM
I.CUSTOM
@ID
1 GB. DESCRIPTION Free text Description to describe the Load.
Name of the T24™ Table to which the Data is been
2 APPLICATION.NAME loaded.
Either ‘OFS.LOAD’ or ‘WRITE’ or
‘READ.REPLACEMENT’ or ‘OFS.REPLACE’ or
‘OFS.FIELD.REPLACE’ to specify if the load is via
OFS module or jBASE Write function or the
3 LOAD.TYPE replacement of a few fields.
A value ‘VALIDATE’ or ‘PROCESS’ will just
validate/process the contents of the data if it fits into
T24™ table. Value is allowed in this field only when
4 OFS.ACTION LOAD.TYPE is set to OFS.
The following FUNCTIONS are allowed to be
specified to be used by the OFS to process the
5 OFS.FUNCTION transaction. (I, R, A, D). “I” is taken as default.
The Type of T24™ files to be updated. Values could
be $NAU, LIVE or $HIS. Value is allowed only when
the LOAD.TYPE is set to WRITE or
6 FILE.TYPE READ.REPLACEMENT.
The T24™ Application’s Version to be used when
loading through OFS. Value is allowed in this field
7 OFS.VERSION only when LOAD.TYPE is set to OFS
To define the way in which the fields are read. Either
8 IN.DATA.DEF DELIM or POSITION or OFS
The Delimiter used to identify each fields in the data.
Value allowed only when IN.DATA.DEF is set to
9 FM.DELIM DELIM
The Delimiter used to identify each multi-value field in
10 VM.DELIM set to DELIM
The Delimiter used to identify each sub-value fields in
11 SM.DELIM set to DELIM
12 ESC.SEQ.FR When a particular character in the incoming data
14 GPACK
needs to be converted, the character to be converted

must be provided here.
Works in conjunction with ESC.SEQ.FR, this is the
character to which the ESC.SEQ.FR character will be
13 ESC.SCR.TO converted.
Either ‘AUTO’ (which system takes care to generate
the ID) ‘DATA’ (hardcoded ID in the coming file itself)
14 ID.TYPE ‘ROUTINE’ (A routine attached that forms the ID)
The Routine that forms the ID for each record loaded.
15 ID.ROUTINE Value allowed only when ID.TYPE is set to ROUTINE
The position in which the ID of each record can be
found. Value allowed only when ID.TYPE is set to
16 ID.POSITION DATA
The Length of the ID in each record in the data file.
Value allowed only when ID.TYPE is set to DATA
Note – This field is used in reference with
ID.POSITION to get the data for the ID from the raw
17 ID.LENGTH file
The field name in the T24™ table to which the data is
updated. 65 characters long (Associated multi-value
set till 22.1).
This field allows to accept the field names and field
positions of the application. For local reference field,
Use the local field name and not the position.
To define the fields from LD.SCHEDULES.DEFINE
18.1 APPL.FIELD.NAME use the respective field names only .
The starting position of the data that will be updated
in the T24™ field (Associated multi-value set till
24.1). Associated multi-value set till 22.1). Value
19.1 FIELD.POSITION allowed only when IN.DATA.DEF is set to POSITION
The length of the data that will be updated in the
T24™ field (Associated multi-value set till 24.1).
Associated multi-value set till 22.1). Value allowed
only when IN.DATA.DEF is set to POSITION
Note – This field is used in reference with
FIELD.POSITION to get the data for the field from the
20.1 FIELD.LENGTH raw file
Either ‘ROUTINE’ – indicated the data will be formed
from the routine for this field (or) ‘CONSTANT’ – a
21.1 FIELD.ATTRIB static value that will be updated for the field
The Static value that will be updated for the field.
Value allowed only when FIELD.ATTRIB is set to
22.1 FIELD.VALUE CONSTANT
The Post update routine , used a s a user exit routine
that will be triggered for every record that is been
23 POST.UPDATE.RTN loaded
The OFS source record to be used when loading
data into T24. Two OFS Source records,
1. DM.OFS.SRC
2. DM.OFS.SRC.VAL
24 OFS.SOURCE 3. DM.OFS.SRC.ORD
15 GPACK
4. DM.OFS.SRC.VAL.ORD
5. DM.LOAD
With FIELD.VAL set to ‘YES’ for cases where
field validation processing must be triggered e.g.
AC.ACCOUNT.LINK are provided by default.
Table 5 – DM.MAPPING.DEFINITION
4.6. DM.SERVICE.CONTROL
This application is used
To define the company for which the data is loaded
The location of the incoming data
Control the execution of the data load process
The following are the fields and associated description

@ID Must be the same as DM.MAPPING.DEFINITION.
The company for which the data is loaded. It is also possible to
provide the load company in the Incoming data. However, once
the value is provided here, this value takes precedence over
1 UPLOAD.COMPANY incoming data.
The directory where the flat file resides. This must be a valid
directory name, e.g. DATA.BP. Actual path or relative path of
2 FLAT.FILE.DIR the directory must be provided.
The flat file name of the incoming data. Must be an existing file
3 FLAT.FILE.NAME name.
4 SERVER.NAME Specifies the name of the server, for multiple application servers
The user name which will be used for the load process. This
username will get updated in the TSA.SERVICE record related
5 USER to the DM.SERVICCE.CONTROL.
No of threads that the TSA.SERVICE must spawn for
6 NO. OF SESSIONS processing this request.
The field MOVE.TO.HIST is to move the error details from DSC
7 MOVE.TO.HIST to another template namely DM.SERVICE.CONTROL.HIST
The status of the process. This can be either
• START – Updated automatically by the system when
the DM.SERVICE.CONTROL record is ‘Verified.
• STOP – Manual stop request to stop the takeover
10 RUN.STATUS process.
11 DSC.TYPE Dsc type should be either DMD or DME
This field is used to run the DM.PRE.PROCESS service as
multi-threaded or single threaded. It is a mandatory field. The
values accept as SINGLE or MULTI. For sequential file upload
12 PRE.PROCESS this type should be ‘SINGLE’.
13 DM.LOAD.TYPE This field is used to specify the load type, either file based or
16 GPACK
message based for straight through processing. Possible values

are blank or "FILE" or "ONLINE". If "blank" or "FILE": File based
processing. If "ONLINE": Message based processing.
Refer section 5.1.2.10 for online processing.
Contains the processing messages of the Service. Auto
15.1.1 CONTROL.LOG updated.
The errors that have been generated after the completion of the
16.1 ERROR.DETAILS process will be captured in this field. Auto updated.
The number of errors that have been recorded after the
completion of the process will be captured in this field. Auto
17.1 NO.OF.ERROR updated.
The type of errors consolidated from all the errors generated
after the completion of the process will be captured in this field.
18.1 TYPE.OF.ERROR Auto updated.
If the error is generated, this field will indicate the path where the
19 ERROR.FILE.PATH error long gets stored. Auto Updated.
If the error is generated, this field will indicate the file name of
20 ERROR.FILE.NAME the error long gets stored. Auto Updated.
The current date of the load process will be updated in this field.
21 DATE Auto updated.
The current start date/time of the load process will be updated in
22 STARTED this field. Auto updated.
The current end date/time of the load process will be updated in
23 STOPPED this field. Auto updated.
The current elapsed date/time of the load process will be
updated in this field. Auto updated.
24 ELAPSED
Table 6 – DM.SERVICE.CONTROL
4.7. DM.SERVICE.SCHEDULER
The services for validating, loading and authorizing of Data in T24 is required to be scheduled
and automated. Most of the tasks are manually performed which needs to be eliminated. The
multithread service will perform the tasks in an automated way to eliminate the manual task to
an extent.

The ID for this application must be a user defined name for the
SCHEDULER.
@ID e.g.: DSS.STATIC
1.1 DESCRIPTION The description of the SCHEDULER.
To indicate whether the service needs to be run for

DM.MAPPING.DEFINITION or DM.EXTRACTOR. It accepts
2 DSS.TYPE values as DMD or DME
The DM.SERVICE.SCHEDULER table record which needs to be
3 VERIFICATION.DSS completed successfully in order for the current service to be
17 GPACK
started.
To indicate whether the service needs to be started or stopped.

4 RUN.STATUS The two options available are START and STOP.
To store the DM.SERVICE.CONTROL table record which needs
5.1 DM.SERVICE.ID to be started
To store the DM.SERVICE.CONTROL table record which needs
6.1
to be completed successfully in order for the service, associated
VERIFICATION to the multivalued set, to be started
To store the specified data file path for that services. This is an
7.1 CURRENT.DIRECTORY associated multi-value field.
To specify the data file name for validate or load the data. This
8.1 DATA.FILE.NAME is an associated multi-value field.
To specify the new data file path for that services. This is an
9.1 NEW.DIRECTORY associated multi-value field.
To specify the maximum number of errors that will be tolerated
10.1 ERR.THRESHOLD before marking the service as failed.
No input field to update the number of records in error from the
corresponding DM.SERVICE.CONTROL after the service is
11 NO.OF.ERRORS complete
To specify if the service needs to be run or can be skipped. The
12.1 SKIP.SERVICE two options are YES and NO
No input field which will be updated with values 0, 1, 2 or 3
based on the current status of the service associated with the
13.1 DSC.STATUS field DM.SERVICE.ID
based on the current status of all the services in the
14 DSS.STATUS SCHEDULER
No input field which will be updated with some details for
15 STATUS.DETAIL information only
To specify TAFJ locking mechanism defined in tafj.properties
file.
If temn.tafj.locking.mode is set to DATABASE (Use database
locks of the underlying database) then input LOCK.MODE as
16 LOCK.MODE DATABASE or else it can be left blank.
Table 7 – DM.SERVICE.SCHEDULER
4.8. DM.AA.MAPPING
This is the table where the parameters are provided.
The ID for this application must be in the format:

Id for this application must be in the format:
@ID A 3 digit number followed by an asterisk (*), followed by a valid
18 GPACK
user name that must be present in the USER table.
If only the USER is provided, then the 3 digit number will be

defaulted automatically
1 DESCRIPTION The descriptions of report / interface

Specifies the task that will be done when the application is
verified. FULL is specified for the entire extract of AA Product
and Properties. The option ‘Only Product’ and ‘Properties’ is
reserved for Future Use.
2 EXTRACT.TYPE
3 VERSION.CHK Has two option Yes or No.
4 PRODUCT.LINE Reserved for future use.
Table 8 – DM.AA.MAPPING
4.9. DM.DATA.COMPARE
The Reconciliation extract will be taken from T24 after completion of load as per the process,
and the reconciliation extract from the Legacy will also be extracted and provided in the
DATA.IN Directory.
The table is used to compare both the Extracts and to provide the output of the comparison.

@ID User defined Id.
1 DESCRIPTION The Description for the comparison

The DM.COMPARE.FIELD.MAPPING table record which will be
used for mapping of the reconciliation Extracts
Two comparisons can be performed using
DM.DATA.COMPARE.
1. FILE.COMPARE – file to file compare.
2. ENVIRONMENT.COMPARE - file to environment
2 COMPARE.TYPE compare.
This field position of the Primary key (ID) in the file that is
3 ID.POSITION provided for comparison.
4 FM.DELIM The field delimiter used in the extract files.
5 VM.DELIM The multi value field delimiter used in the extract files.
6 SM.DELIM The sub value field delimiter used in the extract files.
This field is to flag if both the source and target extract for file
7 HEADER compare has Headers or not.
This field is used for information only to store the Legacy Data
8 LEGACY.FILE.NAME Extract.
9 SOURCE.FILE.PATH The directory name where the extract is provided by the bank.
19 GPACK
10 SOURCE.FILE.NAME The file name of the extract provided by the bank.

The Directory Name where the recon extract from T24 is
11 TARGET.FILE.PATH located.
12 TARGET.FILE.NAME The File Name of the recon extract from T24.

The Output file path where the reconciliation extract is available
13 OUTPUT.FILE.PATH after the comparison.
The Output file name of the reconciliation extract after the
14 OUTPUT.FILE.NAME comparison.
The number of agents that will be required to run the
15 NO.OF.AGENTS comparison can be mentioned in this field.
16 APPLICATION.NAME The application name for the comparison.
This field specifies the position of the field and applicable only
17.1 FIELD.POSITION for environment compare.
18.1 SOURCE.FIELD This field specifies the first field of source data file.
Table 9 – DM.DATA.COMPARE
4.10. DM.EXTRACTOR
Extraction of Data from T24 is necessary when a Migration is to take place between older
releases of T24 to a newer release or for reconciliation extracts.
The application DM.EXTRACTOR is used for extraction of data from T24.

characters long.
A meaningful ID, indicating the application name e.g.,

CUSTOMER should be provided.
CUSTOMER
MM.MONEY.MARKET
LIMIT
@ID
1 DESCRIPTION The descriptions of your report set / interface.
The name of the table for which the extraction is to
be done. The entry in this field must be present in the
STANDARD.SELECTION.
2 APPLICATION
Whether the extraction is Multi Company or not.
3 MULTI.COMPANY
Specifies the type of file which has to be
4 FILE.TYPE extracted($NAU or $HIS or $ARC)
20 GPACK
The value in this field can be either “VALIDATE” or

“PROCESS”. If VALIDATE is selected then the
records corresponding to ‘Application’ will be
validated for errors and if PROCESS then the normal
5 OFS.ACTION extraction is performed.
The description of the selection criteria. This is a
multivalue field.
6.1 SEL.DESC
The Selection field from the application must be
7.1 SEL.FLD specified here. This is an associated multivalue field.
The Selection criteria must be specified here. This is
an associated multivalue field.
8.1 SEL.CRIT
The Selection Value must be specified here. This is
9.1 SEL.VALUE an associated multivalue field.
The Selection Combination must be specified here.
This is an associated multivalue field.
10.1 SEL.COMB
The save list name must be entered in this field.
11 SELECT.LIST
12 TARGET.FILE The output filename for the Extraction.
The output directory where the extracted file will
13 OUTPUT.DIR reside
The Field Marker that will be used in the extract to
14 FM.DELIM separate the fields.
The Value Marker that will be used in the extract to
separate the Multi values.
15 VM.DELIM
The Sub value Marker that will be used in the extract
to separate the Sub values.
16 SM.DELIM
The Local Currency must be specified only if the
17 LOCAL.CCY extract is done for DATA.CAPTURE application.
The takeover account category must be specified
based on which the internal account.
18 DC.TOA.CATEGORY
The number from which the department code part in
19 DC.DAO.START.ID DATA.CAPTURE id must be started is specified.
Whether the headers need to be provided for the
extract or not.
20 FILE.HEADER
The field description for the field to be extracted.
21.1 FLD.LABEL
The application name must be specified from which
22.1 FLD.APP the for concurrent extract of the value is done.
21 GPACK
The extract type for the field is specified here.

23.1 FLD.TYPE
The field name from the application which is to be
24.1.1 FLD.NAME extracted.
The value in this field can be either “APPEND” or
“TRIM” or “REPLACE”. This field performs the
transformation in order to pick values from other
application.
25.1 TRANS.CONDITION
The value provided depends on the type mentioned
in the field “Trans Condition”. This field becomes
mandatory when “Trans Condition” is provided.
26.1 TRANS.VALUE
A subroutine can be attached to this field that will be
27.1 FLD.RTN used for different extraction logic.
The field name from the application mentioned in Fld
App must be specified.
28.1.1 FLD.APP.FLD
Whether the extract is done for DATA.CAPTURE
application or not.
29 DATACAPTURE
The credit transaction code must be specified. The
value is provided only if the extract is done for
DATA.CAPTURE.
30 TRANSACTION.CR
The debit transaction code must be specified. The
value is provided only if the extract is done for
31 TRANSACTION.DR DATA.CAPTURE.
Table 10 – DM.EXTRACTOR
4.11. DM.MAPPING.EXTRACT

@ID Id to this should be valid DMD record id.
The name of the table for which the extraction is to be done. The
entry in this field must be present in the
STANDARD.SELECTION.
1 APPL.NAME
The core field name of the application for which the extraction
2 CORE.FLD.NAME has to be done
This field indicate what type of core validation check is used for
3 SYS.PROG that particular field
22 GPACK
This represent maximum number of alpha or alphanumeric or

4 FMT numeric characters allowed for that particular fields
5 SYS.FLD.NO This field represent the field number of that particular field
The local field name of the application for which the extraction
6 USR.FLD.NAME has to be done
To indicate what type of core validation check is used for that
7 USR.SYS.PROG particular field
To indicate what type of core validation check is used for that
8 USR.FLD.NO particular field
based on the current status of the service associated with the
9 USR.FMT field DM.SERVICE.ID
Table 11 – DM.MAPPING.EXTRACT
4.12. DM.AA.EXTRACT

Id to this should be valid user name that must be present in the
@ID USER table.
1 DESCRIPTION The description about the extract is provided.
This field is used specify the product line for which the extract is
to be taken. Only two options are valid either “Deposits” or
2 PRODUCT.LINE “Lending”.
3 FM.DELIM To specify field level delimiter.
4 VM.DELIM To specify the delimiter for multi value fields.
5 SM.DELIM To specify the delimiter for sub value fields.

To specify the output directory in which the extract will be
6 OUTPUT.DIR placed.
The name in which the extracted file will be created in the
7 EXTRACT.NAME directory.
Table 12 – DM.AA.EXTRACT
4.13. T24.SAB.INFO

@ID Id to this should be SYSTEM
1 DAB.INFO.DETAILS This is an no inputtable field
2 SOURCE.SERVER This field is used to specify the source server name/id
23 GPACK
3 COMPANY.ID This field is used to specify the company ID of the environment
This field is used to specify the savelist ID. If the selected

application need to be compared. If not, the build will be crated for
4 SOURCE.SL.ID all applications
This field will be automatically updated by the system after running
5 INFO.DATE the service with info build date
6 INFO.STATUS the service with status
7 DAB.SOURCE.DETAILS This is an no inputtable field

8 SOURCE.DATE the service with info build date
9 SOURCE.STATUS the service with status
10 DAB.TARGET.DETAILS This is an no inputtable field
11 TARGET.SERVER This field is used to specify the target server name/id

12 TARGET.DATE the service with date
13 TARGET.STATUS the service with status
14 DAB.COMPARE.DETAIL This is an no inputtable field
If the reverse comparison needs to be done then this is set to Y

15 REVERSE.COMPARE (i.e, From Target to Source as well)
16 COMPARE.DATE the service with date
17 COMPARE.STATUS the service with status
18 OAB.SOURCE.DETAILS This is an no inputtable field
This field is to specify the savedlist ID with BP (Directory) names to

19 OAB.SOURCE.SL.ID create the build
20 OAB.SOURCE.DATE the service with info build date
21 OAB.SOURCE.STATUS the service with status
22 OAB.TARGET.DETAILS This is an no inputtable field
This field is to specify the savedlist ID with BP (Directory) names to

23 OAB.TARGET.SL.ID create the build
24 OAB.TARGET.DATE the service with info build date
25 OAB.TARGET.STATUS the service with status
26 OAB.COMPARE.DETAILS This is an no inputtable field

27 OAB.COMPARE.DATE the service with date
24 GPACK

28 OAB.COMPARE.STATUS the service with status
Table 14 – T24.SAB.INFO
5. Process workflow:
This Section covers the functionalities involved in the DMIG tool. Each of the tables and
their related functionalities are explained. Also, sample setups are given. Please Use the
Menu MB.DMMAIN for operations using the DM TOOL.
It has three menus namely Migration Pre-Requisite Check, Client System to T24
Migration , T24 to T24 Migration to facilitate efficient working with DM tool.
A sample screenshot of the Screen is as shown.
25 GPACK
5.1. Menus
5.1.1 Migration Pre-Requisite Check

This menu contains applications for making the pre-requisite checks.
➢ System Dates
26 GPACK
Table
DATES
Purpose
The DATES application is checked for the current system Date before start of Data Migration.
➢ Check Holiday Setup

Table
HOLIDAY
Purpose
The HOLIDAY application is checked for the current holiday setup.
➢ Check Migration User

USER
Purpose
The USER application is checked for existence of Data Migration Users .
➢ Check the Licensed Product

Table
SPF
Purpose
The SPF application is checked for the license in field number 36 , LICENSE.CODE.
➢ Check Company Record Setup

Table
COMPANY
Purpose
The COMPANY application is checked for the current holiday setup.
➢ Check T24 Application Auto Id Setup

Table
AUTO.ID.START
Purpose
The AUTO.ID.START application is checked the Ids Setup of the applications in scope for
Migration.
➢ Check DM Tool Details

Enquiry
ENQUIRY DM.TOOL.DETAILS
Purpose
27 GPACK
Display the details of the DM Tool that will be used for the validation and Load.
5.1.1.1 Check Migration Table Record Count
Table
DM.INFORMATION
Purpose
The application is used to summarise the number of records Loaded. The information of
the
number of counts per application is available in a Live file DATA.MIG.COUNT. This
application
keeps track of the changes in the Load count.
Detailed Working Procedure
This is the table where the parameters are provided. It can be accessed from the
Command line of the Browser.
The ID for this application must be only SYSTEM.
After selecting the correct ID you will get a screen as below. Input The application name
and commit it.
28 GPACK
DM.IFORMATION – verify
After doing the initial setup of parameters, DM.INFORMATION is verified. On

Verification:
1. The count for each application is done and updated in the fields LIVE Count, NAU
Count, HIS Count.
2. The value is updated in a LIVE file DATA.MIG.COUNT.
After committing the record we need to verify the record. We select the record name to be
verified and click the button as shown.
Click the marked button to verify the record.
After the transaction is processed we get the following screen.
29 GPACK
As mentioned, the LIVE file DATA.MIG.COUNT will be updated as shown below.
Multiple counts will also be captured in the LIVE file.
30 GPACK
The latest count of the application in the area will be the first multivalue set.
5.1.2 Client System to T24 Migration
5.1.2.1 T24 Data Loading

This menu contains applications that are used while migrating data from a Client’s system to T24.
It consists of T24 Data Loading and T24 Recon Data Extract.
31 GPACK
5.1.2.2 Data Migration Load Preparation
Table
DM.PREREQUISITE
Purpose
Creation of folder, copying of data files to the respective folders and creating the
DM.SERVICE.CONTROL (DSC) is necessary for the load of Data to
T24.DM.PREREQUISITE by which we can create necessary folders and moves the data files
to their respective paths. We will also be able to create folders for Reconciliation.
The DSC is an integral part of data load. This application also creates specified DSCs
with appropriate field values through Open Financial Service (OFS).
OFS.SOURCE
The following OFS.SOURCE record DSC.CREATE must be available in the deployed area.
32 GPACK
DM.PREREQUISITE – Parameters
This is the table where the parameters are provided. It can be accessed from the Command
line of the Browser.
A 3 digit number followed by an asterisk (*), followed by a valid user name that must be present in
the USER table. (The format is mandatory).
After selecting the correct ID you will get a screen as below.
33 GPACK
Here you can enter the following items
• Description: The descriptions of your report set / interface.

• Process: The task that will be done when the application is verified. Either
creation of DSCs or Only creation of Directories or Both can be specified here.
• Directory Name: The directory name where the data files are stored and under
this directory will other folders get created which will be used as Path Name in
DM.SERVICE.CONTROL. The value DATA.IN is defaulted, which can be
changed to any other directory as and when needed.
• Select List: This is an optional filed, where a valid &SAVEDLISTS& name can be
given.
• Dmd Name: This is an Associated Multivalue set which will hold the DMD name
for which the DM.SERVICE.CONTROL will be created followed by a dot (.) and a
two digit sequence number. (The format is mandatory). The folders that need to
be created for the data file will be based on the input to this field.
• File Name: The data file that will be used for the Load will be selected
automatically based on the input in the previous field. The data file must be
present in the Directory that has been specified in the field Directory Name. The
format of the data file must be as follows.
• <dmd.name>.<2 digit number>.<yyyymmddhhmm>.TXT
34 GPACK
• E.g.: CUSTOME.01.201003031653.TXT
• Reconciliation: We need to specify if Reconciliation Folders are to be created or
not. By default, the value “No” is defaulted.
• Recon Dir: The Directory name must be specified here where the reconciliation
folders will be created. By default RECON.OUT is populated in this field.
• Recon Spec Name: This is a multivalue field that is used to provide the Names of
the folders that need to be created under the Directory specified in the field
Recon Dir.
• DM Extractor Name: This is a multivalue field that contains DM Extractor Id. The
value entered must exist in the DM.EXTRACTOR table.
• File Conv Reqd: File conversion will be done if this field is set to YES.
• File Load Type: This field specifies whether the file load is from Server or Local
host.
• Conversion Type: Conversion type is specified here. Values entered here are NT
or Unix.
• Local Ref: Currently non inputtable, can be used for further developments.
• Override: Provides the overrides.
DM.PREREQUISITE – Verify
After doing the initial setup of parameters, DM.PREREQUISITE is verified. On verification 4
processes are triggered. Creation of folders VERIFY01, VERIFY02, VERIFY03, LOAD01,
AUTH01, DMV under the specified folders. Copying of the data file to the above folders in their
respective paths.
Creation of DSC records via OFS.
Creation of Reconciliation folders.
If DMD with function ‘R’ or ‘D’ records are not available, DSC will not be created. This will be
captured as override. For other DMDs with function as ‘V’, ‘I’ or ‘A’, if record is not present, it
will be an error.
35 GPACK
After committing the record we need to verify the record. We type the record name to be
36 GPACK
The folders are created for Validate, Input and Authorise and also the Reconciliation folders are
created as shown below and the data file is also copied to the respective path
TAFC:
37 GPACK
TAFJ:
The DSCs are also created for DMD.
Data Mapping Layout
Table
DATA.MAPPING.VERIFICATION
38 GPACK
Purpose
The menu is used to do the initial setup for the verification of the Data Mapping Sheet and the
DM.MAPPING.DEFINITION
This is the table where the parameters are provided. It can be accessed from the Command
The ID for this application can be upto 65 characters
39 GPACK
After the transaction is processed we get the following screen
40 GPACK
The result file will be created as below.

TAFC:
The compared DMV fields and the DMD fields are populated in the file as below
By providing the data file name only, the values in the data file will be validated and the
PASS/FAIL status will be updated based on the validation status of each record. The validation
status of each record will be stored in a separate file as a result.
The validation of the record values in the data file can be validated based on the
verification type provided by the user. The following are verification types,
41 GPACK
FIRST
POSITION
RANDOM
1. FIRST
If the datafile name is given and the verification type is “FIRST” then only the first string in
the datafile will be validated and the result for that particular record will be stored in a separate file
in the DMV folder. A sample record is provided below for reference.
On verifying the DMV, the PASS/FAIL status will be updated and the result will be stored
in the DMV folder. Only the file for data file will be created as the field verification is not provided in
this case.
42 GPACK
TAFC:
The result will be stored in the DMV folder as below
TAFJ:
Screen shot for the text and log files location
The status of the validated datafile will be populated in the file as below
43 GPACK
2. POSITION
If the datafile name is given and the verification type is “POSITION” then it’s mandatory to
provide values for the fields “FIRST.POSITION” and “LAST.POSITION”. The number of strings
present between the two position values in the datafile will be validated and the result for those
records will be stored in a separate file in the DMV folder.
in the DMV folder. Only the file for data file will be created as the field verification is not provided in
this case.
3. RANDOM
If the datafile name is given and the verification type is “RANDOM” then a string will be
picked randomly from datafile and will be validated. The result for that particular record will be
stored in a separate file in the DMV folder. A sample record is provided below for reference.
in the DMV folder. Only the file for datafile will be created as the field verification is not provided in
this case.
5.1.2.3 Data Mapping Definition
Table
44 GPACK
Purpose
This is the base mapping definition table, which maps the incoming data with T24™ fields.
The following items are defined here.
• T24™ Table to be Loaded
• Type of Load to be done (Example – OFS or flat jbase write)
• Type of Action to be performed (Example – Only Validate the data or actual
• update)
• Function to be used (Allowed function are Input, Authorise, Delete, Reverse)
• If not mentioned, Input function will be used by default.
• Way to identify the each field in a transaction/record (Example – by delimiter or
• position)
• Associated multi-valued sets to map the T24™ field with Data, by giving the
• position or delimiter to identify the data from the source file
• Any Post Update routine that will be called for every transaction/record being
• Loaded.

This application is used for defining the mapping of T24™ fields with the data received in the
Data file from the Client’s system. This can be defined for different T24™ applications (Core
as well as locally developed applications).
The ID of a record in this file can be any 35 alphanumeric characters. This need not be the
name of the application and any name can be given to a record. It is also possible to define
more than one record for an application since this can be used for multiple loading sessions
for the same application.
The parameters defined in this file include:
1. OFS Write or Flat write – While doing data loading, it is possible that data has to be
loaded in the core tables or in the locally developed tables. In case of Core Tables the
data has to be loaded through the OFS route where for locally developed tables load
can be either through the OFS route or can be a flat write. This however depends
upon the structure and linkages of the locally developed table. In case the load has to
be done on a single table which does not update any other table then the load can be
done through a flat write rather than going through the OFS route.
2. This parameter is governed by the Field “ LOAD.TYPE”. This is a mandatory field and
the possible values are OFS.LOAD or WRITE or READ.REPLACEMENT. When value
OFS.LOAD is selected then the data loading will be done through the OFS route
whereas selecting a value of WRITE will enable direct write to the tables. The
READ.REPLACEMENT option will update certain fields of an already Loaded record
through direct write of only those fields.
3. OFS.ACTION – To Ensure the correctness of the Data been Loaded, a value

‘VALIDATE’ can be set in this field, which does everything with the Load of the data,
45 GPACK
except that the data is not writt en to the disk. It checks all the validations/raise
exceptions/errors. A value ‘PROCESS’ will straight away does the physical write into
the database, after the validation
4. File Type – In case of a flat write, the data can be directly written to either of the $NAU,
$HIS or LIVE files. This parameter is determined by the value in field “ FILE.TYPE”.
The possible values in this field are NULL, $NAU and $HIS. In case NULL is selected
the write will be to LIVE file else the direct write will be done to the respe ctive files
($NAU or $HIS).
5. Defining Incoming Data – Generally the incoming data from the client received in the
Data file will comprise of several records in the form of text strings. For the purpose of
loading these records have to be segregated and this segregation can be done using
different methods. The possible methods for segregation include (i) use of delimiters
for identifying the records and fields within a record (ii) use of position of different
fields e.g. field 7 in a record can be of length 6 and will be starting at a position 25.
This way a field can be defined in a record. In this case it is not possible to define the
multi-value and sub-value fields since the position for mapping will get fixed and it will
not be possible to support the variable field lengths in case of multi -value and sub value fields.
This option is handled through the mandatory field “ IN.DATA.DEF” which has 2 options viz DELIM
or POSITION. The option DELIM is used for defining the delimiters to be used whereas POSITION
i s used for defining the position of the fields.
5. Delimiter Definitions: It is possible to parameterize different delimiters that can be
used for identifying the records, multi -values and sub-values. These definitions can be
provided in the fields FM.DELIM, VM.DELIM and SM.DELIM as each of these fields
represent one type of delimitation.
6. ID Generation:
In T24™ it is possible that for some of the application the ID has to be system
generated whereas for certain other applications the ID has be to be provided
manually.
Accordingly 3 options have been provided in this mandatory field “ ID.TYPE” viz.
AUTO, DATA and ROUTINE.
When the option AUTO is selected the ID will be automatically generated by the
system.
For option DATA the record ID has to be part of the incoming data.
In case of some of the applications require routine for generating the Ids the n the
option ROUTINE can be used. In this case a single argument is passed and returned
back from the routine used for forming the record ID. The name of the ID routine
can be defined in the field ID.ROUTINE.
46 GPACK
The ID position has to be defined in case of data being segregated by fixed positions.
This field ID.POSITION becomes a mandatory field if field IN.DATA.DEF has a value of
POSITION.
7. Escape Sequence:
There is a provision to allow the user to change certain character in the data from one
kind to another. For example if a “,” has to be changed to “:” then this can be done
using an associated multi -value field “ESC.SEQ.FR” and “ECS.SEQ.TO”. The value
defined in the field “ESC.SEQ.FR” will be changed to the value in the field “ESC.SEQ.TO”.
8. Mapping:
These are a set of associated multi -value fields from “APPL.FIELD.NAME” to
“FIELD.VALUE” that are used for mapping either OFS or flat write. This set of fields
comprise of APPL.FIELD.NAME, FIELD.POSITION, FIELD.LENGTH,
FIELD.ATTRIB and FIELD.VALUE.
9. Field “APPL.FIELD.NAME” is for defining the name of the field in given T24™
application (either core or local). It can take up to 65 characters. The field has to be defined in the
STANDARD.SELECTION record of the application. Either the field name or the field
number can be input in this field.
It is possible to provide the company for which the record is loaded. To do this, the
field name must be set to LOAD.COMPANY and the company code must be
provided in the associated field position.
For LD.LOANS.AND.DEPOSITS, an option to provide both the
LD.LOANS.AND.DEPOSITS record as well as the LD.SCHEDULE.DEFINE record is
available. The values must be separated using a message separator, defined using
‘MESSAGE.SEPARATOR’.
10. Field “FIELD.POSITION” is used to define the position of the field in the record given
by the client. For example if there is local reference field in the customer record
defined as field number 40.2 (MERCHANT.NUMBER) and this has been provided at
25th position in the data given by the Client then the field “ APPL.FIELD.NAME” should
have the value MERCHANT.NUMB ER and field “FIELD.POSITION” should have the
value of 25. This is used in case option “DELIM” or “POSITION” is opted in field
IN.DATA.DEF.
11. Field “FIELD.LENGTH is a mandatory field in case field “ IN.DATA.DEF” has value of
“POSITION” and for other cases this s is a no-input field.
12. Field FIELD.ATTRIB has two options viz. CONSTANT and ROUTINE. When option
47 GPACK
“CONSTANT” is selected the value in the field “FIELD.VALUE” will be mapped to the
Application field as constant value. In case option “ROUTINE” is selected the n the
Name of the routine should be defined in the field FIELD.VALUE. The name of the
Routine should be preceded by ‘@’ and should be defined in the PGM.FILE as type “S”.
13. Field FIELD.VALUE is used in conjunction with the field FIELD.ATTRIB. If

FIELD.ATTRIB is provided as CONSTANT, then the value in this field is used for all
incoming records.
14. Field POST.UPDATE.ROUTINE is used to perform the post update processing for a
record. In applications like LD which are single authoriser, this routine will be used to
perform the authorisation of an unauthorised record. any routine is attached to the field
POST.UPDATE.RTN, it can be removed even after the record is authorised.
15. Field OFS.SOURCE is used to define the OFS.SOURCE record to be used when
Loading the data into T24 via OFS. Four OFS.SOURCE records DM.OFS.SRC,
DM.OFS.SRC.VAL, DM.OFS.SRC.ORD and DM.OFS.SRC.VAL.ORD are available.
In cases where the field validation needs to be trigger for incoming OFS message then choose
DM.OFS.SRC.VAL for OFS processing. If update required in OFS.REQUEST.DETAIL file then
choose DM.OFS.SRC.VAL.ORD for OFS processing.
Note: LOG details are controlled using the field LOG.DETAIL.LEVEL in OFS.SOURCE.
Below are the possible options.
1. FULL – Both success and failure transactions captured in error log file.
2. EXCEPT – Only failure transactions captured in error log file.
3. NONE – No log file update.
48 GPACK
Sample DMD Record:
Updating of Multi/sub value field using READ.REPLACEMENT as Load Type

Using the Load.Type option as READ.REPLACEMENT, it is possible to replace particular field
value.
Sub value
Data file:
49 GPACK
DMD Record:
USER.ABBREVIATION record before read replacement:
50 GPACK
USER.ABBREVIATION record after read replacement:
51 GPACK
Loading of $ARC using the DMD record:
DMD Record:
52 GPACK
53 GPACK
54 GPACK
55 GPACK
56 GPACK
57 GPACK
58 GPACK
Before authorization of DMD:
After authorization of DMD:
59 GPACK
The below screenshot shows the $ARC file of the FUNDS.TRANSFER record
60 GPACK
61 GPACK
Sequential Upload through DMD (DM.MAPPING.DEFINITION)

Some Applications require entries in T24 sequentially. The following document explains the
process of uploading Data using DM.TOOL, which require Sequential Entry into T24.
Example: Application is LIMIT. This Application is used for demonstration of Sequential
upload in this document.
Test Case:
Prerequisites:
CUSTOMER application is required as prerequisite for LIMIT application.
10 records are created for CUSTOMER.
• 600000001
• 600000002 to 600000010
The first multi value for APPL.FIELD.NAME must be DATA.UPLOAD.GRP with

FIELD.POSITION as 1. The second multi value for APPL.FIELD.NAME must be
DATA.UPLOAD.SEQ with FIELD.POSITION as 2.
This configuration and sequence must be maintained for Sequential Upload. For Non
Sequential Upload, these values can be ignored.
The screenshot for reference.
62 GPACK
Other Field values mapped as per the Data Mapping Sheet.
Data File
Data File Count: 30 records
63 GPACK
Groups: 10
Each group will contain 3 records where the first record will be the global limit
followed by the product and sub product limits for the particular customer.
Group 1
Group 2
The first block is the Group 1 and the Second block is Group 2. (N number of groups
can be included in the data file). The first field in the Data file must be the Group ID
followed by the second field which must be the Sequence number for the respective
Group.
Sequential Upload Process

Upload
Verify the DM.SERVICE.CONTROL>I.LIMITU
Start the TSM
64 GPACK
The F.DM.SERVICE.DATA.FILE is will have 10 Record Keys for each of the 10

Groups in the Data File.
Group 1 of the data file:
Group 2 of the data file:
The other groups will be created similarly.
• The OFS.REQUEST.DETAIL (ORD) lists all the records in the data file, as processed.
65 GPACK
Processed OFS.REQUEST.DETAIL
Uploaded Records:
Global Limit: 600000001.0010000.01
66 GPACK
67 GPACK
Product Limit: 600000001.0001000.01
68 GPACK
Sub Product Limit: 600000001.0001010.01
69 GPACK
5.1.2.4 Automatic creation of Versions & DMD’s:
It is a program which is used to create the Versions and DMD’s

(DM.MAPPING.DEFINITION) for any input able applications in T24.This program is executed
in jshell prompt, during program execution, it will prompt for
• Application name
• Suffix of DMD name
Once the user provides the appropriate values, the program takes care of creating the
respective Version’s (If the record does not exist in the environment) for the corresponding
DMD and also DMD’s in the environment.
Prerequisites
Need to have these record has the perquisite for successful execution this routine
• VERSION > VERSION,RNT
70 GPACK
• VERSION > DM.DMT.MAPPING,RNT
Process Flow:
Once the application name is keyed, all input able fields are extracted from the
STANDARD.SELECTION and for that particular application and then DMD will be created.
AUTO.DMD.CREATION is modified now. Previously it was working as a mainline routine.

Now, it has been converted to a service.
Please follow the below steps for running the service AUTO.DMD.CREATION
71 GPACK
72 GPACK
Now the records are succefully created.
Creation of Versions and DMD’s for the given application
73 GPACK
Note: All Versions are single level authorization

Below is the sample screenshot of the automatically created DMD for the CUSTOMER
application
DM.MAPPING.DEFINITION>V.SUFFIX
74 GPACK
5.1.2.5 DM Service Control

Table
DM.SERVICE.CONTROL
Purpose
This work-file application is used to control the actual Load process. The following details must
be provided when the DM.SERVICE.CONTROL is set up .
• Load Company – The Company for which the data is loaded. If this information is
not provided in the incoming tape, it must be provided here.
• Data file directory and file name – A valid directory name and file name.
• Number of Sessions – The number of sessions with which the TSA.SERVICE

must be run.
• Run Status – To Request for a STOP of the TSA.SERVICE.
• User – The user name which will be used for the Load process. This username
will get updated in the TSA.SERVICE record related to the
DM.SERVICE.CONTROL. Initially DMUSER was hardcoded as the USER.
• RUN.STATUS – Implies whether the status of service as START or STOP.
• DSC.TYPE – Implies whether the service is for DMD(Loading) or

DME(Extraction)
• Error Details, No Of Error and Type Of Error – The details of the errors that are
generated during validation/process will be updated in these fields. Date, Started,
Stopped and Elapsed – The Current system Date, the start time, end time and
the elapsed time of validation/process activity will be updated in these fields.
DM.SERVICE.CONTROL>I.CUSTOM
75 GPACK

Setting up the Service Control for the first Time
The ID of the DM.SERVICE.CONTROL file must be the same as the

DM.MAPPING.DEFINITION table. After setting up the above mentioned fields, the record must be
committed. This must be done in the INPUT mode.
Pick up the newly setup record in Verify Mode and commit.
When running for the first time, the system will check if the BATCH, TSA.SERVICE and
TSA.WORKLOAD.PROFILE are present and if no they will be created. This is checked in the file
DM.SERVICE.CONTROL.CONCAT. If they don’t exist, they are created by the system. The
following components are created.
Batch
A batch record with the id as DM.SERVICE -<<DM.MAPPING.DEFINITION name>> is created.
This contains three jobs namely
DM.SERVICE.PRE.PROCESS – A single thread process which reads the incoming sequential

file and writes to DM.SERVICE.DATA.FILE
DM.SERVICE – is a multi-threaded job that reads DM.SERVICE.DATA.FILE and updates the job
list. Each record is then processed by BATCH.JOB.CONTROL and error log files generated using
the naming convention below.
<< DM.MAPPING.DEFINIATION Name>>#LOG.<<Session Number>>
DM.SERVICE.POST.PROCESS – is a single threaded process which consolidated all the LOG

files generated for a particular xxxx into a single error output file. Naming convention of the log
file is given below.
<< DM.MAPPING.DEFINIATION Name >>’-‘<< FILE.NAME >>-‘ERROR.txt’
76 GPACK
BATCH>DM.SERVICE-I.CUSTOM
TSA.WORKLOAD.PROFILE record
The number of sessions in the DM.SERVICE.CONTROL record is updated as number of

agents in this record
TSA.WORKLOAD.PROFILE>DM.SERVICE-I.CUSTOM
77 GPACK
TSA.SERVICE record
A TSA.SERVICE record with the following contents is created.

TSA.SERVICE> DM.SERVICE-I.CUSTOM
As can be seen, the user in the TSA.SERVICE record is updated from the
DM.SERVICE.CONTROL.
On verification, the status of the DM.SERVICE.CONTROL record is marked as ‘START’. The

same is updated into TSA.SERVICE record as well. The control log is updated with the starting
request details.
Then start the TSM
Data File:
TAFC
TAFJ:
Run the service.
78 GPACK
Output:
79 GPACK
Marking the service Stop
To mark the DM.SERVICE stop, the DM.SERVICE.CONTROL record must be opened in Input
mode and the RUN.STATUS must be set to STOP.
Immediately the TSA.SERVICE is marked for STOP. The agents will stop after processing the
current records.
Modifying the number of agents at Run time

To modify the number of agents during run time ,pick up the DM.SERVICE.CONTROL
record in Verify mode. Update the number of sessions as required. This will be updated to the
TSA.WORKLOAD.PROFILE application. Once the TSM reaches its review time, it will either
spawn more or less agents as required (in Phantom mode) or request for running more or less
agents (in Debug mode)
Right now this option is available only in Classic
Updating of Time Field in DSC:

The process of enhancing DSC, by capturing the Start and Stop fields in DSC, when the service is
started . The field DSC.TYPE is included in DM.SERVICE.CONTROL which can be updated either
as DME or DMD. If the id of the DM.SERVICE.CONTROL is from DM.MAPPING.DEFINITION
application then the value DMD is given or else if the id is from DM.EXTRACTOR, then DME is
given in the field DSC.TYPE.
80 GPACK
DM.SERVICE.CONTROL ID from DM.MAPPING.DEFINITION
• If the id of the DM.SERVICE.CONTROL is from DM.MAPPING.DEFINITION

application then the value DMD is given
DM.SERVICE.CONTROL>V.CUSTOM
• The DM.SERVICE.CONTROL must be verified
81 GPACK
• On verifying DM.SERVICE.CONTROL the respective service will get started
DM.SERVICE.CONTROL ID from DM.EXTRACTOR
• If the id of the DM.SERVICE.CONTROL is from DM.MAPPING.DEFINITION

application then the value DMD is given, if DM.SERVICE.CONTROL is from
DM.EXTRACTOR then any id can be given.
82 GPACK
83 GPACK
• On verifying DM.SERVICE.CONTROL the respective service will get started
• Start the extraction by executing the START.TSM command in Jshell prompt.
• After the extraction is complete we will find that the time fields in DSC have been
updated.
84 GPACK
Updating of DM.SERVICE.CONTROL.HIST through DSC:

The process of enhancing DSC, by updating the field MOVE.TO.HIST has been included
to move the error details from DSC to another template namely
DM.SERVICE.CONTROL.HIST.
• Mark the values as ‘Y’ in MOVE.TO.HIST field and commit the record.
DM.SERVICE.CONTROL>V.ACCINT
85 GPACK
• Accept Override.
• On verifying DM.SERVICE.CONTROL the error details will be moved to

DM.SERVICE.CONTROL.HIST and the error details in DSC will be removed.
86 GPACK
Updating of TSA.WORKLOAD.PROFILE through DSC:

The process is to enhance DSC, by updating the TSA.WORKLOAD.PROFILE for
each time when DSC is edited and VERIFIED.
The DM.SERVICE.CONTROL (DSC) is verified, and thereby numbers of agents have

been changed from 2 to 4.
DM.SERVICE.CONTROL>V.CUSTOM
The TSA.WORKLOAD.PROFILE is updated correctly. The agents required are

updated as 4 once the corresponding DSC is verified after the number of agents has
been updated in the DSC record.
87 GPACK
TSA.WORKLOAD.PROFILE>DM.SERVICE-V.CUSTOM
5.1.2.6 Service Control
Table
TSA.SERVICE
Purpose
The Menu is used to Start or Stop the TSA.SERVICE record TSM or any other service that
needs to be started or stopped manually.
Service Status
88 GPACK
Enquiry
ENQUIRY DM.ENQ.TSA.STATUS
Purpose
This enquiry provides the information for all Data Migration services as well as the TSM status.
Once the TSA.SERVICE has been marked as START, if the TSM is running in phantom mode
the tSA(agent) will be automatically started. If the same is running in debug mode, then the agents
will have to be manually initiated to start the actual process.

The Enquiry DM.ENQ.TSA.STATUS is used to get the details of TSA.SERVICEs and to
monitor the status of the services from T24. The selection criteria are as shown below.
We need to refresh the enquiry regularly to know the status of the services. For this we need
to enable auto refresh as shown below.
Click on the more options link.
89 GPACK
Enter the desired time to get refresh the display
The result will be as below and the query will refresh every 5 seconds.
5.1.2.7 Application backup
90 GPACK
Table
DM.APP.BACKUP
Purpose
Taking backup of the application is a necessary step in the process of migration. The following
Steps explain the usage of the application DM.APP.BACKUP by which we can take the
Backup of any application.
The entire operation can be successfully complete using the Browser.
DM.APP.BACKUP - parameters
This is the table where the parameters are provided. It can be accessed from the MENU line
of the Browser.
The @id of the application should be APP.<<valid PGM.FILE entry>>
91 GPACK
Here you can enter the following items:
• Application: This field is defaulted with the Application for which the APPLICATION N
backup is to be taken.
• Backup Dir: The Backup Directory where the folders will be created for creating the
backup.
• Backup Folder: The folder name where the APPLICATION records will be moved is
defaulted here.
• No Of Agents: The number of agents that will be required to run the service to clear and
backup the APPLICATION.
• Local Ref: Currently non inputtable, can be used for further developments.
• Override: No overrides are generated with this application.
92 GPACK
DM.APP.BACKUP – verify (T24 Application)
After doing the initial setup of parameters, DM.APP.BACKUP is verified. On verification 3

tables are updated.
1. TSA.WORKLOAD.PROFILE is updated/created with Id as

DOB-<ID of DM.APP.BACKUP>
2. TSA.SERVICE is updated/created with Id as

93 GPACK
3. BATCH is updated/created with Id as

94 GPACK
The Folder for taking the Application backup will be created under DM.BACKUP.
After the transaction is processed, TSA.SERVICE is automatically stopped and the

BATCH record is updated accordingly .
Running the Service
1. The TSA.SERVICE, DOB-APP.CUSTOMER will be started automatically on verifying the

application DM.APP.BACKUP.
2. Start the TSM , but inputting and authorizing the TSA.SERVICE records TSM to “Start”
3. Initiate the TSM in the classic mode like below.
4. The records from the APPLICATION will be moved to the backup folder.
Records count before and After the DM.APP.BACKUP
Before :
95 GPACK
After
Count the number of records in the backup folder to verify all the records are been
moved .
5.1.2.8 AA.MAPPING
Table
DM.AA.MAPPING
Purpose
This application is used to extract the AA products with their respective Properties
and Property class.
Description: The descriptions of your report / interface.

Extract Type: Specifies the task that will be done when the application is
verified. FULL is specified for the entire extract of AA Product and Properties.
The option ‘Only Product’ and ‘Properties’ is reserved for Future Use.
Product: This field is reserved for Future Use.
96 GPACK
Input a record
Verify the record in DM.AA.MAPPING
97 GPACK
After the extraction is completed the status will be as below.
The output will be stored in AA.DMS.OUT directory under the particular product line
name
5.1.2.9 DM.PRE.PROCESS (Multi-Threading)
• Table
DM.PRE.PROCESS
• Purpose
The scope of the table is to explain in detail regarding Multi-Threading
DM.PRE.PROCESS.
98 GPACK
The DM.SERVICE.CONTROL the field Pre Process is included. The field is mandatory
and value can be provided based on the vetting table as SINLGE or MULTI.
DM.SERVICE.CONTROL screenshot with field included:
DM.SERVICE.CONTROL>V.TESTPP1
Changes in DM.SERVICE.CONTROL.RUN
The following are the changes done in DM.SERVICE.CONTROL.RUN
99 GPACK
100 GPACK
CREATION OF BATCH FOR SINGLE
The below screenshot depicts the BATCH for SINLGLE Pre Process
101 GPACK
CREATION OF BATCH FOR MULTI
The below screenshot depicts the BATCH for MULTI Pre Process
102 GPACK
5.1.2.10 STP – Straight Through Processing workflow
A new field is introduced in DM.SERVICE.CONTROL to support message based processing

in addition to conventional file based process. Individual data lines should be pushed to JMS
queues using the message format described below.
Note: OFS source DM.LOAD should be configure in ejb-jar.xml
Kindly refer standard configuration document for JMS queue setup.
Message structure:
DMD.ID, OPERATION, Pay Load (i.e. Data)
Delimiter: ',' - Comma

DMD.ID : DM.MAPPING.DEFINITION record id
OPERATION : Possible values are ‘null’ or ‘1’
‘null' – Indicates straight through processing.
'1' - Indicates two-step process. The actual data is written to interim staging table
DM.SERVICE.DATA.FILE and then followed by DM.SERVICE for actual posting in T24.
Pay Load / Data – To be processed in T24.
Example:
CUSTOMER.UPLOAD,,101106|MARKJ|Mark Josy|Cathy Perry|Nelson
Chambers|1001|1|1000|1||1|US|1
103 GPACK
OPERATION is null - indicating straight through process.
Where CUSTOMER.UPLOAD is a record from DM.MAPPING.DEFINITION application

containing definition for customer record creation.
Pay load/Data – Customer data required for successful record creation.
104 GPACK
105 GPACK
DM.SERVICE.CONTROL with DM.LOAD.TYPE set to Online.
Push the sample message to data migration JSM queues configured (to use DM.LOAD ofs
source) for further processing in T24.
Customer record create in T24 for the sample message shared above.
106 GPACK
Log files generated on the file path specified in DSC record.
After running DM.SERVICE job, a consolidated log file will be generated.
Consolidated output file:
107 GPACK
For OPERATION = 1
CUSTOMER.UPLOAD,1,101116|MARRR|Mark|Cathy Perry|Nelson
Chambers|1001|1|1000|1||1|US|1
After posting messages, please check the interim staging table DM.SERVICE.DAT.FILE.
Query above file using DBTools > JQL LIST-ITEM F.DM.SERVICE.DATA.FILE
Run DM.SERVICE for further processing in T24.
108 GPACK
5.1.3 T24 Recon Data Extract
➢ Directory Creation for Reconciliation extract

Table
DM.PREREQUISITE
Purpose
To create the necessary directories for reconciliation extracts.
➢ T24 Data Extract for Reconciliation

Table
DM.EXTRACTOR
Purpose
109 GPACK
➢ Service Control
Table
TSA.SERVICE
Purpose
To start and stop the services during extraction process.
➢ Service Status
Table
DM.PREREQUISITE
Purpose
To monitor the services status during extraction process.
Directory Creation for Reconciliation extract

Table
DM.PREREQUISITE
Purpose
To create the necessary directories for reconciliation extracts.
5.1.3.1 DM.PREREQUISITE
This is the table where the parameters are provided. It can be accessed from the
Command
A 3 digit number followed by an asterisk (*), followed by a valid user name that must be
present in the USER table. (The format is mandatory).
110 GPACK
• Process: The task that will be done when the application is verified. Either creation of
DSCs or Only creation of Directories or Both can be specified here.
• Directory Name: The directory name where the data files are stored and under this
directory will other folders get created which will be used as Path Name in
111 GPACK
DM.SERVICE.CONTROL. The value DATA.IN is default ed, which can be changed to

any other directory as and when needed.
• Select List: This is an optional filed, where a valid &SAVEDLISTS& name can be
Given.
• Dmd Name: This is an Associated Multivalue set which will hold the DMD name for
Which the DM.SERVICE.CONTROL will be created followed by a dot (.) and a two
Digit sequence number. (The format is mandatory). The folders that need to be
Created for the data file will be based on the input to this field
• File Name: The data file that will be used for the Load will be selected automatically
based on the input in the previous field. The data file must be present in the Directory
that has been specified in the field Directory Name. The format of the data file must
be as follows.
<dmd.name>.<2 digit number>.<yyyymmddhhmm>.TXT

E.g.: CUSTOME.01.201003031653.TXT
• Reconciliation: We need to specify if Reconciliation Folders are to be created or not .

By default, the value “No” is defaulted.
• Recon Dir: The Directory name must be specified here where the reconciliation
folders will be created. By default RECON.OUT is populated in this field.
• Recon Spec Name: This is a multivalue field that is used to provide the Names of the
folders that need to be created under the Directory specified in the field Recon Dir.
• Local Ref: Currently non inputtable, can be used for further developments .
• Override: Provides the overrides.
112 GPACK
DM.PREREQUISITE – verify
After doing the initial setup of parameters, DM.PREREQUISITE is verified. On verification

below process will be triggered:
• Creation of Reconciliation folders.

•
113 GPACK
After the transaction is processed we get the foll owing screen.
The folders are created Reconciliation are shown below .
5.1.3.2 T24 Data Extract for Reconciliation
Table
DM.EXTRACTOR
Purpose
DM.EXTRACTOR – parameters
114 GPACK
This is the table where the parameters are provided. It ca n be accessed from the Command
There are no specifications for the ID of this application.

• Application: The name of the table for which the extraction is to be done. The entry
in this field must be present in the STANDARD.SELECTION.
• Multi Company: Whether the extraction is Multi Company or not.
• Sel Desc: The description of the selection criteria. This is a multivalue field.
• Sel Fld: The Selection field from the application must be specified here. This is an
associated multivalue field.
• Sel Crit: The Selection criteria must be specified here . This is an associated
multivalue field.
• Sel Value: The Selection Value must be specified here. This is an associated
multivalue field.
• Sel Comb: The Selection Combination must be specified here. This is an associated
multivalue field.
Select List: The save list name must be enter ed in this field.
• Target File: The output filename for the Extraction.
• Output Dir: The output directory where the extracted file will reside.
115 GPACK
• FM Delim: The Field Marker that will be used in the extract to separate the fields.
• VM Delim: The Value Marker that will be used in the extract to separate the Multi
values.
• SM Delim: The Sub value Marker that will be used in the extract to separate the Sub
values.
• Fld Label: The field description for the field to be extracted .
• Fld Type: The extract type for the field is specified here.
• Fld Name: The field name from the application which is to be extracted.
• Fld Rtn: A subroutine can be attached to this field that will be used for different
extraction logic
DM.EXTRACTOR – authorize
After doing the initial setup of parameters, DM.EXTRACTOR is authorised. On authorisation 3

tables are updated:
1. TSA.WORKLOAD.PROFILE is updated/created with Id as

DM.EXTRACTOR-<ID of DM.EXTRACTOR>
2. TSA.SERVICE is updated/created with Id as

3. BATCH is updated/created with Id as

After the transactions are processed TSA.WORKLOAD.PROFILE, TSA.SERVICE and the

BATCH record area created as below.
TSA.WORKLOAD.PROFILE
116 GPACK
TSA.SERVICE
BATCH
117 GPACK
Running the Service
After authorization, the service is started manually.
118 GPACK
Start the TSM.
Check the services, if started.
Start the services.
119 GPACK
The output file specified in the application is generated in the output directory.
• DM.EXTRACTOR- Validation process

As in loading process, validation can be done for extraction.
Create a record in the DM.EXTRACTOR with application name as COLLATERAL.
Input the necessary details in the respective fields and OFS.ACTION must be
VALIDATE.
120 GPACK
121 GPACK
After authorising the record, the service has to be started as per the below screen shot.
Once the service is complete, the OFS will be listed as shown below.
122 GPACK
• The headers can be included for the extracts

It is possible to include headers in the extract via DME.
FILE.HEADER when set to Yes – It can be made available in the extract.
123 GPACK
Extracted File with Headers:-
124 GPACK
• Multiple Applications can be extracted simultaneously
It is posible to extract mutilple application via DM.EXTRACTOR

Extraction for Multiple Applications can be done as explained below:-
125 GPACK
126 GPACK
Extracted file with Multiple Applications.
• Extraction can be done for Multicompany/book.

Extraction can also be done for multibook or multicompany via DME as below
127 GPACK
MULTI COMPANY SET TO YES
128 GPACK
OUTPUT:
129 GPACK
• Sub/Multi value for Core/Local. Fields can be extracted

It is possible to extract Core and local fields via DME.
130 GPACK
131 GPACK
132 GPACK
• The specific conversions can be extracted using no routines

Any specific conversion that is required for extraction can also be done.
133 GPACK
Extracted Sample of Records:-
DME Record with Arithmetic Operation
134 GPACK
135 GPACK
Extracted Sample of Records: -
DME Record for Absolute value testing.
136 GPACK
137 GPACK
DME Record with the usage of Substitute:-
138 GPACK
139 GPACK
DME can be used to convert co.code if needed .
140 GPACK
141 GPACK
It is also possible to extract data based on position..
142 GPACK
143 GPACK
• The trail balance for foreign currency can be extracted.

Trail balance for the GL in foreign currency can be extracted through DME.
144 GPACK
TSA.SERVICE record:
On authorisation of the DM.EXTRACTOR record a record in TSA.SERVICE will be created.
The result will be stored in RECON.OUT folder in the bnk.run path:
Sample Output :
TSA.SERVICE record:
On authorisation of the DM.EXTRACTOR record a record in TSA.SERVICE will be created.
145 GPACK
The result will be stored in RECON.OUT folder in the bnk.run path:
Sample Output :
146 GPACK
• Transformation via DME

Any transformation required that is appending values or trimming any value can be done
via DME as below.
Append:
Append is the condition which is used to add a value in the first position or in the last position
of the field value. Also a value can be added at a position mentioned within the field value.
The format is VALUE[POSITION]

E.g.:
VALUE[F] : To append to the first position of the field value
VALUE[L] : To append to the last position of the field value
VALUE[NUMBER] : To append to any position in the field value
The field values are provided as given in the below screen shot to extract from more than one
application using the append condition.
147 GPACK
Create a record in the DM.EXTRACTOR
148 GPACK
Start the service DM.EXTRACTOR-LOANS.TEST
After running the service, target file has been created in the output directory
149 GPACK
Extracted file
Trim:
Trim is the condition which is used to remove a value from the position which is mentioned
within the field value.
The format is [position]

E.g.:
[number1, number2]
[13,19] : Trim from 13th position to 19th position
Or [number]
application using the trim condition.
150 GPACK
151 GPACK
Extracted file
Replace:
Replace is the condition which is used to replace one value with another value in the position
mentioned in the field value.
The format is VALUE[POSITION]
E.g.:
VALUE [number1, number2]
Or VALUE[number]
152 GPACK
application using the replace condition.
153 GPACK
Extracted file
154 GPACK
Specific Conversions
For specific conversions FLD.TYPE field should be set to MANIPULATE .
System Variables
Variables like !TODAY, !USER, !NEXT.WORKING.DAY etc. can be used
DM.EXTRACTOR Record
155 GPACK
EXTRACTED DATA:
156 GPACK
Arithmetic Operation
The following operations can be performed.
+, - , * , /
DM.EXTRACTOR Record
157 GPACK
EXTRACTED DATA:
158 GPACK
Absolute value
Absolute value can be extracted. FLD.NAME should be set to A

DMFLD.ONLINE.BALANCE.
DM.EXTRACTOR Record
159 GPACK
EXTRACTED DATA:
160 GPACK
Substitute
DM.EXTRACTOR Record
161 GPACK
EXTRACTED DATA:
162 GPACK
Convert
This will replace every occurrence of the character X with Y.
DM.EXTRACTOR Record:
163 GPACK
EXTRACTED DATA:
164 GPACK
Extract
The values in the record is Extracted from position N1 to N2.
165 GPACK
EXTRACTED DATA:
166 GPACK
Extracting DATA.CAPTURE via DM.EXTRACTOR
For the DATA.CAPTURE Application the field DATA.CAPTURE should be set to

“YES” and also OPEN.ACTUAL.BAL field should be defined.
In order to create an internal Account we should define the three fields
LOCAL.CCY, DC.TOA.CATEGORY, DC.DAO.START.ID.
Where,
DC.TOA.CATEGORY - The take over account category which is unused must
be specified
DC.DAO.START.ID - The Department account officer id (DAO) which is a part
of DATA.CAPTURE id must be specified.
167 GPACK
168 GPACK
The value “OPEN.ACTUAL.BAL” in the field FLD.NAME will extract the values
for the fields Sign, Transaction Reference and Amount FCY/Amount LCY as
mentioned below.
After the process, three files will be extracted namely

o A file with the name mentioned in the field TARGET.FILE
o DC.ORDER.LIST.txt
o DC.BALANCED.LIST.txt
The final extracted file with the balanced batches is stored in

“DC.BALANCED.LIST.txt” and the same must be considered.
LD.SCHEDULE.DEFINE (future repayment) Extraction
Extract the data from LD and LD.SCHEDULE.DEFINE (future repayment) based

on the multi-value field the future repayment will be extracted
169 GPACK
Before extracting the data, the DME record the LD.SCHEDULE.DEFINE fields must
be in the below format. The @id only required for extracting the future repayment
data. Here the LD records with future repayment schedule will be extracted
The FLD.APP field must be value LD.SCHEDULE.DEFINE and FLD.NAME,

FLD.APP.FLD must be value ‘@ID’ and also DATACAPTURE must be selected ‘NO’
170 GPACK
After starting the services the DME records the LD contract with future repayment will
be extracted.
171 GPACK
Extracted file:
172 GPACK
DM.EXTRACTOR ($ARC) Archival Extraction:
Extraction of archived files in T24 can be extracted by providing the value for the field
FILE.TYPE as “$ARC”.
Similarly the date can be extracted for both HISTORY and UNAUTHORISED records.
The value to be provided in the field FILE.TYPE for extraction of history and
unauthorised files are “$HIS” and “$NAU”.
The FILE.TYPE field must be provided with the value $ARC for extracting archived
records. If the field FILE.TYPE is left blank the live file will be extracted for the
particular application.
173 GPACK
After starting the services the DME records the LD contract with future repayment will
be extracted.
174 GPACK
Extracted file:
Service Control
175 GPACK
Table
TSA.SERVICE
Purpose
The Menu is used to Start or Stop the TSA.SERVICE record TSM or any other service that
needs to be started or stopped manually.
Service Status
Enquiry
ENQUIRY DM.ENQ.TSA.STATUS
Purpose
This enquiry provides the information for all Data Migration services as well as the TSM status.
Once the TSA.SERVICE has been marked as START, if the TSM is running in phantom mode
the tSA(agent) will be automatically started. If the same is running in debug mode, then the agents
will have to be manually initiated to start the actual process.

The Enquiry DM.ENQ.TSA.STATUS is used to get the details of TSA.SERVICEs and to
monitor the status of the services from T24. The selection criteria are as shown below.
176 GPACK
We need to refresh the enquiry regularly to know the status of the services. For this we need
to enable auto refresh as shown below.
Click on the more options link.
Enter the desired time to get refresh the display
177 GPACK
The result will be as below and the query will refresh every 5 seconds.
178 GPACK
5.1.4 T24 to T24 Migration
T24 to T24 migration has the same menus as in Client System to T24 Migration and the
procedure is also the same as seen above.
5.1.5 Data & Object Audit
5.1.5.1 DATA AUDIT BUILD

The prerequisite for DAB comparison is mentioned below:
Check whether the below Routines are present in the environment.
The routine creates the records with ID as system date and application name in source
environment. These records are input to create the source dump.
✓ T24.SAB.INFO
✓ T24.SAB.INFO.FIELDS
✓ T24.SAB.INFO.ID
✓ T24.SAB.INFO.VALIDATE
✓ T24.DAB.INFO
✓ T24.DAB.INFO.FIELDS
✓ T24.DAB.INFO.BUILD
179 GPACK
✓ T24.DAB.INFO.BUILD.LOAD
✓ T24.DAB.INFO.BUILD.SELECT
✓ T24.DAB.INFO.BUILD.POST
The below routines creates the dump file from source environment.
✓ T24.DAB.SOURCE.BUILD
✓ T24.DAB.SOURCE.BUILD.LOAD
✓ T24.DAB.SOURCE.BUILD.SELECT
✓ T24.DAB.SOURCE.BUILD.POST
The below routine creates the dump file from target environment.
✓ T24.DAB.TARGET.BUILD
✓ T24.DAB.TARGET.BUILD.LOAD
✓ T24.DAB.TARGET.BUILD.SELECT
✓ T24.DAB.TARGET.BUILD.POST
The below routine creates the output dump file, which is comparison of source and target
dump in the target environment.
✓ T24.DAB.COMPARE.BUILD
✓ T24.DAB.COMPARE.BUILD.LOAD
✓ T24.DAB.COMPARE.BUILD.SELECT
✓ T24.DAB.COMPARE.BUILD.POST
This routine creates the output dump file, which is comparison of source and target dump in
the target environment.
The Data Audit Build tool is developed for all the data tables.
In this document, we have shown for both AUDIT and NON AUDIT Field data tables. Similarly
the procedure can be used for all the data tables.
Steps to be done in Source environment

RECORD CREATION
The inputs required for DAB has to be provided in this record as shown in the below
screenshot.
180 GPACK
Browser View:
181 GPACK
Putty View:
SOURCE.SL.ID- The savedlists ID with the selected application has to be provided in this
field. If not, the build will be created for all the applications
The table names has to be provided in the savedlists as shown in the below screenshot,
STEP1: Clear files

Before run each and every service the below mentioned has to be cleared
CLEAR.FILE F.TSA.STATUS
CLEAR.FILE F.BATCH.STATUS
CLEAR.FILE F.EB.EOD.ERROR
182 GPACK
STEP2: Start the TSM

Start the TSM first and then start the service T24.DAB.INFO.BUILD in Auto mode
STEP3: Start the T24.DAB.INFO.BUILD service

START THE SERVICE “T24.DAB.INFO.BUILD” to create the table info with the
application provided in savedlists (if savedlists provided) or with all the applications
183 GPACK
Browser View to start/stop the Service:
184 GPACK
Putty View to start/stop the Service:
STEP4: Start the TSM service
TAFJ:
185 GPACK
STEP5: Check the INFO.STATUS

The status can be checked as shown below
LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' INFO.STATUS
Check the T24.SAB.INFO application after completing T24.DAB.INFO.BUILD
186 GPACK
STEP6: List the T24.DAB.INFO

To view the template give the command “T24.DAB.INFO L” as shown in the below screen
shot
187 GPACK
To view records from the template T24.DAB.INFO give S as shown below in the
screenshot
The data record is shown below from the template T24.DAB.INFO.
188 GPACK
DUMP CREATION FOR SOURCE:

Before running the source build service check the INFO STATUS in T24.SAB.INFO is
completed as shown below in the screen shot.
Dump the source extract in the T24.DAB folder.
Step1: Check the INFO.STATUS
Browser View:
Putty View
189 GPACK
Step 2: Start the T24.DAB.SOURCE.BUILD service

Start the TSM first and then start the service T24.DAB.SOURCE.BUILD in AUTO mode
Browser View:
Putty View:
This T24.DAB.SOURCE.BUILD service will pick the data from T24.SAB.INFO &
T24.DAB.INFO
Start the service “T24.DAB.SOURCE.BUILD” to create the source build
190 GPACK
STEP3: Start the TSM service
TAFJ:
STEP 4: Check the SOURCE.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' SOURCE.STATUS
Check whether the date and status has been updated in T24.SAB.INFO
191 GPACK
STEP 5: Check the source dump in T24.DAB/SOURCE folder under the bnk.run
1. Source dump file will be saved in the below directory.

../ bnk.run/T24.DAB/SOURCE
The dump will be saved in the SOURCE path will be as T24.DAB.SOURCE.BUILD

(CURRENT System DATE & TIME)
TAFJ:
1. Source dump file will be saved in the below directory.
../ TAFJ/T24.DAB/SOURCE
192 GPACK
Please select the data table dump folder from Source dump files.
And View of the record contents in the data dump is shown in the below screenshot.
193 GPACK
STEP 6: Pack all the records in source environment

Then pack all the records from T24.DAB.INFO and release in the target environment.
194 GPACK
195 GPACK
DUMP CREATION for Target:

Steps to be done in Target environment
Step 1: Clear files
Before running every service clear the below mentioned files,
Before run the service see the below screen shot SOURCE STATUS is completed and then
input the TARGET.SERVER name.
Step 2: Check the SOURCE.STATUS before start the agent
196 GPACK
Step 3: Input the Target environment details in T24.SAB.INFO table
STEP 4: Start the TSM service

Start the TSM first and then start the service T24.DAB.TARGET.BUILD in AUTO mode
197 GPACK
Step 5: Start the T24.DAB.TARGET.BUILD service

Browser View:
Putty View:
198 GPACK
Start the service “T24.DAB.TARGET.BUILD” to create target dump
TAFJ:
199 GPACK
STEP 7: Check the TARGET.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ ‘SYSTEM’ TARGET.STATUS
200 GPACK
STEP 8: List the T24.DAB.INFO
To view the template give the command “T24.DAB.INFO L” as shown in the below screen
shot,
201 GPACK
To view records from the template T24.DAB.INFO give S as shown below in the screenshot
202 GPACK
The data record is shown below from the template T24.DAB.INFO.
STEP 9: Check the source dump in T24.DAB/TARGET folder under the bnk.run
Target dump file will be saved in the below directory.

../ bnk.run/T24.DAB/TARGET
The dump will be created in the TARGET path with the ID as T24.DAB.TARGET.BUILD
Current System Date & Time)
203 GPACK
Please select the particular data table dump folder from Target dump files.
View of the record contents in the target data dump is shown in the below screenshot.
204 GPACK
TAFJ:
Target dump file will be saved in the below directory.
./ TAFJ/T24.DAB/TARGET
Please select the particular data table dump folder from Target dump files.
View of the record contents in the target data dump is shown in the below screenshot.
205 GPACK
206 GPACK
Steps to be done for comparison between Source dump and Target dump
STEP 1: Clear files
Before running every service the below mentioned files have to be cleared,
Before running the service see the below screen shot SOURCE STATUS &
TARGET.STATUS completed and then input the REVERSE.COMPARE - Y/N
Since we have only the testing data's it’s very less than client data’s. To proceed the reverse
process it will take more time to compare. If you wish to continue Press
Y – Comparison of reverse process, it means compares target dump to source dump
N – Skip the reverse process comparison
STEP2: Start the TSM
207 GPACK
Step 3: Start the T24.DAB.COMPARE.BUILD service
Start the TSM first and then start the service T24.DAB.COMPARE.BUILD in AUTO mode

Start the service “T24.DAB.COMPARE.BUILD” to compare the data’s
TAFJ
Start the service “T24.DAB.COMPARE.BUILD” to compare the data’s
208 GPACK
STEP 5: Check the COMPARE.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' COMPARE.STATUS
209 GPACK
See the below screen shot after completed the dump creation T24.SAB.INFO application is
include the date and completed status
STEP 6: Check the source dump in T24.DAB/RESULT folder under the bnk.run
1. Result dump file will be saved in the below directory.

../ bnk.run/T24.DAB/RESULT
210 GPACK
The dump will be saved in the RESULT path with the ID as T24.DAB.RESULT.BUILD Current
System Date & Time)
211 GPACK
TAFJ:
Result dump file will be saved in the below directory.

../ bnk.run/T24.DAB/RESULT
The dump will be saved in the RESULT path with the ID as T24.DAB.RESULT.BUILD Current
System Date & Time)
212 GPACK
STEP 7: Result files

The result files will be created as,
1) T24.DAB.MISMATCH.BASE
2) T24.DAB.SOURCE.BASE
3) T24.DAB.TARGET.BASE
4) T24DAB.AA.ACTIVITY.CLASS.SOURCE.NEW
5) T24DAB.AA.ACTIVITY.CLASS.TARGET.NEW
T24.DAB.MISMATCH.BASE – The field level mismatches between source and target will be
captured in this file
213 GPACK
TAFJ:
T24.DAB.MISMATCH.BASE – The field level and mismatches between source and target will
be captured in this file
214 GPACK
T24.DAB.SOURCE.BASE- The new records in the source environment will be captured in

this file
215 GPACK
T24.DAB.TARGET.BASE - The new records in the target environment will be captured in this
file
216 GPACK
T24DAB.AA.ACTIVITY.CLASS.SOURCE.NEW- The new record contents in source

environment will be captured in this file
T24DAB.AA.ACTIVITY.CLASS.TARGET.NEW- The new record contents in target

environment will be captured in this file
TAFJ:
T24DAB.ACCOUNT.SOURCE.NEW:
217 GPACK
T24DAB.ACCOUNT.TARGET.NEW
5.1.5.2 OBJECT AUDIT BUILD

The prerequisite for T24 Object Audit Automation are as follows.
Check whether below Routines are present in the environment.
The routine creates the records with ID as system date and application name in source
environment. These records are input to create the source dump.
The below routines creates the base file in the Source environment.
✓ T24.SAB.INFO
✓ T24.SAB.INFO.FIELDS
✓ T24.SAB.INFO.ID
✓ T24.SAB.INFO.VALIDATE
✓ T24.OAB.SOURCE.BUILD
✓ T24.OAB.SOURCE.BUILD.LOAD
✓ T24.OAB.SOURCE.BUILD.SELECT
✓ T24.OAB.SOURCE.BUILD.POST
218 GPACK
The below routines creates the base file in target environment.

✓ T24.OAB.TARGET.BUILD
✓ T24.OAB.TARGET.BUILD.LOAD
✓ T24.OAB.TARGET.BUILD.SELECT
✓ T24.OAB.TARGET.BUILD.POST
Below routine creates the output dump file, which is comparison of source and target
dump in the target environment.
✓ T24.OAB.COMPARE.BUILD
✓ T24.OAB.COMPARE.BUILD.LOAD
✓ T24.OAB.COMPARE.BUILD.SELECT
✓ T24.OAB.COMPARE.BUILD.POST
The Object Audit Build tool is developed for all the Local and Core Source.
TAFC:
Create base in source environment

Step 1: Save list creation:
Create a saved list (User defined name) and give the list of BP names.
JED &SAVEDLISTS& JSHOW.COMMAN.BP
219 GPACK
Procedure for BASE creation

TAFJ:
Create a saved list (User defined name) and give the jar file folder name.
JED &SAVEDLISTS& TSHOW.LIB
Create the test3lib under the TAFJ Path and transfer the checked jar in binary mode
t24@localhost:DEV>CREATE-FILE test3lib TYPE=UD
220 GPACK
Step 2: Clear files

Before run the each every service clear below mention file
The inputs required for OAB has to be provided in this record as shown in the below
screenshot.
Step 3: RECORD CREATION
OAB.SOURCE.SL.ID - The savedlists ID with the selected BP has to be provided in

this field. If not, the build will be created for all the local & core
The BP list has to be provided in the savedlists as shown in the below screenshot,
Browser View:
221 GPACK
222 GPACK
Putty View:
223 GPACK
TAFJ:
Step 4: Start the TSM
224 GPACK
Step 5: Start the T24.OAB.SOURCE.BUILD service

To start the TSM first and then start the service T24.OAB.SOURCE.BUILD in Auto
mode
Browser View:
225 GPACK
Putty View:
226 GPACK
START THE SERVICE “T24.OAB.SOURCE.BUILD” ” to create the dump with the

source provided in savedlists (if savedlists provided) or with all the Bp lists
Step 6: Start the TSM service
TAFJ:
227 GPACK
Step 7: Check the OAB.SOURCE.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' OAB.SOURCE.STATUS
228 GPACK
Check the T24.SAB.INFO application after completing T24.OAB.SOURCE.BUILD
Step 8: Check the source dump in T24.OAB/SOURCE folder under the bnk.run
The Output structure of the base from the Source environment is as follows:
229 GPACK
1.The source base file will be saved in the below directory.

../ bnk.run/T24.OAB/SOURCE
TAFJ:
../ bnk.run/T24.OAB/SOURCE
The base will be saved in the SOURCE path as T24.OAB.BASE.SOURCE stamped by the
present System DATE & TIME.
To view the source base select the file using the following command in the specified path.
230 GPACK
TAFJ:
231 GPACK
STEP 9: Pack all the records in source environment
Creating base in Target environment

Step 1: Savelist creation:
Create a saved list (User defined name) and give the list of BP names.
JED &SAVEDLISTS& JSHOW.COMMAN.BP
232 GPACK
TAFJ:
JED &SAVEDLISTS& TSHOW.LIB
Procedure for BASE creation

Step 2: Clear files
233 GPACK
The inputs required for OAB has to be provided in this record as shown in the below
screenshot.
Step 3: RECORD CREATION
OAB.TARGET.SL.ID - The savedlists ID with the selected BP has to be provided in
this field. If not, the build will be created for all the local & core
The BP list has to be provided in the savedlists as shown in the below screenshot,
To start the TSM first and then start the service T24.OAB.TARGET.BUILD in auto
mode
234 GPACK
Step 5: Start the T24.OAB.TARGET.BUILD service

Browser View:
235 GPACK
Putty View:
236 GPACK
START THE SERVICE “T24.OAB.TARGET.BUILD” to create the dump with the source
provided in savedlists (if savedlists provided) or with all the Bp lists
TAFJ:
237 GPACK
238 GPACK
Step 7: Check the OAB.TARGET.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' OAB.TARGET.STATUS
239 GPACK
Step 8: Check the source dump in T24.OAB/TARGET folder under the bnk.run
The Output structure of the base from the Target environment is as follows:
The target base file will be saved in the below directory.
../ bnk.run/T24.OAB/TARGET
TAFJ:
./TAFJ /T24.OAB/TARGET
The base will be saved in the TARGET path as T24.OAB.BASE.TARGET stamped by the
present System DATE & TIME.
240 GPACK
241 GPACK
TAFJ:
Comparison between Source base and Target base

Steps to be done for comparison between Source dump and Target dump
Compress the source directory(Base) in the source environment
Move the source base file to ../ bnk.run/T24.OAB/ in the target area.
Step 1: Clear files

Step 2: Check the SOURCE.STATUS and TARGET.STATUS before start the agent
See the below screenshot OAB.SOURCE.STATUS AND OAB.TARGET.STATUS is
completed then continue to comparison
242 GPACK
243 GPACK
Step 4: Start the T24.OAB.COMPARE.BUILD service
Browser View:
To start the TSM first and then start the service T24.OAB.COMPARE.BUILD in AUTO mode
244 GPACK
Putty View:
Start the service “T24.OAB.COMPARE.BUILD” to compare the routines
TAFJ:
245 GPACK
246 GPACK
Step 6: Check the OAB.COMPARE.STATUS

LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' OAB.COMPARE.STATUS
See the below screen shot after completed the dump creation T24.SAB.INFO application is
include the date and completed status
247 GPACK
Step 7: Check the source dump in T24.OAB/RESULT folder under the bnk.run
The Output structure of the comparison result from the Target environment is as follows:
The output of the comparison will be saved in the below directory.

../ bnk.run/T24.OAB/RESULT
TAFJ:
./TAJ/T24.OAB/RESULT
STEP 8: Result files
The comparison base will be saved in the RESULT path as T24.OAB.BASE.RESULT

stamped by the present System DATE & TIME
The comparison result will be saved in 3 different files namely:

1) T24.OAB.MATCH (Matched Object Audit)
2) T24.OAB.UNMATCH (Non-Matched Object Audit)
3) T24.OAB.NEW ( new Object Audit)
248 GPACK
TAFJ:
T24.OAB.MATCH - It is based on the comparison result between the Source and Target
base. The result contains the matched Contents and also the new routines (routines found in
Source Base and not in Target Base).
All the output files will have the format
<BP.NAME > ROUTIN.NAME>DD MTH YYYY>HH:MM:SS>NEW>
Where ,<DD MTH YYYY> is the date when the routine was compile Last
<HH:MM:SS>, is the time when the routine was compile Last
<NEW> Applies only when there is a new routine exists and compiled in target
env.
The below is the sample for Matched object audits.
249 GPACK
>
TAFJ:
250 GPACK
T24.OAB.UNMATCH - It is based on the comparison result between the Source and Target
base. The result contains the unmatched Contents. Below is the sample for the unmatched
object audits
251 GPACK
TAFJ:
252 GPACK
T24.OAB.NEW - It is based on the comparison result between the Source and Target base.
The result contains the new routines (routines found in Target Base and not in Source Base).
Below is the sample for the unmatched object audits.
TAFJ:
T24.OAB.NEW - It is based on the comparison result between the Source and Target base.
The result contains the new routines (routines found in Target Base and not in Source Base).
Below is the sample for the unmatched object audits. No new routines in the pack. Hence
blank file generated.
253 GPACK
a. DM Tool Additional Features

i. DM.REF.TABLE
It is data migration reference table for AA Migration. It contains three fields –

DESCRIPTION,
APPLICATION, FIELD.NAME. If we want to extract any specific data (field value) from any
valid t24 table, we need to specify the application name and field names for which the values
has to be extracted.
Here you can enter the following fields.

@ID: The ID must be any valid T24 table.
Description: The descriptions of the T24 table.
Application: It specifies the valid T24 table name.
FIELD.NAME: It specifies the valid T24 field name for the APPLICATION defined . (Its
multi
value set field).
254 GPACK
ii. DM.AA.CUSTOMER.PROXY
Description:
The DM.AA.CUSTOMER.PROXY is a concat table containing arrangement id and proxy
customer id. It is a multi value set. The concat file id must be customer id which provided in
the AA.ARRANGEMENT.ACTIVITY record. Before we update the concat file, we need to be
specify the required fields in DM.REF.TABLE (Ref 4.4.1). Based on the reference table it
updates DM.AA.CUSTOMER.PROXY table.
Functional Process:
The arrangement id and customer id extracted from AA.ARRANGEMENT.ACTIVITY table as
based on the certain condition. First select the AA records, if the ACTIVITY field has
‘PROXY.SERVICES-NEW-ARRANGEMENT’ with FIELD.NAME has ‘PROXY.
If all the records has the value ‘PROXY’ in field FIELD.NAME, the corresponding proxy
customer and arrangement id will be updated in concat file.
Sample: AA.ARRANGEMENT.ACTIVITY record.
255 GPACK
The file FBNK.DM.AA.CUSTOMER.PROXY is built by running the mainline subroutine

DM.AA.CUSTOMER.PROXY.UPDATE .
This routine will update the DM.AA.CUSTOMER.PROXY concat table.
256 GPACK
iii. T24.AA.INT.ACT.DEFAULT
The subroutine will be attached as input routine in specified version with creation of PGM .FILE
and EB.API entry. This routine will default the values as ‘PROXY.ARRANGEMENT’ in the
fields FIELD.NAME and updates the corresponding arrangement id in the FIELD.VALUE field
in AA.ARRANGEMENT.ACTIVITY table (selected from DM.AA.CUSTOMER.PROXY) . It is
multi value set.
257 GPACK
Prerequisites:
Create the PGM.FILE entry for the T24.AA.INT.ACT.DEFAULT
Create the EB.API entry for the T24.AA.INT.ACT.DEFAULT.
258 GPACK
While inputting or Loading the data via this version the specified fields will be defaulted
from the concat table DM.AA.CUSTOMER.PROXY.
259 GPACK
iv. DM.AA.CUSTOMER
Description:
The DM.AA.CUSTOMER table is a concat file containing arrangement id for the
corresponding PROXY CUSTOMER. The arrangement id filed is a multi value set. The concat
file id must be customer id which provided in the AA.ARRANGEMENT.ACTIVITY (Proxy)
record. Before we update the concat file, we need to be specify the required fields in
DM.REF.TABLE (Ref 4.4.1). Based on this reference table, it updates the
DM.AA.CUSTOMER table.
Functional Process:
The arrangement id extracted from AA.ARRANGEMENT.ACTIVITY table as based on the
certain condition. First select the AA records, if the ACTIVITY field has
260 GPACK
‘INTERNET.SERVICES-NEW-ARRANGEMENT’ and update the arrangement id in the concat

table.
Sample: AA.ARRANGEMENT.ACTIVITY record.
The FBNK.DM.AA.CUSTOMER needs to be build by running the program
DM.AA.CUSTOMER.UPDATE.
This subroutine will update the DM.AA.CUSTOMER concat table.
261 GPACK
v. T24.EB.EXT.ARR.ACT.DEFAULT
The subroutine will be attached as input routine in specified version with creation of
PGM.FILE
and EB.API entry. This routine will default the values in the fields ARRANGEMENT from the
concat table DM.AA.CUSTOMER in EB.EXTERNAL.USER table.
Prerequisites
Create the PGM.FILE entry for t he T24.EB.EXT.ARR.ACT.DEFAULT.
262 GPACK
Create the EB.API entry for the T24.EB.EXT.ARR.ACT.DEFAULT.
263 GPACK
While inputting or Loading the data via this version the arrangement id will be defaulted from
the concat table DM.AA.CUSTOMER.
264 GPACK
vi. SC.PERF.DETAIL Load and

SC.PERF.DETAIL.CONCAT updating
This is used to convert the data file of SC.PERF.DETAIL into the required utility format file
and
to update the concat File SC.PERF.DETAIL.CONCAT.
Routine Updation
DM.SC.FORMAT:
This utility is used to convert the provided data file into RUN.PERFORMANCE.TAK EON
execution format.
Required Input for DM.SC.FORMAT:
Steps to be followed for Program execution.
1. Create a directory PERF.DATA in ...bnk.run path
2. Enter the path and file name
3. In PERF.DATA directory create a file data.txt and save it
265 GPACK
4. Run the program DM.SC.FORMAT it will create a new Data file in data.txt.
Expected output
Before Processing DM.SC.FORMAT data file in format:
After Processing DM.SC.FORMAT data file in format:
266 GPACK
267 GPACK
DM.SC.PERF.CONCAT.UPDATE
The routine will update the concat file SC.PERF.DETAIL.CONCAT based on the loaded
SC.PERF.DETAIL record. It contains the SC.PERF.DETAIL id with corresponding date
(YYYYMM).
SC.PERF.DETAIL:
268 GPACK
269 GPACK
Before Processing the DM.SC.PERF.CONCAT.UPDATE
270 GPACK
Listing SC.PERF.DETAIL.CONCAT as shown below:
271 GPACK
vii. Data Compare

• Table
DM.DATA.COMPARE
• Purpose
The scope of the table is to compare both the Extracts and to provide
the output of the comparison.
• Description: The Description for the comparison.
• Compare Type: The field specifies whether to compare environment or file.
• Recon Mapping: The DM.COMPARE.FIELD.MAPPING table record which
will be used for mapping of the reconciliation Extracts.
• Id Key: This field will hold the Primary key (ID) position of the record.
• Legacy File Name: This field is used for information only to store the Legacy
Data Extract.
• Source File Path: The directory Name where the Extract is provided by the
bank.
• Source File Name: The File Name of the Extract provided by the bank.
• Target File Path: The Directory Name where the Recon Extract from T24 is
located.
• Target File Name: The File Name of the Recon Extract from T24.
• Output File Path: The Output File Path where the reconciliation extract is
available after the comparison.
• Output File Name: The Output File name of the reconciliation extract after the
comparison.
• No. Of Agents: The number of agents that will be required to run the
comparison can be
• mentioned in this field.
• Application Name: The application name for the comparison.
272 GPACK
• Field Position.1: This field specifies the position of the field and applicable
only for environment compare.
• Source Field.1: This field specifies the first field of source data file.
Verify the record as shown below
273 GPACK
On Verifying you get the below output.
Data File:
In the below source file, the first two string ids are ending with 004,005. But the target file,
the first two string ids are ending with 005,004.
SOURCE.txt
TARGET.txt
274 GPACK
DM.DATA.COMPARE record
Record ID: TEST
Verify the DM.COMPARE record
Start the service
275 GPACK
Output:
The source and target new records are created in the separate file.
Source New Records
Target new Records
Mismatch records
• DM.COMPARE does one to many comparison.
276 GPACK
the first two string ids are ending with 005,004.
SOURCE.txt
TARGET.txt
Record ID: TEST
277 GPACK
Start the service
The source and target new records are created in the separate file.
Source New Records
Target new Records
278 GPACK
Mismatch records
Mismatch records
DM.DATA.COMPARE writes the comparison errors in a file.

the first string is in the second position.
SOURCE.txt
TARGET.txt
Record ID: TEST
279 GPACK
Start the service
280 GPACK
The Error log is created.
After updating the error log file, the source and target concat file are clear by the routine.
viii. DM Scheduler
• Table
DM.SERVICE.SCHEDULER
• Purpose
• The services for validating, loading and authorising of Data in T24 is required
to be scheduled and automated. Most of the tasks are manually performed
which needs to be eliminated. The multithread service will perform the tasks
in an automated way to eliminate the manual task to an extent.
• Description: The description of the SCHEDULER.
281 GPACK
• Verification Dss: This field is used to store the DM.SERVICE.SCHEDULER

ID which needs to be completed successfully in order for the current service
to be started.
• Run Status: To indicate whether the service needs to be started or stopped.
The two options available are START and STOP.
• DM Service Id: To store the DM.SERVICE.CONTROL ID which needs to be
started. This is a multi-value field.
• Verification: To store the DM.SERVICE.CONTROL ID which needs to be
completed successfully in order for the service, associated to the multivalued
set, to be started. This is an associated multi-value field.
• Err Threshold: To specify the maximum number of errors that will be tolerated
before marking the service as failed. This is an associated multi-value field.
• No Of Errors: No input field to update the number of records in error from the
corresponding DM.SERVICE.CONTROL after the service is complete. This
is an associated multivalue field.
• Skip Service: To specify if the service needs to be run or can be skipped. The
two options are YES and NO.
• Dsc Status: No input field which will be updated with values 0, 1, 2 or 3 based
on the current status of the service associated with the field DM Service Id.
• Dss Status: No input field which will be updated with values 0, 1, 2 or 3 based
on the current status of all the services in the SCHEDULER.
• Status Detail: No input field which will be updated with some details for
information only.
• Lock Mode - Optional values can be given like JDBC,DATABASE.etc. To

specify the Tafj locking mechanism specified in default properties file
(temn.tafj.locking.mode).
282 GPACK
Input a Record in DM.DATA.SCHEULER.
283 GPACK
Verify the Record.
On verifying the record, we get as below .
On Verifying the DSS, the RUN status becomes Start
284 GPACK
285 GPACK
Data File:
Output:
286 GPACK
Once the Scheduler is completed, the DSS updates with Sceduler Status as
Scheduler Completed.And also indicating No of Errors as 0 for both (Positive Test case).
287 GPACK
ix. DM.DATA.TARNSLATION
• Table
DM.DATA.TRANSLATION
• Purpose
• The data provided by the Client will contain values that correspond to the
Legacy Data Format which cannot be loaded into T24 without any
TRANSLATION. Hence a valid TRANSLATION must be done so that the
Data is converted into a T24 Data format and can be loaded.
• Application: The application for which the TRANSLATION carried out.
• Source Dir: The source directory of the data file consisting of Legacy ID is
provided in this field.
• (Please note that any error log generated from the TRANSLATION will
be available in this directory)
• Source Fname: The Datafile name co
• nsisting of Legacy ID is given.
288 GPACK
• Target Dir: The name of the output directory where the converted file will be
available after the TRANSLATION is over. Any error log generated will be
available as mentioned above.
• By default DATA.BP is defaulted which can be modified as per the user.
• Target Fname: The name of the converted data file with T24 Ids must be
given here.
• FM Delim: The Field Marker that is used in the datafile to delimit field values.
By default ‘|’ is defaulted which can be modified as per the user.
• VM Delim: The Value Marker that is used in the datafile to delimit field
values. By default ‘::’ is defaulted which can be modified as per the user.
• SM Delim: The Sub Value Marker that is used in the datafile to delimit field
values. By default ‘!!’ is defaulted which can be modified as per the user.
• Mapping Table: Any Concat file name that will be used for the
TRANSLATION can be provided in this field. This is a multivalue field.
• Pos Convert: The positions in the data file where the TRANSLATION has to
be done and replaced with T24 Ids. This is a sub value field associated with
Mapping Table field.
• Pos Value: fixed values change the position in the data file where the
TRANSLATION has to be done and replaced the fixed value. This is an
associated sub value set with Pos Check field.
• Pos Routine: A subroutine can be attached to this field that will be used for
TRANSLATION logic. This is an associated sub value set with Pos Check
field.
• No. Of Service: The number of agents that will be required to run the
TRANSLATION can be mentioned in this field.
Input a record.
289 GPACK
Verify the record as shown below.
Data file in which the translation has to be done:
290 GPACK
Output
Thus any changes that are to be done in the data file can me made through this table.
x. Handling BYTE Length in ORD

• When loading the UTF converted data file or data file which consists of
more than 1024 characters, there should not be any broken records in
DM.SERVICE.DATA.FILE which means there is no breakage of record
into 2.
Verifying DSC to start the service:
Start the service
291 GPACK
After starting the service, while listing the OFS.REQUEST.DETAIL, it is found there is
no breakage of record even it consists of special characters or more than 1024
characters.
In the above screenshots, it is found that there is no truncation of record even if there
is special characters or more than 1024 characters.
292 GPACK
xi. DM.AA.LENDING.BAL.EXTRACT
Balances can be extracted for Reconciliation Purpose using the routine
DM.AA.LENDING.BAL.EXTRACT.
Execution:
OUTPUT File:
Sample Output:
293 GPACK
xii. DM.AA.LENDING.SCHEDULE.EXTRACT
It is possible to extract the Schedules for Reconciliation Purpose
Execution:
OUTPUT File:
Sample Output:
294 GPACK
xiii. DM.DC.BATCH.UPDATE
DM.DC.BATCH.UPDATE can be done via DSC and also it checks for the updation of
DC.BATCH.CONTROL and DC.DEPT.BATCH.CONTROL.
It also checks the ID format for Data capture like Number of characters, prefixed with
DC and the current Julian Date in T24
DSC record:
After verifying DSC, there are no errors
DC.BATCH.CONTROL and DC.DEPT.BATCH.CONTROL records are updated

accordingly,
295 GPACK
If the batch already exist in the environment then the below error will throw
xiv. Mnemonic duplication:

On loading the file, if there are any duplication of mnemonic it would be captured and
error message will be created for the same.
Starting the DM.SERVICE.CONTROL
296 GPACK
Error log is created in the respective path for Mnemonic Duplication.
Error Detail is displayed in the below mentioned screenshot.
297 GPACK
xv. AA - Product Proofing and Publishing
During AA load. Suppose if the AA product is proofed and not published, error log is
created.
AA.PRODUCT record shows that the product SMALL.BUSINESS.LOAN is in proofed

status.
298 GPACK
After running the service, if in the data file the product used is
SMALL.BUSINESS.LOAN then error log is created as shown below.
xvi. TDM.DATA.STRUCTURE.EXTRACT
It is a program which is used to extract all the fields and properties of any table given in
the saved list.
Create the savedlists by entering the name of a specific application.
299 GPACK
Please logout and login to T24 before running the routine.

At the jshell prompt run the routine TDM.DATA.STRUCTURE.EXTRACT.
The save list name must be entered in the below.
Once the savedlists name is given, it will extract the field properties of that application and
also it will get stored in the T24.DATA.STRUCTURE.LIST directory in the format of .xls.
A sample excel (output) file generated is attached below
300 GPACK
xvii. ENQUIRY DM.ENQ.ISSUE.LOG

The purpose of the ENQUIRY DM.ENQ.ISSUE.LOG is to get the number of error,
number of records validated and the error details of the load process.
To run the enquiry
Selection Criteria
Output of the selection showing number of error, number of records validated and the
error details
xviii. UTF8 conversion

The UTF8 conversion of data file for swift character handling has to be incorporated in
generic DM Tool.
301 GPACK
The data file with Arabic character.
The above data file should be in DATA.IN folder.
The DMP will be created and verified as below
302 GPACK
After verifying the DMP we need to specify the value ‘Yes’ for converting the data file and the
converted data file is generated in same path.
303 GPACK
After converting the data file.
xix. DM.CLEANUP
1. The purpose of the routine is to clean up the existing DMD'S, DSC'S, TSA’s
(DM.SERVICE) and BATCH records related to DM SERVICE and
VERSIONS and The lib & bin files (GR0800005bin, GR0800005lib) and
DM.BP and T24MIG.BP folders are decataloged and deleted
2. For this we need to run program DM.CLEANUP.
Prerequisites
To export the corresponding LIB and BIN :

export JBCDEV_LIB=GR0800005lib
304 GPACK
DM.CLEANUP process flow:

• This routine DM.CLEANUP has to be run after export the LIB and BIN.
• Run the routine, it has been read the DMD and get the version ID from the
DMD (OFS.VERSION).
• Then read version record and get the CURR.NO, based on the CURR.NO the
record will be delete the Version’s LIVE NAU and HISTORY path.
• DM.BP and T24MIG.BP routines get decataloged and the folder get deleted.
• The LIB and BIN folders get deleted.
Record count before run the routine
305 GPACK
Clean-up Process:
306 GPACK
307 GPACK
6.Conclusions:
Thus the document explaining the functionality of a non -core T24™ Data Migration Tool that
is used for Data extract from T24 Load into T24 from any Client system. This could be used
as a base for using Data Migration tool in any T24 data Extract & Load process.
308 GPACK

Data Migration Userguide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Migration Userguide

Uploaded by

Copyright:

Available Formats

TEMENOS – PBG – Country Model Bank

Data Migration Tool

Information in this document is subject to change without notice.

COPYRIGHT 2007 - 2008 TEMENOS HEADQUARTERS SA. All rights reserved.

Table of Contents ...................................................................................................................... 1

5.1.2.9 DM.PRE.PROCESS (Multi-Threading) .......................................................... 98

Author Version Date

Gpack 1.0 11th April 2013

Gpack 2.0 5th August 2013

Data Migration 3.0 13th September 2013

Gpack 4.0 17th February 2016

Gpack 5.0 27th July 2016

Jeya Sudha.K 5.1 13 Mar 2017

R.Srisailesan 6.0 15 Mar 2017

B Srinivas Rao 6.1 Updateddesc of the DMD

K Jeya Sudha 7.0 Reviewed

B Srinivasarao 7.1 Updated the Description of the

K Jeya Sudha 8.0 Reviewed

Ragachandrika 8.1 Updated Error log id format

Sarath Balaji 8.2 New Field in

Sarath Balaji 8.3 New Field in

Sarath B 8.4 New field introduced in

Sarath B 8.5 OFS REPLACE functionality

Sarath B 8.6 New fields introduced in

Overview of this guide

Any queries in any part of this document can be addressed to gpack@temenos.com.

Abbreviations used in this Guide

▪ S – Single Value Field

T24 Modules Supported

4. Template, Fields and Description

No. Field Name Description

2.1 DESCRIPTION. The descriptions of your report set / interface.

The migration type that is going to be done (E.g. TM0, DR1,

5 MNEMONIC Specify the company Mnemonic

10 OVERRIDE Overrides that are generated, if any.

13 VM.DELIM.REPLACE Same as above

14 SM.DELIM.REPLACE Same as above

No. Field Name Description

The positions in the data file where the conversion

A subroutine can be attached to this field that will be

No. Field Name Description

format of the data file must be as follows.

We need to specify if Reconciliation Folders are to be

No. Field Name Description

A meaningful ID, indicating the application name e.g.,

Name of the T24™ Table to which the Data is been

The Directory name where the DMV status result will

No. Field Name Description

A meaningful ID, indicating the application name e.g.

needs to be converted, the character to be converted

No. Field Name Description

message based for straight through processing. Possible values

No. Field Name Description

1.1 DESCRIPTION The description of the SCHEDULER.

To indicate whether the service needs to be run for

To indicate whether the service needs to be started or stopped.

No. Field Name Description

@ID A 3 digit number followed by an asterisk (*), followed by a valid

user name that must be present in the USER table.

If only the USER is provided, then the 3 digit number will be

1 DESCRIPTION The descriptions of report / interface

3 VERSION.CHK Has two option Yes or No.

4 PRODUCT.LINE Reserved for future use.