If you performed step
3, then use the %RMDMUPKG macro to unpackage the physical data that
was created in step 3. Unpackage the physical data into the SAS IT
Resource Management 3.21 IT data marts. If step 4 was executed to
rename the pathnames and data sets, then those new names are used
in this step.
Note: If you are migrating a single
IT data mart from SAS IT Resource Management 3.1.1 or 3.2 to 3.21,
and you are not using the SAS Migration Utility to do so, set the
SMU= option to
NO. This setting indicates
that the SAS Migration Utility was not used to migrate the metadata
associated with this IT data mart.
The %RMDMUPKG macro
unpackages all the transport files in the package directory that were
created by the %RMDMPKG macro. It performs this task by reading an
index file in the package directory that describes all the libraries
that have been packaged. Each library in the index file is then matched
with its corresponding library object in the SAS IT Resource Management
3.21 IT data mart. PROC CIMPORT is executed to import the libraries
from the transport files and write them to the SAS IT Resource Management
3.21 destination libraries. Those libraries are created if they do
not currently exist.
For information, see Macros That Are Used for the Migration Process.Certain libraries in
SAS IT Resource Management 3.21 might have a different internal format
than SAS IT Resource Management 3.1.1 or 3.2 libraries. In order to
perform the reformatting, the %RMDMUPKG macro first executes PROC
CIMPORT to transfer the libraries into the WORK libref. The macro
then performs the reformatting tasks in WORK and uses PROC COPY to
write the data sets to the permanent SAS IT Resource Management 3.21
library.
Therefore, in order
to run successfully, %RMDMUPKG might require large amounts of WORK
space. The maximum amount of WORK space needed is slightly larger
than the largest single library to be imported. Refer to your operating
system companion documentation for instructions about specifying a
larger WORK library. To locate the companion documentation for your
operating environment, navigate to
http://support.sas.com/documentation/index.html. Use the Products Index A–Z to select the Web
page for Base SAS. On the
Base SAS 9.3 Web page, scroll down to the section called “Operating Environment
Specific Information” where you can find the companion documents.
Like %RMDMPKG, each
IT data mart requires a separate invocation of %RMDMUPKG pointing
to a separate package directory. The directory is specified by the
PKGDIR parameter. The %RMDMUPKG macro can be run
in report mode first, so that only a report of what would be unpackaged
is produced. This setting is the default value for this macro. Here
is an example of using the %RMDMUPKG macro for Windows to unpackage
a SAS IT Resource Management 3.1.1 IT data mart:
%RMDMUPKG( DATAMART=NTSMFdatamart,
METAPASS=mypassword,
METAPORT=8561,
METASERVER=my.metadata.server,
METAUSER=admin,
PKGDIR=c:\migration\311packages\NTSMFdatamart
); The value of the
DOPACKAGES parameter defaults to
NO. Therefore, this invocation of %RMDMUPKG produces a report of only
what would be unpackaged if the value of the
DOPACKAGES parameter is set to
YES. If the value
of the
DOPACKAGES parameter is
YES, then the macro unpackages all the physical SAS
libraries that are found in
c:\migration\311packages\NTSMFdatamart. The macro unpackages these libraries into
the corresponding SAS libraries found in the NTSMFdatamart.
Here is an example of
using the %RMDMUPKG macro for
z/OS to unpackage a SAS IT Resource
Management 3.1.1 IT data mart:
%RMDMUPKG( DATAMART=SMFdatamart,
METAPASS=mypassword,
METAPORT=8561,
METASERVER=my.metadata.server,
METAUSER=admin,
DOPACKAGES=YES,
PKGDIR=MIG.311PKG.SMFDM,
FILEDEVICE=DISK,
FILEUNIT=CYL,
FILESPACEPRIMARY=10,
FILESPACESECONDARY=20
); For
z/OS, the
PKGDIR parameter can specify a PDS, PDSE, or zFS directory. You can use
the
z/OS file allocation parameters to control the creation of the
new SAS libraries on the traditional
z/OS file system.
The %RMDMUPKG macro
can be invoked in SAS interactive or batch mode. However, running
in batch mode is recommended if the physical data libraries are large
or numerous. This macro does not update any metadata on the SAS Metadata
Server.