<?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: Remote sessions Parent and child relationship in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Remote-sessions-Parent-and-child-relationship/m-p/386035#M92425</link>
    <description>1. Use a separate libref for data that should be shared.   INHERITLIB= SIGNON option can make that easier. Or download the remote saswork data to the local session. Or use the pathname info to assign a new library from the local session to the remote saswork (hint: see %syslput and %sysrput).&lt;BR /&gt;2. See the LOG= option for the SIGNON statement. &lt;BR /&gt;3.Then why have wait=no?</description>
    <pubDate>Mon, 07 Aug 2017 14:41:19 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2017-08-07T14:41:19Z</dc:date>
    <item>
      <title>Remote sessions Parent and child relationship</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Remote-sessions-Parent-and-child-relationship/m-p/386012#M92417</link>
      <description>&lt;P&gt;Hi all, I f&lt;/P&gt;&lt;P&gt;have a simple peace of code:&lt;/P&gt;&lt;P&gt;/*Grid Enabling section*/&lt;BR /&gt;%let rc=%sysfunc(grdsvc_enable(_all_,resource=SASAppCore));&lt;BR /&gt;%let rc=%sysfunc(grdsvc_nnodes(resource=SASAppCore));&lt;BR /&gt;%put Number of Grid Nodes=&amp;amp;rc;&lt;BR /&gt;options autosignon;&lt;BR /&gt;/*End of Enablement Signon*/&lt;BR /&gt;&lt;BR /&gt;%put %sysfunc(pathname(work));&lt;BR /&gt;&lt;BR /&gt;rsubmit task1 wait=no ;&lt;BR /&gt;%put %sysfunc(pathname(work));&lt;BR /&gt;OPTIONS FULLSTIMER SOURCE SOURCE2 MSGLEVEL=I MPRINT NOTES;&lt;BR /&gt;Data TEST2;&lt;BR /&gt;X=1;&lt;BR /&gt;Run;&lt;BR /&gt;endrsubmit;&lt;BR /&gt;&lt;BR /&gt;Data TEST1;&lt;BR /&gt;x=10;&lt;BR /&gt;Run;&lt;BR /&gt;&lt;BR /&gt;signoff task1;&lt;/P&gt;&lt;P&gt;We are running SAS Grid 9.4 on Linux. &amp;nbsp;&lt;/P&gt;&lt;P&gt;1. I need to share the two work sessions created, because I may have a dataset in one which I would like to merge with Test1.&lt;/P&gt;&lt;P&gt;2. I would like to have two sets of logs, parent and child (test1.log and test2.log)&lt;/P&gt;&lt;P&gt;3. If task 1 has an error, I would like the dataset Test1 not to execute&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please help. Thank you&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 14:53:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Remote-sessions-Parent-and-child-relationship/m-p/386012#M92417</guid>
      <dc:creator>Deonjpret</dc:creator>
      <dc:date>2017-08-07T14:53:25Z</dc:date>
    </item>
    <item>
      <title>Re: Remote sessions Parent and child relationship</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Remote-sessions-Parent-and-child-relationship/m-p/386035#M92425</link>
      <description>1. Use a separate libref for data that should be shared.   INHERITLIB= SIGNON option can make that easier. Or download the remote saswork data to the local session. Or use the pathname info to assign a new library from the local session to the remote saswork (hint: see %syslput and %sysrput).&lt;BR /&gt;2. See the LOG= option for the SIGNON statement. &lt;BR /&gt;3.Then why have wait=no?</description>
      <pubDate>Mon, 07 Aug 2017 14:41:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Remote-sessions-Parent-and-child-relationship/m-p/386035#M92425</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-08-07T14:41:19Z</dc:date>
    </item>
  </channel>
</rss>

