2.T24DirectoryStructureAndImportatntFilesInGlobus

T24 Directory Structure And Important Files In T24

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, electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.


“Copyright © 2004 TEMENOS HOLDINGS NV” “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.

DateO Dat eOff Iss Issue ue

Versio Ver sion n

Chang Ch anges es

By

2001

1.0

Initial

Alagammai Palaniappan

2002

1.1

jBASE Changes


2002

1.2

Infobasic Alagammai Program Palaniappan ming changes

July 2004

1.3

G14 changes

Temenos Training Publications T2BTT – R06 – 1.0

Page 2 of 21


March 2004


Table of Content Table of Conte Content nt .............. ........................... ........................... ........................... ........................... ........................... ........................... ............................ ......................... ...................... ........... 3 T24 Directo Directory ry Structu Structure................ re............................. ........................... ........................... ........................... ............................ ........................... ....................... ........................ .............. 4 Directories Direct ories That Get Installed When T24 Is Install Installed ed ............ .......................... ........................... ........................... ........................... ....................... .......... 4 bnk.data............. bnk.d ata........................... ............................ ........................... ........................... ........................... ........................... ............................ ........................ ....................... .................. ..... 4 bnk.dict bnk.d ict .............. ............................ ........................... ........................... ........................... ........................... ............................ ........................... ....................... ........................ ................... ..... 4 bnk.help...................... bnk.h elp................................... ........................... ............................ ........................... ........................... ........................... ........................... ......................... .................... ......... 4 bnk.jnll ............. bnk.jn ........................... ............................ ........................... ........................... ........................... ........................... ........................... ......................... ........................ .................... ........ 4 bnk.run bnk.ru n ............. .......................... .......................... .......................... ........................... ........................... ........................... ........................... ........................... ........................... .................. ..... 5 bnk.backu bnk.b ackup p ............. .......................... ........................... ........................... ........................... ............................ ........................... ........................... ........................ ........................ .............. 5 GLOBUS.BP.................... GLOBUS .BP.................................. ............................ ............................ ............................ ........................... ........................... ............................ ........................ ............. ... 5 File Types In T24 ............ ......................... ........................... ........................... ........................... ........................... ........................... ........................... ....................... ........................ .............. 5 Live file.................. file............................... ........................... ........................... ........................... ............................ .......................... ........................... .......................... ........................ .................. ..... 5 The Unauth Unauthorize orized d File........................ File..................................... .......................... ........................... ........................... .......................... ........................... ........................ ............... ..... 5 The History File ............ ........................... ........................... ........................... ........................... .......................... ........................... .......................... ......................... ....................... ........... 5 File Classi Classificati fication.................... on................................. ........................... ........................... .......................... .......................... ........................... .......................... ......................... .................. ..... 6 File Class Classificatio ification.................. n............................... ........................... ........................... ........................... ............................ ........................... ....................... ........................ .............. 6 File Prefixe Prefixes..................... s................................... ........................... ........................... ............................ ........................... ........................... ......................... ......................... ................. ... 7 Core Param Parameter eter Files In T24......... T24...................... .......................... ........................... ........................... .......................... ........................... ......................... ........................ ............. 8 PGM.FILE PGM.FIL E ............. .......................... ........................... ........................... ........................... ........................... ........................... ............................ ......................... ........................ .................. ..... 8 FILE.CONTROL........................ FILE.CON TROL...................................... ........................... ........................... ........................... ........................... ........................... ......................... ..................... ......... 10 STANDARD.SELECT STANDARD .SELECTION ION .............. ........................... .......................... ........................... ........................... ........................... ........................... ........................... ................. ... 11 DATES ............. ........................... ........................... ........................... ............................ ........................... ........................... ............................ ........................... ......................... .................. ...... 13 HOLIDAY .............. ........................... ........................... ............................ ........................... ........................... ............................ ............................ ........................ ....................... ................ ... 14 COMPANY.............................. COMPANY................ ........................... ........................... ............................ ............................ ........................... ........................... ........................ ...................... ............ 16 SPF ............. ........................... ............................ ........................... ........................... ............................ ............................ ........................... ........................... ........................ ...................... ............ 19


