01-27-2015 12:16 PM
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!
01-27-2015 03:27 PM
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.
01-28-2015 04:46 AM
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 .
05-28-2015 03:12 PM
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.
05-28-2015 03:25 PM
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