Hi Pishachi,
You have already posted this issue on the General board and I also answered it there (both post were on December 29th).
Unfortunately this thread was somehow removed from General board (I didn't find it there) and I was able to find my answer only in the archives. It seems so, your thread was moved onto this board, but it could be ranked in deep by its date stamp.
I copied my answer and paste it here again for you.
Regards,
Zoltán
P.S.: Have you ever read my original reply previously?
======================================================================
Hi Pishachi,
I am afraid that this board (General) not the most appropriate place for your issue. Please, see the description of this board on the Main Index screen:
======================================================================
General
General questions about the Forum and JDEList Support.
======================================================================
Most appropriate boards are the two XE professional Forums.
But I do not want to leave you without answer, so I try to explain what I know about RDB spec and TAM spec.
OneWorld stores the specifications of the objects (e.g. everything which were created with Designer Tools, Data Dictionary, etc.) in a very special manner in "spec"-s. With other words, "spec"-s are the collection of the informations which determines an object (e.g. Form Name, Control names, attributes, position on form, etc, etc, etc, ...)
"Spec"-s have a very special variable structures not like relational databases.
"Spec"-s can reside:
1.) In operating system files (e.g. fdaspec.ddb + fdaspec.xdb) on the workstations, Enterprise Server and in the Packages on the Deployment Server under the "spec" sub-folder. All type of "spec"-s consist of two OpSys file with the same name but with differen extensions like ".ddb" and ".xdb"
These representations of "spec"-s are "TAM spec"-s.
2.) In OneWorld tables. As far as I know all of these "spec" tables resides in the "Central Objects" Data Sources of Path Codes. These tables are F98306 and many of the F987xy tables (e.g. F98751 for FDA Spec).
These tables consist of columns for main identification data (e.g. OBNM for Object Name) and a variable length large column, named BLOB (Binary Large Object) to store the specification (e.g. FDABLOB in F98751 table). The structure of information is very special and vary inside these BLOB fields.
These representations of "spec"-s are "RDB spec"-s.
If you add the
TAMMenus=Show
entry to the
[INTERACTIVE RUNTIME]
section of your "jde.ini" file on your workstation then you will get three new selection under the File menu of UTB (Universal Table Browser) like:
* Open Local TAM
* Open Remote TAM...
* Open RDB...
You can open the different representations of "spec"-s on different locations with these new selections with a special manner. UTB will explore the content of BLOB fields and show you in the appropriate structure, many times sub-structures and the structures are vary from record type to record type.
Have a good investigation in the mysterious world of OneWorld Spec's,
...AND...
Happy New Year!
Regards,
Zoltán
P.S.: I hope, somebody will correct me if I was wrong in somtehing in the explanation.
======================================================================
B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
