2.T24DirectoryStructureAndImportatntFilesInGlobus

(1)

Important Files In T24

(2)

“Warning: This document [Banking Introduction – Courseware] is protected by copyright law and international treaties.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any

purpose, without the express written permission of TEMENOS Holdings NV

Unauthorized reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal penalties,

and will be prosecuted to the maximum extent possible under applicable law.”

Information in this document is subject to change without notice.

Dat

DateOeOf f IssIssue ue VerVersiosion n ChChanganges es ByBy 2001

2001 1.0 1.0 Initial Initial AlagammaiAlagammai

Palaniappan Palaniappan 2002 2002 1.1 1.1 jBASEjBASE Changes Changes Alagammai Alagammai Palaniappan Palaniappan 2002 2002 1.2 1.2 InfobasicInfobasic Program Program ming ming changes changes Alagammai Alagammai Palaniappan Palaniappan July July 2004 2004 1.3 1.3 G14G14 changes changes Alagammai Alagammai Palaniappan Palaniappan

(3)

Table of Content

Table

Table of of ConteContentnt...33

T24

T24 DirectoDirectory ry StructuStructure...re...44

Direct

Directories That ories That Get Installed When T24 Get Installed When T24 Is Is InstallInstalleded...44

bnk.d bnk.data...ata...44 bnk.d bnk.dictict...44 bnk.h bnk.help...elp...44 bnk.jn bnk.jnll...44 bnk.ru bnk.runn...55 bnk.b bnk.backuackupp...55 GLOBUS GLOBUS.BP...BP...55 File

File Types Types In In T24T24...55

Live

Live file...file...55

The

The UnauthUnauthorizeorized d File...File...55

The

The History History FileFile...55

File

File ClassiClassificatification...on...66

File

File ClassClassificatioification...n...66

File

File PrefixePrefixes...s...77

Core

Core ParamParameter eter Files Files In In T24...T24...88

PGM.FIL

PGM.FILEE...88

FILE.CON

FILE.CONTROL...TROL...1010

STANDARD

STANDARD.SELECT.SELECTIONION...1111

DATES DATES...1313 HOLIDAY HOLIDAY...1414 COMPANY... COMPANY...1616 SPF SPF...1919

(4)

T24 Directory Structure

Each T24 account is completely self-contained and stand-alone. That

Each T24 account is completely self-contained and stand-alone. That is, it is, it contains files and programscontains files and programs

catalogued locally to run T24. As such, the account is transportable from one machine to another,

provided jBASE has been installed on both machines. However, if different hardware is used, object

code produced as a result of compiling programs on that specific hardware need to be used. The

structures and information given below refer to a T24 account. All T24 accounts will have the same

configuration as detailed below:

Directories That Get Installed When T24 Is

Installed

When T24 is installed a number of directories get installed. Some of them are very crucial for the

efficient working of T24. They are

bnk.data

We could call this the T24 database, as this is the directory where the data files of all applications in

T24 are stored.

bnk.dict

As the name implies, it is the directory that contains the dictionary files of all applications in T24.

bnk.help

As the name implies, it contain all the help files relating to T24.

bnk.jnl

This directory is the transaction journal of T24. It contains a very important file in T24 called

F.JOURNAL. F.JOURNAL is the file that will hold the mirror of every transaction in T24. The life of this

journal file is “one day”. You will learn more about journaling etc in the End Of Day session

journal file is “one day”. You will learn more about journaling etc in the End Of Day session..

bnk

bnk.run bnk.backup

bnk.run bnk.databnk.data bnk.dictbnk.dict bnk.helpbnk.help bnk.jnlbnk.jnl bnk.backup

ac ac fx fx eb eb lobusbin lobusbin lobuslib lobuslib bin bin lib lib GLOBUS.BP GLOBUS.BP

(5)

bnk.run

This is the login account for T24 users of BNK, in simple terms it is the home directory of all users who

log on to T24. It is in this directory that the .profile file of the user will be situated. Apart from other

directories, it contains 4 very important directories namely

•

• globusbin globusbin (Contains (Contains t24 t24 executables)executables)

•

• globuslib globuslib (Contains (Contains T24 T24 library library files)files)

•

• bin bin (Usually (Usually used used to to store store non non T24(local) T24(local) executables)executables)

•

• lib lib (Usually (Usually used used to to store store non non T24(local) T24(local) libraries)libraries)

bnk.backup

This directory contains the files pertaining to the pre end of day and the post end of day backups.

(This is applicable when using T24 release lesser then G14).

GLOBUS.BP

It is the directory that contains a number of insert files that are used in programs/subroutines. Please

refer to ‘Programming In Infobasic’ for detailed information.

File Types In T24

Each application serves one main file. The main file is the live file or authorized file. In addition there

can be two other related files:

Live file

This has no suffix and holds the current authorized record.

The Unauthorized File

This is suffixed with $NAU and holds the record as input or changed before it has been authorized.

Records with record statuses

a.

a. INAU : INAU : Input Input not not authorisedauthorised

b. INAO

b. INAO : : Input Input not not authorised authorised overrideoverride

c.

c. INA2 INA2 : : Input Input not not authorised authorised by by authoriser authoriser 22

d.

d. RNAU RNAU : : Reversal Reversal not not authorisedauthorised

e.

e. RNA2 RNA2 : : Reversal Reversal not not authorised authorised by by authoriser authoriser 22

f.

f. CNAU CNAU : : Copied Copied record record not not authorisedauthorised

