GPAC DAMI Reference 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.

TEMENOS – Country Model Bank

GPAC_DAMI

DM Tool

User Guide

GPACK 2

DM Tool – User Guide

Table of Contents

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

Document History ...................................................................................................................... 4

Overview of this guide ............................................................................................................... 5

Assumptions .............................................................................................................................. 5

Document Support ................................................................................................................. 5

Abbreviations used in this Guide ........................................................................................... 5

T24 Modules Supported ............................................................................................................ 5

1. Introduction ......................................................................................................................... 6

2. Product Overview ............................................................................................................... 6

3. Workflow Diagram .............................................................................................................. 7

4. Template, Fields and Description ....................................................................................... 8

4.1. DM.INFORMATION ................................................................................................. 8

4.2. DM.DATA.TRANSLATION ...................................................................................... 8

4.3. DM.PREREQUISITE ............................................................................................. 10

4.4. DATA.MAPPING.VERIFICATION ......................................................................... 11

4.5. DM.MAPPING.DEFINITION .................................................................................. 12

4.6. DM.SERVICE.CONTROL ...................................................................................... 14

4.7. DM.SERVICE.SCHEDULER ................................................................................. 16

4.8. DM.AA.MAPPING .................................................................................................. 17

4.9. DM.DATA.COMPARE ........................................................................................... 17

4.10. DM.EXTRACTOR .................................................................................................. 18

4.11. DM.MAPPING.EXTRACT ...................................................................................... 21

4.12. DM.AA.EXTRACT ................................................................................................. 21

4.13. T24.SAB.INFO ....................................................................................................... 22

5. Process workflow: ............................................................................................................ 23

5.1. Menus .................................................................................................................... 24

5.1.1 Migration Pre-Requisite Check .......................................................................... 24

5.1.1.1 Check Migration Table Record Count ............................................................ 26

5.1.2 Client System to T24 Migration .......................................................................... 29

5.1.2.1 T24 Data Loading ........................................................................................... 29

5.1.2.2 Data Migration Load Preparation ................................................................... 30

5.1.2.3 Data Mapping Definition ................................................................................. 41

5.1.2.4 Automatic creation of Versions & DMD’s: ...................................................... 66

5.1.2.5 DM Service Control ........................................................................................ 70

5.1.2.6 Service Control ............................................................................................... 85

5.1.2.7 Application backup ......................................................................................... 87

5.1.2.8 AA.MAPPING ................................................................................................. 93

GPACK 3


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

5.1.3 T24 Recon Data Extract ..................................................................................... 99

5.1.3.1 DM.PREREQUISITE .................................................................................... 100

5.1.3.2 T24 Data Extract for Reconciliation .............................................................. 103

5.1.4 T24 to T24 Migration ........................................................................................ 170

5.1.5 Data & Object Audit ......................................................................................... 170

5.1.5.1 DATA AUDIT BUILD .................................................................................... 170

5.1.5.2 OBJECT AUDIT BUILD ................................................................................ 202

5.2. DM Tool Additional Features ............................................................................... 228

5.2.1. DM.REF.TABLE ............................................................................................... 228

5.2.2. DM.AA.CUSTOMER.PROXY .......................................................................... 229

5.2.3. T24.AA.INT.ACT.DEFAULT............................................................................. 231

5.2.4. DM.AA.CUSTOMER ........................................................................................ 233

5.2.5. T24.EB.EXT.ARR.ACT.DEFAULT ................................................................... 235

5.2.6. SC.PERF.DETAIL Load and SC.PERF.DETAIL.CONCAT updating .............. 238

5.2.7. Data Compare .................................................................................................. 245

5.2.8. DM Scheduler .................................................................................................. 254

5.2.9. DM.DATA.TARNSLATION............................................................................... 261

5.2.10. Handling BYTE Length in ORD .................................................................... 264

5.2.11. DM.AA.LENDING.BAL.EXTRACT ............................................................... 266

5.2.12. DM.AA.LENDING.SCHEDULE.EXTRACT .................................................. 267

5.2.13. DM.DC.BATCH.UPDATE ............................................................................. 268

5.2.14. Mnemonic duplication: .................................................................................. 269

5.2.15. AA - Product Proofing and Publishing .......................................................... 271

5.2.16. TDM.DATA.STRUCTURE.EXTRACT .......................................................... 272

5.2.17. ENQUIRY DM.ENQ.ISSUE.LOG ................................................................. 274

5.2.18. UTF8 conversion .......................................................................................... 274

5.2.19. DM.CLEANUP .............................................................................................. 277

6. Conclusions: ................................................................................................................... 281

GPACK 4


Document History

Author Version Date

Gpack 1.0 11th April 2013

Gpack 2.0 5th August 2013

Data Migration 3.0 13th September 2013

Comments:

DM Tool

GPACK 5


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_pack.requests <[email protected]>

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

GPACK 6


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.

GPACK 7