Page 3 of 21

March 2004


T24 Directory Structure Each T24 account is completely self-contained and stand-alone. That is, it contains 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: bnk

bnk.run

bnk.data

lobusbin

ac

lobuslib

fx

bin

eb

bnk.dict

bnk.help

bnk.jnl

bnk.backup

lib GLOBUS.BP

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


Page 4 of 21

March 2004


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 (Contains t24 executables)

•

globuslib (Contains T24 library files)

•

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

•

lib (Usually used to store non T24(local) 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. INAU

:

Input not authorised

b.

INAO

:

Input not authorised override

c.

INA2

:

Input not authorised by authoriser 2

d. RNAU :

Reversal not authorised

e. RNA2 :

Reversal not authorised by authoriser 2

f.

Copied record not authorised

CNAU :

g. CNA2 :

Copied record not authorised by authoriser 2

h. RNAO :

Reversal not authorised override

i.

Input on hold

IHLD

:

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 Temenos Training Publications T2BTT – R06 – 1.0

Page 5 of 21

March 2004


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

Application Name

:

Customer

Live File Name

:

CUSTOMER

Unauthorized File Name

:

CUSTOMER$NAU

History File Name

:

CUSTOMER$HIS

File Classification File Classification Assume a scenario where T24 is to be implemented implemented in a bank which has the following structure Head Office

Branch 1

Branch 2

Branch 3

When T24 is implemented in a bank with the above structure, there would be a number of files that are 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 Installation

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

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

This 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 Customer Tables

This covers files like SECTOR, TRAGET, INDUSTRY. These types of files are usually used as check files for customer level files. They have the same properties of CUS file.


Page 6 of 21

March 2004


FTD Financial Table Descriptive

FTF Financial Table Financial

This group covers files like BASIC.INTEREST, GROUP.CONDITION etc. These types of files are usually used as check files f or financial level files. The files in this group contain non-financial data. They have the same properties as FIN files. This group covers files like GROUP.DEBIT.INT, TXN etc. These files are linked to financial level files and also contain financial level data. They have the same properties like FIN files.

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

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 discussed later in this section) as a prefix. CUSTOMER file in Head Office : FBNK.CUSTOMER (BNK is the mnemonic of the the Head Office) CUSTOMER file in Branch 1

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

CUSTOMER file in Branch 2


CUSTOMER file in Branch 3


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

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

ACCOUNT file in Branch 1

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






Page 7 of 21

March 2004


For INT files, since only once copy of the files exists, the above rule doesn’t apply for them. PGM.FILE file in Head Office

: F.PGM.FILE

PGM.FILE file in Branch 1

: F.PGM.FILE


: F.PGM.FILE


: F.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 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. PGM.FILE is also checked to obtain the characteristics of the application. ID : Application/Program/Batch Routine Name. (No special characters allowed other than ‘.’) Field TYPE

Description Denotes the type of application/program that is being defined.(Possible values listed below)

GB SCREEN TITLE

Identifies the program title that will be displayed as a header when the corresponding application (ID) is invoked in the action line.

ADDITIONAL.INFO

Holds the special characteristics of the application/program being defined. (Some of the possible values listed below)

BATCH.JOB

Identifies batch jobs when the program has been defined with the type as ‘B’. For more information on this refer to the training document ‘Advanced Technical Training’

PRODUCT

Identifies the product to which the application or 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

Holds the description of the application/program being defined

APPL.FOR.SUBR

Used when defining version routines. Used for administrative purposes. For more information on this refer training document ‘Advanced Technical Training’ and ‘Advanced ‘Advanced Technical Training - Plus’

BATCH.LIST.MAXIMUM

Holds the maximum number of ids that can be stored 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’.


Page 8 of 21

March 2004


MT.KEY.COMPONENT MT.KEY.FILE •

Used for Multi Book Used for Multi Book

TYPE

H

A program that has this type maintains three files the unauthorised, live and history files. The unauthorised file is updated at Input; Input; the live file at authorisation; and and the history file whenever whenever there is an authorised authorised change to a record. E.g. CUSTOMER

U

A program similar to type 'H' except that history is not maintained. e.g. ABBREVIATION

