Migration

Execution: Migrate Files

Special Topic: Migrating with SLIBREF= on the Same Computer

In this example, the source and target libraries are on one computer. Because the source library contains catalogs that are incompatible with the current release of SAS, the SLIBREF= option is required. To be certain this method is appropriate for your needs, use the PROC MIGRATE Calculator, which sends you to the correct instructions.

Because the source and target are on one computer, this example assigns the source library (except the catalogs) to the IN= argument directly.

The example uses the SLIBREF= argument to access the catalogs in the source library. The SLIBREF= argument must be assigned to a SAS/CONNECT or SAS/SHARE server running in a session of SAS that can access the catalogs. For example, if the source library contains SAS 8.2 catalogs created by 32-bit Solaris, SLIBREF= must be assigned to a SAS 8.2 32-bit Solaris server.

To be certain this method is appropriate for your needs, use the PROC MIGRATE Calculator, which sends you to the correct instructions.

Program

In this example, the source library was created in SAS 8.2. If catalogs were created in SAS 6 or SAS 8.2, SLIBREF= must be assigned through a SAS 8.2 server.

From a session in the current release of SAS, submit the SIGNON command to invoke a SAS/CONNECT server session:
```
signon v8srv sascmd='my-v8-sas-invocation-command';
```
Within this remote SAS 8.2 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 srclib <engine> 'source-library-pathname';
endrsubmit;
```
In the local (client) session in the current release, assign to the same source library 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, V8SRV) that you assigned in the SIGNON command in step 1:
```
libname srclib <engine> server=v8srv;
```
Assign two librefs: one to the source library and another to the target library. The source library is the same one that is assigned in step 2, but you must use a different libref:
```
libname source <engine> 'source-library-pathname;
libname target <engine> 'target-library-pathname';
```
Use PROC MIGRATE with the SLIBREF= option. For the IN= and OUT= options, specify the librefs that you assigned in step 4 (in this example, SOURCE and TARGET, respectively). Set SLIBREF= to the libref that uses the SERVER= option (in this example, SRCLIB):
```
proc migrate in=source out=target slibref=srclib <options>;
run;
```
If CATALOG is the only member type in the library and you are using the SLIBREF= option, then omit the IN= argument:
```
proc migrate out=target slibref=srclib <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.

You must have access to a 32-bit Version 8 SAS/CONNECT or SAS/SHARE server in order to specify the SLIBREF= option, which migrates the catalogs. If that is not possible, then use an alternative to PROC MIGRATE.

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:

migrate_macros.sas
migrate_RLStemplate.sas