3. Workflow Diagram

GPACK 8


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.

3 MIG.TYPE

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

LIVE)

4 SELECT.LIST

This is an optional filed, where a valid &SAVEDLISTS& name

can be given.

5 MNEMONIC Specify the company Mnemonic

6.1 APPLICATION

This is a multivalue set where we should provide the Application

Names for which the count is to be done

7.1 LIVE.COUNT

This is an associated multivalue set where the number of

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.

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.


@ID The id of this application is free format text, 25 characters long

GPACK 9


1 APPLICATION The application for which the conversion carried out.

2 SOURCE.DIR The source directory of the data file consisting of Legacy ID is provided in this field

3 SOURCE.FNAME The Datafile name consisting of Legacy ID is given.

4

TARGET.DIR

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.

5 TARGET.FNAME The name of the converted data file with T24 Ids must be given here.

6 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.

7 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.

8 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.

9.1 MAPPING.TABLE

Any Concat file name that will be used for the conversion can be provided in this field. This is a multivalue field.

10.1.1 POS.CONVERT

The positions in the datafile where the conversion has to be done and replaced with T24 Ids. This is a sub value field associated with Mapping Table field.

11.1.1

POS.VALUE

The positions in the data file where the conversion values are defined .This is a sub value field associated field.

12.1.1 POS.ROUTINE

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 value field associated field.

13 NO.OF.SERVICE

The number of agents that will be required to run the conversion can be mentioned in this field. Default value is 16

Table 2 – DM.DATA.TRANSLATION

GPACK 10


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.


@ID

A 3 digit number followed by an asterisk (*), followed by a valid user name that must be present in the USER table

1 DESCRIPTION Free text Description.

2 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.

3 DMD.PREFIX

The prefix that will be used to identify the DM.MAPPING.DEFINITION for creation of the respective DM.SERVICE.CONTROL.

4

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.

5 SELECT.LIST This is an optional filed, where a valid &SAVEDLISTS& name can be given

6.1 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.

7.1 FILE.NAME

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 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.: CUSTOM.01.201203031653.txt

12 RECONCILIATION We need to specify if Reconciliation Folders are to be created or not. By default, the value “No” is defaulted.

13 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.

14.1 RECON.SPEC.NAME This is a multivalue field that is used to provide the Names of the folders that need to be created under

GPACK 11


the Directory specified in the field Recon Dir.

15.1 DM.EXTRACTOR.NAME

This is a multivalue field that contains DM Extractor Id. The value entered must exist in the DM.EXTRACTOR table

16 FILE.CONV.REQD File conversion will be done if this field is set to YES.

17 FILE.LOAD.TYPE This field specifies whether the file load is from Server or Local host

18 CONVERSION.TYPE Conversion type is specified here. Values entered 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.


@ID

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

1 DESCRIPTION Free text Description.

2 APPLICATION.NAME Name of the T24™ Table to which the Data is been loaded.

3 DMD.NAME DMD Name to be specified.

4

DIRECTORY.NAME The Directory name where the DMV status result will be stored.

5 MAPPING.STATUS

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 PASS.

GPACK 12


6 CORE.LIST

This is the name of the file where the core fields are given for comparison. This file is to be placed in DATA.IN.

7 LOCAL.LIST

This is the name of the file where the local fields if any are given for comparison. This file is to be placed in DATA.IN.

8.1 CORE.FIELDS

This is an associated Multivalued field which gets updated with the fields in the CORE.LIST i.e the Core fields upon verification.

9.1 CO.FIELD.STATUS

The Delimiter used to identify each multi-value field in the data. Value allowed only when IN.DATA.DEF is set to DELIM. This is an associated Multivalued field

10.1 LOCAL.FIELDS

This is a Multivalue field which gets updated with the fields in the LOCAL.LIST i.e the local fields upon verification

11 DATAFILE.NAME This field specifies the Data file name. The file has to be placed in DMV directory.

12 VERIFICATION.TYPE

This field becomes mandatory on providing value for the field DATAFILE.NAME.Values allowed is FIRST,POSITION,RANDOM.

13 FIRST.POSITION

This field becomes Mandatory on specifying POSITION in VERIFICATION.TYPE.This field specifies the position from where verification has to be done for the file.

14 LAST.POSITION

This field becomes Mandatory on specifying POSITION in VERIFICATION.TYPE.This field specifies the position till where verification has to be done for the file

15 DATAFILE.COUNT The number of records in datafile will be updated here.

16 ERROR.DESC If there is any error then the error message will be 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.


@ID


A meaningful ID, indicating the application name e.g. first six characters of the application name, CUSTOMER and the Load process, should be provided.

GPACK 13


R12.V.CUSTOM

R12.A.CUSTOM

R12.I.CUSTOM

1 GB. DESCRIPTION Free text Description to describe the Load.

2 APPLICATION.NAME Name of the T24™ Table to which the Data is been loaded.

3 LOAD.TYPE

