<?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: ERROR faced in SAS Data Integration Studio 3.4 in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-faced-in-SAS-Data-Integration-Studio-3-4/m-p/68217#M19533</link>
    <description>This webpage I found using the SEARCH facility at the SAS support  &lt;A href="http://support.sas.com/" target="_blank"&gt;http://support.sas.com/&lt;/A&gt;  website mentions the CEDA (cross-environment data access) limitations and also version-migration (to include different OS platforms) considerations.&lt;BR /&gt;
&lt;BR /&gt;
You will need to investigate your own SAS operating environment (server or local) and the origin of your SAS database(s) to determine if the contents were created on a different SAS-environment OS platform.  What SAS is telling you is that the file you are attempting to access was likely created on a SAS system installed in a different OS platform environment -- only you can determine this fact through investigation, but it's likely that you will need to figure out the problem cause.&lt;BR /&gt;
&lt;BR /&gt;
For the purpose of "transport" to a different CEDA-compatible OS platform, SAS provides a "transport format" file structure making its database files compatible for transfer between operating platforms.  So if you intend to "move SAS application processing" to a different OS, there are definitely migration considerations which are also discussed at the SAS support website.  The webpage below has several links to relevant topic-oriented articles and SAS-hosted documentation.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
MIGRATION - CEDA (cross-environment data access) topic:&lt;BR /&gt;
&lt;A href="http://support.sas.com/rnd/migration/planning/files/ceda.html" target="_blank"&gt;http://support.sas.com/rnd/migration/planning/files/ceda.html&lt;/A&gt;</description>
    <pubDate>Mon, 31 Aug 2009 12:42:54 GMT</pubDate>
    <dc:creator>sbb</dc:creator>
    <dc:date>2009-08-31T12:42:54Z</dc:date>
    <item>
      <title>ERROR faced in SAS Data Integration Studio 3.4</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-faced-in-SAS-Data-Integration-Studio-3-4/m-p/68216#M19532</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
ERROR: File STG_SEAB.PU_NAME cannot be updated because its encoding does not match the session encoding or the file is in a format &lt;BR /&gt;
       native to another host, such as HP_UX_64, RS_6000_AIX_64, SOLARIS_64, HP_IA64.&lt;BR /&gt;
&lt;BR /&gt;
Have anyone seen this error before?&lt;BR /&gt;
&lt;BR /&gt;
Previously my job can run succesfully.&lt;BR /&gt;
&lt;BR /&gt;
Now because of this error, my job ended up with error(s).&lt;BR /&gt;
&lt;BR /&gt;
Do anyone know how to sovle this error?&lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;BR /&gt;
&lt;BR /&gt;
Yours Sincerely,&lt;BR /&gt;
helphelp

Message was edited by: HelpHelp</description>
      <pubDate>Mon, 31 Aug 2009 03:18:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/ERROR-faced-in-SAS-Data-Integration-Studio-3-4/m-p/68216#M19532</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-08-31T03:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR faced in SAS Data Integration Studio 3.4</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-faced-in-SAS-Data-Integration-Studio-3-4/m-p/68217#M19533</link>
      <description>This webpage I found using the SEARCH facility at the SAS support  &lt;A href="http://support.sas.com/" target="_blank"&gt;http://support.sas.com/&lt;/A&gt;  website mentions the CEDA (cross-environment data access) limitations and also version-migration (to include different OS platforms) considerations.&lt;BR /&gt;
&lt;BR /&gt;
You will need to investigate your own SAS operating environment (server or local) and the origin of your SAS database(s) to determine if the contents were created on a different SAS-environment OS platform.  What SAS is telling you is that the file you are attempting to access was likely created on a SAS system installed in a different OS platform environment -- only you can determine this fact through investigation, but it's likely that you will need to figure out the problem cause.&lt;BR /&gt;
&lt;BR /&gt;
For the purpose of "transport" to a different CEDA-compatible OS platform, SAS provides a "transport format" file structure making its database files compatible for transfer between operating platforms.  So if you intend to "move SAS application processing" to a different OS, there are definitely migration considerations which are also discussed at the SAS support website.  The webpage below has several links to relevant topic-oriented articles and SAS-hosted documentation.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
MIGRATION - CEDA (cross-environment data access) topic:&lt;BR /&gt;
&lt;A href="http://support.sas.com/rnd/migration/planning/files/ceda.html" target="_blank"&gt;http://support.sas.com/rnd/migration/planning/files/ceda.html&lt;/A&gt;</description>
      <pubDate>Mon, 31 Aug 2009 12:42:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/ERROR-faced-in-SAS-Data-Integration-Studio-3-4/m-p/68217#M19533</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-08-31T12:42:54Z</dc:date>
    </item>
  </channel>
</rss>