g.

g. CNA2 CNA2 : : Copied Copied record record not not authorised authorised by by authoriser authoriser 22

h. RNAO

h. RNAO : : Reversal Reversal not not authorised authorised overrideoverride

i. IHLD :

i. IHLD : Input Input on on holdhold

are stored here.

The History File

This is suffixed by $HIS and contains images of the record prior to each change. The user

inputs/amends data in the unauthorized file. Another user must then view the data and authorize it at

(6)

which point it is moved from the unauthorized file into the live file. The existing record in the live file is

moved to the history file.

Example 1 Example 1

Application Name

Application Name : : CustomerCustomer

Live

Live File File Name Name : : CUSTOMERCUSTOMER

Unauthorized

Unauthorized File File Name Name : : CUSTOMER$NAUCUSTOMER$NAU

History

History File File Name Name : : CUSTOMER$HISCUSTOMER$HIS

File Classification

Assume a scenario where T24 is to be imple

Assume a scenario where T24 is to be implemented in a bank which has the following structuremented in a bank which has the following structure

When T24 is implemented in a bank with the above structure,

When T24 is implemented in a bank with the above structure, there would be a number of files that there would be a number of files that areare

common to all the branches and the head office. These files usually would usually be basic parameter

tables that are set up during the implementation phase. These types of files that are common to the

entire bank are stored only at the Head Office and all the braches are allowed to access them. These

types of files are called INT files.

INT

INTInstallationInstallation This group covers files like SECTOR, PGM.FILE, FILE.CONTROL etcThis group covers files like SECTOR, PGM.FILE, FILE.CONTROL etc

where only version of the file will exist regardless of the number of

companies. These files will be stored at the Head Office and will be

accessed by all the branches.

CUS

CUSCustomerCustomer This group covers files like CUSTOMER. Usually these files exist inThis group covers files like CUSTOMER. Usually these files exist in

the HO and will have the bank mnemonic as the prefix. They are

shared among all the branches. Alternatively, these files can be

stored at each of the branches as well. If maintained at each of the

braches, they cannot be shared. These files primarily contain static

information.

T24 contains a number of files that contain financial information. These files are stored at each of the

braches, but are not shared by the rest of the bank as they contain financial data. These types of files

are called FIN files.

FIN

FINFinancialFinancial This group covers files like ACCOUNT, LD.LOANS.AND.DEPOSITSThis group covers files like ACCOUNT, LD.LOANS.AND.DEPOSITS

etc where each of the branches contain a copy of the file but do not

share with the rest of the bank.

CST

CSTCustomer TablesCustomer Tables This This covers covers files files like like SECTOR, SECTOR, TRAGET, TRAGET, INDUSTRY. INDUSTRY. These These types types ofof

files are usually used as check files for customer level

files are usually used as check files for customer level files. Theyfiles. They

have the same properties of CUS file.

Head Office

B

(7)

FTD

Financial Table Descriptive

Financial Table Descriptive This group covers files like BASIC.INTEREST, GROUP.CONDITIONThis group covers files like BASIC.INTEREST, GROUP.CONDITION

etc. These types of files are usually used as check files f

etc. These types of files are usually used as check files for financialor financial

level files. The files

level files. The files in this group contain non-financial data. Theyin this group contain non-financial data. They

have the same properties as FIN files.

FTF

Financial Table Financial

Financial Table Financial This group covers files like GROUP.DEBIT.INT, TXN etc. These filesThis group covers files like GROUP.DEBIT.INT, TXN etc. These files

are linked to financial level files

are linked to financial level files and also contain financial level data.and also contain financial level data.

They have the same properties like FIN files.

CCY

CCYCurrencyCurrency This group covers files like CURRENCY, RANK.CURRENCY,This group covers files like CURRENCY, RANK.CURRENCY,

FORWARD.RATES. These files are currency-associated files. They

have the same properties as of INT files.

NOS

NOSNostroNostro This group covers files like NOSTRO.ACCOUNT, AGENCY etc.This group covers files like NOSTRO.ACCOUNT, AGENCY etc.

These files are for files that are held for Nostro accounts. They have

the same properties as of CUS files.

File Prefixes

Every single file in T24 has a mandatory prefix ‘F.’ Hence the files that we just discussed, like,

PGM.FILE, FILE.CONTROL, CUSTOMER, ACCOUNT etc will all have prefix as ‘F.’ Let us understand

this with an example.

Since CUSTOMER is a CUS type of file each branch and the Head Office will have a copy of the

CUSTOMER file with that branch’s customer records and all of them will be called F.CUSTOMER.

Imagine a situation where a customer of Branch 1 walks into Branch 2 and wants to perform some

transaction. Now the user needs to obtain the customer information form the CUSTOMER file in

Branch 1. If he issues an instruction to read the F.CUSTOMER file, this will only result in the

F.CUSTOMER file in Branch 2 being read. How does the user instruct the system to read

F.CUSTOMER file in Branch 1? This will not be possible if the CUSTOMER files stored in various

branches have the same name. In order to solve this, in T24, for all CUS files, apart from the

mandatory prefix, the files have the branch’s mnemonic (A branch’s mnemonic can be obtained from

the COMPANY file which is

the COMPANY file which is discussed later in this section) as a prefix.discussed later in this section) as a prefix.

CUSTOMER file in Head Office

CUSTOMER file in Head Office : FBNK.CUSTOMER (BNK is the mnemonic of th: FBNK.CUSTOMER (BNK is the mnemonic of the Head Office)e Head Office)