Either ‘OFS’ or ‘WRITE’ or ‘READ.REPLACEMENT’ to specify if the load is via OFS module or jBASE Write function or the replacement of a few fields.

4

OFS.ACTION

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 LOAD.TYPE is set to OFS.

5 OFS.FUNCTION

The following FUNCTIONS are allowed to be specified to be used by the OFS to process the transaction. (I, R, A, D). “I” is taken as default.

6 FILE.TYPE

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 READ.REPLACEMENT.

7 OFS.VERSION

The T24™ Application’s Version to be used when loading through OFS. Value is allowed in this field only when LOAD.TYPE is set to OFS

8 IN.DATA.DEF To define the way in which the fields are read. Either DELIM or POSITION or OFS

9 FM.DELIM

The Delimiter used to identify each fields in the data. Value allowed only when IN.DATA.DEF is set to DELIM

10 VM.DELIM

The Delimiter used to identify each multi-value field in the data. Value allowed only when IN.DATA.DEF is set to DELIM

11 SM.DELIM

The Delimiter used to identify each sub-value fields in the data. Value allowed only when IN.DATA.DEF is set to DELIM

12 ESC.SEQ.FR

When a particular character in the incoming data needs to be converted, the character to be converted must be provided here.

13 ESC.SCR.TO

Works in conjunction with ESC.SEQ.FR, this is the character to which the ESC.SEQ.FR character will be converted.

14 ID.TYPE

Either ‘AUTO’ (which system takes care to generate the ID) ‘DATA’ (hardcoded ID in the coming file itself) ‘ROUTINE’ (A routine attached that forms the ID)

15 ID.ROUTINE The Routine that forms the ID for each record loaded. Value allowed only when ID.TYPE is set to ROUTINE

16 ID.POSITION The position in which the ID of each record can be found. Value allowed only when ID.TYPE is set to

GPACK 14


DATA

17 ID.LENGTH

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 file

18.1 APPL.FIELD.NAME

The field name in the T24™ table to which the data is updated. 65 characters long (Associated multi-value set till 22.1).

19.1 FIELD.POSITION

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 allowed only when IN.DATA.DEF is set to POSITION

20.1 FIELD.LENGTH

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 raw file

21.1 FIELD.ATTRIB

Either ‘ROUTINE’ – indicated the data will be formed from the routine for this field (or) ‘CONSTANT’ – a static value that will be updated for the field

22.1 FIELD.VALUE

The Static value that will be updated for the field. Value allowed only when FIELD.ATTRIB is set to CONSTANT

23 POST.UPDATE.RTN

The Post update routine , used a s a user exit routine that will be triggered for every record that is been loaded

24 OFS.SOURCE

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 3. DM.OFS.SRC.ORD 4. DM.OFS.SRC.VAL.ORD

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

GPACK 15



@ID Must be the same as DM.MAPPING.DEFINITION.

1 UPLOAD.COMPANY

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 incoming data.

2 FLAT.FILE.DIR

The directory where the flat file resides. This must be a valid directory name, e.g. DATA.BP. Actual path or relative path of the directory must be provided.

3 FLAT.FILE.NAME The flat file name of the incoming data. Must be an existing file name.

4 SERVER.NAME Specifies the name of the server, for multiple application servers

5 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.SERVICCE.CONTROL.

6 NO. OF SESSIONS No of threads that the TSA.SERVICE must spawn for processing this request.

7 MOVE.TO.HIST The field MOVE.TO.HIST is to move the error details from DSC to another template namely DM.SERVICE.CONTROL.HIST

10 RUN.STATUS

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 process.

11 DSC.TYPE Dsc type should be either DMD or DME

12 PRE.PROCESS

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 this type should be ‘SINGLE’.

15.1.1 CONTROL.LOG Contains the processing messages of the Service. Auto updated.

16.1 ERROR.DETAILS The errors that have been generated after the completion of the process will be captured in this field. Auto updated.

17.1 NO.OF.ERROR

The number of errors that have been recorded after the completion of the process will be captured in this field. Auto updated.

18.1 TYPE.OF.ERROR

The type of errors consolidated from all the errors generated after the completion of the process will be captured in this field. Auto updated.

19 ERROR.FILE.PATH If the error is generated, this field will indicate the path where the error long gets stored. Auto Updated.

20 ERROR.FILE.NAME If the error is generated, this field will indicate the file name of the error long gets stored. Auto Updated.

21 DATE The current date of the load process will be updated in this field. Auto updated.

22 STARTED The current start date/time of the load process will be updated in

GPACK 16


this field. Auto updated.

23 STOPPED The current end date/time of the load process will be updated in this field. Auto updated.

24 ELAPSED

The current elapsed date/time of the load process will be updated in this field. Auto updated.

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.


@ID

The ID for this application must be a user defined name for the SCHEDULER.

e.g.: R11.DSS.STATIC

1.1 DESCRIPTION The description of the SCHEDULER.

