In LANSA, making a table operational may involve three different tasks in the following order:
When a table is first defined, it must be made operational and all three tasks are to be performed, (assuming there are indexes), by either you or LANSA.
If you change your column definitions or your table definitions in the Repository, you may need to perform some or all of the above tasks as you make the tables operational once more. All three tasks do not always have to be performed. For example, adding a validation check will not require recompiling the physical tables or indexes. (Refer to What to Recompile.)
In most circumstances, LANSA will check which of the three tasks needs to be performed; however, LANSA cannot detect all changes made at the column level. For example, if you change a default value for a column on a table, you should use impact analysis and then tell LANSA to recompile the OAM when you make the table operational. If you changed a column's length, LANSA will know to perform all three tasks of rebuilding tables, indexes and OAM. (Refer to When To Recompile.)
Making tables operational is an excellent example of how LANSA shields developers from the underlying technical layers of the database and operating system. Under IBM i, making tables operational will create physical tables and indexes. Under Windows, making tables operational will create SQL tables in the appropriate database manager.
To make a table operational, use the Compile Table option. The Compile Option dialog will appear. This dialog allows you to specify which tasks should be performed when the table is made operational.
Using the Compile only if Necessary option, LANSA will check if the table compile needs to be performed; however, LANSA cannot detect all changes made at the column level. For example, if you change a column level rule for a column in the table, you must tell LANSA to recompile the OAM when you make the table operational. If you changed a column's length, LANSA will know to recompile the table.
When a table is recompiled, you have the option to save and reimport any existing data in the table. The types of changes to your table will determine how much of the data can be restored. (Refer to What about Data?)
You do not need to keep the generated source code unless you are planning to move your application to another platform which requires the C code (for example, Linux).
Also See
Table Compile Options in the Technical Reference Guide
