TMF Planning and Configuration Guide (G06.24+)

Moving Between Earlier TMF Environments and D46
HP NonStop TMF Planning and Configuration Guide—522416-004
A-2
D20 to D46
D20 to D46
When migrating from the D20 product, you cannot do so directly. You should first
migrate to D38 with the associated fallback IPMs, run your applications in that
environment long enough to assure that they work properly, and then migrate from
there to D46.
D3x to D46
When migrating from a D30 through D37 product, it is recommended that you first
migrate to D38 with the associated fallback IPMs, run your applications in that
environment long enough to assure that they work properly, and then migrate from
there to D46.
It is possible to migrate directly to D46. If you do that, however, and then have to fall
back later, you must fall back to D38 without any prior application experience with that
product version.
D4x to D46
When migrating from a D40 through D43 product, it is recommended that you first
migrate to either D44 or D45 with the associated fallback IPMs, run your applications in
that environment long enough to assure that they work properly, and then migrate from
there to D46.
It is possible to migrate directly to D46. If you do that, however, and then have to fall
back later, you must fall back to either D44 or D45 without any prior application
experience with that product version.
The above recommendation is particularly important if you are migrating from D40 or
D41. Both of those products use version R5 of the TMF audit-trail format. The D42
through D45 products use version R6; D46 uses version R7. When migrating directly
from D40 or D41 to D46, you are migrating from the R5 format to R7. Should you later
need to fall back to D44 or D45, you would be falling back to yet another audit-trail
format (R6) with no prior application experience in that environment.
Preparing for Migration
New TMF online dumps are not needed when migrating to D46. D46 TMF file recovery
can use online dumps that were created prior to the migration. Note, however, that a
new online dump is required after migrating whenever an existing format 1 file is
converted to a format 2 file.
Programs that use the TMFARLIB audit reading procedures will need few, if any,
changes. If a program contains ARGETRECADDR calls, those calls might have to be
replaced by ARGETRECADDR64 calls. ARGETRECADDR calls will return error -21
when accessing an audit record for any format 2 file whose maximum EOF exceeds