When you upgrade your operating system from Microsoft Windows 32-bit to Microsoft Windows 64-bit running a release of SAS prior to SAS^® 9.3, Cross-Environment Data Access (CEDA) is invoked to access your 32-bit SAS data sets. For more information about CEDA processing restrictions, see CEDA Limitations. 64-bit SAS provides no access to 32-bit catalogs. You should not remove your 32-bit version of SAS until it can be verified that all 32-bit catalogs were successfully migrated.

For releases prior to SAS 9.3, the MIGRATE procedure can be used to migrate 32-bit SAS data sets to 64-bit, thus changing the format so that CEDA is not required to translate the file. For a code example, step through the Migration Calculator to obtain specific instructions for your environment. Click here for access to the Migration Calculator. PROC MIGRATE can be used for migrating catalogs if you have SAS/SHARE^® software or SAS/CONNECT^® running in the source and target environment. The remainder of this note addresses conversion methods for individual files within a library.

 

• 32-bit to 64-bit conversion of data files (data sets)

  Regarding individual SAS data files, PROC COPY in conjunction with the NOCLONE option can be submitted in your SAS 64-bit Windows session. If you are referencing a 32-bit Windows data set, you will be using CEDA to access it unless you are running SAS 9.3, so processing restrictions will apply. However, the NOCLONE option prevents cloning the data representation in the copy operation. The resulting file will be native to the 64-bit operating system, and CEDA will no longer be necessary to process the file. See an example in SAS Note 15379, "Cross-Environmental Data Access (CEDA) utilization message."

   

• 32-bit to 64-bit conversion of catalogs

  Regarding catalogs, if you are running SAS in a 64-bit session and attempt to open a catalog created in a 32-bit SAS session, you will receive the following error:

  ERROR: CATALOG was created for a different operating system.
  

  The CPORT procedure can be used to create a transport file in the 32-bit SAS session and the CIMPORT procedure can be used to re-create the catalogs in the 64-bit operating system. PROC CPORT defaults to converting the entire library unless you specify members of the library using a SELECT or EXCLUDE statement or the MEMTYPE= option. The sample code on the Full Code tab illustrates how to convert a Windows 32-bit catalog to a Windows 64-bit catalog using the MEMTYPE= option. Note that stored compiled macro catalogs are not supported by PROC CPORT and must be recompiled in the new operating environment, see SAS Note 46846, "Compatibility of stored compiled macro catalogs across releases of SAS and across operating systems."

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	Base SAS	Microsoft® Windows® for 64-Bit Itanium-based Systems	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	9.1 TS1M3 SP4
		Microsoft Windows XP 64-bit Edition	9.1 TS1M3 SP4
		Microsoft Windows 2000 Advanced Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional	9.1 TS1M3 SP4
		Microsoft Windows NT Workstation	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition	9.1 TS1M3 SP4
		Microsoft Windows XP Professional	9.1 TS1M3 SP4
		Windows Vista	9.1 TS1M3 SP4

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

One way to convert a 32-bit Windows catalog to Windows 64-bit is to create a transport file in the 32-bit SAS session using PROC CPORT and import the transport file using PROC CIMPORT in your 64-bit SAS session. The example below introduces the MEMTYPE= option in PROC CPORT to subset the catalogs. In the example below, the only files being converted are those with the .SAS7BCAT extensions.

---

/* In 32-bit SAS, assume that the source */
/* folder exists as 'c:\my32files' */
filename all 'c:\trans.cpo';
libname my32 'c:\my32files';

proc cport file=all lib=my32 memtype=catalog;
run;

/* In 64-bit SAS, assume that the target */
/* folder exists as 'c:\my64files' */

filename all 'c:\trans.cpo';
libname my64 'c:\my64files';

proc cimport infile=all lib=my64;
run;

This note provides information for customers who are upgrading from 32-bit to 64-bit Microsoft Windows.

Type:	Usage Note
Priority:

Date Modified:	2010-04-22 15:13:18
Date Created:	2010-01-08 15:43:56