CUSTOMER

CUSTOMER file file in in Branch Branch 1 1 : : FBR1.CUSTOMER FBR1.CUSTOMER (BR1 (BR1 is is the the mnemonic mnemonic of of Brach Brach 1)1)

CUSTOMER

Now, when a customer of Branch 1 walks into Branch 2, the user can instruct the system to read the

FBR1.CUSTOMER.

The same rule of prefixes will hold good for FIN files as well as they are also stored at each of the

braches.

ACCOUNT file in Head Office

ACCOUNT file in Head Office : FBNK.ACCOUNT(BNK is the mnemonic of the Head Office): FBNK.ACCOUNT(BNK is the mnemonic of the Head Office)

ACCOUNT file in Branch 1

ACCOUNT file in Branch 1 : FBR1.ACCOUNT (BR1 is the mnemonic of Brach 1): FBR1.ACCOUNT (BR1 is the mnemonic of Brach 1)

ACCOUNT file in Branch 2 : FBR2.ACCOUNT (BR1 is the mnemonic of Brach 2): FBR2.ACCOUNT (BR1 is the mnemonic of Brach 2)

(8)

For INT files, since only once copy of

For INT files, since only once copy of the files exists, the above rule doesn’t apply for them.the files exists, the above rule doesn’t apply for them.

PGM.FILE

PGM.FILE file file in in Head Head Office Office : : F.PGM.FILEF.PGM.FILE

PGM.FILE

PGM.FILE file file in in Branch Branch 1 1 : : F.PGM.FILEF.PGM.FILE

PGM.FILE

Core Parameter Files In T24

T24 is made up of number of files. Before we proceed to learn how to program in T24 it is vital for us

to know about some of the files and tables that

to know about some of the files and tables that constitute an important part in T24.constitute an important part in T24.

PGM.FILE

PGM.FILE stands for ‘Program File’. As the name denotes, this is the application that keeps track of

all applications (programs) in T24. For an application to be executed within the T24 environment

(command line), a valid entry should exist in PGM.FILE.

(command line), a valid entry should exist in PGM.FILE. PGM.FILE is also checked to obtain thePGM.FILE is also checked to obtain the

characteristics of the application.

ID

ID : Application/Program/Batch Routine Name. (No special characters allowed other than ‘.’) : Application/Program/Batch Routine Name. (No special characters allowed other than ‘.’)

Field Description

TYPE

TYPE Denotes Denotes the the type type of of application/program application/program that that is is beingbeing

defined.(Possible values listed below)

GB

GB SCREEN SCREEN TITLE TITLE Identifies Identifies the the program program title title that that will will be be displayed displayed as as aa

header when the corresponding application (ID) is

invoked in the action line.

ADDITIONAL.INFO

ADDITIONAL.INFO Holds Holds the the special special characteristics characteristics of of thethe

application/program being defined. (Some of the

possible values listed below)

BATCH.JOB

BATCH.JOB Identifies Identifies batch batch jobs jobs when when the the program program has has beenbeen

defined with the type as ‘B’. For more information on

this refer to the training document ‘Advanced

Technical Training’

PRODUCT

PRODUCT Identifies Identifies the the product product to to which which the the application application oror

program belongs. Contains valid product names.

These products are subdirectories under the ‘.data’

directory. (Some of the possible values are listed

below)

SUB.PRODUCT NA

DESCRIPTION

DESCRIPTION Holds Holds the the description description of of the the application/program application/program beingbeing

defined

APPL.FOR.SUBR

APPL.FOR.SUBR Used Used when when defining defining version version routines. routines. Used Used forfor

administrative purposes. For more information on this

refer training document ‘Advanced Technical Training’

and ‘Advanc

and ‘Advanced Technical ed Technical Training - Training - Plus’Plus’

BATCH.LIST.MAXIMUM

BATCH.LIST.MAXIMUM Holds Holds the the maximum maximum number number of of ids ids that that can can be be storedstored

in a LIST file. This is used when defining batch

programs. For more information on this refer training

document ‘Advanced Technical Training’ or ‘T24 Non

Stop’.

(9)

MT.KEY.COMPONENT

MT.KEY.COMPONENT Used Used for for Multi Multi BookBook

MT.KEY.FILE

MT.KEY.FILE Used Used for for Multi Multi BookBook

•

• TYPETYPE

H

H A A program program that that has has this this type type maintains maintains three three files files the the unauthorised, unauthorised, live live and and historyhistory

files.

files. The unauthorised file The unauthorised file is updated at Inpuis updated at Input; the live file at authorisation; at; the live file at authorisation; and thend the

history file whe

history file whenever never there is there is an authoan authorised change rised change to a to a record.record.

E.g. CUSTOMER

U

U A A program program similar similar to to type type 'H' 'H' except except that that history history is is not not maintained.maintained.

e.g. ABBREVIATION

L

L A A program program that that displays displays the the data data of of a a live live file file but but does does not not allow allow updates. updates. Updates Updates toto

these files would be controlled by the System automatically.

e.g. STMT.ENTRY

T

T A A program program that that displays displays data data in in a a table table file file (such (such as as a a list list of of keys) keys) but but does does not not allowallow

update.

e.g. LMM.CUSTOMER

W

W A A program program that that permits permits updates updates to to a a work work or or temporary temporary file. file. A A typical typical example example wouldwould

be the REPGEN.OUTPUT program where print or display parameters for a

