<?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: Mainframe to Unix in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333238#M62828</link>
    <description>&lt;P&gt;You would have to copy your data files to Unix first perhaps using FTP with the BINARY option then use the S370**** informats on your SAS INPUT statement to read the data.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Feb 2017 00:14:35 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2017-02-16T00:14:35Z</dc:date>
    <item>
      <title>Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333224#M62821</link>
      <description>Hi&lt;BR /&gt;If I m.running sas on Unix can i still import or read in files from mainframe or even my local.machine?&lt;BR /&gt;&lt;BR /&gt;Thx</description>
      <pubDate>Wed, 15 Feb 2017 23:29:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333224#M62821</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-15T23:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333227#M62822</link>
      <description>&lt;P&gt;What sort of files? Data files, SAS datasets or something else? If mainframe data files then you need to be very careful as they could contain mainframe-specific data formats like packed decimal or packed binary. You can still read these on Unix if you&amp;nbsp;transfer them from the mainframe in binary format. If the files are just&amp;nbsp;text or numbers then probably a non-binary transfer would be OK. Reading PC files is no issue as both Unix and PCs use the ASCII data representation standard. Mainframe uses EBCDIC&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 23:50:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333227#M62822</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-02-15T23:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333229#M62823</link>
      <description>Yea simple data files ( text n numbers)&lt;BR /&gt;So i can read them in in a date step but i cannot import them?</description>
      <pubDate>Wed, 15 Feb 2017 23:58:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333229#M62823</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-15T23:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333232#M62824</link>
      <description>And if i need to read them in as a binary file how do i specify it. Is it with the infile statement ?</description>
      <pubDate>Thu, 16 Feb 2017 00:00:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333232#M62824</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333233#M62825</link>
      <description>&lt;P&gt;Both should work if either one does. I suspect there may be some fun involved with paths though. And servers can throw in complications as the paths have to be as seen by the server.&lt;/P&gt;
&lt;P&gt;I'm not fond of Proc Import as there is too much guessing going on.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 00:02:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333233#M62825</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2017-02-16T00:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333235#M62826</link>
      <description>Thank you all! Much appreciated</description>
      <pubDate>Thu, 16 Feb 2017 00:04:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333235#M62826</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333236#M62827</link>
      <description>They already have the paths in the code but they been running it on EG and i feel more comfortable running it on unix so wanted to make sure i can still read in from mainframe and the local machine as they like to keep the files there</description>
      <pubDate>Thu, 16 Feb 2017 00:06:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333236#M62827</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:06:35Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333238#M62828</link>
      <description>&lt;P&gt;You would have to copy your data files to Unix first perhaps using FTP with the BINARY option then use the S370**** informats on your SAS INPUT statement to read the data.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 00:14:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333238#M62828</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-02-16T00:14:35Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333239#M62829</link>
      <description>I was hoping to automate that process so i hope i wont need to move the files manually</description>
      <pubDate>Thu, 16 Feb 2017 00:19:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333239#M62829</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333240#M62830</link>
      <description>&lt;P&gt;You can FTP from SAS. Check with IT admin regarding how you can access the mainframe and its data&amp;nbsp;from Unix.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 00:25:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333240#M62830</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-02-16T00:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333241#M62831</link>
      <description>Thanks. But can i still specify a binary format from within sas?</description>
      <pubDate>Thu, 16 Feb 2017 00:28:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333241#M62831</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: Mainframe to Unix</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333243#M62832</link>
      <description>Ok just checked on sas.com and i can specify it all&lt;BR /&gt;Thank you</description>
      <pubDate>Thu, 16 Feb 2017 00:34:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Mainframe-to-Unix/m-p/333243#M62832</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-02-16T00:34:07Z</dc:date>
    </item>
  </channel>
</rss>