L

A program that displays the data of a live file but does not allow updates. Updates to these files would be controlled by the System automatically. e.g. STMT.ENTRY

T

A program that displays data in a table file (such as a list of keys) but does not allow update. e.g. LMM.CUSTOMER

W

A program that permits updates to a work or temporary file. A typical example would be the REPGEN.OUTPUT program where print or display parameters for a report can be loaded.

B

A Batch job that can only be accessed during the 'off-line' processing in BATCH.CONTROL.

M

Main-line program that can be run from the action line but has no file directly associated with it.

S

Subroutine. A program used in the T24 system but one that is executed Automatically whenever required. It cannot be entered by the user either at at the action line or from within within the Batch Control system. It is recommended that that these are loaded only when they are needed by the report generator e.g. IN2... routines.

ADDITIONAL INFO

".NOH" (no hold facility after 1st 1st input) ".GUI" (application can can run under GUI) ".NOG" (application cannot cannot be run under GUI) PRODUCT

ST,EB,AC,FX etc.


Page 9 of 21

March 2004


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 ROL application. ID : Application Name. (No special characters allowed other than ‘.’. Must match the equivalent entry in PGM.FILE) Field DESCRIPTION

Description Holds the description of the record.

PRODUCT

Identifies the product to which the application belongs. It is the name 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

Holds the various types of files supported by this application. Valid values : $NAU (Unauthorised file) $HIS (History file) All applications by default support live files. This field specifies the other types of files supported by the application other than live fil es. Example: LiveFile:FBNK.CUSTOMER UnauthFile:FBNK.CUSTOMER$NAU HistoryFile:FBNK.CUSTOMER$HIS

FILE.TYPE

This field is used only when the database used is uniVerse. It holds the file type of the file. 1 or 19 – Non hashed files 2 to 18 – Hashed files

MODULO

This field is used only when the database used is uniVerse. It holds the modulo of the file.

SUB.PRODUCT

NA

SYS.CLEAR.FILES

Valid Values : ‘Y’ or ‘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

Valid Values : ‘Y’ or ‘N’ Obsolete

BRANCH.FILE RELATED.FILE


NA NA

Page 10 of 21

March 2004