2 DSS.TYPE

To indicate whether the service needs to be run for DM.MAPPING.DEFINITION or DM.EXTRACTOR. It accepts values as DMD or DME

3 VERIFICATION.DSS

The DM.SERVICE.SCHEDULER table record which needs to be completed successfully in order for the current service to be started.

4 RUN.STATUS To indicate whether the service needs to be started or stopped. The two options available are START and STOP.

5.1 DM.SERVICE.ID To store the DM.SERVICE.CONTROL table record which needs to be started

6.1

VERIFICATION

To store the DM.SERVICE.CONTROL table record which needs to be completed successfully in order for the service, associated to the multivalued set, to be started

7.1 CURRENT.DIRECTORY To store the specified data file path for that services. This is an associated multi-value field.

8.1 DATA.FILE.NAME To specify the data file name for validate or load the data. This is an associated multi-value field.

9.1 NEW.DIRECTORY To specify the new data file path for that services. This is an associated multi-value field.

10.1 ERR.THRESHOLD To specify the maximum number of errors that will be tolerated before marking the service as failed.

11 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

12.1 SKIP.SERVICE To specify if the service needs to be run or can be skipped. The

GPACK 17


two options are YES and NO

13.1 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

14 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

15 STATUS.DETAIL No input field which will be updated with some details for information only

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

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.

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

defaulted automatically

1 DESCRIPTION The descriptions of report / interface

2 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.

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.

GPACK 18



@ID User defined Id.

1 DESCRIPTION The Description for the comparison

2 COMPARE.TYPE

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

compare.

3 ID.POSITION This field position of the Primary key (ID) in the file that is 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.

7 HEADER This field is to flag if both the source and target extract for file compare has Headers or not.

8 LEGACY.FILE.NAME This field is used for information only to store the Legacy Data Extract.

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.

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

12 TARGET.FILE.NAME The File Name of the recon extract from T24.

13 OUTPUT.FILE.PATH The Output file path where the reconciliation extract is available after the comparison.

14 OUTPUT.FILE.NAME The Output file name of the reconciliation extract after the comparison.

15 NO.OF.AGENTS The number of agents that will be required to run the comparison can be mentioned in this field.

16 APPLICATION.NAME The application name for the comparison.

17.1 FIELD.POSITION This field specifies the position of the field and applicable only 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.

GPACK 19



@ID


A meaningful ID, indicating the application name e.g., CUSTOMER should be provided.

CUSTOMER

MM.MONEY.MARKET

LIMIT

1 DESCRIPTION The descriptions of your report set / interface.

2 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.

3 MULTI.COMPANY

Whether the extraction is Multi Company or not.

4 FILE.TYPE Specifies the type of file which has to be extracted($NAU or $HIS or $ARC)

5

OFS.ACTION

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 extraction is performed.

6.1 SEL.DESC

The description of the selection criteria. This is a multivalue field.

7.1 SEL.FLD The Selection field from the application must be specified here. This is an associated multivalue field.

8.1 SEL.CRIT

The Selection criteria must be specified here. This is an associated multivalue field.

9.1 SEL.VALUE The Selection Value must be specified here. This is an associated multivalue field.

10.1 SEL.COMB

The Selection Combination must be specified here. This is an associated multivalue field.

11 SELECT.LIST

The save list name must be entered in this field.

12 TARGET.FILE The output filename for the Extraction.

13 OUTPUT.DIR The output directory where the extracted file will reside

14 FM.DELIM The Field Marker that will be used in the extract to separate the fields.

GPACK 20


15 VM.DELIM

The Value Marker that will be used in the extract to separate the Multi values.

16 SM.DELIM

The Sub value Marker that will be used in the extract to separate the Sub values.

17 LOCAL.CCY The Local Currency must be specified only if the extract is done for DATA.CAPTURE application.

18 DC.TOA.CATEGORY

The takeover account category must be specified based on which the internal account.

19 DC.DAO.START.ID The number from which the department code part in DATA.CAPTURE id must be started is specified.

20 FILE.HEADER

Whether the headers need to be provided for the extract or not.

21.1 FLD.LABEL

The field description for the field to be extracted.

22.1 FLD.APP

The application name must be specified from which the for concurrent extract of the value is done.

23.1 FLD.TYPE

The extract type for the field is specified here.

24.1.1 FLD.NAME The field name from the application which is to be extracted.

25.1 TRANS.CONDITION

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.

26.1 TRANS.VALUE

The value provided depends on the type mentioned in the field “Trans Condition”. This field becomes mandatory when “Trans Condition” is provided.

27.1 FLD.RTN A subroutine can be attached to this field that will be used for different extraction logic.

28.1.1 FLD.APP.FLD

The field name from the application mentioned in Fld App must be specified.

29 DATACAPTURE

Whether the extract is done for DATA.CAPTURE application or not.

30 TRANSACTION.CR

