If you want to migrate
all SAS 9.1.3, 9.2, or 9.3 system content and configuration to SAS
IT Resource Management 3.3 on a SAS 9.3 system, migrate your data
and metadata using the SAS Migration Utility. Option 2 is best suited
to sites that have a significant investment in the data produced by
the current IT Resource Management system, the customizations made
for that system, and the processes that analyze that data.
Choose this option if
you want to have access to all IT data marts that were defined in
your current SAS IT Resource Management 3.1.1, 3.2, 3.21, or 3.3 system.
It is also the best choice if you have a significant investment in
SAS 9.1.3, 9.2, or 9.3 system metadata other than that for SAS IT
Resource Management.
If the total size of
all metadata for the SAS 9.1.3, 9.2, or 9.3 system is extremely large,
you might encounter (or choose to eliminate the likelihood of) resource
constraints such as out-of-memory errors while using this option.
If you encounter this problem, you should select Option 3.
Note: This migration process uses
more overall disk space because IT data marts must be replicated.
If disk space is an issue, you might decide to not migrate and to
follow the process described in Option 1. (Option 1 does not recommend
migration. Instead, it recommends that you install SAS IT Resource
Management 3.3 and establish new IT data marts.)
After the migration
process is completed, the metadata and (optionally) the data are available
in SAS IT Resource Management 3.3. However, SAS code that is associated
with a User-Written Staging transformation is not included in the
migration of the metadata or the data. To enable your user-written
staging transformation to execute as you specified, you must move
the SAS code that is associated with the User-Written Staging transformation
to an appropriate place. Then you must also update the transformation
to point to the new location of that SAS code.
Note: New report definitions are
supplied with SAS IT Resource Management 3.3. Migrated jobs with gallery
transformations will continue to use the migrated report definitions
from the previous version until the job is modified and new report
definitions are selected in their place. (The migration process deletes
any supplied report definitions from the previous version of the software
unless they are used by a migrated job.) If you want to change these
report definitions to use newly available report definitions, you
can modify these jobs or create new jobs. User-defined report definitions
will not be deleted in any case.