STANDARD.SELECTION As you would be aware by now, all the applications in T24 will have a data file f ile and a dictionary 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 application in T24, there would be 3 Data Files FBNK.CUSTOMER (To store live 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 the application. (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 24. The user-defined fields can be modified.

Field SYS FIELD NAME

Description Name of the field

SYS TYPE

Holds the type of 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. I – I types (I Descriptors) J – J types (J Descriptors)

SYS FIELD NO

Holds the field number of the field being defined. The @ID field will always have the field number set to 0. The rest of the fields will have field numbers starting from 1.

SYS VAL PROGRAM

Contains the name of the IN2 routine that will be used to perform data type validation on the field that is being defined.

SYS CONVERSION

Specifies the conversion to be performed on the field being defined when a SELECT or a LIST statement is executed. Eg : D2/E-Converts the internal date to dd/mm/yy f ormat.

SYS DISPLAY FMT

Contains the maximum number of characters and the default alignment (Left or Right) Eg : 10R


Page 11 of 21

March 2004


SYS ALT INDEX

SYS INDEX FILE

SYS INDEX NULLS

SYS SINGLE MULTI

SYS LANG FIELD

SYS GENERATED SYS CNV TYPE SYS REL FILE

USR FIELD NAME

USR TYPE USR FIELD NO USR VAL PROG USR CONVERSION USR DISPLAY FMT

USR ALT INDEX USR INDEX FILE USR INDEX NULLS USR SINGLE MULTI

USR LANG FIELD USR CONV TYPE Temenos Training Publications T2BTT – R06 – 1.0

Indicates whether there is to be an alternate index associated with the field name specified in SYS FIELD NAME. Valid values : Y and N. Specifies to which version (Live or History) the alternate index is to 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 subvalued to allow the input of both LIVE and HISTORY. Indicates whether null alternate key values are to be indexed. This field only applies if field SYS ALT INDEX has been set to 'Y'. If null data values are to be maintained in the alternate index for the data field then this field should be set to 'Y'. Otherwise it should s hould be set to 'N'. Specifies whether the field being defined is a single or a multi value field. Valid values : S – Single value field M – Multi value field Sub value fields will have the value ‘M. Specified if the field being specified is a Language specific field. All language specific fields are multi value fields. When multi-valued, they will allow input of data in multiple languages. Specified whether it is a system-generated field (Core T24 field). Valid values ‘Y’. NA If the field being specified is to contain data from another file, then 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. Fields starting from this field until USR REL FILE are used to specify user-defined fields. E.g. Local Reference Fields. This field contains the name of the user-defined field being specified. Similar to SYS TYPE Contains the field number of the field being defined. Contains the name of the IN2 routine that is used to perform data type validation on the field being defined. Similar to SYS CONVERSION Contains the maximum number of characters and the default alignment of the field being specified. E.g.; 10L (Maximum of 10 characters and Left justified) Similar to SYS ALT INDEX Similar to SYS INDEX FILE Similar to SYS INDEX NULLS Specifies if the field being defined is a single or a multi value field. S – Single value field M – Multi value field Specifies if the field being defined is a language specific multi value field. Similar to SYS CONV TYPE Page 12 of 21

March 2004


USR REL FILE

Contains the name of the related file whose IDs will be used as valid data values for the field being defined. If set to ‘Y’, T24 will rebuild the SS record and the dictionary file associated with the application. Contains the name of the field whose value will appear as default enrichment when the ID of the application being defined is input in any other application.

REBUILD SYS FIELDS DEFAULT ENRICH

As mentioned above, the user defined can be modified. Once they are modified, the SS record 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 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 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 the COMPANY file that is covered in the later part of this document). ID : IN0010001

Field TODAY

Description Contains the current T24 date. This is not the system date on which T24 is installed.

VERSION

NA

LAST.WORKING.DAY

Contains the last working day of T24

NEXT.WORKING.DAY

Contains the next working day of T24.

LOCAL.PAYMENT.DAY

Used only for reference purposes. NA

LOCAL.DISPO.DAY

Used only for reference purposes. NA

BACK.VALUE.MINIMUM

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

BACK.VALUE.MAXIMUM

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

FORW.VALUE.MINIMUM

The minimum date that can be supplied for forward valued transactions.

FORW.VALUE.MAXIMUM

The maximum date that can be supplied for forward valued transactions.

CO.BACTH.STATUS

Contains the status of a company. 0 – Online B – Batch (COB in progress) (Not used by T24) releases lesser than 14)

PERIOD.END

Close of business date. Either the next working day minus one calendar day or the end of


Page 13 of 21

March 2004


month whichever is earlier. ACCOUNTING.STAGE JULIAN.DATE

CURRENT.DAY

NA This field is the date in TODAY held in the Julian format. The Julian format consists of the four-digit year followed by t he day in the year. Eg : The Julian value for 27th March 1986 is 1986086. 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 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 release 14 or above, then the you will find 2 dates records per company. Please refer to the ‘T24 NonStop’ or ‘Basic ‘ 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. The non-working weekend days are then generated generated automatically for the year and for 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 non-working days. ID : CountryCoderegionCod CountryCoderegionCodeYear eYear ID : IN002004 Field JANUARY

Description Contains the days of the month(Month name is the field name) that are to be holidays.

Eg. 1 10 17 31 1st,10th,17th and 31st of January are holidays. Multiple days can be defined as holidays by specifying multiple days delimited by spaces (as defined above). FEBRUARY

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for FEBRUARY.

MARCH

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

APRIL

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

MAY

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


Page 14 of 21

March 2004


for MAY. JUNE

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for JUNE.

JULY

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for JULY.

AUGUST

Has the Same purpose of the field ‘JANUARY’, ‘JANUARY’ , but holds the holidays for AUGUST.

SEPTEMBER

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for SEPTEMBER.

OCTOBER

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for OCTOBER.

NOVEMBER

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for NOVEMBER.

DECEMBER

Has the Same purpose of the field ‘JANUARY’, but holds the holidays for DECEMBER.

WEEKEND.DAYS

