CoreParameterFiles - Part I-R10.01

8/19/2019 CoreParameterFiles - Part I-R10.01

http://slidepdf.com/reader/full/coreparameterfiles-part-i-r1001 1/21EN5.CoreParameterFiles - Part I-R09.01

1. Welcome to “The Core Parameter Tables in T24” learning unit. This learning unit

will teach you the importance of Core Parameter Tables in T24.


http://slidepdf.com/reader/full/coreparameterfiles-part-i-r1001 2/21EN5.CoreParameterFiles - Part I-R09.01

After completing this learning unit/course, you will be able to:

Explain the need for the following Core Parameter Tables in T24

PGM.FILE

FILE.CONTROL

STANDARD.SELECTION


http://slidepdf.com/reader/full/coreparameterfiles-part-i-r1001 3/21

1. What is T24 made up of?

2. T24 is made up of number of applications

and tables that work together. The coreparameter tables to be discussed in thislearning unit act more like indexes rather thanparameter tables.

3. Core Parameter Tables will be set up for anysoftware for it to function. Such tables will be

referred to at any point in time.

3.1 PGM.FILE

3.2 FILE.CONTROL

3.3 STANDARD.SELECTION

EN5.CoreParameterFiles - Part I-R09.01



1. PROGRAM FILE stands for PGM.FILE. Any thing that T24 needs to understandshould have an entry in this table. 2. All applications and routines that needs to beexecuted in T24 should have an entry in this table. It is an index of all applications androutines.

3. PGM.FILE is INT type of file and therefore the file name at database level isF.PGM.FILE (as this file is not company specific).

4. ID of a record in PGM.FILE is Application name or Routine name.

For example, CUSTOMER, FUNDS.TRANSFER, VERSION, etc.,.




As you already know, anything that T24 needs to understand should have an entry in the PGM.FILE. Therefore all

the applications or routines executed in T24 will have a record in this table. The record ID will be the name of the Application or the Routine.

Applications in T24 have multiple files associated with it at database level. For example an application likeCUSTOMER has a LIVE, $NAU and $HIS file. The information about what type of files are stored at the databaselevel is specified in the following field.

TYPE : This field specifies the type of data an application can store. Different types available in T24 are A B D H LM O R S T U V W. However, irrespective of the type mentioned in this file, all applications store Live records. Livefiles are updated on authorizing a record.

Type A denotes Access to T24 environment. A routine of this type can actually determine whether we are workingon the CUI or GUI interface of T24 and allow it to behave accordingly. There is only one entry in the PGM.FILE withtype A, called "EX“.

Type H denotes that the application can store the Unauthorized and History files. The Unauthorized file is updatedon inputting a record and the History file is updated on authorizing a reversed record. Example: CUSTOMER

Type L denotes that an application stores data of live files but does not allow updates. Updates to these files wouldbe controlled by the System automatically. Example: STMT.ENTRY

Type U denotes that a program can store only Unauthorized files. Example: ABBREVIATION

Type T denotes Concat files which stores only Live records. A program that displays data in a table file but does

not allow any input. Data in such files is updated by T24. Example: CUSTOMER.ACCOUNT

Type W denotes that an application supports Verify function. This type of applications store only Live files but unlikeT type of applications, user is allowed to update a file. Example: DL.DEFINE

Type B denotes a Batch job that can only be accessed during the 'off-line' processing in BATCH.CONTROL.Signifies a routine that gets executed as a part of COB.

Type S denotes Subroutine. A program used in the T24 system but one that is executed automatically wheneverrequired. It cannot be entered by the User either at the command line or from within the Batch Control system. It isrecommended that these are loaded only when they are needed by the report generator. Example: IN2.

Type M denotes Main-line programming. This type is set for Routines that can be run from the command line buthas no file directly associated with it. These routines does not store any data. Example: BATCH.CONTROL

Type R denotes Report Generator routine. There is an application in T24 named REPGEN which will be used togenerate reports after executing routines that will gather data. These routines are set to TYPE R in PGM.FILE.

Type D denotes Dynamic applications. Every application in T24 should have associated code executing in the back

