Interpreting merged file_list produced by util a/17/10/2.

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
In my proto-18, I was only seeing my own file list via Util a/17/10/2. I changed the library-type to file_list_type and added

file_list_size DEMO

I am now seeing an merged file as my 1/7/a/10/2 output. Looks like this:

TAB z07a 5M 0K TS2D
IND z07a_id 5M 0K TS2X
TAB z07p 100K 0K ts0
IND z07p_id 100K 0K ts1
TAB z11 300M 0K TS3D
IND z11_id 300M 0K TS3X
IND z11_id1 30M 0K TS3X
TAB z13 200M 0K TS3D
IND z13_id 20M 0K TS3X
IND z13_id1 20M 0K TS3X
TAB z13u 400K 0K ts0
IND z13u_id 100K 0K ts1
TAB z120 100K 0K TS1D

So, does this means that some of my ABC01 data is sitting in ts0 and ts1 table space? And if I want to make it live instead in our TS2D space, I should edit my file list and then drop and recreate?

Resolution:
The output from util a/17/10/2 is a merged *file_list*. The tables coming from the template (shown with ts0 and ts1, in this case) exist *only* if you have actually run util a/17/1 to create them (-- just as the other tables in the file_list exist only if you have run util a/17/1 to create them).

If you want to actually create these tables, but in TS2D/TS2X rather than ts0/ts1, you have two choices. The first is to, as you suggest, add them to your $data_root/file_list -- and then run util a/17/1 for them. That is probably the simplest.

An alternative, described in SKB 8037, would be to use the "setenv file_list_tsnn" parameter to redirect a template tablespace to your own tablespace.

In your case, that would be:

setenv file_list_ts0 TS2D
setenv file_list_ts1 TS2X