be the REPGEN.OUTPUT program where print or display parameters for a report canreport can

be loaded.

B

B A A Batch Batch job job that that can can only only be be accessed accessed during during the the 'off-line' 'off-line' processing processing inin

BATCH.CONTROL.

M

M Main-line Main-line program program that that can can be be run run from from the the action action line line but but has has no no file file directlydirectly

associated with it.

S

S Subroutine. Subroutine. A A program program used used in in the the T24 T24 system system but but one one that that is is executedexecuted

Automatically whenever required.

Automatically whenever required. It cannot be entered by the user either aIt cannot be entered by the user either at thet the

action line or from w

action line or from within the Batch Control system. ithin the Batch Control system. It is recommended thaIt is recommended thatt

these are loaded only when they

these are loaded only when they are needed by the report are needed by the report generatorgenerator

e.g. IN2... routines.

ADDITIONAL INFO ADDITIONAL INFO

".NOH"

".NOH" (no hold (no hold facility after 1facility after 1st input)st input)

".GUI"

".GUI" (application ca(application can run n run under GUI)under GUI)

".NOG"

".NOG" (application cann(application cannot be run ot be run under GUI)under GUI)

PRODUCT PRODUCT

ST,EB,AC,FX etc.

(10)

FILE.CONTROL

To execute any application in T24, in addition to having an entry in the PGM.FILE, an entry for that

particular application should also exist in the F.FILE.CONTROL application. FILE.CONTROL, as the

name denotes, controls the type of information being stored in a file (application).

In the PGM.FILE application, entries are made for programs, applications and batch routines. Apart

from applications, the others do not store data. Hence only applications that store data will have an

entry in the FILE.CONTROL application.

Find below the fields of the FILE.CONT

Find below the fields of the FILE.CONTROL application.ROL application.

ID

ID : Application Name. (No special characters allowed other than ‘.’. Must match the equivalent entry : Application Name. (No special characters allowed other than ‘.’. Must match the equivalent entry

in PGM.FILE)

Field Description

Field Description DESCRIPTION

DESCRIPTION Holds Holds the the description description of of the the record.record.

PRODUCT

PRODUCT Identifies Identifies the the product product to to which which the the application application belongs. belongs. It It is is the the namename

of the sub directory under the ‘.data’ directory where the data files of

this application will be stored. Should match the value given in the

PGM.FILE entry.

SUFFIXES

SUFFIXES Holds Holds the the various various types types of of files files supported supported by by this this application.application.

Valid values :

$NAU (Unauthorised file)

$HIS (History file)

All

All applications applications by by default default support support live live files. files. This This field field specifies specifies thethe

other types of files supported by the application other than live fil

other types of files supported by the application other than live files.es.

Example: Example: LiveFile:FBNK.CUSTOMER LiveFile:FBNK.CUSTOMER UnauthFile:FBNK.CUSTOMER$NAU UnauthFile:FBNK.CUSTOMER$NAU HistoryFile:FBNK.CUSTOMER$HIS HistoryFile:FBNK.CUSTOMER$HIS FILE.TYPE

FILE.TYPE This This field field is is used used only only when when the the database database used used is is uniVerse. uniVerse. It It holdsholds

the file type of the file.

1 or 19 – Non hashed files

2 to 18 – Hashed files

MODULO

MODULO This This field field is is used used only only when when the the database database used used is is uniVerse. uniVerse. It It holdsholds

the modulo of the file.

SUB.PRODUCT NA

SYS.CLEAR.FILES

SYS.CLEAR.FILES Valid Valid Values Values : : ‘Y’ ‘Y’ or or ‘N’‘N’

If set to ‘Y’, denotes that the contents of the application being

defined can be cleared when the SYSTEM.CLEAR.FILES is

executed.

CUS.CLEAR.FILES

CUS.CLEAR.FILES Valid Valid Values Values : : ‘Y’ ‘Y’ or or ‘N’‘N’

Obsolete Obsolete BRANCH.FILE NA BRANCH.FILE NA RELATED.FILE NA RELATED.FILE NA

(11)

STANDARD.SELECTION

As

As you you would would be aware be aware by by now, all now, all the the applications in applications in T24 T24 will will have a have a data fdata file ile and a and a dictionary dictionary file.file.

The data will store all the records of the application where as the dictionary file will store all the field

names and their definitions. For example, for the CUSTOMER

names and their definitions. For example, for the CUSTOMER application in T24, there would beapplication in T24, there would be

3 Data Files

FBNK.CUSTOMER (To store live

FBNK.CUSTOMER (To store live records)records)

FBNK.CUSTOMER$NAU (To store unauthorised records)

FBNK.CUSTOMER$HIS (To store history records) and

1 Dict(ionary) File

F.CUSTOMER]D

Note that the dictionary file will always have the prefix as ‘F.’ like INT files. There will be only one copy

of the dictionary file irrespective of the number of branches.

In T24, the entire control of the applications is held at the application layer (within T24). Hence, the

layout of the fields in an application is not only held at the database level but also at the application

level.

The application STANDARD.SELECTION contains 1 record per application and will contain the field

definition of all the fields in

definition of all the fields in the application. the application. (Default abbreviation for STANDARD.SELECTION: SS)(Default abbreviation for STANDARD.SELECTION: SS)

The STANDARD.SELECTION application not only contains the field definition of the core T24 fields

(system fields), but also the definition of all local reference fields (user defined fields). All the system

fields are no input fields and can be modified only by T

