<?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: An error occurred executing the workspace job &amp;quot;input method&amp;quot; in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834510#M35888</link>
    <description>&lt;P&gt;See if this helps:&lt;/P&gt;
&lt;PRE&gt;Data Ex_3;
infile '‪‪D:\example_3.txt' encoding='utf-16le';
Input Name$ 1-7 height 9-10 weight 12-14;
BMI=700*weight/(height*height);
output;
run;&lt;/PRE&gt;
&lt;P&gt;This should tell SAS that the external file is that encoding and set up how to read it.&lt;/P&gt;
&lt;P&gt;You may need to increase the number of "columns" read as some of the UTF-16 characters may take up more space when converted. You may also get some very interesting results depending on the actual source.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For what it is worth one of the first UTF-16 files I encountered had every character when read preceded by a space. What looked like "Fred" in the file was read as " F r e d".&lt;/P&gt;</description>
    <pubDate>Wed, 21 Sep 2022 15:10:12 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2022-09-21T15:10:12Z</dc:date>
    <item>
      <title>An error occurred executing the workspace job "input method"</title>
      <link>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834431#M35876</link>
      <description>&lt;P&gt;Integration technologies failed to submit the code. [Error] Failed to transcode data from utf-16le to wlatin1 encoding because it contained character which are not supported by your SAS session encoding.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;that's the dataset i am trying to run&lt;/P&gt;&lt;P&gt;Data Ex_3;&lt;BR /&gt;infile '‪‪D:\example_3.txt';&lt;BR /&gt;Input Name$ 1-7 height 9-10 weight 12-14;&lt;BR /&gt;BMI=700*weight/(height*height);&lt;BR /&gt;output;&lt;BR /&gt;run;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 08:49:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834431#M35876</guid>
      <dc:creator>vinayp913</dc:creator>
      <dc:date>2022-09-21T08:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: An error occurred executing the workspace job "input method"</title>
      <link>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834510#M35888</link>
      <description>&lt;P&gt;See if this helps:&lt;/P&gt;
&lt;PRE&gt;Data Ex_3;
infile '‪‪D:\example_3.txt' encoding='utf-16le';
Input Name$ 1-7 height 9-10 weight 12-14;
BMI=700*weight/(height*height);
output;
run;&lt;/PRE&gt;
&lt;P&gt;This should tell SAS that the external file is that encoding and set up how to read it.&lt;/P&gt;
&lt;P&gt;You may need to increase the number of "columns" read as some of the UTF-16 characters may take up more space when converted. You may also get some very interesting results depending on the actual source.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For what it is worth one of the first UTF-16 files I encountered had every character when read preceded by a space. What looked like "Fred" in the file was read as " F r e d".&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 15:10:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834510#M35888</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2022-09-21T15:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: An error occurred executing the workspace job "input method"</title>
      <link>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834516#M35889</link>
      <description>&lt;P&gt;Two issues.&lt;/P&gt;
&lt;P&gt;1) WLATIN1 is a single byte encoding. So it can only represent 256 distinct characters.&amp;nbsp; At least one of the characters in your file is not one of those characters.&amp;nbsp; To fix this you need to start SAS using a different encoding.&amp;nbsp; How to do that differs based on how you are running SAS.&amp;nbsp; If you have it installed on your PC look for "SAS 9.4 (Unicode support)" icon in your Start menu.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) Fixed column input will not work well with Unicode characters.&amp;nbsp; Some characters use more than one byte, which will mess up the column counting.&amp;nbsp; &amp;nbsp;Does the data contain a delimiter between the fields?&amp;nbsp; Post some of the lines of data as plain text instead of as an attachment.&amp;nbsp; Just open the text file in a text editor and copy a few lines and paste them into the pop-up window that appears when you click the Insert Code icon in the forum editor (the icon looks like the character string&amp;nbsp; &amp;lt; / &amp;gt; ).&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 15:38:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/An-error-occurred-executing-the-workspace-job-quot-input-method/m-p/834516#M35889</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2022-09-21T15:38:33Z</dc:date>
    </item>
  </channel>
</rss>

