Help using Base SAS procedures

Using PROC MIGRATE

Reply
New Contributor
Posts: 2

Using PROC MIGRATE

Hello all,

I would like to know if it is possible to use Proc Migrate to bring in SAS formats made on a 32-bit system into a 64-bit system.

Thank you

PS- The syntax will equally be useful

SAS Employee
Posts: 232

Re: Using PROC MIGRATE

Hi there - thank you for joining the community!

I just moved your question out of the General Community into the Procedures community as I think you'll get more traction for an answer there. Have a great day!

New Contributor
Posts: 2

Re: Using PROC MIGRATE

Thank you

Super User
Posts: 10,497

Re: Using PROC MIGRATE

I have no idea on whether migrate will work. I would say try it.

If you still have a 32-bit SAS install that can see those libraries I would run proc format on each library with a format catalog and create a Cntlout dataset just in case.

I have all of the code that generates permanent user-defined formats generate cntlout datasets as datasets have the fewest issues with cross-platform conversions and can always rebuild the format catalog from them.

Super User
Posts: 9,676

Re: Using PROC MIGRATE

My reckoning is NO . proc migrate are used to migrate low version sas dataset to the high version under the same platform (i.e. both are 32 or 64 bit ).

Cross platform , you should use proc import + proc cport to transform dataset .

Xia Keshan

SAS Employee
Posts: 12

Re: Using PROC MIGRATE

PROC MIGRATE does support migrating catalogs across many incompatible environments, with the SLIBREF argument. Check your specifics with Migration: PROC MIGRATE Calculator. If the migration is supported, the calculator points you to some example code in the Base SAS Procedures Guide. If using the SLIBREF argument, you must have access to a SAS/CONNECT or SAS/SHARE server that is running on the same type of operating environment as the source library.

Valued Guide
Posts: 3,208

Re: Using PROC MIGRATE

See the reply of Maggiem   Proc migrate is encapsulating some more basic SAS routines. You are really needing SAS/Connect or SAS/Share as thye are doing the real conversion.
Could you use notepad++ to convert catalogs? Same kind of answer, yes . The real thing:  you can code you SAS-source in notpad++ so SAS/connect SAS/share will do the conversion.
Whatever you do, you must have SAS/Connect or SAS/Share. Having SAS/connect available and you have only some catalog to migrate (upload/download) than it is easy to do that.

The biggest advantage you can have with SAS/connect is you can have both versions alive and supported  as it can also downgrade catalogs 64->32bit.
Proc cport/cimport will not work due tp bitness, that is why Proc migrate is using SAS/share SAS/connect   

---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 6 replies
  • 261 views
  • 0 likes
  • 6 in conversation