The need to reorganize the LANSA database depends on the frequency and volume of changes made to the LANSA field and file definitions.
It is recommended that the LANSA database be reorganized weekly during a development phase. In general, a stable production system only needs to be reorganized after importing a large number of LANSA objects or if major changes are made to the Help text.
Scheduling of the Reorganization Job
The Reorganize job clears all data more than 3 months (90 days) old from a LANSA internal file named DC@F16. This file is used to exchange information between LANSA online tasks and batch jobs that they have submitted.
For example, it exchanges the list of fields to print between the online 'Print Field Definitions' facility and the actual batch job that produces the report. Likewise, it exchanges details between online RDML programs and batch RDML programs invoked by using the SUBMIT command (most notably the exchange list contents).
If there is a delay of more than 90 days between a LANSA batch job being submitted and being executed, and if a Reorganize job is run to remove the 90 day old information from DC@F16, unpredictable results may occur. This happens because the stored information that was exchanged between the online job and the batch job, and that is older than 90 days, has been erased by the Reorganize job.
Deleted record space in file DC@F16 is also reorganized and removed.
The Reorganize job also clears all temporarily saved working lists that have reached the end of their retention period from a LANSA internal file named DC@F80. This file is used to store saved working lists. Refer to List Handling Built-In Functions in the list of LANSA Built-In Functions by Category in the Technical Reference Guide for more information on saving, restoring, and deleting working lists.
Deleted record space in file DC@F80 is also Reorganized and removed.
The Reorganize job may optionally reorganize the shared data files which exist in library QGPL. These files are shared by all LANSA systems which exist on this machine. These files are typically used in communication activity and include some web files.
