Migrating to a Different Platform

About Migrating to a Different Platform

PDB migration is performed on the same system where the workspace server for SAS IT Resource Management 3.2 is executed.

The existing SAS IT Resource Management 2.7 PDB might be on a different platform than what is used by the SAS IT Resource Management 3.2 software. For example, the PDB might be on a Windows file system, but the IT data mart is going to reside on a UNIX file system. A more subtle example is if the PDB is on a Windows file system using a 32-bit Windows operating system, and the IT data mart is on a Windows file system using a 64-bit Windows operating system.

In any of these cases of different platforms, the PDB must first be moved to the new platform, and then PDB migration can be performed. The process to do this has three basic steps:

Export the PDB and SITELIB SAS libraries into a transferable format.
Transfer the exported libraries to the target system.
Import the PDB and SITELIB libraries from the export package into new SAS libraries on the target system.

Each step of this process is explained in the following topics.

Export the PDB and SITELIB SAS Libraries

Because the format of SAS libraries differs by platform and SAS release, a portable format of the PDB and SITELIB SAS libraries must be created on the SAS IT Resource Management 2.7 system. A tool to assist with this task is included as a member in the SAS IT Resource Management 3.2 SASMISC directory. This member is called RMPDBEXP.SAS. To export the libraries, perform the following steps:

Transfer the RMPDBEXP.SAS member from the SAS IT Resource Management 3.2 system into a location where it can be used from the SAS IT Resource Management 2.7 system.

The RMPDBEXP.SAS member resides in the following locations on your SAS IT Resource Management 3.2 server tier:

Windows Specifics: <sasroot>\itmsmvadata\sasmisc

UNIX Specifics: <sasroot>/misc/itmsmvadata

z/OS Specifics: <high-level-qualifier>.ITRM.CPMISC

Note: The directory names and locations for SAS IT Resource Management macros did not change between SAS IT Resource Management 3.1.1 and SAS IT Resource Management 3.2.

Run a SAS session with the following code:

options nofmterr;
/* include from the appropriate location */
%include ‘rmpdbexp.sas’;
/* activate the PDB and SITELIB in readonly mode */
%cpstart(mode=batch,
    access=readonly,
    mxglib=MXG-format-library,
    mxgsrc=(‘mxg-userid-sourclib’ ‘mxg-mxg-sourclib’),
    pdb=<2.7_pdb>,
    sitelib=<2.7_sitelib>);
%rmpdbexp(targetLocation=<high-level-qualifer or directory of export>);

Note: The TARGETLOCATION parameter of %RMPDBEXP is a writable directory (for UNIX or Windows). For z/OS, the TARGETLOCATION parameter is a high-level qualifier in the traditional file system, where a set of transport files is written out. One transport file is created for each needed library. The file is named with the library libref name and an extension of .cpo. Thus, if the user specifies targetLocation=/itrm/Transports, the following transport files are created:

/itrm/Transports/ADMIN.cpo
/itrm/Transports/COLLECT.cpo
/itrm/Transports/DAY.cpo
/itrm/Transports/DETAIL.cpo
/itrm/Transports/DICTLIB.cpo
/itrm/Transports/MONTH.cpo
/itrm/Transports/SITELIB.cpo
/itrm/Transports/WEEK.cpo
/itrm/Transports/YEAR.cpo

For z/OS, the created export files can be allocated in advance if the default space settings are insufficient. The DCB parameter for the files must have the following attributes: RECFM=FB, LRECL=80, and BLKSIZE=8000.

Transfer the Exported Libraries

After the libraries have been exported, the .cpo files need to be moved to the target platform. This can be accomplished by doing a binary FTP transfer or similar copy operation. If the target platform is z/OS, these transport files must reside in the traditional z/OS file system. In addition, these files must have the following DCB attributes: RECFM=FB, LRECL=80, and BLKSIZE=8000.

Import the PDB and SITELIB SAS Libraries

When the .cpo files are on the target platform, they need to be unloaded into SAS libraries on the target platform. A tool to assist with this is included as a member in the SAS IT Resource Management 3.2 SASMISC directory. This member is called RMPDBIMP.SAS. The RMPDBIMP.SAS member resides in the following locations on your SAS IT Resource Management 3.2 server tier:

Windows Specifics: <sasroot>\itmsmvadata\sasmisc

UNIX Specifics: <sasroot>/misc/itmsmvadata

z/OS Specifics: <high-level-qualifier>.ITRM.CPMISC

To perform this operation, invoke the RMPDBIMP.SAS macro as shown in the following example:

options nofmterr; 
%rmmxgini; 
/* include from the appropriate location */ 
%include ‘rmpdbimp.sas’; 
%rmpdbimp(targetLocation=c:\itrm\Ready2Migrate, sourceLocation=c:\itrm\Transports);

The following information applies to the previous example.

The TARGETLOCATION parameter of %RMPDBIMP is a writable directory or z/OS high-level qualifier where the respective libraries will be created.
On z/OS, the SOURCELOCATION parameter must specify a high-level qualifier in the traditional file system.
On z/OS, the TARGETLOCATION parameter can specify a high-level qualifier in the traditional file system or a directory in the hierarchical file system.
If the directory specified by the TARGETLOCATION parameter does not exist, it is created.
Upon successful execution of RMPDBIMP.SAS, the directory specified by the TARGETLOCATION parameter is the value to specify as the PDB parameter on the %RMPDB2DM macro.
Upon successful execution of RMPDBIMP.SAS, the SITELIB directory beneath the location specified by the TARGETLOCATION parameter is the value to specify as the SITELIB parameter to the %RMPDB2DM macro.