T24 Directory Structure And File Classification

TEMENOS EDUCATION CENTRE

Warning: This document, 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 HEADQQATERS SA. 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.

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

Version History
Version 1.0 1.1 1.2 1.3 1.4 Changes Initial Browser Changes Layout, file type and field highlight changes Changes Holiday changes. File classification corrections. Addition of explanation of all core parameter tables. Date 2004 2005 14-Sept-2006 2007 2007 Author Alagammai Sara Cleur Alagammai B.Nandakumar Alagammai Reviewer

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

What You Will Learn In This Session T24 directory structure File types in T24 File classification in T24

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

T24 Directory Structure

bnk bnk.data ac fx bnk.dict eb globusbin bnk.run globuslib bin bnk.help lib bnk.jnl bnk.backup

bnk is the parent directory bnk.data : Holds all the data files of T24. Contains subdirectories. Each of the subdirectories refer to the various products installed. Data files of applications are stored under the appropriate subdirectories bnk.dict : Holds all the dictionary files of all applications in T24 bnk.run : Home directory for all t24 users. Contains globusbin, globuslib which store the business logic of T24. Bin and lib are used to store any local dev business logic bnk.help : Directory where help files are installed bnk.jnl : Holds the F.JOURNAL file which is an application level log file that captures all data input in T24. Only the last 20 transactions data are stored in this file. Journaling is achieved by using jBASE Transaction Journaling if j4 is the database. bnk.backup : If desired, backup of T24 can be stored here.
GEN4 2007.1 Copyright 2006 TEMENOS HEADQUATERS SA
4

Workshop

List the VOC entry for the FBNK.CUSTOMER file. Check if the data file and the dict file are available in the path specified

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

File Types
User inputs and commits a record in the CUSTOMER application File that gets updated : FBNK.CUSTOMER$NAU User authorizes the record in the CUSTOMER application Files that get updated
Record deleted from FBNK.CUSTOMER$NAU Record written to FBNK.CUSTOMER

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

File Types
User amends the authorized CUSTOMER record (Record becomes unauthorised again) Files that get updated
Record written to FBNK.CUSTOMER$NAU (Amended record) The authorized record remains in the FBNK.CUSTOMER file

User authorizes the amended CUSTOMER record Files that get updated
Record deleted from FBNK.CUSTOMER$NAU Amended record written to FBNK.CUSTOMER Previously authorized record moved to FBNK.CUSTOMER$HIS

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

File Types (Cont.) Valid file types

Live file Holds only authorised records Unauthorised file ($NAU)
INAU,INAO,INA2,RNAU,RNA2, CNAU,CNA2, RNAO,IHLD

History file ($HIS) Holds copies of authorized records

ID format : <Record ID>;<Sequence Number>

Most of the applications support all the 3 types of files

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

File Types
List authorized CUSTOMER records
jsh..>LIST FBNK.CUSTOMER

List unauthorised CUSTOMER records

jsh..>LIST FBNK.CUSTOMER$NAU

List CUSTOMER history records

jsh..>LIST FBNK.CUSTOMER$HIS

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

Workshop

List the VOC entry for the CUSTOMER applications unauthorized and history file and check if the files are available in the specified location. From the jsh prompt, list the contents of ACCOUNT applications unauthorized file.

GEN4 2007.1

Copyright 2006 TEMENOS HEADQUATERS SA

10

File Classification
Assumption : CUSTOMER files are stored at individual branch level Customer of Branch 1 walks in to Head Office to perform a transaction
All files have the same name ??????

Head Office
CUSTOMER FBNK.CUSTOMER FBNK.ACCOUNT F.COMPANY

Branch 1
FBR1.CUSTOMER CUSTOMER FBR1.ACCOUNT

Branch 2
FBR2.CUSTOMER CUSTOMER FBR2.ACCOUNT

Branch 3
FBR3.CUSTOMER CUSTOMER FBR3.ACCOUNT

CUS One file per branch or one file to store data for all branches. Support sharing of information between branches. Have company mnemonic as prefix FIN Files that can hold financial information. One file per branch. Do not support sharing of information between branches. Have company mnemonic as prefix INT Files that hold installation information. Only one file irrespective of the number of branches. All branches will be able to access the files
GEN4 2007.1 Copyright 2006 TEMENOS HEADQUATERS SA
11