Contains the days that are to be declared as weekend days. Eg : SA (Saturday) SU (Sunday) Contains an entry for each day in the month (Month number is a part 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 st will be marked with a X).

MTH.01.TABLE

Eg.

MTH.02.TABLE MTH.03.TABLE MTH.04.TABLE MTH.05.TABLE MTH.06.TABLE MTH.07.TABLE MTH.08.TABLE MTH.09.TABLE MTH.10.TABLE MTH.11.TABLE MTH.12.TABLE


Same as MTH.01.TABLE, but holds the details of month February. Same as MTH.01.TABLE, but holds the details of month March. Same as MTH.01.TABLE, but holds the details of month April. Same as MTH.01.TABLE, but holds the details of month May. Same as MTH.01.TABLE, but holds the details of month June. Same as MTH.01.TABLE, but holds the details of month July. Same as MTH.01.TABLE, but holds the details of month August. Same as MTH.01.TABLE, but holds the details of month September. Same as MTH.01.TABLE, but holds the details of month October. Same as MTH.01.TABLE, but holds the details of month November. Same as MTH.01.TABLE, but holds the details of month December.

Page 15 of 21

March 2004


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 : IN0010001 Field COMPANY.NAME

Description Contains the name of the company being defined. Can be defined in multiple languages.

NAME.ADDRESS

Contains the name and address of the company being defined.

MNEMONIC

Contains the mnemonic of the company being defined. It is unique for each company and will be used as a prefix for FIN and CUS type of files.

LANGUAGE.CODE

Contains the language of T24 installed in the bank. Can contain valid values from the LANGUAGE application.

STAT.REP.AREA

Identifies the area to which the Statutory reports are to be sent. Will be printed in the header region of the statutory reports.

STAT.REP.NAME

Identifies the person to whom the Statutory reports are to be sent. Will be printed in the header region of the statutory reports.

STAT.REP.DELIV

Identifies the location to which the Statutory reports are to be sent. Will be printed in the header region of the statutory reports.

MGMT.REP.AREA

Identifies the area to which the Company Management reports are to be sent. Will be printed in the header region of the statutory reports.

MGMT.REP.NAME

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

MGMT.REP.DELIV

Similar to STAT.REP.DELIV but will apply to MI reports

CONSOLIDATION.MARK

Indicates whether the Company record has been set for consolidation 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

Contains the default number of authorisers for all applications in the bank. This can be overridden in Versions. Valid values : 0, 1 or 2

PGM.AUTOM.ID

LOCAL.COUNTRY LOCAL.REGION LOCAL.CURRENCY Temenos Training Publications T2BTT – R06 – 1.0

Contains the names of T24 applications that can automatically 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. Country in which the company is situated. NA Local currency of the bank. It is not mandatory to use the local Page 16 of 21

March 2004


RATE.SYSTEM

CUSTOMER.COMPANY CUSTOMER.MNEMONIC DEFAULT.CUS.COM DEFUALT.CUS.MNE SPCL.CUST.FILE

SPCL.CUST.COM SPCL.CUST.MNE DEFAULT.FINAN.COM DEFAULT.FINAN.MNE SPCL.FIN.FILE SPCL.FIN.COM SPCL.FIN.MNE CURRENCY.COMPANY CURRENCY.MNEMONIC FINAN.FINAN.COM FINAN.FINAN.MNE NOSTRO.COMPANY NOSTRO.MNEMONIC NOSTRO.SUB.DIV