The credit transaction code must be specified. The value is provided only if the extract is done for DATA.CAPTURE.

GPACK 21


31 TRANSACTION.DR

The debit transaction code must be specified. The value is provided only if the extract is done for DATA.CAPTURE.

Table 10 – DM.EXTRACTOR

4.11. DM.MAPPING.EXTRACT


@ID Id to this should be valid DMD record id.

1 APPL.NAME

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 CORE.FLD.NAME The core field name of the application for which the extraction has to be done

3 SYS.PROG This field indicate what type of core validation check is used for that particular field

4 FMT This represent maximum number of alpha or alphanumeric or numeric characters allowed for that particular fields

5 SYS.FLD.NO This field represent the field number of that particular field

6 USR.FLD.NAME The local field name of the application for which the extraction has to be done

7 USR.SYS.PROG To indicate what type of core validation check is used for that particular field

8 USR.FLD.NO To indicate what type of core validation check is used for that particular field

9 USR.FMT

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

Table 11 – DM.MAPPING.EXTRACT

4.12. DM.AA.EXTRACT


@ID Id to this should be valid user name that must be present in the USER table.

1 DESCRIPTION The description about the extract is provided.

2 PRODUCT.LINE This field is used specify the product line for which the extract is to be taken. Only two options are valid either “Deposits” or

GPACK 22


“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.

6 OUTPUT.DIR To specify the output directory in which the extract will be placed.

7 EXTRACT.NAME The name in which the extracted file will be created in the 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

3 COMPANY.ID This field is used to specify the company ID of the environment

4 SOURCE.SL.ID

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 all applications

5 INFO.DATE This field will be automatically updated by the system after running the service with info build date

6 INFO.STATUS This field will be automatically updated by the system after running the service with status

7 DAB.SOURCE.DETAILS This is an no inputtable field

8 SOURCE.DATE This field will be automatically updated by the system after running the service with info build date

9 SOURCE.STATUS This field will be automatically updated by the system after running 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 This field will be automatically updated by the system after running the service with date

13 TARGET.STATUS This field will be automatically updated by the system after running the service with status

14 DAB.COMPARE.DETAIL This is an no inputtable field

15 REVERSE.COMPARE If the reverse comparison needs to be done then this is set to Y (i.e, From Target to Source as well)

16 COMPARE.DATE This field will be automatically updated by the system after running the service with date

GPACK 23


17 COMPARE.STATUS This field will be automatically updated by the system after running the service with status

18 OAB.SOURCE.DETAILS This is an no inputtable field

19 OAB.SOURCE.SL.ID This field is to specify the savedlist ID with BP (Directory) names to create the build

20 OAB.SOURCE.DATE This field will be automatically updated by the system after running the service with info build date

21 OAB.SOURCE.STATUS This field will be automatically updated by the system after running the service with status

22 OAB.TARGET.DETAILS This is an no inputtable field

23 OAB.TARGET.SL.ID This field is to specify the savedlist ID with BP (Directory) names to create the build

24 OAB.TARGET.DATE This field will be automatically updated by the system after running the service with info build date

25 OAB.TARGET.STATUS This field will be automatically updated by the system after running the service with status

26 OAB.COMPARE.DETAILS This is an no inputtable field

27 OAB.COMPARE.DATE This field will be automatically updated by the system after running the service with date

28 OAB.COMPARE.STATUS This field will be automatically updated by the system after running 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.

GPACK 24


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

5.1.1 Migration Pre-Requisite Check

This menu contains applications for making the pre-requisite checks.


GPACK 25


System Dates

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

GPACK 26


ENQUIRY DM.TOOL.DETAILS

Purpose

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.

GPACK 27


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.

GPACK 28


As mentioned, the LIVE file DATA.MIG.COUNT will be updated as shown below.

Multiple counts will also be captured in the LIVE file.

GPACK 29


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.


GPACK 30


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.

GPACK 31


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).

After selecting the correct ID you will get a screen as below.

GPACK 32


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.

Dmd Prefix: The prefix that will be used to identify the DM.MAPPING.DEFINITION for creation of the respective DM.SERVICE.CONTROL.

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.

GPACK 33


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.: CUSTOM.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 VALIDATE01, VALIDATE 02, VALIDATE 03, INPUT01, AUTHORISE01 and 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.

GPACK 34


After committing the record we need to verify the record. We type the record name to be


GPACK 35



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

GPACK 36


The DSCs are also created for DMD.

Data Mapping Layout

Table

DATA.MAPPING.VERIFICATION

Purpose

The menu is used to do the initial setup for the verification of the Data Mapping Sheet and the

DM.MAPPING.DEFINITION

.




The ID for this application can be upto 65 characters


GPACK 37




After the transaction is processed we get the following screen

GPACK 38


The result file will be created as below.

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,

FIRST

POSITION

RANDOM

GPACK 39


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.

GPACK 40


The result will be stored in the DMV folder as below

