Posts

Showing posts from August, 2012

LIMIT.PROCESS.INCREASE

The purpose of this T24 API is to increase the amount of a LIMIT. This can be either in the Online or during COB. The syntax of the API is given below LIMIT.PROCESS.INCREASE (LIMIT.ID,LIM.REC,INCREASE.TYPE,INCREASE.CCY,INCREASE.AMOUNT,AMT.TYPE) Input Parameters : ---------------- LIMIT.ID      - ID of the Limit for which the increase has to be done. LIM.REC       - Entire Limit record for which increase is done.                 Optional argument. INCREASE.TYPE - It can be either FULL/SINGLE.                 FULL - Increase is done for the entire Limit structure.                 SINGLE - IncreasINCREAthat Limit. INCREASE.CCY    - Increase amount currency. INCREASE.AMOUNT - Amount to be ...

Combining Jbase and linux commands

You can jbase and linux command into a single command and execute. This is really powerful option. For example if you want to list only COB services from the file F.TSA.STATUS you can do it like below. prompt --> SH LIST F.TSA.STATUS | grep COB This will do. The command SH is a jbase command which will execute linux commands in Jbase. This will work on mw42 also prompt -->SH mw42 | grep tSA prompt -->SH mw42| grep tSA    10    r10 1409350      6 (5)    5    1    25     6   18 5.25M  0.00  2 E SH mw42| grep tSA (SH,48)    41    r10 1511704     47 (8)    4    1 12045  1382  295 20.5M  1.81  2 SLEEP tSA 29 (BATCH.JOB.CONTROL,943)    43    r10 2470242     47 (8)    4  ...

Select all failed OFS transactions

You can select all the failed OFS transactions using this query SELECT F.OFS.RESPONSE.QUEUE WITH F1 LIKE -... This will select all the records from the file F.OFS.RESPONSE.QUEUE which are failed due to any reason. If you want to select only the failures due to error then use this query SELECT F.OFS.RESPONSE.QUEUE WITH F1 LIKE -1... If you want to select only the failures due to overrides then use this query SELECT F.OFS.RESPONSE.QUEUE WITH F1 LIKE -2...

Query to list all User Login VOC

The following query can be used in a Jbase server to list all the User login VOCs created in that environment. LIST VOC WITH TYPE EQ PA AND F3 EQ EX In this query the Variable F3 denotes the position of the command EX in the VOC entry. In the below entry EX is in 3rd line hence the query uses the variable F3. If it is in line 2 then we need to use the query as LIST VOC WITH TYPE EQ PA AND F2 EQ EX An example VOC record is given below File VOC , Record 'A1' Command-> 0001 PA 0002 ETS 0003 EX 0004 DATA INPUTT 0005 DATA 123456 0006 DATA Y

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

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...

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: ...

An useful script

I develop T24 component and my browser is hosted in Jboss. The problem in Jboss is that if I change something in a routine or in a version or enquiry I have to restart the "jbase_agent"s. If not the changes won't take place in the browser immediately. For this i have to use several unix commands to kill the agents. To simplify this i created a simple script. You need to compile this as a Program in your jbase server environment and run. This program is self explanatory. PROGRAM JK2 $INCLUDE T24.BP I_COMMON $INCLUDE T24.BP I_EQUATE CRT "INPUT PORT NO" INPUT Y.PORT IF Y.PORT NE "" THEN Y.EXC.CMD = "SH ps -ef | grep ":Y.PORT:" | grep -v grep | awk '{print $2}' | xargs kill" EXECUTE Y.EXC.CMD Y.EXC.CMD = "SH nohup jbase_agent -p ":Y.PORT:" &" EXECUTE Y.EXC.CMD END ELSE CRT "INVALID PORT NO" END STOP This program will kill all the running jbase_agent pro...

Local Ref Master