fields are no input fields and can be modified only by T24. The user-defined fields can be modified.24. The user-defined fields can be modified.

Field Description

Field Description SYS

SYS FIELD FIELD NAME NAME Name Name of of the the fieldfield

SYS

SYS TYPE TYPE Holds Holds the the type type of of field.field.

D – Data field

C – Used for CONCAT files

R – Infobasic Routines (Used for Nofile Enquiry – Refer to

‘Advanced Technical Training’ material for more information on

this. this. I – I types (I Descriptors) I – I types (I Descriptors) J – J types (J Descriptors) J – J types (J Descriptors) SYS

SYS FIELD FIELD NO NO Holds Holds the the field field number number of of the the field field being being defined. defined. The The @ID @ID field field willwill

always have the field number set to 0. The rest of the fields will

have field numbers starting from 1.

SYS

SYS VAL VAL PROGRAM PROGRAM Contains Contains the the name name of of the the IN2 IN2 routine routine that that will will be be used used to to performperform

data type validation on the field that is being defined.

SYS

SYS CONVERSION CONVERSION Specifies Specifies the the conversion conversion to to be be performed performed on on the the field field being being defineddefined

when a SELECT or a LIST

when a SELECT or a LIST statement is executed.statement is executed.

Eg : D2/E-Converts the internal date to dd/mm/yy f

Eg : D2/E-Converts the internal date to dd/mm/yy format.ormat.

SYS

SYS DISPLAY DISPLAY FMT FMT Contains Contains the the maximum maximum number number of of characters characters and and the the defaultdefault

alignment (Left or Right)

Eg : 10R

(12)

SYS

SYS ALT ALT INDEX INDEX Indicates Indicates whether whether there there is is to to be be an an alternate alternate index index associated associated withwith

the field name specified in SYS FIELD NAME.

Valid values : Y and N.

SYS

SYS INDEX INDEX FILE FILE Specifies Specifies to to which which version version (Live (Live or or History) History) the the alternate alternate index index is is toto

apply.

If the SYS ALT INDEX field is set to 'Y' then specify here the types

of files the alternate index should relate to i.e the History or Live

version of the filename specified in FILE NAME. This field is

sub-valued to allow the input of both LIVE

valued to allow the input of both LIVE and HISTORY.and HISTORY.

SYS

SYS INDEX INDEX NULLS NULLS Indicates Indicates whether whether null null alternate alternate key key values values are are to to be be indexed. indexed. ThisThis

field only applies if field SYS ALT INDEX has been set to 'Y'.

If null data values are to be maintained in the

If null data values are to be maintained in the alternate index foralternate index for

the data field then this field should be set to

the data field then this field should be set to 'Y'. Otherwise it s'Y'. Otherwise it shouldhould

be set to 'N'.

SYS

SYS SINGLE SINGLE MULTI MULTI Specifies Specifies whether whether the the field field being being defined defined is is a a single single or or a a multi multi valuevalue

field.

Valid values :

S – Single value field

M – Multi value field

Sub value fields will have the value ‘M.

SYS

SYS LANG LANG FIELD FIELD Specified Specified if if the the field field being being specified specified is is a a Language Language specific specific field. field. AllAll

language specific fields are multi value fields. When multi-valued,

they will allow input of

they will allow input of data in multiple languages.data in multiple languages.

SYS

SYS GENERATED GENERATED Specified Specified whether whether it it is is a a system-generated system-generated field field (Core (Core T24 T24 field).field).

Valid values ‘Y’.

SYS

SYS CNV CNV TYPE TYPE NANA

SYS

SYS REL REL FILE FILE If If the the field field being being specified specified is is to to contain contain data data from from another another file, file, thenthen

the name of the related file is specified here.

E.g. If a field named CUSTOMER.NO is to be defined in the SS

record for ACCOUNT, then this field would contain the value

‘CUSTOMER’ to denote that the valid values that the

CUSTOMER.NO field can have are the IDs from the CUSTOMER

file.

USR

USR FIELD FIELD NAME NAME Fields Fields starting starting from from this this field field until until USR USR REL REL FILE FILE are are used used toto

specify user-defined fields.

E.g. Local Reference Fields.

This field contains the name of the user-defined field being

specified.

USR

USR TYPE TYPE Similar Similar to to SYS SYS TYPETYPE

USR

USR FIELD FIELD NO NO Contains Contains the the field field number number of of the the field field being being defined.defined.

USR

USR VAL VAL PROG PROG Contains Contains the the name name of of the the IN2 IN2 routine routine that that is is used used to to perform perform datadata

type validation on the field being defined.

USR

USR CONVERSION CONVERSION Similar Similar to to SYS SYS CONVERSIONCONVERSION

USR

USR DISPLAY DISPLAY FMT FMT Contains Contains the the maximum maximum number number of of characters characters and and the the defaultdefault

alignment of the field being specified.

E.g.; 10L (Maximum of 10 characters and Left justified)

USR

USR ALT ALT INDEX INDEX Similar Similar to to SYS SYS ALT ALT INDEXINDEX

USR

USR INDEX INDEX FILE FILE Similar Similar to to SYS SYS INDEX INDEX FILEFILE

USR

USR INDEX INDEX NULLS NULLS Similar Similar to to SYS SYS INDEX INDEX NULLSNULLS

USR

USR SINGLE SINGLE MULTI MULTI Specifies Specifies if if the the field field being being defined defined is is a a single single or or a a multi multi value value field.field.

S – Single value field

M – Multi value field

USR

USR LANG LANG FIELD FIELD Specifies Specifies if if the the field field being being defined defined is is a a language language specific specific multi multi valuevalue

field.

USR

(13)

USR

USR REL REL FILE FILE Contains Contains the the name name of of the the related related file file whose whose IDs IDs will will be be used used asas

valid data values for the field being defined.

REBUILD

REBUILD SYS SYS FIELDS FIELDS If If set set to to ‘Y’, ‘Y’, T24 T24 will will rebuild rebuild the the SS SS record record and and the the dictionary dictionary filefile

associated with the application.

DEFAULT

DEFAULT ENRICH ENRICH Contains Contains the the name name of of the the field field whose whose value value will will appear appear as as defaultdefault

enrichment when the ID of the application being defined is input in

any other application.

As mentioned above, the

As mentioned above, the user defined can be user defined can be modified. Once they are modified. Once they are modified, the SS modified, the SS record needsrecord needs

to be rebuilt by setting the ‘REBUILD SYS FIELD’ to Y. Once done, commit and authorise the record.

Ensure that users are not using the application before rebuild the SS record of t

Ensure that users are not using the application before rebuild the SS record of that application.hat application.

DATES

DATES is a very important application in T24. It is of type INT and hence only one copy of the file will

exist irrespective of the number of branches that a bank may have. As the name denotes, the DATES

application is used to store the date of T24. It is vital to understand that t24 maintains its own date and

does not go by the system date.

The DATES application contains one

The DATES application contains one dates record per branch (company).dates record per branch (company).

ID : Company Code (Every branch(company) will have a company code in T24 to uniquely identify

itself. This is defined in

itself. This is defined in the COMPANY file that is the COMPANY file that is covered in the later part of this document).covered in the later part of this document).

