Installation and the Repository
The Repository contains several DB2 tables. When you install a new version of Log Master, the Installation System prompts with the following choices:
Whether to create new Repository tables, or continue using existing tables from the version that is already installed
The Installation System displays this prompt only when:
The previous version of Log Master is version 10.1 or later
If Log Master version 11.1 is installed with repository reuse and the previous version is version 10.1, in order to continue using the online menu in version 10.1, you must apply a PTF with support repository reuse in version 10.1.
Whether to migrate information from the previous version’s Repository, or insert only new information into the Repository after installation is complete
The Installation System always displays this prompt:
If you choose to migrate information from the previous version’s Repository, the Installation System generates the $768ALP job. The Installation system runs this job to migrate information after it creates the new Repository. If you need to migrate your Repository information after installation is complete, run the Installation System again and select the choice to migrate information.
If you choose to insert only new information, the Installation System generates an empty Repository.
The Installation System automatically generates the repository tables to accommodate the maximum object name length that your version of DB2 supports.
If you migrate a DB2 subsystem from compatibility mode of a DB2 version to new-function mode without reinstalling Log Master, complete the following after the DB2 catalog is in new-function mode:
Run the job stored in the ALPURPTB member of the data set where you stored the JCL jobs that were generated during installation. (For example, HLQ.JCL, where HLQ is the high-level qualifier that you assign during installation.)
Run a DB2 REORG utility to remove the advisory reorg (AREO) status from several Repository table spaces.