Step 3: Package SAS IT Resource Management 3.1.1 or 3.2 IT Data Marts for Migration

Copy the %RMDMPKG macro from the SAS IT Resource Management 3.21 installation location to your SAS IT Resource Management 3.1.1 or 3.2 system. Execute the macro to package all the physical data in your SAS IT Resource Management 3.1.1 or 3.2 IT data marts. If necessary, transfer all packaged data to a location that is accessible by your SAS IT Resource Management 3.21 system.

The %RMDMPKG macro resides in the following locations on your SAS IT Resource Management 3.21 server tier:

In the preceding line of code, “&prefix” is your chosen data set prefix and nn is the two-byte encoding such as W0, W3, W9, J0, V0, and so on. An example of a z/OS location is SAS.ITRM.W0.AUTOLIB.

Copy or transfer this macro to the corresponding macro location on your SAS IT Resource Management 3.1.1 or 3.2 server tier so that it can be executed there.

The %RMDMPKG macro packages the physical libraries for a single SAS IT Resource Management 3.1.1 or 3.2 IT data mart. The macro performs this task by scanning the specified IT data mart for SAS libraries and executing PROC CPORT. PROC CPORT creates transport files for each library. The transport files are then written to the specified output package directory. For information, see Macros That Are Used for the Migration Process.

Each SAS IT Resource Management 3.1.1 or 3.2 IT data mart requires a separate invocation of %RMDMPKG that points to a separate output package directory. (The PKGDIR parameter specifies the separate output packages.) Do not point to the same output package directory for different IT data marts.

The %RMDMPKG macro can be run in Report mode first, so that only a report of what would be done is produced. (The default mode of execution is to run in Report mode.) Here is an example of using the %RMDMPKG macro for Windows to package a SAS IT Resource Management 3.1.1 data mart:

%RMDMPKG(
    DATAMART=NTSMFdatamart,
    METAPASS=mypassword,
    METAPORT=8561,
    METASERVERr=my.metadata.server,
    METAUSER=admin,
    PKGDIR=c:\migration\311packages\NTSMFdatamart
    );

The value of the DOPACKAGES parameter defaults to NO. Therefore, the preceding invocation of %RMDMPKG produces only a report of what packages would be created if the DOPACKAGES parameter were set to YES. If the value of the DOPACKAGES parameter is set to YES, then the macro packages all the physical SAS libraries that are found in the NTSMFdatamart. The macro writes the transport files to c:\migration\311packages\NTSMFdatamart.

Here is an example of the %RMDMPKG macro for z/OS:

%RMDMPKG(
    DATAMART=SMFdatamart,
    METAPASS=mypassword,
    METAPORT=8561,
    METASERVER=my.metadata.server,
    METAUSER=admin,
    PKGDIR=MIG.311PKG.SMFDM,
    DOPACKAGES=YES
    );

For z/OS, the PKGDIR parameter can specify a PDS, PDSE, or zFS directory.

The %RMDMPKG macro can be invoked in SAS interactive or batch mode. However, if the physical data libraries are large or numerous, running in batch mode is more practical. To rerun the macro in the event of an error, clear out the output directory that is specified by the PKGDIR parameter and rerun the macro. This macro does not update any metadata on the SAS Metadata Server.

If the file systems that are used by SAS IT Resource Management 3.1.1 or 3.2 and SAS IT Resource Management 3.21 are not shared, you must transfer all package directories and their contents to locations that are accessible by SAS IT Resource Management 3.21. You can do this by means of FTP or a similar tool. If the file systems are shared, then the package directories are accessible by SAS IT Resource Management 3.21. In that situation, transferring the data is not necessary.