ID : IN0010001

Field Description

Field Description TODAY

TODAY Contains Contains the the current current T24 T24 date. date. This This is is not not the the system system date date on on whichwhich

T24 is installed.

VERSION NA

LAST.WORKING.DAY

LAST.WORKING.DAY Contains Contains the the last last working working day day of of T24T24

NEXT.WORKING.DAY

NEXT.WORKING.DAY Contains Contains the the next next working working day day of of T24.T24.

LOCAL.PAYMENT.DAY

LOCAL.PAYMENT.DAY Used Used only only for for reference reference purposes. purposes. NANA

LOCAL.DISPO.DAY

LOCAL.DISPO.DAY Used Used only only for for reference reference purposes. purposes. NANA

BACK.VALUE.MINIMUM

BACK.VALUE.MINIMUM The The minimum minimum date date that that can can be be supplied supplied for for back back valued valued transactions.transactions.

BACK.VALUE.MAXIMUM

BACK.VALUE.MAXIMUM The The maximum maximum date date that that can can be be supplied supplied for for back back valued valued transactions.transactions.

FORW.VALUE.MINIMUM

FORW.VALUE.MINIMUM The The minimum minimum date date that that can can be be supplied supplied for for forward forward valuedvalued

transactions.

FORW.VALUE.MAXIMUM

FORW.VALUE.MAXIMUM The The maximum maximum date date that that can can be be supplied supplied for for forward forward valuedvalued

transactions.

CO.BACTH.STATUS

CO.BACTH.STATUS Contains Contains the the status status of of a a company.company.

0 – Online

B – Batch (COB in

B – Batch (COB in progress)progress)

(Not used by T24) releases lesser than 14)

PERIOD.END

PERIOD.END Close Close of of business business date.date.

Either the next working day minus one calendar day or the end of

(14)

month whichever is earlier.

ACCOUNTING.STAGE

ACCOUNTING.STAGE NANA

JULIAN.DATE

JULIAN.DATE This This field field is is the the date date in in TODAY TODAY held held in in the the Julian Julian format. format. The The JulianJulian

format consists of the four-digit year followed by t

format consists of the four-digit year followed by the day in the year.he day in the year.

Eg : The Julian value for 27th March 1986 is

Eg : The Julian value for 27th March 1986 is 1986086.1986086.

CURRENT.DAY NA

COB, which stands for Close Of Business is run at the end of the day to mark the close of all financial

transactions for the day. During this process, the values in TODAY, NEXT.WORKING.DAY and

LAST.WORKING.DAY change.

When COB is initiated, the value in CO.BATCH.STATUS is changed from O to B. The value B, as

mentioned above, denotes that the COB is running and hence will prevent certain action by the

users.(Please note that when the value is set to O – which denotes Online, all users can login and

perform any activity that is permitted by their user

perform any activity that is permitted by their user profile).profile).

COB updates the

LAST.WORKING.DAY with the value of TODAY

TODAY field with the value of NEXT.WORKIN.DAY and

NEXT.WORKING.DAY with the appropriate value from the HOLIDAY file.

If you are using a T24

If you are using a T24 release 14 or above, then the you will release 14 or above, then the you will find 2 dates records per company. Pleasefind 2 dates records per company. Please

refer to the ‘T24 NonStop’ or ‘

refer to the ‘T24 NonStop’ or ‘Basic Technical Training’ materials for more information on this.Basic Technical Training’ materials for more information on this.

HOLIDAY

The purpose of this table is to indicate the public holidays for each Country, or Region within a

Country, for the calendar years over which the bank's current business is spread. The User must

indicate, for each Country or Region, the public holidays and which day(s) of the week make up the

weekend.

