<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Migrating SAS dataset between environments in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108357#M30177</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the suggestions. To clarify couple of items :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) We are migrating SAS datasets between 2 environments(Solaris x64 to Linux x64), we need them to be in native format. Hence, CEDA is not used while accessing them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) CPORT/CIMPORT works well for this situation. However, we are planning to provide scripts to SAS users to convert their individual SAS datasets. I want this script to validate if the dataset is in native format &amp;amp; then convert using CPORT/CIMPORT if needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jul 2012 13:26:21 GMT</pubDate>
    <dc:creator>Nithin</dc:creator>
    <dc:date>2012-07-17T13:26:21Z</dc:date>
    <item>
      <title>Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108350#M30170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are migrating our SAS Environment from Solaris x86 to Linux x86 environment &amp;amp; need to migrate all existing SAS datasets to new environment.&lt;/P&gt;&lt;P&gt;I have used proc cport &amp;amp; cimport to do this. Is there a better way to do this? Also is there a way to validate if SAS dataset if optimized to current environment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Nithin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 15:32:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108350#M30170</guid>
      <dc:creator>Nithin</dc:creator>
      <dc:date>2012-07-16T15:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108351#M30171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you even need to do anything?&amp;nbsp; Unless your Linux is on an IBM mainframe then SAS should be able to read them.&lt;/P&gt;&lt;P&gt;It should put out a message if it needs to resort to the CEDA engine to convert on the fly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should be able to determine the representation for a dataset useing the DATAREP field in the dictionary table TABLES.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 16:55:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108351#M30171</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2012-07-16T16:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108352#M30172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;Yes, SAS datasets will work with CEDA. As there are few limitations &amp;amp; using CEDA consumes additional cpu overhead, we are planning to migrate these datasets into respective native format.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 18:06:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108352#M30172</guid>
      <dc:creator>Nithin</dc:creator>
      <dc:date>2012-07-16T18:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108353#M30173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure what the question is then.&lt;/P&gt;&lt;P&gt;Are you not able to distinguish between the migrated and non-migrated versions using the fields in either PROC CONTENTS output or the DICTIONARY tables?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 19:39:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108353#M30173</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2012-07-16T19:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108354#M30174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that Nithin misinterpreted your first comment.&amp;nbsp; As I read it, you were saying&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do a simple copy of a SAS dataset to the new environment.&amp;nbsp; Open it with SAS in the new space.&amp;nbsp; If it uses CEDA, then he should convert the files with CPORT/CIMPORT.&amp;nbsp; If not, all he needs to do is copy the files using *nix utilities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree with Nithin that using CEDA for long-term production work might be problematic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 20:08:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108354#M30174</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2012-07-16T20:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108355#M30175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another way of moving SAS data between different operating systems but maintaining "native" and optimal format is to use SAS/CONNECT and the UPLOAD/DOWNLOAD procedures. If this way is used then there is no need to CPORT/CIMPORT, even with SAS catalogs as SAS handles any translations internally. Of course you do need SAS/CONNECT licensed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 20:15:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108355#M30175</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2012-07-16T20:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108356#M30176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another way is to use PROC COPY + XPORT engine.&lt;/P&gt;&lt;P&gt;But CPORT/CIMPORT is better. why don't you want it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ksharp&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2012 02:06:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108356#M30176</guid>
      <dc:creator>Ksharp</dc:creator>
      <dc:date>2012-07-17T02:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108357#M30177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the suggestions. To clarify couple of items :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) We are migrating SAS datasets between 2 environments(Solaris x64 to Linux x64), we need them to be in native format. Hence, CEDA is not used while accessing them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) CPORT/CIMPORT works well for this situation. However, we are planning to provide scripts to SAS users to convert their individual SAS datasets. I want this script to validate if the dataset is in native format &amp;amp; then convert using CPORT/CIMPORT if needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2012 13:26:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108357#M30177</guid>
      <dc:creator>Nithin</dc:creator>
      <dc:date>2012-07-17T13:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108358#M30178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A approach is making a Linux x64 version dataset at local Solaris x64 computer, then transport it to your desired destination .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTREP= Data Set Option&lt;/P&gt;&lt;P&gt;Specifies the data representation for the output SAS data set.&lt;/P&gt;&lt;P&gt;Valid in:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTREP= Value Alias* Environment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALPHA_TRU64 ALPHA_OSF Tru64 UNIX&lt;/P&gt;&lt;P&gt;ALPHA_VMS_32 ALPHA_VMS OpenVMS on Alpha&lt;/P&gt;&lt;P&gt;ALPHA_VMS_64 OpenVMS on Alpha&lt;/P&gt;&lt;P&gt;HP_IA64 HP_ITANIUM HP-UX on Itanium 64-bit platform&lt;/P&gt;&lt;P&gt;HP_UX_32 HP_UX HP-UX on 32-bit platform&lt;/P&gt;&lt;P&gt;HP_UX_64 HP-UX on 64-bit platform&lt;/P&gt;&lt;P&gt;INTEL_ABI ABI UNIX on Intel 32-bit platform&lt;/P&gt;&lt;P&gt;LINUX_32 LINUX Linux for Intel Architecture on 32-bit&lt;/P&gt;&lt;P&gt;platform&lt;/P&gt;&lt;P&gt;LINUX_IA64 Linux for Itanium-based system on&lt;/P&gt;&lt;P&gt;64-bit platform&lt;/P&gt;&lt;P&gt;LINUX_X86_64 LINUX on x64 64-bit platform&lt;/P&gt;&lt;P&gt;MIPS_ABI ABI UNIX on 32-bit platform&lt;/P&gt;&lt;P&gt;MVS_32 MVS z/OS on 32-bit platform&lt;/P&gt;&lt;P&gt;OS2 OS/2 on Intel 32-bit platform&lt;/P&gt;&lt;P&gt;RS_6000_AIX_32 RS_6000_AIX AIX UNIX on 32-bit RS/6000&lt;/P&gt;&lt;P&gt;RS_6000_AIX_64 AIX UNIX on 64-bit RS/6000&lt;/P&gt;&lt;P&gt;SOLARIS_32 SOLARIS Solaris on SPARC 32-bit platform&lt;/P&gt;&lt;P&gt;SOLARIS_64 Solaris on SPARC 64-bit platform&lt;/P&gt;&lt;P&gt;SOLARIS_X86_64 Solaris on x64 64-bit platform&lt;/P&gt;&lt;P&gt;VAX_VMS OpenVMS VAX&lt;/P&gt;&lt;P&gt;VMS_IA64 OpenVMS for HP Integrity servers&lt;/P&gt;&lt;P&gt;64-bit platform&lt;/P&gt;&lt;P&gt;WINDOWS_32 WINDOWS Microsoft Windows on 32-bit platform&lt;/P&gt;&lt;P&gt;WINDOWS_64 Microsoft Windows 64-bit Edition (for&lt;/P&gt;&lt;P&gt;both Itanium-based systems and x64)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ksharp&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 01:48:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108358#M30178</guid>
      <dc:creator>Ksharp</dc:creator>
      <dc:date>2012-07-18T01:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108359#M30179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Ksharp... But, can I validate input dataset if its already in Linux X64 format &amp;amp; then convert if necessary?&lt;/P&gt;&lt;P&gt;-Nithin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jul 2012 18:53:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108359#M30179</guid>
      <dc:creator>Nithin</dc:creator>
      <dc:date>2012-07-24T18:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating SAS dataset between environments</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108360#M30180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure. Check it at dictionary table.&lt;/P&gt;&lt;P&gt;Notice "Data Representation Name" column contains the information you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;data class;
 set sashelp.class;run;
data class1(OUTREP=linux);
 set sashelp.class;run;
proc sql;
create table x as
 select * from dictionary.tables
&amp;nbsp; where libname='WORK';
quit;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ksharp&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2012 02:16:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Migrating-SAS-dataset-between-environments/m-p/108360#M30180</guid>
      <dc:creator>Ksharp</dc:creator>
      <dc:date>2012-07-25T02:16:23Z</dc:date>
    </item>
  </channel>
</rss>

