G06.27 Software Installation and Upgrade Guide

Overview of Installing G06.27

G06.27 Software Installation and Upgrade Guide—540067-001

1-43

TMF (G06.23, G06.24, G06.25, and G06.26)

TMF 3.3 (G06.26)

If you do not use any new configurable features after migrating to TMF 3.3, falling back

to the RVU from which you migrated is not a problem. If you use the new TMF 3.3

feature that allows you to add auxiliary audit trails while TMF is started, however, it is

important to first understand how that impacts any subsequent fall back. For G06.26

TMF 3.3 fallback and migration issues, see the G06.26 Release Version Compendium

and the TMF Planning and Configuration Guide.

TMF Migration Considerations for SQL/MX Release 2.0

If you initially install SQL/MX Release 2.0, fallback and migration concerns could apply

if you have to fall back to a previous RVU. See the T8607AFH or later softdoc for

detailed migration information for TMF. See also the TMF Planning and Configuration

Guide and the TMF Operations and Recovery Guide.

If the Install SQL/MX script has not been run on your system while running on the new

RVU, and no native-format SQL/MX metadata tables (or their resource forks) or audit

records for them have been created, there are no TMF fallback considerations.

Otherwise, you must use the appropriate DP2 (T9053) fallback SPR if you have not

performed a clean TMF shutdown.

You must successfully complete a clean TMF shutdown (with all audited disks up)

before falling back to a prior RVU. This step is particularly important whenever the RVU

you are falling back from supports any new format files or objects or audit records for

them, and the fallback RVU does not.

To establish complete TMF file recovery protection for your SQL/MX metadata tables,

update your TMF online dump (and Backup) scripts to include the names of all

SQL/MX metadata tables, including those that are SQL objects and their resource

forks. The TMFCOM DUMP FILES and RECOVER FILES commands support all the

new SQL/MX metadata tables (using their Guardian names).

TMF Migration Considerations for Format 2 Audit Trails

TMF provides the capability to create much larger audit-trail files with the introduction

of the G06.24 RVU, but TMF must be stopped in a clean state to execute the

TMFCOM command that enables this ability. If audit-trail files greater than 2 GB are

part of the long-term audit-trail configuration strategy, consider altering the audit-trail

format at migration time, given that TMF is already stopped. If not done at this time,

then altering the audit-trail configuration to enable format 2 audit-trail files will require a

STOP TMF command at some later date.