weekend. The non-working weekend The non-working weekend days are then generatedays are then generated automatically for the year and d automatically for the year and for thisfor this

reason they do not have to be specified individually as public holidays. Each T24 Application will refer

to this table during input validation to verify that any dates entered by the user are working days or to

force an override to accept

force an override to accept non-working days.non-working days.

ID :

ID : CountryCoderegionCodCountryCoderegionCodeYeareYear

ID : IN002004

Field Description

Field Description JANUARY

JANUARY Contains Contains the the days days of of the the month(Month month(Month name name is is the the field field name) name) that that areare

to be holidays.

Eg. 1 10 17 31

1

1stst,10,10thth,17,17thth and 31 and 31stst of January are holidays. of January are holidays.

Multiple days can be defined as holidays by specifying multiple days

delimited by spaces (as defined above).

FEBRUARY

FEBRUARY Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for FEBRUARY.

MARCH

MARCH Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for MARCH

APRIL

APRIL Has the Has the Same purpose of Same purpose of the field the field ‘JANUARY’, ‘JANUARY’, but holds but holds the holidaysthe holidays

for APRIL.

MAY

(15)

for MAY.

JUNE

JUNE Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for JUNE.

JULY

JULY Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for JULY.

AUGUST

AUGUST Has the Has the Same purpose Same purpose of the of the field ‘JANUARY’field ‘JANUARY’, but , but holds the holds the holidaysholidays

for AUGUST.

SEPTEMBER

SEPTEMBER Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for SEPTEMBER.

OCTOBER

OCTOBER Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for OCTOBER.

NOVEMBER

NOVEMBER Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for NOVEMBER.

DECEMBER

DECEMBER Has Has the the Same Same purpose purpose of of the the field field ‘JANUARY’, ‘JANUARY’, but but holds holds the the holidaysholidays

for DECEMBER.

WEEKEND.DAYS

WEEKEND.DAYS Contains Contains the the days days that that are are to to be be declared declared as as weekend weekend days.days.

Eg : SA (Saturday)

SU (Sunday)

MTH.01.TABLE

MTH.01.TABLE Contains Contains an an entry entry for for each each day day in in the the month month (Month (Month number number is is a a partpart

of the field name - January)

Value W : Working Day

Value H : Holiday

Value X : Not used (For the month of Feb as there may be only 28/29

days, the remaining days until the 31

days, the remaining days until the 31stst will be marked with a X). will be marked with a X). Eg.

Eg.

MTH.02.TABLE

MTH.02.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month February.February.

MTH.03.TABLE

MTH.03.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month March.March.

MTH.04.TABLE

MTH.04.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month April.April.

MTH.05.TABLE

MTH.05.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month May.May.

MTH.06.TABLE

MTH.06.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month June.June.

MTH.07.TABLE

MTH.07.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month July.July.

MTH.08.TABLE

MTH.08.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month August.August.

MTH.09.TABLE

MTH.09.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month September.September.

MTH.10.TABLE

MTH.10.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month October.October.

MTH.11.TABLE

MTH.11.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month November.November.

MTH.12.TABLE

MTH.12.TABLE Same Same as as MTH.01.TABLE, MTH.01.TABLE, but but holds holds the the details details of of month month December.December.

XXX XXX

(16)

COMPANY

The Company file, as the name denotes contains the details of the various companies(branches) of a

bank. There will be one record per company in the COMPANY file. This is a INT type of file and hence

there will be only one copy of this file(F.COMPANY).

ID : CompanyCode ID : CompanyCode ID : IN0010001 ID : IN0010001 Field Description Field Description COMPANY.NAME

COMPANY.NAME Contains Contains the the name name of of the the company company being being defined. defined. Can Can be be defined defined inin

multiple languages.

NAME.ADDRESS

NAME.ADDRESS Contains Contains the the name name and and address address of of the the company company being being defined.defined.

MNEMONIC

MNEMONIC Contains Contains the the mnemonic mnemonic of of the the company company being being defined. defined. It It is is unique unique forfor

each company and will be used as a prefix for FIN and CUS type of

files.

LANGUAGE.CODE

LANGUAGE.CODE Contains Contains the the language language of of T24 T24 installed installed in in the the bank. bank. Can Can contain contain validvalid

values from the LANGUAGE application.

STAT.REP.AREA

STAT.REP.AREA Identifies Identifies the the area area to to which which the the Statutory Statutory reports reports are are to to be be sent. sent. Will Will bebe

printed in the header region of the statutory reports.

STAT.REP.NAME

STAT.REP.NAME Identifies Identifies the the person person to to whom whom the the Statutory Statutory reports reports are are to to be be sent. sent. WillWill

be printed in the header region of the statutory reports.

STAT.REP.DELIV

STAT.REP.DELIV Identifies Identifies the the location location to to which which the the Statutory Statutory reports reports are are to to be be sent. sent. WillWill

be printed in the header region of the statutory reports.

MGMT.REP.AREA

MGMT.REP.AREA Identifies Identifies the the area area to to which which the the Company Company Management Management reports reports are are toto

be sent. Will be printed in the header region of

be sent. Will be printed in the header region of the statutory reports.the statutory reports.

MGMT.REP.NAME

MGMT.REP.NAME Similar Similar to to STAT.REP.NAME STAT.REP.NAME but but will will apply apply for for MI MI reports.reports.

MGMT.REP.DELIV

MGMT.REP.DELIV Similar Similar to to STAT.REP.DELIV STAT.REP.DELIV but but will will apply apply to to MI MI reportsreports

