1

1Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

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.

2

2Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

Version History

Alagammai2004Initial1.0

Sara Cleur2005Browser Changes1.1

Alagammai14-Sept-2006Layout, file type and field highlight changes

1.2

B.Nandakumar2007Changes1.3

Alagammai2007Holiday changes. File classification corrections. Addition of explanation of all core parameter tables.

1.4

ReviewerAuthorDateChangesVersion

3

3Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

What You Will Learn In This Session

T24 directory structure

File types in T24

File classification in T24

4

4Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

T24 Directory Structure

ac fx eb

bnk.data bnk.dict

globusbin globuslib bin lib

bnk.run bnk.help bnk.jnl bnk.backup

bnk

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.

5

5Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

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

6

6Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

File Types

User inputs and commits a record in the CUSTOMER applicationFile that gets updated : FBNK.CUSTOMER$NAU

User authorizes the record in the CUSTOMER applicationFiles that get updated

Record deleted from FBNK.CUSTOMER$NAURecord written to FBNK.CUSTOMER

7

7Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

File Types

User amends the authorized CUSTOMER record (Record becomes unauthorised again)

Files that get updatedRecord written to FBNK.CUSTOMER$NAU (Amended record)The authorized record remains in the FBNK.CUSTOMER file

User authorizes the amended CUSTOMER recordFiles that get updated

Record deleted from FBNK.CUSTOMER$NAUAmended record written to FBNK.CUSTOMERPreviously authorized record moved to FBNK.CUSTOMER$HIS

8

8Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

File Types (Cont.)

Valid file typesLive file – Holds only authorised records

Unauthorised file ($NAU) INAU,INAO,INA2,RNAU,RNA2, CNAU,CNA2, RNAO,IHLD

History file ($HIS) – Holds copies of authorized recordsID format : <Record ID>;<Sequence Number>

Most of the applications support all the 3 types of files

9

9Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

File Types

List authorized CUSTOMER records

List unauthorised CUSTOMER records

List CUSTOMER history records

jsh..>LIST FBNK.CUSTOMER

jsh..>LIST FBNK.CUSTOMER$NAU

jsh..>LIST FBNK.CUSTOMER$HIS

10

10Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

Workshop

List the VOC entry for the CUSTOMER application’s unauthorized and history file and check if the files are available in the specified location.

From the ‘jsh’ prompt, list the contents of ACCOUNT application’s unauthorized file.

11

11Copyright © 2006 TEMENOS HEADQUATERS SAGEN4 – 2007.1

File Classification

Head Office

Branch 3Branch 2Branch 1

Assumption : CUSTOMER files are stored at individual branch level

Customer of Branch 1 walks in to Head Office to perform a transaction

CUSTOMER

CUSTOMER CUSTOMER CUSTOMER

All files have the

same name

?????? FBNK.CUSTOMER

FBR1.CUSTOMER FBR2.CUSTOMER FBR3.CUSTOMER

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

FBNK.ACCOUNT

FBR3.ACCOUNTFBR2.ACCOUNTFBR1.ACCOUNT

FIN – Files that can hold financial information. One file per branch. Do not support sharing of information between branches. Have company mnemonic as prefix

F.COMPANY

INT– Files that hold installation information. Only one file irrespective of the number of branches. All branches will be able to access the files