6_GEN4 T24DirectoryStructureAndFileClassification-R10 01.pdf

Welcome to the “T24 Directory Structure and File Classification” learning unit. This learning un t w tea teac you t e rect rector ory y str structu ucture re an t e con content tents s o some some mpo mportan rtantt rect rectores ores t at are created when you install T24. It will also teach you the various application classifications in relationship to the files that store st ore data at database level.

GEN4-T24 Directory Structure and Application Classification-R09.01

1

Trusted by over 1 million members

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.













After completion of this learning unit, you will be able to: xpa n t e rectory str structur ture o an t e erent c ass cat ons o app cat ons n















When you install T24, it creates a directory structure similar to the one you are looking at. , . directories that you must know about will be discussed. bnk is the name of the parent directory of T24. There are 5 important sub-directories under under it which you must know of. T24 uses J4 files to store its data in. As you know, a J4 file is made up of a Data file f ile and a DICT (Dictionary (Dictionary)) file. Note: The client can decide which files to t o convert to JR if required. m ultiple bnk.data : This directory stores the data files f or all applications in T24. There are multiple sub-directories that represent the different products in T24. Data files for applications are stored under the appropriate subdirectories. Examples of subdirectories are AC for the Account product, FX for the FOREX product, EB for the T24 core and so on T 24. There are no bnk.dict : This directory stores the dictionary files for all applications in T24. further subdirectories here. hom e directory for all T24 users. It contains the sub directories t24bin, bnk.run : This is the home t24lib, bin and lib. For any software a bin directory executables and a lib directory library f iles. The sub-directories t24bin and t24lib t24lib holds T24’s core executables executables and libraries whereas the















Data which is entered into T24 applications are stored in Files at database level. 1. At database level these files are broadly classified into three different categories. They are Live files, Unauthorized files and History files. 1.1 Live files store only authorized records. There will be no Record Status for records in Live files. 1.2 Unauthorized files ($NAU) store unauthorized records. There are various Record Statuses that can be associated with records in Unauthorized Files. The Record Statuses are: INAU – Input Not Authorized IN A O – Input Not Authorized due to Overrides INA2 – Input requires Second Authorizer RNAU – Reversal Not Authorized RNA2 – Reversal requires second Authorizer R NAO – Reversal Not Authorized awaiting Overrides HNAU – History Not Authorized IHLD – Input on HOLD. 1.3 History files ($HIS) store old copies of authorized records. When an authorized record is edited and the changes authorized, authorized, the latest version of the record is stored in the Live file f ile and the old version is moved to the History file. If an authorized record is reversed and the reversal authorized, that record too moves from the Live file to the History file. The T he Record Status of a reversed record is REVE.















T24 application records might have different statuses at different points in their life cycle. or t s pur purpose pose,, app app cat cat ons ons ave mu t p e es at ata ata ase ase eve eve to stor store e t ese ese records based on their statuses. When you input and commit a record in the CUSTOMER CUSTO MER application, the record is stored in the unauthorized file CUSTOMER$NAU.















When a CUSTOMER record in INAU status is authorized, the record is deleted from t e unaut or ze e an wr tten to t e ve e.

















When you edit an existing authorized CUSTOMER record, this am ended copy of the record s wr tten to t e unaut or ze e w en comm tte . e aut or ze copy of this record still remains in the Live CUSTOMER file. At this point in time tim e it is important im portant to understand that if you request for the record using the Input or Authorize function, T24 returns the record from the $NAU f ile. If you request for this record using the See function, T24 return the record from the Live CUSTOMER File.

















When you authorize the record currently in $NAU it is deleted f rom CUSTOMER$NAU and wr tten to t e ve e. e prev ous y aut or ze recor w e mov move to History that is the CUSTOMER$HIS file in order to keep a trail of all changes to the record.

















Depending in which file (that is Unauthorised / Live / History) a record is present in, you must use erent unct ons to v ew t. Viewing data from the GUI is pretty simple. You m ust use an appropriate function depending on the record status. The alternate way to list the CUSTOMER (or any application) records is to do a listing from the jBASE SHELL prompt as follows: To list LIVE Customer records

















1.

Do you you think the the LIST LIST command without without FBNK will will give you you the require required d output? output? No. It w not wor w t out .

2.

What does does FBNK FBNK stand stand for for and and Why is it impor importan tant? t?

















To understand the naming conventions of files at database level that T24 Applications use, you mus must rst un erstan ow pp cat ons are c ass e .



















1. All banks will have branches. In T24 a branch is referred to as company. T24 supports the



















1. When you install T24, the bnk.data directory already contains a set of f iles to store



















This is the contents of the T24 bnk.data directory when only the Master Company is present.



















Now when we add another company, a new set of f iles get created. But, how can you have



















So in order to differentiate one Company file set f rom another, the Company Mnemonic is













































































































































































































































































































































































































6_GEN4 T24DirectoryStructureAndFileClassification-R10 01.pdf

Recommend Documents