Image
When local reference field is added for an application, the same field is added to all the applications for which the field "Local Ref Master" in FILE.CONTROL record is set to the current application name. For example the applications AA.ARR.CUSTOMER, AA.PRD.CAT.CUSTOMER, etc... For the application AA.ARR.CUSTOMER, the Local Reference Master is AA.PRD.DES.CUSTOMER. If we try to attach a LT to AA.ARR.CUSTOMER directly the system will throw message as "Application uses local table of AA.PRD.DES.CUSTOMER". Only way to attach a LT to AA.ARR.CUSTOMER is to attach the LT to the master file.

Date less than 1950

In T24 by default the Date type field will not allow entering a date which is older than the year 1950. In case if you enter a date 19490203 in a Date type field  the system will throw error "YEAR CANNOT PRECEDE 1950" To overcome this the field 2 of the T array of the field in subject should be set to 1000. An example is given below. fieldName = 'XX<FIELD1' fieldLength = '35.1' fieldType = 'D' fieldType<2> = 1000 CALL Table.addFieldDefinition(fieldName, fieldLength, fieldType, neighbour) After defining the date field in this fashion the system will allow dates of years from 1000 to 2049

How to attach drop down enquiry to many versions quickly?

 In T24 R8+  you can use the application called EB.DYNAMIC.ATTRIBUTES in that create a record called SYSTEM and you can attach a routine in VERSION.RTN which will be triggered for all VERSION's before displaying so you can just modify the R.VERSION and send it back with the drill down enquiry you want to attach then it will be displayed to the user in Browser

A program to sort numbers

This program will sort numbers based on their values. Usually SORT will sort not based on the value of the numbers PROGRAM TEST.SORT $INCLUDE T24.BP I_COMMON $INCLUDE T24.BP I_EQUATE Y.ARR1 = 1:FM:4:FM:2:FM:8:FM:6:FM:3:FM:13 Y.ARR2 = '1':FM:'4':FM:'2':FM:'8':FM:'6':FM:'3':FM:'13' Y.CNT = DCOUNT(Y.ARR2, FM) FOR I = 1 TO Y.CNT Y.SORT.ITEM = MAXIMUM(Y.ARR2) Y.SORT.ARR := FM:Y.SORT.ITEM LOCATE Y.SORT.ITEM IN Y.ARR2 SETTING Y.ITEM.POS THEN DEL Y.ARR2<Y.ITEM.POS> END NEXT I DEL Y.SORT.ARR<1> CRT Y.SORT.ARR STOP

Reverse Locate

You can locate from the back of the string using option "DR" in the locate command. Example:  PROGRAM TEST.LOCATE$INCLUDE T24.BP I_COMMON $INCLUDE T24.BP I_EQUATE Y.STRING = 30:VM:30:VM:30:VM:30:VM:30:VM:30 LOCATE 30 IN Y.STRING<1,1> BY "DR" SETTING POS THEN CRT POS END STOP The result will be 6. Usually the answer will be 1 using LOCATE command

Collateral and Collateral Right

Every loan contract in T24 can be covered using a Collateral. The Collateral details are stored in the file COLLATERAL. The Collateral is independent of the Loan. The file which connects a Collateral to a Loan is COLLATERAL.RIGHT. There are two ways a Loan can be attached to the COLLATERAL.RIGHT. Way 1: Creating a new record in the file COLLATERAL.RIGHT and entering the Loan contract ID in the field LIMIT.REFERENCE of the COLLATERAL.RIGHT. This is the process of attaching a Collateral to a loan without limit. Way 2: Creating a new record in the file COLLATERAL.RIGHT and enter the Limit reference of the Loan contract in the field LIMIT.REFERENCE of the file COLLATERAL.RIGHT. In this case the system will identify the LIMIT. When we create a loan contract the system will by default create a record in LIMIT application for the customer as per the limit reference of the Loan contract. This will happen if the parent limit line is created for the customer. In cas...

Hello World

Hi all, This is my first blog post, same like "Hello World" program. The posts i update will not be in a perfect format, everything will be in my own style. I hope you all will accept. it. About me, I work in Temenos in T24 domain. I have an experience of 3 years.