[T24] Concat files

[Phuong Do Duc]

Hi, Please help me, T24 has 2 tables:

FBNK.CATEGORY
FBNK.LD.LOANS.AND.DEPOSITS: there is a field called CATEGORY in this table

Now I want to create a concat file like that: @ID is CATEGORY.ID and content are List of Category's LD contracts.

Please help me to create this table, and how to STORE DATA to this concat table?

Thank you!

[FAISAL FAYYAZ]

Hi Phuong Do Duc,

 

You only need to create a new template with Type 'T' and attache in FIELD.DEFINITIONS file of LD.LOANS.AND.DEPOSITS. T24 will automaticallly store the LD Contracts against Categories. If you dont have the LD's FIELD.DEFINITIONS file then you will have to do this by a routine.

 

Regards,

 

Faisal

[JOSE L MARTINEZ-AVIAL]

Well, you can create a table, let's say FBNK.CAT.CON.LD, with @ID  the category and the record will contain the LD record IDs. But how will you update that concat? in the cob, in a batch process? Or online, with a routine in the version? By the way, why you need that?.

2009/9/18 Phuong Do Duc <mit...@gmail.com>

[jlm...@gmail.com]

Hi,
LD.LOANS.AND.DEPOSITS is a table from the core of T24. I doubt he can or should do that, even if he had the source code. I really wouldn't do that.

Sent via BlackBerry from T-Mobile

---

From: FAISAL FAYYAZ
Date: Sat, 19 Sep 2009 10:52:25 +0500
To: <jb...@googlegroups.com>
Subject: Re: [T24] Concat files

[DAUBA OLIVIER]

Hi,

EB.ALTERNATE application can do for you.
Create a alternate key based on CATEGORY field.


Regards

jlm...@gmail.com a écrit :

> Hi,
> LD.LOANS.AND.DEPOSITS is a table from the core of T24. I doubt he can
> or should do that, even if he had the source code. I really wouldn't
> do that.
>
> Sent via BlackBerry from T-Mobile
>

> ------------------------------------------------------------------------
> *From*: FAISAL FAYYAZ
> *Date*: Sat, 19 Sep 2009 10:52:25 +0500
> *To*: <jb...@googlegroups.com>
> *Subject*: Re: [T24] Concat files

> Hi Phuong Do Duc,
>
> You only need to create a new template with Type 'T' and attache in
> FIELD.DEFINITIONS file of LD.LOANS.AND.DEPOSITS. T24 will
> automaticallly store the LD Contracts against Categories. If you dont
> have the LD's FIELD.DEFINITIONS file then you will have to do this by
> a routine.
>
> Regards,
>
> Faisal
>
> On Sat, Sep 19, 2009 at 7:09 AM, Phuong Do Duc <mit...@gmail.com
> <mailto:mit...@gmail.com>> wrote:
>
> Hi, Please help me, T24 has 2 tables:
>
> FBNK.CATEGORY
> FBNK.LD.LOANS.AND.DEPOSITS: there is a field called CATEGORY in
> this table
>
> Now I want to create a concat file like that: @ID is CATEGORY.ID

> <http://category.id/> and content are List of Category's LD contracts.

[Phuong Do Duc]

Hi all, thank you for reply me. The reason for my question are:

 

1) I want to know: How many LD contract are created with CATEGORY number1, number2, ...

2) I want to know how to create concat table and how to store data to.

 

I have Template "T" file, but I dont know how to attach to FIELD.DEFINITION of table LD.LOANS.AND.DEPOSITS. Please show me details.

 

"T24 will automaticallly store the LD Contracts against Categories": THAT'S ALL I NEED. I can coding to insert data to any table but with concat table, I dont want to coding anything, I think concat table same with VIEW in SQL2000, Oracle,... or some others DBMS...

 

Thank you very much.

 

>EB.ALTERNATE application can do for you.
>Create a alternate key based on CATEGORY field.

[Phuong Do Duc]

Hi all, thank you for reply me. The reason for my question are:

 

1) I want to know: How many LD contract are created with CATEGORY number1, number2, ...

2) I want to know how to create concat table and how to store data to.

 