INTER.COM.CATEGORY APPLICATIONS PARENT.COY.RES LOCAL.PROCESS.NAME Temenos Training Publications T2BTT – R06 – 1.0

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. Defines the rate system to be used. BUY.SELL.RATE SELL.BUY.RATE MID.REVAL.RATE Used for multi company environments. Defines the company that will hold the Customer information. Contains the mnemonic of the company defined in the field ‘CUSTOMER.COMPANY’ Indicates under which company the Customer table files(CUS tye)are maintained. Holds the mnemonic of the company defined in the field ‘DEFAULT.CUS.COM’. Indicates the name of customer table file (CST) which is to be maintained under a different company to the majority of the customer table files for this company. Indicates under which company the Special Customer table file is maintained. Indicates the mnemonic of the company defined in the SPCL.CUST.COM field. Indicates under which company the Financial Static table files are maintained for this Company. Contains the mnemonic of the company defined in the field DEFAULT.FINAN.COM Indicates the Mnemonic code for the company under which the Financial Static table files are maintained f or this Company. NA NA Indicates under which company the currency files are maintained for this company. Indicates the Mnemonic code for the company under which the currency files are maintained for this. Indicates under which company the Financial Financial table files are maintained for this Company. Indicates the Mnemonic code for the company under which the Financial Financial table files are maintained for t his company. Indicates which company maintains the Nostro accounts used by this company. Indicates the Mnemonic code for the company maintains the Nostro accounts used by this company. If Nostro accounts are maintained in another company then the Sub 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. Contains the category code to be used when inter company accounting entries are raised. Contains the various applications installed for the company being defined. NA This field specifies the name of the local Central Bank processing. Page 17 of 21

March 2004


DEFAULT.RATE.ALLOW FCY.CONV.TOLER.MIN FCY.CONV.TOLER.MAX CHARGE.CALCULATION

FINANCIAL.YEAR.END

INACTIVITY.MONTHS SUB.DIVISION.CODE

SWIFT.ADD.COM.REF LAST.YEAR.END DC.TOLERANCE.RATE DC.MAX.ROUND.AMT ACCT.CHECKDIG.TYPE ACC.BKNO.PREFIX ACCOUNT.MASK

BOOK RELATIVE.TIME SEPARATE.EOD CONS.KEY.CO COMPANY.GROUP OFFICIAL.HOLIDAY BRANCH.HOLIDAY BATCH.HOLIDAY BRANCH.CLOSED


Input to this field means that local Central Bank processing is to take place. must be the ID of an existing record on the file BANK.RETURN.PARAMS. Indicates the maximum variance allowed when inputting an exchange rate when no variance has been loaded on the currency record. Indicates the variance allowed when checking the conversion of amounts for which no override will be requested. Indicates the variance above which when checking the conversion of amounts for which no override will be allowed. Indicates the calculation period for charges. Valid values : M = Monthly Q = Quarterly S = Six monthly Indicates the calculation period for charges. This is the next financial year end with a twelve month frequency cycle. So at the end of each year the next year year end can be calculated. Previous year end is stored in LAST.YEAR.END. Indicates the number of months without customer activity before an account is declared as inactive. Indicates the sub division code allocated to this company. This code is used when building the internal account number for inter company accounting. This happens when Nostro Accounts are maintained in one company for use by other companies. Specifies the 6 characters of the S.W.I.F.T address to be used as part of the common reference for this company. Specifies the last year-end of the company being defined. Used by DC. Used by DC. Identifies the check digit calculation method for the company being entered. Identifies, in countries like l ike Belgium and Luxembourg, the Bank Prefix which is part of the local account number. Contains the format of the account number in the company being defined. Eg : ####-#### Every hash denotes a character. Any special character (Like ‘-‘ as specified above) that needs to be part of the account number needs to be defined here. The account mask for internal accounts is hard coded. NA NA Used with the GP (Global Processing) product. Used with the GP (Global Processing) product. Used with the GP (Global Processing) product. Used with the GP (Global Processing) product. Used with the GP (Global Processing) product. Used with the GP (Global Processing) product. Used with the GP (Global Processing) product.

Page 18 of 21

March 2004


SPF SPF stands for ‘SYSTEM PARAMETER FILE’. This file, as the name denotes is the parameter file for the entire T24 and is one of the first files to be setup in a T24 installation. This file holds the details of the system wide parameters that are required to run the T24 system. This file will and can contain only ONE record with the ID ‘SYSTEM’. Field RUN.DATE

Description Contains the system date on which the last EOD was run. Not applicable for T24 release 14 and above.

SITE.NAME

Name of the company

OP.MODE

Contains the mode of the company. O – Online B – Batch R - Recovery Not applicable for T24 releases 14 and above. For T24 releases 14 and above, the CO.BATCH.STATUS field in the DATES record for the company being defined is used to obtain the status of the company.

