Page History
[ |../../index.htm#lansa/ladugub3_0010.htm]
You are here:
...
These points provide basic information about the IBM i high speed table facility. They should all be read and understood before this facility is used in any way.
...
The sequence of commands:
EXEC_OS400 CMD('DLTUSRIDX DC@TBLIDX')
or with option:
*HSTABEXTEND EXEC_OS400 CMD('DLTUSRIDX DC@TBLIDY')
USE BUILTIN(REBUILD_TABLE_INDEX) WITH_ARGS('''*ALL''')
will physically delete the entire IBM i user index area and then rebuilt the indices of all high speed table within the current partition. The first file rebuild will recreate the IBM i user index if it does not currently exist.
Q: What happens when I change the layout of a file?
If you change the layout of a file and then "make the change operational" a resynchronization of the table and index will be automatically performed. This automatic synchronization is not performed if you then export the changed definition to another system.
Q: What happens if I import a high speed table to another system?
A high speed table is imported to another system just like a normal file. However, if the file data is imported, or the file layout is changed, the associated index is not automatically updated/reformatted. To do this you should trigger a "resynchronization" of the file and its index using any of the techniques described in this guide.
Note: A user index greater than 1 gigabyte or with an entry record length greater than 108 bytes cannot be saved to or restored from an OS400 release prior to V2R2M0.
[ |../../index.htm#lansa/ladugub3_0010.htm]