T24 Directory Structure bnk
bnk.data
ac
fx
bnk.dict
eb
globusbin
bnk.run
bnk.help
globuslib
bin
bnk.jnl
bnk.backup
lib
bnk.data
: the directory where the data files of all applications are stored.
bnk.dict
: the directory where the dictionary files of all applications are stored.
bnk.help
: the directory where all the help files are stored
bnk.jnl
: this directory contains a very important file of T24 called F.JOURNAL which will hold the mirror of every transaction in T24. The life cycle of this file is 1 day.
bnk.run
: this is the home directory of all users who log on to T24. This directory contains an important file called .profile and 4 very important directories – (1) globusbin (T24 executables), (2) globuslib (T24 libraries), (3) bin (local executables), and (4) lib (local libraries)
bnk.backup
: this directory contains files pertaining to the pre EOD and post EOD backups.
GLOBUS.BP : this directory contains a number of insert files that are used in programs or subroutines. File Types:
Live Unauthorised ($NAU) – INAU, INAO, INA2, RNAU, RNA2, CNAU, CNA2, RNAO, IHLD History ($HIS)
File Classification:
INT (Installation) o Only a single copy of the file exists regardless of the number of companies
o o o
These files are stored in Head office and will be accessed by all the branches. Examples : ABBREVIATION, ACCOUNT.CLASS, BATCH, CATEGORY, etc. Prefix F
CUS (Customer) o These files are stored in Head office and will have the company mnemonic as the prefix. o Examples : BROKER, COLLATERAL, CONDITION.PRIORITY, CUSTOMER, etc. o These files are shared among the branches. o These files can be stored at each branch in which case they can not be shared. o These files primarily contain static data
CST (Customer Table) o Check files for CUS level files o Examples : SECTOR, TARGET, INDUSTRY, CUSTOMER.STATUS etc. o Inherit properties of CUS files
FIN (Financial) o Store financial information. o Each branch has its own copy. Can not be shared. o Examples : ACCOUNT, ACCOUNT.CLOSURE, ACCOUNT.DEBIT.INT, FUNDS.TRANSFER, etc. o Prefix : Branch Mnemonic
FTD (Financial Table Descriptive) o Check files for FIN level files o Examples : BASIC.INTEREST, GROUP.CONDITION, DEAL.SLIP.PARAMETER, etc. o Contain non financial data o Inherit properties of FIN files
FTF (Financial Table Financial) o Linked to FIN files and contain financial data o Examples : GROUP.DEBIT.INT, TXN, FT.CHARGE.TYPE, FT.COMMISSION.TYPE, etc. o Inherit properties of FIN files
CCY (Currency) o Currency associated files o Examples : CURRENCY, PERIODIC.INTEREST, FORWARD.RATES, etc. o Inherit properties of INT files
NOS (Nostro) o Files for Nostro accounts o Examples : NOSTRO.ACCOUNT, NOSTRO.BALANCES, AGENCY, etc. o Inherit properties of CUS files
CORE PARAMETER FILES PGM.FILE
Stands for Program File
This is the application that keeps track of all the applications in T24
Every application in T24 must have a valid entry in this file
Important fields are: o
ID
o
TYPE
No special characters allowed except ‘.’
H (unauthorized, live and history files will be maintained. Example - CUSTOMER) U (similar to H but history is not maintained. Example ABBREVIATION) L (displays data of live files but does not allow updates. Updates will be controlled by System automatically. Example – STMT.ENTRY) T (displays data of table file but does not allow updates. Example – LMM.CUSTOMER) W (permits updates to a work or temporary file. Example – REPGEN.OUTPUT where print or display parameters for a report can be loaded) B (batch job that can only be accessed during off-line processing in BATCH.CONTROL) M (main-line program. No file directly associated with it.) S (subroutine)
o
ADDITIONAL.INFO .NOH (no hold facility after 1st input) .GUI (application can run under GUI) .NOG (application can not be run under GUI)
o
BATCH.JOB Identifies batch jobs. Used only where TYPE = B
o
PRODUCT Valid product name Alternatively valid subdirectories under bnk.data
o
APPL.FOR.SUBR Used when defining version routines
o
BATCH.LIST.MAXIMUM Maximum number of IDs that can be stored in a LIST file Used only where TYPE = B
FILE.CONTROL
FILE.CONTROL as the name implies controls the type of information that can be stored in an 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 FILE.CONTROL application.
Important fields are: o
ID
No special characters allowed except ‘.’ Must match an equivalent entry in PGM.FILE
o
SUFFIX $NAU, $HIS
o
FILE.TYPE Used only if database is universe.
o
MODULO Used only if database is universe.
o
SUB.PRODUCT N/A
o
SYS.CLEAR.FILES Y or N Y denotes that the contents of the application can be cleared when the SYSTEM.CLEAR.FILES is executed.
o
CUS.CLEAR.FILES Obsolete
STANDARD.SELECTION
Each application in T24 has two parts, namely Data and Dictionary. The data part contains all the records whereas the dictionary part contains the field names and their definitions.
Example : o FBNK.CUSTOMER (data file)
o o o
FBNK.CUSTOMER$NAU (data file) FBNK.CUSTOMER$HIS (data file) F.CUSTOMER]D (dictionary file)
Dictionary files will always have the prefix ‘F.’
There will be one copy of the dictionary irrespective of the number of branches.
STANDARD.SELECTION application contains this dictionary part. It not only contains the core fields but also the definition of all local reference fields.
The fields in the STANDARD.SELECTION record are split into two parts System and User defined. All the system (T24) defined fields begin with SYS and cannot be modified. The user defined fields begin with USR.
Important fields are : o o o o o o o o o o o o o o o o o o o o o o o o
SYS FIELD NAME SYS TYPE SYS FIELD NO SYS VAL PROGRAM SYS CONVERSION SYS DISPLAY FMT SYS ALT INDEX SYS INDEX FILE SYS INDEX NULL SYS GENERATED SYS REL FILE USR FIELD NAME USR TYPE USR FIELD NO USR VAL PROGRAM USR CONVERSION USR DISPLAY FMT USR ALT INDEX USR INDEX FILE USR INDEX NULLS USR CONV TYPE USR REL FILE REBUILD SYS FIELDS DEFAULT ENRICHMENT
DATES
It is of type INT and hence only 1 copy of the file will be available.
T24 maintains its own date and does not go by the system date
This application will contain one record per company and the ID will be the company code
Important fields are : o TODAY (T24 System date) o LAST.WORKING.DAY o NEXT.WORKING.DAY o BACK.VALUE.MINIMUM o BACK.VALUE.MAXIMUM o FORW.VALUE.MINIMUM o FORW.VALUE.MAXIMUM o CO.BATCH.STATUS ( O – Online, B – Batch/COB in progress) o PERIOD.END (Next working day – 1 calendar day or end of the month whichever is earlier) o JULIAN.DATE
During COB Process, values in TODAY, LAST.WORKING.DAY and NEXT.WORKING.DAY change.
When COB initiated, value in CO.BATCH.STATUS is changed from O B.
COB updates as follows: o LAST.WORKING.DAY = TODAY o TODAY = NEXT.WORKING.DAY o NEXT.WORKING.DAY = value from HOLIDAY file.
In T24 two date records per company is available.
By use of the User Profile limited access to this record should be maintained.
HOLIDAY
This application holds the values to indicate public holidays for each country for calendar years.
Users need to input public holidays except the dates for the weekend.
Weekend days are defined only and the system will generate those dates as holiday automatically.
Each T24 application will check this application during date validation.
ID format is : o
<2 uppercase alpha country code> <1-2 numeric region code> <4 digit year>
The REGION and COUNTRY tables must be set up before this table can be created.
COMPANY
The Company file contains details of the Company's name, the Mnemonic (by which all the files maintain at this company's level are prefixed), the file classification details, the applications to be run and Company level defaults and parameters. This is an INT type file and hence there will be only 1 copy of this file.
The Reverse (R) function is not allowed for a company record.
Important fields are: o
CONSOLIDATION.MARK Indicates whether the Company record has been set for consolidation purposes only, or the company is a full processing company. A value of N indicates that the company is a live processing company and was created within installation of a new company routine. The value of 'N' may not be entered manually into a new Company record. In this respect, the record must be loaded through the installation process as described in the Overview. A value of C indicates that the company is for consolidation only and that it was created through the normal running of the application Company. If C (consolidation), no further data is allowed in this Company record. Any further input will be systematically refused. A value of R indicates that the company has been created for reporting purposes within installation of a new company routine. If R (Reporting), no further data is allowed in this company record except for fields CURRENCY, COMPANY and APPLICATIONS. Mandatory input. Cannot be changed.
o
DEFAULT.NO.OF.AUTH 0, 1 or 2 This value can be overridden in Versions
o
PGM.AUTOM.ID Names of T24 applications that can be automatically generate IDs.
o
RATE.SYSTEM Indicates whether the Buy and Sell Rates or the Middle Rate will be used for entering exchange rates into the system.
o
BUY.SELL.RATE means that the Buy and Sell Rates are entered and the Middle rates are calculated. MIDDLE.RATE means that the Middle Rates are entered and the system uses the Spread rates to calculate Buy and Sell rates.
CUSTOMER.COMPANY Used for multi company environment Defines the company which will hold the Customer information
SPF
Stands for System Parameter File Is the parameter file for the entire T24 This file will contain only one record with the ID ‘SYSTEM’ Important fields are: o MAIN.ACCOUNT o CURRENT.RELEASE o HIST.FILE o ENQ.PAGE.LIMIT o HOLD.BATCH.OUTPUT o REPORT.RETENTION o DATA.ACC.NAME o RUN.ACC.NAME o DICT.ACC.NAME o OPERATING.SYSTEM o CACHE.SIZE o PATCH.INSTLD o MAINTENANCE.DATE o MAINTENANCE.CODE o PRODUCTS o PRODUCT.CODES o NO.OF.USERS o TIMEOUT.MODE o AUTOLOG.TIME.MINS o PWD.REPETITION o SERVICE.PCK.INSTLD
