HP-UX 11i v3 Persistent DSF Migration Guide

Identify User Applications That Require DSFs or Hardware Paths as Input
There may be applications that need DSFs and/or hardware paths for mass storage devices as input. For
example, a database application may require a user to type in a DSF. Identify such applications and map the
legacy DSFs and hardware paths to persistent DSFs and lunpath hardware paths using the ioscan outputs as
described above (see Mapping Commands
). Test the applications. Make notes of what changes are needed
and record the changes.
Save Other Configuration Files
In addition to saving the original files (found by iofind and other user applications) before migrating them,
there is other information that needs to be saved for diagnostic purposes in case there are issues with
migration. Save the following output to files before performing the last step in migration (Disable Legacy DSFs
below):
Outputs of:
ioscan –kfnN
ioscan –kfn
ioscan –m dsf
ioscan –m hwpath
ll /dev/dsk
ll /dev/rdsk
ll /dev/rmt
NOTE: Worksheets at the end of this document give examples on what information to save.
Disable Legacy DSFs
After users have made all the changes described in the steps above and checked that the migrated applications
work using agile view, there are two ways to complete the migration:
1. Full migration
o Disable legacy naming model (will remove the legacy DSFs)
o Test applications with legacy naming model disabled
If all the migrated applications work as expected, the migration is complete.
2. Partial migration
If there are applications with limited support for persistent DSFs (such as the ones discussed above),
there are two approaches that can be taken:
o Disable legacy naming model and test the applications that support running in the agile
view to make sure that they are operating successfully with legacy naming model disabled.
Then re-enable legacy naming model to be able to use those applications that need legacy
naming model. This testing ensures that the applications that were migrated to agile view
have been migrated successfully.
or
o If disabling the legacy naming model is not possible due to the application limitations,
simply continue to operate with the legacy naming model enabled. However, since the
legacy naming model is still enabled, it is not certain that applications have been migrated
successfully to agile view.
12