<?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: Replicating UNIX Commands when NOXCMD set in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193776#M36423</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have a look a new FCOPY function, new to SAS 9.4.&amp;nbsp; It looks to be able to replace data step for file copy.&amp;nbsp; I have not used it, no 9.4 for me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Mar 2015 12:01:41 GMT</pubDate>
    <dc:creator>data_null__</dc:creator>
    <dc:date>2015-03-04T12:01:41Z</dc:date>
    <item>
      <title>Replicating UNIX Commands when NOXCMD set</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193773#M36420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to be able to replicate some basic UNIX commands but work in an environment where the NOXCMD option is set and, therefore, cannot use X, call system or %sysexec in my SAS programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My requirement is to be able to move .XML and .txt files between UNIX directories and (potentially delete them), i.e. to replicate the mv and rm UNIX commands.&amp;nbsp; I've found several examples that use data step processing to copy files on a byte-by-byte basis so could use this as the first part of a 2 step move, but can find nothing that would delete the original source file after it had been copied. Apologies if I'm missing something obvious.&amp;nbsp; If this can't be done then I have shell scripts to do this but will have to somehow include them in my LSF Flow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2015 10:57:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193773#M36420</guid>
      <dc:creator>jj_mk</dc:creator>
      <dc:date>2015-03-04T10:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating UNIX Commands when NOXCMD set</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193774#M36421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try the external file functions, e.g. FDELETE. haven't tried then under NOXCMD, but the documentation doesn't mention that as a constraint.&lt;/P&gt;&lt;P&gt;A part from that NOXCMD are typically set for a reason, you should interfere with OS level operations.&lt;/P&gt;&lt;P&gt;If you have a requirement for this, convince the SAS admin to let you have this restriction removed.&lt;/P&gt;&lt;P&gt;There is (are several?) threads in the forum on this matter, use search. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2015 11:14:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193774#M36421</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2015-03-04T11:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating UNIX Commands when NOXCMD set</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193775#M36422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On any well-maintained system, I see no need for the noxcmd restriction.&lt;/P&gt;&lt;P&gt;Moving files is a typical OS-level activity and should be done with OS tools (and shell escapes if done from within other software, eg SAS)&lt;/P&gt;&lt;P&gt;Aside from that, fdelete and the other file-related functions work even under the noxcmd restriction (just tested with fdelete()); which could make for some interesting communication if the SAS admin thinks himself safe behind the -noxcmd and you manage to delete a file that SHOULD NOT BE DELETED.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2015 11:29:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193775#M36422</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2015-03-04T11:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating UNIX Commands when NOXCMD set</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193776#M36423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have a look a new FCOPY function, new to SAS 9.4.&amp;nbsp; It looks to be able to replace data step for file copy.&amp;nbsp; I have not used it, no 9.4 for me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2015 12:01:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193776#M36423</guid>
      <dc:creator>data_null__</dc:creator>
      <dc:date>2015-03-04T12:01:41Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating UNIX Commands when NOXCMD set</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193777#M36424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys. FCOPY plus FDELETE does the job - apologies that I'd not picked up on these before. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2015 16:01:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Replicating-UNIX-Commands-when-NOXCMD-set/m-p/193777#M36424</guid>
      <dc:creator>jj_mk</dc:creator>
      <dc:date>2015-03-04T16:01:38Z</dc:date>
    </item>
  </channel>
</rss>

