Kevin and Daniel,
We are facing the same problem as we have to leave XP for W7
which one ?
32bits with limited memory
or 64 with more memory
with 32bit for sas or fully 64 bits for sas ?
Proc migrate seems support only sas datafiles not catalogs
the problem of catalogs is evocated at
The only solution is proc cport under Xp followed by proc cimport in W7
or for formats see at
But perhaps i am missunderstanding proc migrate
as on the preceeding page twice above Sas is writing
"To migrate catalogs, PROC MIGRATE calls PROC CPORT and PROC CIMPORT. You might notice that CPORT and CIMPORT
notes are written to the SAS log during migration. PROC CPORT and CIMPORT restrictions apply."
As proc cport must be applied on the source computer (32) and proc cimport under the target one (64)
how is it working then?
except if a sas connect derivation is builded with the use of slibref= see example 4.
After accepting the cport-cimport step:
Now the practical problem with previous sas archived data (both catalogs and tables) on cdrom dvd or inside
zip files is what to do if you have missed the 'shop' conversion
I am actually wondering if the new stattransfer 11 which is announced as fully compatible 32 64 bits
will not be the solution for the failures
despite Daniel question
(Or maybe they are defending themselves against people who have reverse engineered their proprietary dataset structure, especially in the 32-bit Windows world.)
Any comment is welcome.
Le 2/08/2011 09:25, Daniel Nordlund a écrit :
>> -----Original Message-----
>> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Kevin
>> Sent: Monday, August 01, 2011 6:27 PM
>> To: SAS-L@LISTSERV.UGA.EDU
>> Subject: SAS on 64 bit Windows 7 with 32 Bit SAS Catalogs and Data Sets
>> Guys, please tell me there is something obvious that I'm missing...
>> Finally had my first opportunity to start working with SAS under 64 bit
>> Windows 7. Didn't anticipate any major problems, but ran into some
>> From what I'm seeing, it appears that SAS under 64 bit Windows 7 can't
>> properly read SAS files (especially SAS catalogs) created under a 32 bit
>> Windows version of SAS, or vice-versa. Surely I am missing something.
>> There are far too many shops running a mixed bag of 32 and 64 bit
>> systems. There have been for a while now, and that situation doesn't
>> ready to make an abrupt change in the near future.
>> Given all of that, it would seem absolutely critical that SAS under 64 bit
>> Windows should be able to directly work with SAS files created under 32
>> Windows and vice-versa. NOT by using PROC MIGRATE, NOT by using PROC
>> Please tell me that I'm missing something obvious!!!
> Sorry to disappoint you, but you are probably not missing anything. The documentation states that 32-bit and 64-bit catalogs are not compatible. You should be able to read both 32-bit and 64-bit datasets with either 32-bit or 64-bit SAS.
> BUT, you will see notes in the log that the CEDA engine was used when reading a dataset created on the other platform, warning that efficiency might be impacted. In addition, user defined formats that are attached will not be recognized cross-platform.
> As far as SAS is concerned, 32-bit and 64-bit windows are different platforms. Apparently SAS changed the underlying dataset structure in anticipation of some future needs in a 64-bit environment. (Or maybe they are defending themselves against people who have reverse engineered their proprietary dataset structure, especially in the 32-bit Windows world.)
> Sorry I can't give you any comfort here.
> Daniel Nordlund
> Bothell, WA USA
INED (Institut National d'Etudes Démographiques)
133 Boulevard Davout 75980 Paris Cedex 20
mél : email@example.com tél : 33 (0) 1 56 06 21 54