Preserving your CL/Supersession Table Database
Sue DeMarrais 270001YJ22 Visits (3138)
The most vital element of your CL/Supersession environment is your Table Database, or TDB. This is where all profiles are stored. These profiles contain all of your user, group, and global menu customizations, including the ordering of available sessions, initial dialogs, triggers, and logmode selections.
In support, sometimes we see trouble with the TDB. There are a few things that you can do that will reduce your exposure to TDB woes.
First and foremost, make periodic backups. If you recycle on a regular schedule, the perfect time to make a backup is when your system is down. If your users have the ability to highly customize their menu, you may want to do so often.
Second, consider a REORG to reduce fragmentation if you delete or change many profiles at once. If you need more space, you can REPRO a copy of your TDB, then delete and reallocate a new, larger one.
Third, do not use the SPANNED parameter in the allocation of the TDB. We see far more problems with SPANNED record TDBs than without. We have a support technote that describes how to convert your TDB from a SPANNED format to non-spanned, see technote 1648954.
If you're in the unfortunate circumstance of having a corrupt TDB, there may be a solution.
If you suspect that a control record is corrupt, you may be able to restore your TDB by doing the following:
If you have another corrupt record, deleting just that record might get you past the trouble. The KLSTBUNL utility, which unloads the TDB to a partitioned dataset, may help figure out which, if any, records are affected. This utility is decribed in Chapter 15 of the CL/Supersession Customization Guide.
Hopefully these suggestions will keep your TDB running smoothly!