CONSOLIDATION.MARK

CONSOLIDATION.MARK Indicates Indicates whether whether the the Company Company record record has has been been set set for for consolidationconsolidation

purposes only, or the company is a full processing company.

Valid values :

A : Live processing company

C : Used for consolidation purposes only

R : Used for reporting purposes only

DEFAULT.NO.OF.AUTH

DEFAULT.NO.OF.AUTH Contains Contains the the default default number number of of authorisers authorisers for for all all applications applications in in thethe

bank. This can be overridden in Versions.

Valid values : 0, 1 or

Valid values : 0, 1 or 22

PGM.AUTOM.ID

PGM.AUTOM.ID Contains Contains the the names names of of T24 T24 applications applications that that can can automaticallyautomatically

generate IDs. If an application can generate IDs automatically, but

foes not have an entry in this field, then T24 does not allow Auto ID

generation.

LOCAL.COUNTRY

LOCAL.COUNTRY Country Country in in which which the the company company is is situated.situated.

LOCAL.REGION NA

LOCAL.CURRENCY

(17)

currency of the country in which the company is situated as the local

currency of the company.

Eg. A company with LOCAL.COUNTRY ‘DE’ can have local currency

as ‘USD.

Can contain valid currencies defined in the CURRENCY file.

RATE.SYSTEM

RATE.SYSTEM Defines Defines the the rate rate system system to to be be used.used.

BUY.SELL.RATE BUY.SELL.RATE SELL.BUY.RATE SELL.BUY.RATE MID.REVAL.RATE MID.REVAL.RATE CUSTOMER.COMPANY

CUSTOMER.COMPANY Used Used for for multi multi company company environments.environments.

Defines the company that will hold the Customer information.

CUSTOMER.MNEMONIC

CUSTOMER.MNEMONIC Contains Contains the the mnemonic mnemonic of of the the company company defined defined in in the the fieldfield

‘CUSTOMER.COMPANY’

DEFAULT.CUS.COM

DEFAULT.CUS.COM Indicates Indicates under under which which company company the the Customer Customer table table files(CUS files(CUS tye)aretye)are

maintained.

DEFUALT.CUS.MNE

DEFUALT.CUS.MNE Holds Holds the the mnemonic mnemonic of of the the company company defined defined in in the the fieldfield

‘DEFAULT.CUS.COM’.

SPCL.CUST.FILE

SPCL.CUST.FILE Indicates Indicates the the name name of of customer customer table table file file (CST) (CST) which which is is to to bebe

maintained under a different company to the majority of the customer

table files for this company.

SPCL.CUST.COM

SPCL.CUST.COM Indicates Indicates under under which which company company the the Special Special Customer Customer table table file file isis

maintained.

SPCL.CUST.MNE

SPCL.CUST.MNE Indicates Indicates the the mnemonic mnemonic of of the the company company defined defined in in thethe

SPCL.CUST.COM field.

DEFAULT.FINAN.COM

DEFAULT.FINAN.COM Indicates Indicates under under which which company company the the Financial Financial Static Static table table files files areare

maintained for this Company.

DEFAULT.FINAN.MNE

DEFAULT.FINAN.MNE Contains Contains the the mnemonic mnemonic of of the the company company defined defined in in the the fieldfield

DEFAULT.FINAN.COM

SPCL.FIN.FILE

SPCL.FIN.FILE Indicates Indicates the the Mnemonic Mnemonic code code for for the the company company under under which which thethe

Financial Static table files are maintained f

Financial Static table files are maintained for this Company.or this Company.

SPCL.FIN.COM NA

SPCL.FIN.MNE NA

CURRENCY.COMPANY

CURRENCY.COMPANY Indicates Indicates under under which which company company the the currency currency files files are are maintained maintained forfor

this company.

CURRENCY.MNEMONIC

CURRENCY.MNEMONIC Indicates Indicates the the Mnemonic Mnemonic code code for for the the company company under under which which thethe

currency files are maintained for this.

FINAN.FINAN.COM

FINAN.FINAN.COM Indicates Indicates under under which which company company the the Financial Financial Financial Financial table table files files areare

maintained for this Company.

FINAN.FINAN.MNE

FINAN.FINAN.MNE Indicates Indicates the the Mnemonic Mnemonic code code for for the the company company under under which which thethe

Financial Financial table files are maintained for t

Financial Financial table files are maintained for this company.his company.

NOSTRO.COMPANY

NOSTRO.COMPANY Indicates Indicates which which company company maintains maintains the the Nostro Nostro accounts accounts used used by by thisthis

company.

NOSTRO.MNEMONIC

NOSTRO.MNEMONIC Indicates Indicates the the Mnemonic Mnemonic code code for for the the company company maintains maintains the the NostroNostro

accounts used by this company.

NOSTRO.SUB.DIV

NOSTRO.SUB.DIV If If Nostro Nostro accounts accounts are are maintained maintained in in another another company company then then the the SubSub

division code from the Nostro company record is stored in this field.

If Nostro accounts are maintained in the company being processed

then this field is left blank.

INTER.COM.CATEGORY

INTER.COM.CATEGORY Contains Contains the the category category code code to to be be used used when when inter inter companycompany

accounting entries are raised.

APPLICATIONS

APPLICATIONS Contains Contains the the various various applications applications installed installed for for the the company company beingbeing

defined.

PARENT.COY.RES NA

LOCAL.PROCESS.NAME