Tip: For best results, make sure you are migrating only what is useful
at your site. In order to limit that amount of data that is migrated,
mark any tables that you do not want to be migrated as not kept before
you run the migration utility. (Use either the SAS IT Resource Management
2.6 or 2.7 %CPDDUTL utility or the SAS IT Resource Management 2.6
or 2.7 user interface to mark tables as not kept.) The following prerequisites
must be satisfied before migrating a PDB:
-
-
SAS IT Resource Management 3.21
software must be installed, configured, and operational.
-
Sufficient disk space for the
resulting IT data mart must exist.
As point of reference,
a PDB of about 510 megabytes was migrated and the resulting IT data
mart was 1.92 gigabytes. Approximately four times the space allocation
of the existing PDB libraries was needed to contain the migrated PDB
in the IT data mart.
This amount of space
was required because, unlike the PDB, the IT data mart does not use
views. In SAS IT Resource Management 2.6 and 2.7, several statistics
in a table were computed dynamically in the PDB’s views. These
views required temporary utility file space, which was released when
the processing of the table was finished. In SAS IT Resource Management
3.21, the same table does not compute statistics dynamically. Instead,
the statistics are calculated when the table is read, thus requiring
additional temporary space. By not using views, SAS IT Resource Management
has an improved overall efficiency. However, the efficiency in processing
requires additional space.
For this same PDB migration,
65 megabytes of space was required for external files, and 3 gigabytes
of SASWORK space was required. This space is needed only to run %RMPDB2DM,
and is released upon completion.
For
z/OS, disk space
can be in the traditional
z/OS file system or in a hierarchical directory.
(HFS or zFS are the recommended hierarchical directories.)
Note: All items in the WORKDIR
and SASWORK directories are deleted only after the PDB migration is
finished.
-
A valid user ID and password are
required for connecting to the SAS IT Resource Management 3.21 Metadata
Server. The user ID needs authority to define objects in the Foundation
repository.
-
A valid user ID and password are
required for running the SAS macro to perform the migration. This
user ID needs authority to create files and create the physical storage
for the IT data mart.
-
A workspace server must be defined
for the host system where the migration executes. If the workspace
server is named something other than
SASITRM, then the name must be specified in the
APPSERVER parameter of the %RMPDB2DM macro.
-
The TCP/IP service (port) that
the SAS Metadata Server is listening on must be known in order to
specify it to the %RMPDB2DM macro.
-
The SAS IT Resource Management
2.6 or 2.7 SITELIB that was associated with the PDB must be identified
by the user.
-
The SAS IT Resource Management
2.6 or 2.7 PDB should not be accessed by any programs while migration
is in progress.
-
No outstanding reduction checkpoints
or other issues with the PDB should exist. The SAS IT Resource Management
2.6 or 2.7 PDB must be accessible on the same host file system that
SAS IT Resource Management 3.21 uses for IT data mart storage.
-
The JREOPTIONS in the SAS configuration
file used to execute the %RMPDB2DM macro needs to include the following:
-Djava.awt.headless=false -XX:MaxPermSize=128m -Xmx768m
-
Due to memory concerns, a SAS session
or batch job should perform only a single PDB migration at a time.
-
If you are running %RMPDB2DM on
z/OS, you need to ensure that the batch job has a region of at least
1024M. Also, ensure that the user ID that migration will run under
has a value of 1024M (1342177280 bytes) in the OMVS RACF segment.
-
If you are running %RMPDB2DM on
z/OS, you also need to ensure that the TKMVSENV data set includes
a statement to set the TKJNI_OPT_DISPLAY environment variable to an
X Windows Server. This setting is needed due to the internal use of
certain Java graphics code. However, nothing is ever displayed. For
more information, see the SAS Note at:
http://support.sas.com/kb/12599.