ground. T24 allows the user to create his own applications without writing a single line of code. All that you will haveto do is describe the fields and the properties of the application and T24 will generate the associated code.

Type V denotes a routine to pass mandatory parameters for the program. This parameter is given inthe ADDITIONAL.INFO field. This is almost similar to that of Type S. EN5.CoreParameterFiles - Part I-R09.01



Type O is obsolete and not used.




The Bank may want a different name to be displayed on the title bar when the corresponding application islaunched. T24 offers this flexibility to the Bank.

ADDITIONAL INFO : This field defines any special attributes or characteristics that an application or batchroutine can have. The values that this field can hold are as follows.

.IDA stands for auto id generation which add one for the next record ID.

.NOD denotes no dates checking required - For example applications like BATCH ,PGM.FILE can be modified both during COB as well as Online.

.GUI implies that the application can run under GUI.

.NOG implies that the application cannot be run under GUI.

.BDA is not a valid input.




Some other values which the ADDITIONAL INFO filed can hold are

.NO! stands for no level down processing

.NOH stands for no hold facility after 1st input.

.PAR stands for parameters to be passed for report records.

.NOFS tells that the application cannot be run in OFS.

.UNP states that the application will be taken for generic unauthorized processing.

.OEU is OFS End of Day Update which means that update is allowed via OFS duringend of day.

.NUH states that the INAU records will not be put on HOLD by unauthorizedprocessing.

.NTX tells the system that the particular service need not be bound within a transactionboundary.




BATCH.JOB : This field is used only if the TYPE field holds the value of B or R. Thevalue in this field identifies the Batch job or the Routine to be called when the programis being executed respectively. If the value in this field is @BATCH.JOB.CONTROL orit is NULL then the routine is a multi threaded routine and if the value is @<name of

the routine> then it is a single threaded routine.

Data files of the application are stored in one place in the bnk.data directory. Thename of the sub directory is mentioned in the following field.

PRODUCT : This field holds the name of the sub directory under the bnk.datadirectory under which the data files of the application are stored. All the files related toa particular application (Live, $NAU, $HIS files) will be stored in the respective subdirectory mentioned in this field.




1. List the history records of the ABBREVIATION application.

2. Check the ‘TYPE’ in the PGM.FILE for the ABBREVIATION application.

3. List the unauthorized records of the CUSTOMER.ACCOUNT application

4. Check the ‘TYPE’ in the PGM.FILE for the CUSTOMER.ACCOUNT application.

5. List the live, unauthorized and history records of the ACCOUNT application.

6. Check the ‘TYPE’ in the PGM.FILE for the ACCOUNT application.

7. List the contents of the CUSTOMER.ACCOUNT file and understand the contents




1. How do you find out whether an application is a CUS,FIN or INT type?

2. How do you find out how many files an application has

at database level?2.1 FILE.CONTROL table holds all this information.

3. This is an INT type of file which is not companyspecific and therefore file name is F.FILE.CONTROL.

4. ID of a record in FILE.CONTROL is Application name.

5. All applications in T24 will have an entry in this file.

6. Routines will not have an entry in FILE.CONTROLtable as they do not store any data.




Audio for screen shot:

PGM.FILE and FILE.CONTROL complement each other. The function I cannot beused in the application FILE.CONTROL.

DESCRIPTION : This field holds the description of the record ID.

Data files of the application are stored in one place in the bnk.data directory. Thename of the sub directory is mentioned in the following field.

PRODUCT : This field holds the name of the sub directory under the bnk.datadirectory under which the data files of the application are stored. All the files related toa particular application (Live, $NAU, $HIS files) will be stored in the respective subdirectory mentioned in this field. The value in this field should be same as that of thevalue in the PRODUCT field in PGM.FILE application.

The value entered in the field TYPE in PGM.FILE application is replicated in the multivaluable field SUFFIXES in FILE.CONTROL application.

SUFFIXES : This field holds the suffixes of data files that the application supports. Apart from live file, an application can have unauthorized ($NAU) and history ($HIS)files.

Since the SUFFIXES are $HIS and $NAU and the TYPE in PGM.FILE is H, theCUSTOMER application has three data files. As the product is ST in PGM.FILE andFILE.CONTROL, the data files of the CUSTOMER application are stored underbnk.data directory under st sub directory.





