Hi,
1)Currently we are migrating SAS Data from Unix server to Linux server.
We have identified that some sas datasets have Data Representation as WINDOWS_32. The data files (.sas7bdat) are getting migrated successfully but not the index files. For these files , the output of PROC CONTENTS shows Indexes as 0.
How to understand this and how would we migrate these index files?
2) Some catalog files (.sas7bcat) ,when tried accessing using PROC CATALOG procedure, the message in the log was " xxxxxx.catalog "was created for a different operating system. How do we handle this.
Most of these catalog files have formats in them.
Thanks,
Vijayanand.
1) As much as I know you can't emigrate indexes. You should recreate them.
2) You can continue work with the catalogs and ignore the message: "...catalog was created for a different operating system"
but it may require more cpu resources. Other way to emigrate them is by CPORT and CIMPORT functions.
http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/viewer.htm#a002576217.htm
http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/viewer.htm#a002576216.htm
When you say data files "are getting migrated successfully," what are you using to migrate?
PROC MIGRATE can migrate your indexes and most other library members and attributes.
If you have access to a SAS/CONNECT or SAS/SHARE server, PROC MIGRATE can also migrate the catalogs.
See PROC MIGRATE.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.