The status of the validated datafile will be populated in the file as below

GPACK 41


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.

5.1.2.3 Data Mapping Definition

Table

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.


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

GPACK 42


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,

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.

GPACK 43


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.

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.

GPACK 44


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

“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, 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 provided.

In cases where the field validation needs to be triggered for incoming OFS message

then the DM.OFS.SRC.VAL option need to be used and if OFS.REQUEST.DETAIL

GPACK 45


has to be updated then the DM.OFS.SRC.VAL.ORD option need to be used .

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:

GPACK 46


DMD Record:

USER.ABBREVIATION record before read replacement:

USER.ABBREVIATION record after read replacement:

GPACK 47


GPACK 48


Loading of $ARC using the DMD record:

DMD Record:

GPACK 49


GPACK 50


GPACK 51


GPACK 52


GPACK 53


GPACK 54


GPACK 55


Before authorization of DMD:

After authorization of DMD:

GPACK 56


The below screenshot shows the $ARC file of the FUNDS.TRANSFER record

GPACK 57


GPACK 58


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.

GPACK 59


Other Field values mapped as per the Data Mapping Sheet.

GPACK 60


Data File

Data File Count: 30 records

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.

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

Start the TSM

Group 1

Group 2

GPACK 61


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:

GPACK 62


The other groups will be created similarly.

The OFS.REQUEST.DETAIL (ORD) lists all the records in the data file, as processed.

Processed OFS.REQUEST.DETAIL

GPACK 63


Uploaded Records:

Global Limit: 600000001.0010000.01

GPACK 64


Product Limit: 600000001.0001000.01

GPACK 65


Sub Product Limit: 600000001.0001010.01

GPACK 66


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

Prefix of DMD 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

GPACK 67


VERSION > DM.MAPPING.DEFINITION,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.

Creation of Versions and DMD’s for the given application

GPACK 68


Note: All Versions are single level authorization

Below is the few pages of sample screenshot of the automatically created DMD for the

CUSTOMER application

GPACK 69


GPACK 70


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.

GPACK 71



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 – A multi threaded job which reads the DM.SERVICE.DATA.FILE and updates

the job list. Each record is then processed using OFS.GLOBUS.MANAGER and the error

output is logged into <<DM.MAPPING.DEFINITION name>>.LOG.<<Session Number>>

DM.SERVICE.POST.PROCESS - A single threaded process which consolidated all the LOG

files into 1 single error output file. <<DM.MAPPING.DEFINITION name>>ERROR.txt

GPACK 72


TSA.WORKLOAD.PROFILE record

The number of sessions in the DM.SERVICE.CONTROL record is updated as number of

agents in this record

TSA.SERVICE record

GPACK 73


A TSA.SERVICE record with the following contents is created.

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:

Run the service.

Output:

GPACK 74


Marking the service Stop

GPACK 75


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

GPACK 76


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.

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

GPACK 77


The DM.SERVICE.CONTROL must be verified

On verifying DM.SERVICE.CONTROL the respective service will get started

GPACK 78


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.

GPACK 79



On verifying DM.SERVICE.CONTROL the respective service will get started

GPACK 80


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.

GPACK 81


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.

GPACK 82



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..

GPACK 83


GPACK 84


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.

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.

GPACK 85


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

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.


GPACK 86


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.

Enter the desired time to get refresh the display

GPACK 87


The result will be as below and the query will refresh every 5 seconds.

5.1.2.7 Application backup

GPACK 88


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>>

GPACK 89


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.

DM.APP.BACKUP – verify (T24 Application)

After doing the initial setup of parameters, DM.APP.BACKUP is verified. On verification 3

tables are updated.

GPACK 90


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


GPACK 91


3. BATCH is updated/created with Id as


.


GPACK 92


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 :

GPACK 93


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.

GPACK 94


Input a record

Verify the record in DM.AA.MAPPING

GPACK 95


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.

GPACK 96



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:

CREATION OF BATCH FOR SINGLE

The below screenshot depicts the BATCH for SINLGLE Pre Process

GPACK 97


CREATION OF BATCH FOR MULTI

The below screenshot depicts the BATCH for MULTI Pre Process

GPACK 98


GPACK 99


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


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.

GPACK 100


5.1.3.1 DM.PREREQUISITE


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).


GPACK 101




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.

Dmd Prefix: The prefix that will be used to identify the DM.MAPPING.DEFINITION f or

creation of the respective DM.SERVICE.CONTROL.

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 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.: CUSTOM.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.

GPACK 102


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.



GPACK 103


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

GPACK 104


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.

FM Delim: The Field Marker that will be used in the extract to separate the fields.

GPACK 105


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

GPACK 106


TSA.SERVICE

BATCH

GPACK 107


Running the Service

After authorization, the service is started manually.

GPACK 108


Start the TSM.

Check the services, if started.

Start the services.

GPACK 109


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.

GPACK 110


GPACK 111


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.