All files are classified to be either CUS type or INT type or FIN type of files.

CLASSIFICATION : This field holds the file classification of that particular application.

This is the field that decides the prefix for the files.INT files have F. as the prefix.

CUS files have F<Branch mnemonic>. as the prefix.

FIN files have F<Branch mnemonic>. as the prefix.

Since the CLASSIFICATION field holds the value CUS, the CUSTOMER file hasFBNK as its prefix. Three data files for CUSTOMER are

FBNK.CUSTOMER

FBNK.CUSTOMER$NAU

FBNK.CUSTOMER$HIS

The field which decides whether the contents of the file are to be deleted or not isdiscussed below.

SYS CLEAR FILES : This field may hold the value Y or N. If this contains a value Y,then the contents of all data files of the application will be cleared whenSYSTEM.CLEAR.FILES is executed from the command line.




1. SS stands for STANDARD.SELECTION

2. SS table holds all the field names and definitions of all the files in T24.

3. This table contains the DICT information of an application.

3. The ID of a record in SS is the name of the application itself.

4. SS is an INT type of file (not company specific) and therefore named asF.STANDARD.SELECTION

5. DICT file for CUSTOMER is stored as F.CUSTOMER]D in bnk.dict




The DICT information is actually stored in bnk.dict directory. The above screen shotshows how the DICT file is stored.





The table STANDARD.SELECTION contains one record per application and willcontain the field definitions of all the fields in the application. It not only contains thefield definitions 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 canbe modified only by T24. The user-defined fields can be modified.

The label of the field to be appeared in a particular application is to be set in theappropriate record in the SS table.

SYS.FIELD.NAME : This field defines the name of the field in an application.

SYS.TYPE : This field defines the type of the field that is to appear in SYS FIELD NO.It is used by the enquiry system to determine what type of selection is to be made.

D stands for Data field on the record.

I stands for I type descriptor. This is used to store the values of concatenated fields.Data is not stored in such fields but only generated during run time.

J stands for J type descriptor. It specifies field join specification. Allows selection to beperformed on data in other applications.





SYS FIELD NO : This field holds the position of the field in an application. @ID whichrepresents the ID of any application will always be field 0.

To validate different data types T24 has many subroutines. What if you input text in amountfield? How will T24 know that you have input a wrong value? For this reason, certain routinesare used to validate the data input into the fields.

SYS VAL PROG : This field holds the name of the routine that will perform data type validationon the respective field. All such routines are prefixed with IN2.

IN2CUS - Input must be a valid customer number. Input of a customer mnemonic will also beaccepted and converted to the customer number.

IN2A - Allows alphanumeric input. The character set is defined in ASCII.VALUES and ASCII.VAL.TABLE.

SYS DISPLAY FMT : This field gives the display format. It contains the maximum number ofcharacters the field name can hold followed by the justification (R – Right justified and L – LeftJustified)

SYS SINGLE MULTI : This field is used to specify if the respective field is a single or a multivalue field.

SYS LANG FIELD : This field specifies if the field is a language specific field which meanswhether or not the field can hold data in multiple languages.

SYS GENERATED : This denotes whether or not the respective field and its properties aresystem defined or not. If set to Y these are core fields and therefore cannot be amended by theuser. For all the core fields it is set to Y and for other set to N.




Audio for the screen shot:

NAME.ADDRESS is a logical field and hence has the field SYS TYPE set to “I”. It

holds the values of Short Name, Name 1, Name 2, Street and Town Countryconcatenated. The field does not store data. Assume, to generate reports for

customers, you need a set of details to be displayed from the CUSTOMER application.Instead of getting the values for each report, you can define a logical field with SYSTYPE set to I so that when required T24 will populate the values of all the fieldsmentioned in SYS FIELD NO. This does not become a physical field in the application,but the value is built at run time.






In this learning unit/course, you learnt about the Core Parameter Tables in T24

You will now be able to

Explain the importance of

PGM.FILE

FILE.CONTROL

STANDARD.SELECTION




Documents

CoreParameterFiles - Part I-R10.01