T24 Optimisation tips

-
I am recently getting some knowledge in T24 performance tuning. I will share some of my experience from my work while creating reports for APAP

* Never put a select blindly on heavily populated tables like ACCOUNT, CUSTOMER etc
* Even a medium sized bank have nearly 1 million records in the ACCOUNT table (including the internal accounts.). Blind selects on tables like these will never return.
* Index highly queried columns of the most common tables like CUSTOMER, ACCOUNT, CARD/ISSUE etc..
* Make sure you index only the necessary fields only. If you index large number of fields, it will inturn kill the server, as every commit on the table need to update all the indexes.
* Its better to use more robust databases like Oracle DB or SQL Server DB as the backend database instead of JBase as they have better performance.
* If you are writing a nofile enquiry never do a SSELECT if you need sorted output. Instead finish the processing of the output array and sort the array using the SORT function. This function uses quick sort algorithm and will be very fast.
* Before using a SORT fuction change all the VMs and SMs in the sort array and have seperation only on FM.

I will update this post more often with my experience.

Comments

Post a Comment

Popular posts from this blog

Current Variables in T24

-
CURRENT VARIABLE Introduction In addition to the system common variables that can be used in ENQUIRY and VERSION there is a feature where the user can populate a variable of their own and use it later. There are now a series of new system variables and a much wider option for users to create and use their own which are: CURRENT.CUSTOMER CURRENT.ARRANGEMENT CURRENT.EXTERNAL.USER These may be set on login by an external user and cleared when they logout. This means that ENQUIRY & VERSION can be tailored to accept the content of the variable instead of forcing a user to enter their own customer number or arrangement etc. Similarly in VERSION you can now default a field content by using the !CURRENT.CUSTOMER to populate a customer field with the current content of the variable. So the variable could be set in one Enquiry and used in either another Enquiry linked to it; or via VERSION to populate fields in an application triggered from the Enquiry. Note: ...
Read more

All accounting entries of an T24 account

-
There is a core routine that will return all the accounting entries for an account it is EB.ACCT.ENTRY.LIST Syntax: EB.ACCT.ENTRY.LIST(ACCOUNT.NUMBER,FROM.DATE,END.DATE,YID.LIST,OPENING.BAL,ER) Passed Parameters. ACCOUNT.NUMBER :- Account for which balance & entries is to be returned. FROM.DATE :- Start date for opening balance and entries. END.DATE :- The last date to be considered. Outgoing : YID.LIST :- List of statement entry ids. OPENING.BAL :- Opening balance on the startt date. ER :- Any errors found
Read more

Drop down enquiry based on condition.

-
Description: We need to generate different drop downs on a version field based on another version field. We tried to populate the T array of the target field by making it as a Hot field Validation field, but it did not help. So to resolve this we created a Nofile enquiry and attached it to the target field. As this is a Nofile enquiry we can manage what to display in the field. Below are the details: There are 2 associated multi value fields and are, 1) THIRD.PARTY - YES or NO Field 2) APPL.TRANS - Normal Field Version Validation: IF THIRD.PARTY = NO THEN ONLY 8 TRANSACTION TYPES SHOULD COME IN DROP DOWN IN THE TRANSACTION.TYPE FIELD END ELSE ONLY 3 TRANSACTION TYPES SHOULD COME IN DROP DOWN IN THE TRANSACTION.TYPE FIELD END To achieve the code is written as below and attached with the field THIRD.PARTY: THIRD.PARTY = COMI IF THIRD.PARTY EQ 'YES' THEN T (QTC.CBD.APPL.TRANS) <2> = "Withdrawal_Earning _Distribution_Loan Advances...
Read more