OP.CONSOLE

Specifies the terminal numbers that will serve as operator consoles to receive any messages from the system. The t erminal numbers entered here will receive any critical error messages sent out by the T24 system.

MAIN.ACCOUNT

Contains the name of the directory where all the data files of T24 are stored. This will act as the main account of the company.

BACKUP.CYCLE.1

Specifies the backup areas and backup devices for the start of day backup. This field should contain the names of the start of day backup areas on on disk disk corresponding corresponding to the list of accounts specified in MAIN ACCOUNT. Not applicable for T24 releases 14 and above as backup is not part of COB.

BACKUP.CYCLE.2

Specifies the backup areas and backup devices for the start of batch backup. This field should contain the names of the start of batch backup areas on disk corresponding to the list of accounts specified in MAIN ACCOUNT. Not applicable for T24 releases 14 and above as backup is not part of COB.

CURRENT.RELEASE

Contains the current release of T24.

HIST.LIFE

Specifies the number of days a record can remain in the history file before it can be deleted.

BREAK.KEY.NUMBER

Specifies the ascii number of the break key. Eg. P would be ascii character 16.

CATALOG

Provides the option to locally catalog the T24

programs.

Used only when the database used is i s universe. ENQ.PAGE.LIMIT Temenos Training Publications T2BTT – R06 – 1.0

The maximum number of pages that can be displayed when an enquiry is executed in T24. This value only restricts the number of Page 19 of 21

March 2004


pages that can be viewed in T24 but not the number of pages that can be printed RECV.DATE.TIME

SYS.ABCKUP.MODE HOLD.BATCH.OUTPUT

MICROFICHE.OUTPUT REPORT.RETENTION RESTRICT.RPT.VIEW

DATA.ACC.NAME RUN.ACC.NAME DICT.ACC.NAME AUTO.MANUAL.BATCH

OPERATING.SYSTEM UNIX.BACKUP

UNIX.RESTORE

PRODUCT.ACCOUNT

HELP.RPT.RETENTION

CACHE.SIZE MASTER.ACCOUNT PREVIOUS.RELEASE PATCH.INSTLD BATCH.SESSIONS Temenos Training Publications T2BTT – R06 – 1.0

Indicates the date and time (seconds since midnight) on which the last system recovery was done. Not applicable for T24 releases 14 and above. The default media that is to be used to take a backup during EOD. Not applicable for T24 releases 14 and above. If this flag is set to 'Y' then all output from the batch is stored in the HOLD file. This can be printed (in sorted order) by using the SPOOL.BATCH.OUTPUT application. Default value : NO Specifies the number of days after which a report will be removed from the hold file &HOLD&. Restricts the reprint and view of reports to those received at end of day.If this is set a user will only be allowed to reprint or view reports which he specifically receives from the end of day run.This is in addition to any SMS controls applied to the HOLD.CONTROL application. Specifies the directory where the data files are stored. Usually set to ‘bnk.data’ Specifies the directory that is to be used as the home directory of the user. Usually set to ‘bnk.run’ Specifies the directory where all the dictionary files are to be stored. Usually set to ‘bnk.dict’. Not applicable for T24 releases 14 and above. above. Used for EOD purposes. When set to ‘AUTO’, it will suffice if the user initiates the EOD, the ‘Auto Batch’ and ‘Start Online’ will be automatically completed. If set to ‘MANUAL’, the Contains the operating system on which T24 is installed. Unix system backup commands to be used for BACKUP.CYCLE.1 and BACKUP.CYCLE.2 should be entered in this field. Please refer to ‘End Of Day’ section of the ‘Basic Technical Training’ material for detailed explanation and examples on this. Unix system restore commands to be used for BACKUP.CYCLE.1 and BACKUP.CYCLE.2 should be entered in this field. Please refer to ‘End Of Day’ section of the ‘Basic Technical Training’ material for detailed explanation and examples on this. Specifies the data account for specific products. Defaults to the data account name (field 19). If any products are held on separate data accounts they may be specified here. Specifies the number of days after which a report that has been spooled and held will be removed from the hold file, the customer held file, and the &HOLD& file. If this field is set to null the number of days will default to the standard report retention (REPORT RETENTION). This value will be overridden by the value set up in the REPORT.CONTROL record for the report if a value has been entered. Specifies the cache size to be used within the T24 system for record writes. NA Contains the last release installed in this account. this field contains the numbers of any patch releases which have been installed, when interim patch releases have been missed out. Used in conjunction with the T24 GUI End of Day process, this field Page 20 of 21