GPACK 112


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.

GPACK 113


Extracted File with Headers:-

GPACK 114


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:-

GPACK 115


GPACK 116


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

MULTI COMPANY SET TO YES

GPACK 117


OUTPUT:

GPACK 118


GPACK 119


Sub/Multi value for Core/Local. Fields can be extracted

It is possible to extract Core and local fields via DME.

GPACK 120


GPACK 121


GPACK 122


The specific conversions can be extracted using no routines

Any specific conversion that is required for extraction can also be done.

GPACK 123


GPACK 124


Extracted Sample of Records:-

DME Record with Arithmetic Operation

GPACK 125


GPACK 126


Extracted Sample of Records: -

DME Record for Absolute value testing.

GPACK 127


GPACK 128


DME Record with the usage of Substitute:-

GPACK 129


GPACK 130


DME can be used to convert co.code if needed .

GPACK 131


GPACK 132


It is also possible to extract data based on position..

GPACK 133


GPACK 134


The trail balance for foreign currency can be extracted.

Trail balance for the GL in foreign currency can be extracted through DME.

GPACK 135


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.

GPACK 136


The result will be stored in RECON.OUT folder in the bnk.run path:

Sample Output :

GPACK 137


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.

GPACK 138


Create a record in the DM.EXTRACTOR

GPACK 139


GPACK 140


Start the service DM.EXTRACTOR-LOANS.TEST

After running the service, target file has been created in the output directory

GPACK 141


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]

The field values are provided as given in the below screen shot to extract from more than one application using the trim condition.

GPACK 142



GPACK 143


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]

The field values are provided as given in the below screen shot to extract from more than one application using the replace condition.

GPACK 144



GPACK 145


Extracted file

GPACK 146


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

GPACK 147


EXTRACTED DATA:

GPACK 148


Arithmetic Operation

The following operations can be performed.

+, - , * , /

DM.EXTRACTOR Record

GPACK 149


EXTRACTED DATA:

GPACK 150


Absolute value

Absolute value can be extracted. FLD.NAME should be set to A DMFLD.ONLINE.BALANCE.

DM.EXTRACTOR Record

GPACK 151


EXTRACTED DATA:

GPACK 152


Substitute

DM.EXTRACTOR Record

GPACK 153


EXTRACTED DATA:

GPACK 154


Convert

This will replace every occurrence of the character X with Y.

DM.EXTRACTOR Record:

GPACK 155


EXTRACTED DATA:

GPACK 156


Extract

The values in the record is Extracted from position N1 to N2.


GPACK 157


EXTRACTED DATA:

GPACK 158


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.

GPACK 159


GPACK 160


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

GPACK 161


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’

GPACK 162


After starting the services the DME records the LD contract with future repayment will be extracted.

GPACK 163


Extracted file:

GPACK 164


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.

GPACK 165


After starting the services the DME records the LD contract with future repayment will be extracted.

GPACK 166


Extracted file:

Service Control

GPACK 167


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.

GPACK 168


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

GPACK 169


The result will be as below and the query will refresh every 5 seconds.

GPACK 170


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

GPACK 171


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.

GPACK 172


Browser View:

GPACK 173


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

GPACK 174


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

GPACK 175


Browser View to start/stop the Service:

GPACK 176


Putty View to start/stop the Service:

STEP4: Start the TSM service

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

GPACK 177


STEP6: List the T24.DAB.INFO

To view the template give the command “T24.DAB.INFO L” as shown in the below screen shot

GPACK 178


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.

GPACK 179


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

GPACK 180


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

GPACK 181


STEP3: Start the TSM service

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

GPACK 182


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)

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.

GPACK 183


STEP 6: Pack all the records in source environment

Then pack all the records from T24.DAB.INFO and release in the target environment.

GPACK 184


GPACK 185


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

GPACK 186


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

GPACK 187


Step 5: Start the T24.DAB.TARGET.BUILD service

Browser View:

Putty View:

GPACK 188



Start the service “T24.DAB.TARGET.BUILD” to create target dump

STEP 7: Check the TARGET.STATUS


LIST F.T24.SAB.INFO WITH @ID EQ ‘SYSTEM’ TARGET.STATUS


GPACK 189


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,

GPACK 190


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.

GPACK 191


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)

GPACK 192


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.

GPACK 193


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

GPACK 194


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

STEP 5: Check the COMPARE.STATUS


LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' COMPARE.STATUS

GPACK 195


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

GPACK 196


The dump will be saved in the RESULT path with the ID as T24.DAB.RESULT.BUILD Current System Date & Time)

GPACK 197


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

GPACK 198


T24.DAB.SOURCE.BASE- The new records in the source environment will be captured in this file

GPACK 199


GPACK 200


T24.DAB.TARGET.BASE - The new records in the target environment will be captured in this file

GPACK 201


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

GPACK 202


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

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.

GPACK 203


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

Procedure for BASE creation

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.