I have Template "T" file, but I dont know how to attach to FIELD.DEFINITION of table LD.LOANS.AND.DEPOSITS. Please show me details.

 

"T24 will automaticallly store the LD Contracts against Categories": THAT'S ALL I NEED. I can coding to insert data to any table but with concat table, I dont want to coding anything, I think concat table same with VIEW in SQL2000, Oracle,... or some others DBMS... Am I right?

[Rashid K.P]

Concat table is not like a view in other DBMS . It is a separate table in itself and data needs to be inserted into it. In this case when an LD is created in T24 , core system itself will insert values into this table (If I'am not wrong the Table name is LMM.CATEGORY im not sure !!).

[Phuong Do Duc]

You right, there is a table named LMM.CATEGORY, but in our system, this table is empty, I dont know why. Are you sure Concat table is not like a view in other DBMS ???

 

You said Concat table not like View in other DBMS, but someone in above said: "T24 will automaticallly store the LD Contracts against Categories" if I can create a concat . Does he right?

I know LD is system table, very important, it should not be changed by any reason, I dont want to change FIELD.DEFINITION this table.

 

No my question only is: IF I CREATE A CONCAT TABLE WITH @ID IS CATEGORY.ID AND CONTENT IS LIST OF THIS CaTEGORY.ID'S LD.ID. DOES T24 AUTOMATICALLY INSERT DATA TO THIS TABLE (like a View in SQL)?

 

If everybody said no, I must write a Routine to insert data, or use EB.ALTERNATE.KEY.

 

Many thanks

2009/9/22 Rashid K.P <kpra...@gmail.com>

--
Đỗ Đức Phương
Mobile: 84 904 302 898
Home phone: 84 4 5543349

[Niels]

I would problably just create an index on LD.

CREATE-INDEX FBNK.FBNK.LD.LOANS.AND.DEPOSITS CATEGORY BY CATEGORY

Retrieve would be somethink like , forgot coce

SELECTINDEX ?filename? ?indexname? ?selection? TO ID.LIST

FORMLIST ID.LIST
Then use EB.READLIST TO do selection in selection

[Pawel (privately)]

Hi,

You have been offered with at least two solutions. None of them is good
to me, because your problem is probably not easy to solve :( You want to
select part of the data from file and you want to avoid traversing of
whole file.

Do you really need to store references of your LD contracts per
CATEGORY? I would expect thousands of contracts for some of the
(popular) LD categories. Just imagine that you store a lot of references
under single CATEGORY key. Concat file record will be large and regular
jBASE index will hash a lot of LD keys to single CATEGORY key (and this
is poor in terms of performance). None of the solutions is therefore
good.

1) Index cons
jBASE index may kill some of the multithreaded COB jobs. Imagine that
there is core job that moves LD contracts to history file on maturity
date. Usage of jBASE index may kill multithreaded nature of this job (a
lot of multithreaded DELETEs will need to synchronize on index update).
Expect some problems.

Usage of jBASE indexes is not a perfect solution. Maintenance of index
data kills multithreaded jobs and introduces overhead in online.

We have found out also, that jBASE indexes may get out-of-sync in some
scenarios. This is however fixed in one of the recent jBASE 4.1 releases
I think. But still it seems to us that indexes may suffer from some kind
of "fragmentation" problem. They are working slower and slower over
time, so we regularly are rebuilding them to improve performance.

Jim could probably say some more info about indexes implementation. (As
far as I remember from this group) They are organized as B-trees. There
are different kinds of B-Trees, I am not sure which kind of B-Tree was
used in jBASE implementation.

2) Concat file cons
Large concat file records may suffer from record size problem. I would
however prefer this kind of solution over regular jBASE indexes.
Concat files are "application level" programmed indexes (independent
tables, that need to be populated with user code).

Niels suggested some statements to retreive data when you use regular
jBASE indexes. Here is my favourite (written from top of my head):
EXECUTE "KEY-SELECT FBNK.LD.LOANS.AND.DEPOSITS WITH CATEGORY EQ 'sth'".
Simple and straightforward.

Kind regards
Pawel

----------------------------------------------------
Wygraj wymarzony skuter!
Wyznacz najprostszą drogę - docelu.pl - Kliknij:
http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fchapman1.html&sid=863