March 2004


COMP.MNE.CCY MIN.ROUNDING NON.2DEC.CCY LICENCE.CODE MAINTENANCE.DATE MAINTENANCE.CODE PRODUCTS PRODUCT.CODES EXTENDED.PREC

SOURCE.RELEASE NO.OF.USERS USER.CODE TXN.MANAGEMENT

TIMEOUT.MODE

AUTOLOG.TIME.MINS

PWD.REPETITION

POS.MVMT.HIST DATABASE.TYPE GAC.ACCOUNT DATE.TIME.MV PRE.BATCH.ROUT Temenos Training Publications T2BTT – R06 – 1.0

specifies the number of sessions which will run the end of day process. NA NA NA Specifies your license code code for T24. Specifies the date on which your maintenance contract is due for renewal. Code required to enable maintenance date to be amended. Specifies all the T24 products which have been installed. Code required to enable a new product to be added. This field specifies whether extended precision (string maths)is being used. This increases the length length of amount fields to allow up to 14 integers. Extended precision can only be used if the revision of universe is rev 8.3.3.1b or above. Not applicable for other databases. Specifies whether source releases are required or not. Used only by T24 release lesser than or equal to 8. Specifies the number of users for which T24 is licensed. Code required to enable a new product to be added. If set to ‘’ it denotes that transaction management is on. This will ensure that all database transactions fall within a transaction block. Can set it to ‘OFF’ ‘OFF ’ to stop transaction management. Defines whether users are automatically signed off the system after the specified time out period is exceeded, or whether sign off occurs at the next input. Valid Values : ACTIVE : Will cause the automatic sign off of a user after the TIME.OUT.MINUTES specified in the USER profile during normal processing or after the AUTOLOG.TIME.MINS if defined in the SPF record. The AUTOLOG.TIME.MINS only becomes effective during the authorisation/validation phase of the transaction. PASSIVE(or ‘’) : Will sign the user off if the TIME.OUT.MINUTES specifed in the user profile is exceeded, at the NEXT input made by the user. There is no distinction made between the authorization / validation phase and normal processing. Defines the time a user may be inactive during the authorisation/validation phase of a transaction before the user is timed out. The authorisation/commit phase inactivity is only considered when ACTIVE TIMEOUT.MODE is selected. Defines the time a user may be inactive during the authorisation/validation phase of a transaction before the user is timed out. The authorization / commit phase inactivity is only considered when ACTIVE TIMEOUT.MODE is selected. Minimum Value : 3 Specifies how many days history of position movement entries are to be maintained. Used by GAC Used by GAC. NA Can specify a routine. EOD : Gets executed once you choose 8 (Initiate EOD) Page 21 of 21

March 2004


ACTIVE.USER.BATCH PASS.MIN.LENGTH PASS.UPPER.ALPHA PASS.LOWER.ALPHA PASS.NUMERIC PASS.OTHER VERSION.AUTH.CTRL EVENT.SERV.LVL EVENT.SERV.TYPE INFO.JOURNAL BROWSER.REC.LOCK

COMMIT.TIME.OUT MIN.PASSWORD.DAYS GLOBAL.PROCESS

SERVICE.PCK.INSTLD


COB : Gets executed as the first job of COB BATCH ID : COB.INITIALISE BATCH STAGE : A000 NA NA NA NA NA NA NA NA NA NA To be used only when the front end used in Browser. When set to ‘YES’, will enable locking information being written into F.RECORD.LOCK file. NA NA Used for GP(Global Processing) module. If set to ‘YES’ will allow a specific/group of companies to execute COB while other companies are still online. Contains the service packs installed.

Page 22 of 21

March 2004

2.T24DirectoryStructureAndImportatntFilesInGlobus

Recommend Documents