GPACK 204


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:

GPACK 205


Putty View:

GPACK 206


Step 4: Start the TSM

GPACK 207


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:

GPACK 208


Putty View:

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

GPACK 209


Step 7: Check the OAB.SOURCE.STATUS


LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' OAB.SOURCE.STATUS

Check the T24.SAB.INFO application after completing T24.OAB.SOURCE.BUILD

GPACK 210


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:

1.The source base file will be saved in the below directory.

../ 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.

GPACK 211


GPACK 212


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

GPACK 213


Procedure for BASE creation

Step 2: Clear files





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

GPACK 214



GPACK 215


Step 5: Start the T24.OAB.TARGET.BUILD service

Browser View:

GPACK 216


Putty View:

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


GPACK 217


Step 7: Check the OAB.TARGET.STATUS


LIST F.T24.SAB.INFO WITH @ID EQ 'SYSTEM' OAB.TARGET.STATUS


GPACK 218


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

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.

Comparison between Source base and Target base

Steps to be done for comparison between Source dump and Target dump

GPACK 219


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

GPACK 220



GPACK 221


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

GPACK 222


Putty View:

Start the service “T24.OAB.COMPARE.BUILD” to compare the routines


GPACK 223


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

GPACK 224


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

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)

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

GPACK 225


<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.

>

GPACK 226


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

GPACK 227


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.

GPACK 228


5.2. DM Tool Additional Features

5.2.1. 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).

GPACK 229


5.2.2. 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.

GPACK 230


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.

GPACK 231


5.2.3. 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.

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.

GPACK 232


While inputting or Loading the data via this version the specified fields will be defaulted

from the concat table DM.AA.CUSTOMER.PROXY.

GPACK 233


5.2.4. 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

GPACK 234


‘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.

GPACK 235


5.2.5. 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.

GPACK 236


Create the EB.API entry for the T24.EB.EXT.ARR.ACT.DEFAULT.

GPACK 237


While inputting or Loading the data via this version the arrangement id will be defaulted from

the concat table DM.AA.CUSTOMER.

GPACK 238


5.2.6. 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

GPACK 239


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:

GPACK 240


GPACK 241


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:

GPACK 242


GPACK 243


Before Processing the DM.SC.PERF.CONCAT.UPDATE

GPACK 244


Listing SC.PERF.DETAIL.CONCAT as shown below:

GPACK 245


5.2.7. 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.

GPACK 246


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

GPACK 247


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

GPACK 248


DM.DATA.COMPARE record

Record ID: TEST

Verify the DM.COMPARE record

Start the service

GPACK 249


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.

GPACK 250


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


Record ID: TEST


GPACK 251


Start the service

The source and target new records are created in the separate file.

Source New Records

Target new Records

GPACK 252


Mismatch records

Mismatch records

DM.DATA.COMPARE writes the comparison errors in a file.

In the below source file, the first two string ids are ending with 004,005. But the target file, the first string is in the second position.

SOURCE.txt

TARGET.txt


Record ID: TEST

GPACK 253



Start the service

GPACK 254


The Error log is created.

After updating the error log file, the source and target concat file are clear by the routine.

5.2.8. 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.

GPACK 255


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.

GPACK 256



Input a Record in DM.DATA.SCHEULER.

GPACK 257


Verify the Record.

On verifying the record, we get as below .

On Verifying the DSS, the RUN status becomes Start

GPACK 258


GPACK 259


Data File:

Output:

GPACK 260


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).

GPACK 261


5.2.9. 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 consisting of Legacy ID is given.

GPACK 262


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.

GPACK 263


Verify the record as shown below.

Data file in which the translation has to be done:

GPACK 264


Output

Thus any changes that are to be done in the data file can me made through this table.

5.2.10. 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

GPACK 265


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.

GPACK 266


5.2.11. 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:

GPACK 267


5.2.12. DM.AA.LENDING.SCHEDULE.EXTRACT

It is possible to extract the Schedules for Reconciliation Purpose

Execution:

OUTPUT File:

Sample Output:

GPACK 268


5.2.13. 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,

GPACK 269


If the batch already exist in the environment then the below error will throw

5.2.14. 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

GPACK 270


Error log is created in the respective path for Mnemonic Duplication.

Error Detail is displayed in the below mentioned screenshot.

GPACK 271


5.2.15. 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.

GPACK 272


After running the service, if in the data file the product used is

SMALL.BUSINESS.LOAN then error log is created as shown below.

5.2.16. 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.

GPACK 273


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

GPACK 274


5.2.17. 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

5.2.18. UTF8 conversion

The UTF8 conversion of data file for swift character handling has to be incorporated in generic DM Tool.

GPACK 275


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

GPACK 276


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.

GPACK 277


After converting the data file.

5.2.19. 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

GPACK 278


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

GPACK 279


Clean-up Process:

GPACK 280


GPACK 281


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.

Documents

GPAC DAMI Reference Guide