TMF Planning and Configuration Guide (G06.24+)

Moving Between Earlier TMF Environments and D46
HP NonStop TMF Planning and Configuration Guide—522416-004
A-3
Migrating to D46
2 GB. ARGETRECADDR64 calls can access audit records for both format 1 and
format 2 files (regardless of size). The TMF audit reading procedures are described in
the TMF Application Programmer’s Guide.
Programs that read audit trails directly will need many changes (and might need to
continue to work with prior audit-trail formats). Note that reading audit trails directly is
not recommended. For information abouting altering such programs, contact your
service provider.
Third party software products that read audit-trail information might need changes.
Migrating to D46
To migrate from an earlier TMF product to the D46 product, perform the following
steps:
1. Do a clean shutdown of the TMF product:
Ensure that all your data volumes are enabled and all database tables and files on
them are in a consistent state (by doing file recovery, if necessary).
Execute a TMFCOM STOP TMF command, which must complete without the
failure of any TMF components.
If you are using the RDF product, you must also wait for it to finish processing the
audit trail and shut itself down. (The RDF subsystem shuts itself down
automatically when TMF is stopped).
If the RDF subsystem is either crashed or not running when you stop TMF, you
should restart the RDF subsystem and allow it to shut down cleanly. To restart the
RDF subsystem, you must first restart TMF. Once the RDF subsystem is started, it
scans the audit trail and shuts down whenever it encounters a TMF shutdown
record. Consequently, you might have to restart the RDF subsystem more than
once while TMF is running, until the RDF subsystem is able to scan the entire audit
trail. At that point you can stop TMF, and the RDF subsystem shuts down cleanly.
2. Back up all critical TMF files.
To aid in reconstructing the intermediate TMF environment in case something goes
wrong during migration, back up the ZTMFCONF subvolume and any audit-trail
files currently on disk that have not yet been dumped. Note that you must use the
BACKUP utility to do this, not FUP DUP commands.
3. Cold load the system with the D46 software.
The cold load must include the D46 version of all TMF software, the DP2 disk
process, and the RDF subsystem (if you are using it). It must also include at least
the same level of all other system software used.