SAS Institute. The Power to Know

FOCUS AREAS

Step 2

Migration

Execution: Migrate Files

Special Topic: Migrating without SLIBREF= across Computers

In this example, the source and target libraries are on different computers, and the SLIBREF= option is not required. If your library contains catalogs, you might need SLIBREF=. So to be certain this method is appropriate for your needs, use the PROC MIGRATE Calculator, which sends you to the correct instructions.

You can assign the source library to the IN= argument in one of the following two ways:

The direct method is possible only if you can access the library via an NFS, which is a standard protocol of UNIX operating environments. If you want to use that method, see the documentation for NFS and for your operating environment.

This example uses SAS/CONNECT software. The SAS/CONNECT server that you assign to the IN= argument must be a SAS 9 server.

Program

  1. From a session in the current release of SAS, submit the SIGNON command to invoke a SAS/CONNECT server session. Note that because you are working across computers, you might specify a machine name in the server ID:

    signon serv-ID sascmd='my-sas-invocation-command';

  2. Within this remote session, assign a libref to the source library that contains the library members to be migrated. Use the RSUBMIT and ENDRSUBMIT commands for SAS/CONNECT:

    rsubmit;
    libname source <engine> 'source-library-pathname';
    endrsubmit;

  3. In the local (client) session in the current release, assign the same source libref as in step 2. But do not assign the libref to a physical location. Instead, specify the SERVER= option with the server ID (in this example, serv-ID) that you assigned in the SIGNON command in step 1:

    libname source <engine> server=serv-ID;

  4. Assign the target library:

    libname target <engine> 'target-library-pathname';

  5. Use PROC MIGRATE:

    proc migrate in=source out=target <options>;
    run;

About RLS

See the SAS online documentation for RLS, which is a feature of SAS/SHARE and SAS/CONNECT software. If you don't have access to SAS/SHARE or SAS/CONNECT software, contact the Customer Interaction Center (phone 1-800-727-0025 or send e-mail to CICenter@sas.com).

If you cannot use RLS, then follow the instructions for migrating to a different operating environment family.

Migrating with Validation Tools

When you run PROC MIGRATE with validation tools, you generate Output Delivery System (ODS) reports that validate a successful migration. To get more information and download the tools, see see Migrating a Library with Validation Tools. Because you are migrating across machines, you are using RLS and therefore you need to download the following files:

Note that because you have no catalogs in the source library, the SLIBREF= option and the CATLIB libref in the example are not necessary. They will produce a harmless warning that you can ignore.


Return to Step 2.