Professional Documents
Culture Documents
Gpac Dami Userguide
Gpac Dami Userguide
GPAC_DAMI
DM Tool
User Guide
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.
Table of Contents
2 GPACK
DM Tool – User Guide
3 GPACK
DM Tool – User Guide
Document History
Comments:
DM Tool
4 GPACK
DM Tool – User 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
CUSTOMER
ACCOUNT
COLLATERAL
CURRENCY
SECURITY.MASTER
AA.ARRANGEMENT.ACTIVITY, etc
5 GPACK
DM Tool – User Guide
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.
6 GPACK
DM Tool – User Guide
3. Workflow Diagram
7 GPACK
DM Tool – User Guide
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
1.1 CLIENT.NAME The name of the client for which the migration is to be done
Table 1 – DM.INFORMATION
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.
8 GPACK
DM Tool – User Guide
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.
9 GPACK
DM Tool – User Guide
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.
10 GPACK
DM Tool – User Guide
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.
11 GPACK
DM Tool – User Guide
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
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.
12 GPACK
DM Tool – User Guide
V.CUSTOM
A.CUSTOM
I.CUSTOM
13 GPACK
DM Tool – User Guide
DATA
4.6. DM.SERVICE.CONTROL
This application is used
14 GPACK
DM Tool – User Guide
15 GPACK
DM Tool – User Guide
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.
16 GPACK
DM Tool – User Guide
4.8. DM.AA.MAPPING
This is the table where the parameters are provided.
The ID for this application must be in the format:
Table 8 – DM.AA.MAPPING
17 GPACK
DM Tool – User Guide
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.
9 SOURCE.FILE.PATH The directory name where the extract is provided by the bank.
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.
18.1 SOURCE.FIELD This field specifies the first field of source data file.
Table 9 – DM.DATA.COMPARE
18 GPACK
DM Tool – User Guide
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.
19 GPACK
DM Tool – User Guide
20 GPACK
DM Tool – User Guide
4.11. DM.MAPPING.EXTRACT
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
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
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
9 USR.FMT field DM.SERVICE.ID
Table 11 – DM.MAPPING.EXTRACT
21 GPACK
DM Tool – User Guide
4.12. DM.AA.EXTRACT
4.13. T24.SAB.INFO
22 GPACK
DM Tool – User Guide
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.
23 GPACK
DM Tool – User Guide
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.
5.1. Menus
24 GPACK
DM Tool – User Guide
System Dates
Table
DATES
Purpose
The DATES application is checked for the current system Date before start of Data Migration.
25 GPACK
DM Tool – User Guide
Purpose
Display the details of the DM Tool that will be used for the validation and Load.
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.
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.
26 GPACK
DM Tool – User Guide
After selecting the correct ID you will get a screen as below. Input The application name
and commit it.
DM.IFORMATION – verify
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.
27 GPACK
DM Tool – User Guide
28 GPACK
DM Tool – User Guide
The latest count of the application in the area will be the first multivalue set.
29 GPACK
DM Tool – User Guide
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.
30 GPACK
DM Tool – User Guide
DM.PREREQUISITE – Parameters
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 in the format:
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).
31 GPACK
DM Tool – User Guide
32 GPACK
DM Tool – User Guide
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.
33 GPACK
DM Tool – User Guide
After committing the record we need to verify the record. We type the record name to be
verified and click the button as shown.
34 GPACK
DM Tool – User Guide
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:
35 GPACK
DM Tool – User Guide
TAFJ:
Table
DATA.MAPPING.VERIFICATION
36 GPACK
DM Tool – User Guide
Purpose
The menu is used to do the initial setup for the verification of the Data Mapping Sheet and the
DM.MAPPING.DEFINITION
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 can be upto 65 characters
37 GPACK
DM Tool – User Guide
After committing the record we need to verify the record. We type the record name to be
verified and click the button as shown.
38 GPACK
DM Tool – User Guide
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,
39 GPACK
DM Tool – User Guide
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.
40 GPACK
DM Tool – User Guide
TAFC:
The result will be stored in the DMV folder as below
TAFJ:
The status of the validated datafile will be populated in the file as below
41 GPACK
DM Tool – User Guide
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.
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.
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.
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 datafile will be created as the field verification is not provided in
this case.
Table
42 GPACK
DM Tool – User Guide
DM.MAPPING.DEFINITION
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.
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.
43 GPACK
DM Tool – User Guide
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.
44 GPACK
DM Tool – User Guide
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
45 GPACK
DM Tool – User Guide
“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”.
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.
46 GPACK
DM Tool – User Guide
47 GPACK
DM Tool – User Guide
DMD Record:
48 GPACK
DM Tool – User Guide
49 GPACK
DM Tool – User Guide
DMD Record:
50 GPACK
DM Tool – User Guide
51 GPACK
DM Tool – User Guide
52 GPACK
DM Tool – User Guide
53 GPACK
DM Tool – User Guide
54 GPACK
DM Tool – User Guide
55 GPACK
DM Tool – User Guide
56 GPACK
DM Tool – User Guide
57 GPACK
DM Tool – User Guide
The below screenshot shows the $ARC file of the FUNDS.TRANSFER record
58 GPACK
DM Tool – User Guide
59 GPACK
DM Tool – User Guide
600000002 to 600000010
60 GPACK
DM Tool – User Guide
Data File
61 GPACK
DM Tool – User Guide
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.
62 GPACK
DM Tool – User Guide
The OFS.REQUEST.DETAIL (ORD) lists all the records in the data file, as processed.
63 GPACK
DM Tool – User Guide
Processed OFS.REQUEST.DETAIL
Uploaded Records:
Global Limit: 600000001.0010000.01
64 GPACK
DM Tool – User Guide
65 GPACK
DM Tool – User Guide
66 GPACK
DM Tool – User Guide
67 GPACK
DM Tool – User Guide
Application 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
68 GPACK
DM Tool – User Guide
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.
Please follow the below steps for running the service AUTO.DMD.CREATION
69 GPACK
DM Tool – User Guide
70 GPACK
DM Tool – User Guide
71 GPACK
DM Tool – User Guide
DM.MAPPING.DEFINITION>V.SUFFIX
72 GPACK
DM Tool – User Guide
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.
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.
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
73 GPACK
DM Tool – User Guide
Batch
A batch record with the id as DM.SERVICE -<<DM.MAPPING.DEFINITION name>> is created.
This contains three jobs namely
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>>
74 GPACK
DM Tool – User Guide
BATCH>DM.SERVICE-I.CUSTOM
TSA.WORKLOAD.PROFILE record
TSA.WORKLOAD.PROFILE>DM.SERVICE-I.CUSTOM
75 GPACK
DM Tool – User Guide
TSA.SERVICE record
As can be seen, the user in the TSA.SERVICE record is updated from the
DM.SERVICE.CONTROL.
Data File:
TAFC
TAFJ:
76 GPACK
DM Tool – User Guide
Output:
77 GPACK
DM Tool – User Guide
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.
78 GPACK
DM Tool – User Guide
DM.SERVICE.CONTROL>V.CUSTOM
79 GPACK
DM Tool – User Guide
80 GPACK
DM Tool – User Guide
81 GPACK
DM Tool – User Guide
After the extraction is complete we will find that the time fields in DSC have been
updated.
82 GPACK
DM Tool – User Guide
Mark the values as ‘Y’ in MOVE.TO.HIST field and commit the record.
DM.SERVICE.CONTROL>V.ACCINT
83 GPACK
DM Tool – User Guide
Accept Override.
84 GPACK
DM Tool – User Guide
85 GPACK
DM Tool – User Guide
TSA.WORKLOAD.PROFILE>DM.SERVICE-V.CUSTOM
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
86 GPACK
DM Tool – User Guide
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.
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.
87 GPACK
DM Tool – User Guide
The result will be as below and the query will refresh every 5 seconds.
88 GPACK
DM Tool – User Guide
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.
DM.APP.BACKUP - parameters
This is the table where the parameters are provided. It can be accessed from the MENU line
of the Browser.
89 GPACK
DM Tool – User Guide
90 GPACK
DM Tool – User Guide
91 GPACK
DM Tool – User Guide
92 GPACK
DM Tool – User Guide
The Folder for taking the Application backup will be created under DM.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.
Before :
93 GPACK
DM Tool – User Guide
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.
94 GPACK
DM Tool – User Guide
Input a record
95 GPACK
DM Tool – User Guide
The output will be stored in AA.DMS.OUT directory under the particular product line
name
Table
DM.PRE.PROCESS
Purpose
The scope of the table is to explain in detail regarding Multi-Threading
DM.PRE.PROCESS.
96 GPACK
DM Tool – User Guide
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>V.TESTPP1
Changes in DM.SERVICE.CONTROL.RUN
97 GPACK
DM Tool – User Guide
98 GPACK
DM Tool – User Guide
The below screenshot depicts the BATCH for SINLGLE Pre Process
99 GPACK
DM Tool – User Guide
The below screenshot depicts the BATCH for MULTI Pre Process
100 GPACK
DM Tool – User Guide
Service Control
Table
TSA.SERVICE
Purpose
To start and stop the services during extraction process.
Service Status
101 GPACK
DM Tool – User Guide
Table
DM.PREREQUISITE
Purpose
To monitor the services status during extraction process.
5.1.3.1 DM.PREREQUISITE
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).
102 GPACK
DM Tool – User Guide
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
103 GPACK
DM Tool – User Guide
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.
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 .
DM.PREREQUISITE – verify
104 GPACK
DM Tool – User Guide
105 GPACK
DM Tool – User Guide
Table
DM.EXTRACTOR
Purpose
The application DM.EXTRACTOR is used for extraction of data from T24.
DM.EXTRACTOR – parameters
This is the table where the parameters are provided. It ca n be accessed from the Command
line of the Browser.
There are no specifications for the ID of this application.
106 GPACK
DM Tool – User Guide
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.
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
TSA.WORKLOAD.PROFILE
107 GPACK
DM Tool – User Guide
TSA.SERVICE
BATCH
108 GPACK
DM Tool – User Guide
109 GPACK
DM Tool – User Guide
110 GPACK
DM Tool – User Guide
The output file specified in the application is generated in the output directory.
111 GPACK
DM Tool – User Guide
112 GPACK
DM Tool – User Guide
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.
113 GPACK
DM Tool – User Guide
114 GPACK
DM Tool – User Guide
115 GPACK
DM Tool – User Guide
116 GPACK
DM Tool – User Guide
117 GPACK
DM Tool – User Guide
118 GPACK
DM Tool – User Guide
119 GPACK
DM Tool – User Guide
OUTPUT:
120 GPACK
DM Tool – User Guide
121 GPACK
DM Tool – User Guide
122 GPACK
DM Tool – User Guide
123 GPACK
DM Tool – User Guide
124 GPACK
DM Tool – User Guide
125 GPACK
DM Tool – User Guide
126 GPACK
DM Tool – User Guide
127 GPACK
DM Tool – User Guide
128 GPACK
DM Tool – User Guide
129 GPACK
DM Tool – User Guide
130 GPACK
DM Tool – User Guide
131 GPACK
DM Tool – User Guide
132 GPACK
DM Tool – User Guide
133 GPACK
DM Tool – User Guide
134 GPACK
DM Tool – User Guide
135 GPACK
DM Tool – User Guide
TSA.SERVICE record:
On authorisation of the DM.EXTRACTOR record a record in TSA.SERVICE will be created.
Sample Output :
TSA.SERVICE record:
On authorisation of the DM.EXTRACTOR record a record in TSA.SERVICE will be created.
136 GPACK
DM Tool – User Guide
Sample Output :
137 GPACK
DM Tool – User Guide
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 field values are provided as given in the below screen shot to extract from more than one
application using the append condition.
138 GPACK
DM Tool – User Guide
139 GPACK
DM Tool – User Guide
After running the service, target file has been created in the output directory
140 GPACK
DM Tool – User Guide
Extracted file
Trim:
Trim is the condition which is used to remove a value from the position which is mentioned
within the field value.
141 GPACK
DM Tool – User Guide
142 GPACK
DM Tool – User Guide
After running the service, target file has been created in the output directory
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]
143 GPACK
DM Tool – User Guide
The field values are provided as given in the below screen shot to extract from more than one
application using the replace condition.
144 GPACK
DM Tool – User Guide
After running the service, target file has been created in the output directory
Extracted file
145 GPACK
DM Tool – User Guide
Specific Conversions
For specific conversions FLD.TYPE field should be set to MANIPULATE.
System Variables
DM.EXTRACTOR Record
146 GPACK
DM Tool – User Guide
EXTRACTED DATA:
147 GPACK
DM Tool – User Guide
Arithmetic Operation
+, - , * , /
DM.EXTRACTOR Record
148 GPACK
DM Tool – User Guide
EXTRACTED DATA:
149 GPACK
DM Tool – User Guide
Absolute value
DM.EXTRACTOR Record
150 GPACK
DM Tool – User Guide
EXTRACTED DATA:
151 GPACK
DM Tool – User Guide
Substitute
DM.EXTRACTOR Record
152 GPACK
DM Tool – User Guide
EXTRACTED DATA:
153 GPACK
DM Tool – User Guide
Convert
DM.EXTRACTOR Record:
154 GPACK
DM Tool – User Guide
EXTRACTED DATA:
155 GPACK
DM Tool – User Guide
Extract
DM.EXTRACTOR Record:
156 GPACK
DM Tool – User Guide
EXTRACTED DATA:
157 GPACK
DM Tool – User Guide
158 GPACK
DM Tool – User Guide
159 GPACK
DM Tool – User Guide
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.
160 GPACK
DM Tool – User Guide
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
DM.EXTRACTOR Record:
161 GPACK
DM Tool – User Guide
After starting the services the DME records the LD contract with future repayment will
be extracted.
162 GPACK
DM Tool – User Guide
Extracted file:
163 GPACK
DM Tool – User Guide
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”.
DM.EXTRACTOR Record:
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.
164 GPACK
DM Tool – User Guide
After starting the services the DME records the LD contract with future repayment will
be extracted.
165 GPACK
DM Tool – User Guide
Extracted file:
Service Control
166 GPACK
DM Tool – User Guide
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.
167 GPACK
DM Tool – User Guide
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.
168 GPACK
DM Tool – User Guide
The result will be as below and the query will refresh every 5 seconds.
169 GPACK
DM Tool – User Guide
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.
170 GPACK
DM Tool – User Guide
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.
171 GPACK
DM Tool – User Guide
Browser View:
172 GPACK
DM Tool – User Guide
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,
173 GPACK
DM Tool – User Guide
174 GPACK
DM Tool – User Guide
175 GPACK
DM Tool – User Guide
TAFJ:
176 GPACK
DM Tool – User Guide
177 GPACK
DM Tool – User Guide
178 GPACK
DM Tool – User Guide
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.
179 GPACK
DM Tool – User Guide
Putty View
180 GPACK
DM Tool – User Guide
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
181 GPACK
DM Tool – User Guide
TAFJ:
Check whether the date and status has been updated in T24.SAB.INFO
182 GPACK
DM Tool – User Guide
STEP 5: Check the source dump in T24.DAB/SOURCE folder under the bnk.run
183 GPACK
DM Tool – User Guide
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.
184 GPACK
DM Tool – User Guide
185 GPACK
DM Tool – User Guide
186 GPACK
DM Tool – User Guide
187 GPACK
DM Tool – User Guide
188 GPACK
DM Tool – User Guide
Putty View:
189 GPACK
DM Tool – User Guide
TAFJ:
190 GPACK
DM Tool – User Guide
Check whether the date and status has been updated in T24.SAB.INFO
191 GPACK
DM Tool – User Guide
To view the template give the command “T24.DAB.INFO L” as shown in the below screen
shot,
192 GPACK
DM Tool – User Guide
To view records from the template T24.DAB.INFO give S as shown below in the screenshot
193 GPACK
DM Tool – User Guide
STEP 9: Check the source dump in T24.DAB/TARGET folder under the bnk.run
The dump will be created in the TARGET path with the ID as T24.DAB.TARGET.BUILD
Current System Date & Time)
194 GPACK
DM Tool – User Guide
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.
195 GPACK
DM Tool – User Guide
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.
196 GPACK
DM Tool – User Guide
197 GPACK
DM Tool – User Guide
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,
CLEAR.FILE F.TSA.STATUS
CLEAR.FILE F.BATCH.STATUS
CLEAR.FILE F.EB.EOD.ERROR
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
198 GPACK
DM Tool – User Guide
Start the TSM first and then start the service T24.DAB.COMPARE.BUILD in AUTO mode
TAFJ
Start the service “T24.DAB.COMPARE.BUILD” to compare the data’s
199 GPACK
DM Tool – User Guide
200 GPACK
DM Tool – User Guide
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
201 GPACK
DM Tool – User Guide
The dump will be saved in the RESULT path with the ID as T24.DAB.RESULT.BUILD Current
System Date & Time)
202 GPACK
DM Tool – User Guide
TAFJ:
The dump will be saved in the RESULT path with the ID as T24.DAB.RESULT.BUILD Current
System Date & Time)
203 GPACK
DM Tool – User Guide
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
204 GPACK
DM Tool – User Guide
TAFJ:
T24.DAB.MISMATCH.BASE – The field level and mismatches between source and target will
be captured in this file
205 GPACK
DM Tool – User Guide
206 GPACK
DM Tool – User Guide
T24.DAB.TARGET.BASE - The new records in the target environment will be captured in this
file
207 GPACK
DM Tool – User Guide
TAFJ:
T24DAB.ACCOUNT.SOURCE.NEW:
208 GPACK
DM Tool – User Guide
T24DAB.ACCOUNT.TARGET.NEW
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
209 GPACK
DM Tool – User Guide
The Object Audit Build tool is developed for all the Local and Core Source.
TAFC:
210 GPACK
DM Tool – User Guide
Create the test3lib under the TAFJ Path and transfer the checked jar in binary mode
t24@localhost:DEV>CREATE-FILE test3lib TYPE=UD
211 GPACK
DM Tool – User Guide
212 GPACK
DM Tool – User Guide
213 GPACK
DM Tool – User Guide
Putty View:
214 GPACK
DM Tool – User Guide
TAFJ:
215 GPACK
DM Tool – User Guide
Browser View:
216 GPACK
DM Tool – User Guide
Putty View:
217 GPACK
DM Tool – User Guide
TAFJ:
218 GPACK
DM Tool – User Guide
219 GPACK
DM Tool – User Guide
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:
220 GPACK
DM Tool – User Guide
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.
221 GPACK
DM Tool – User Guide
TAFJ:
222 GPACK
DM Tool – User Guide
Create a saved list (User defined name) and give the list of BP names.
JED &SAVEDLISTS& JSHOW.COMMAN.BP
223 GPACK
DM Tool – User Guide
TAFJ:
JED &SAVEDLISTS& TSHOW.LIB
224 GPACK
DM Tool – User Guide
CLEAR.FILE F.TSA.STATUS
CLEAR.FILE F.BATCH.STATUS
CLEAR.FILE F.EB.EOD.ERROR
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
225 GPACK
DM Tool – User Guide
226 GPACK
DM Tool – User Guide
Putty View:
227 GPACK
DM Tool – User Guide
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
Step 6: Start the TSM service
TAFJ:
228 GPACK
DM Tool – User Guide
229 GPACK
DM Tool – User Guide
Check whether the date and status has been updated in T24.SAB.INFO
230 GPACK
DM Tool – User Guide
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.
To view the source base select the file using the following command in the specified path.
231 GPACK
DM Tool – User Guide
232 GPACK
DM Tool – User Guide
TAFJ:
To view the source base select the file using the following command in the specified path.
Move the source base file to ../ bnk.run/T24.OAB/ in the target area.
233 GPACK
DM Tool – User Guide
234 GPACK
DM Tool – User Guide
Browser View:
To start the TSM first and then start the service T24.OAB.COMPARE.BUILD in AUTO mode
235 GPACK
DM Tool – User Guide
Putty View:
Start the service “T24.OAB.COMPARE.BUILD” to compare the routines
TAFJ:
236 GPACK
DM Tool – User Guide
237 GPACK
DM Tool – User Guide
See the below screen shot after completed the dump creation T24.SAB.INFO application is
include the date and completed status
238 GPACK
DM Tool – User Guide
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:
TAFJ:
./TAJ/T24.OAB/RESULT
239 GPACK
DM Tool – User Guide
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).
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.
240 GPACK
DM Tool – User Guide
>
TAFJ:
241 GPACK
DM Tool – User Guide
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
242 GPACK
DM Tool – User Guide
TAFJ:
243 GPACK
DM Tool – User Guide
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.
244 GPACK
DM Tool – User Guide
FIELD.NAME: It specifies the valid T24 field name for the APPLICATION defined . (Its
multi
245 GPACK
DM Tool – User Guide
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.
246 GPACK
DM Tool – User Guide
247 GPACK
DM Tool – User Guide
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
248 GPACK
DM Tool – User Guide
Prerequisites:
249 GPACK
DM Tool – User Guide
While inputting or Loading the data via this version the specified fields will be defaulted
from the concat table DM.AA.CUSTOMER.PROXY.
250 GPACK
DM Tool – User Guide
iv. DM.AA.CUSTOMER
Description:
corresponding PROXY CUSTOMER. The arrangement id filed is a multi value set. The concat
record. Before we update the concat file, we need to be specify the required fields in
DM.AA.CUSTOMER table.
Functional Process:
certain condition. First select the AA records, if the ACTIVITY field has
251 GPACK
DM Tool – User Guide
DM.AA.CUSTOMER.UPDATE.
252 GPACK
DM Tool – User Guide
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
Prerequisites
253 GPACK
DM Tool – User Guide
254 GPACK
DM Tool – User Guide
While inputting or Loading the data via this version the arrangement id will be defaulted from
255 GPACK
DM Tool – User Guide
This is used to convert the data file of SC.PERF.DETAIL into the required utility format file
and
Routine Updation
DM.SC.FORMAT:
This utility is used to convert the provided data file into RUN.PERFORMANCE.TAK EON
execution format.
256 GPACK
DM Tool – User Guide
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:
257 GPACK
DM Tool – User Guide
258 GPACK
DM Tool – User Guide
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:
259 GPACK
DM Tool – User Guide
260 GPACK
DM Tool – User Guide
261 GPACK
DM Tool – User Guide
262 GPACK
DM Tool – User Guide
263 GPACK
DM Tool – User Guide
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.
264 GPACK
DM Tool – User Guide
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
265 GPACK
DM Tool – User Guide
DM.DATA.COMPARE record
Record ID: TEST
266 GPACK
DM Tool – User Guide
Output:
The source and target new records are created in the separate file.
Mismatch records
267 GPACK
DM Tool – User Guide
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
DM.DATA.COMPARE record
Record ID: TEST
268 GPACK
DM Tool – User Guide
The source and target new records are created in the separate file.
269 GPACK
DM Tool – User Guide
Mismatch records
Mismatch records
SOURCE.txt
TARGET.txt
DM.DATA.COMPARE record
Record ID: TEST
270 GPACK
DM Tool – User Guide
271 GPACK
DM Tool – User Guide
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.
272 GPACK
DM Tool – User Guide
273 GPACK
DM Tool – User Guide
274 GPACK
DM Tool – User Guide
275 GPACK
DM Tool – User Guide
276 GPACK
DM Tool – User Guide
Data File:
Output:
277 GPACK
DM Tool – User Guide
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).
278 GPACK
DM Tool – User Guide
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.
279 GPACK
DM Tool – User Guide
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.
280 GPACK
DM Tool – User Guide
281 GPACK
DM Tool – User Guide
Output
Thus any changes that are to be done in the data file can me made through this table.
282 GPACK
DM Tool – User Guide
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.
283 GPACK
DM Tool – User Guide
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:
284 GPACK
DM Tool – User Guide
xii. DM.AA.LENDING.SCHEDULE.EXTRACT
Execution:
OUTPUT File:
Sample Output:
285 GPACK
DM Tool – User Guide
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:
286 GPACK
DM Tool – User Guide
If the batch already exist in the environment then the below error will throw
287 GPACK
DM Tool – User Guide
288 GPACK
DM Tool – User Guide
During AA load. Suppose if the AA product is proofed and not published, error log is
created.
289 GPACK
DM Tool – User Guide
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.
290 GPACK
DM Tool – User Guide
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.
291 GPACK
DM Tool – User Guide
Selection Criteria
Output of the selection showing number of error, number of records validated and the
error details
292 GPACK
DM Tool – User Guide
293 GPACK
DM Tool – User Guide
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.
294 GPACK
DM Tool – User Guide
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
295 GPACK
DM Tool – User Guide
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.
296 GPACK
DM Tool – User Guide
Clean-up Process:
297 GPACK
DM Tool – User Guide
298 GPACK
DM Tool – User Guide
4. 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.
299 GPACK