<?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: PROC SQL disconnect error in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/478834#M71410</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13628"&gt;@advoss&lt;/a&gt;&amp;nbsp;- Good to hear you have a workaround. Please mark the post as answered (by you). And yes, time to move on from SAS 8.2. SAS 9.5 is due by year end!&lt;/P&gt;</description>
    <pubDate>Tue, 17 Jul 2018 20:55:34 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2018-07-17T20:55:34Z</dc:date>
    <item>
      <title>PROC SQL disconnect error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477145#M71273</link>
      <description>&lt;P&gt;We have an application that interfaces to SAS8.2.&amp;nbsp;Although SAS8.2 is no longer supported by SAS,&amp;nbsp;we need to support it&amp;nbsp;until the application is replaced.&amp;nbsp;&amp;nbsp; The UNIX sas program retrieves data from DB2 successfully, but when we do a disconnect from db2; we receive a CLI error (DB2) that the disconnect was unsuccessful, and, of course everything is broken from that point on. Everything works fine if I run with SAS9.3/SAS9.4 but there are issues, that prevent us from moving to either of those environments.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This program worked fine until this week. The only change in the SAS environment was the installation of HADOOP connectivity for SAS9.4. It should have had no impact on SAS8.2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Adding OPTION SASTRACE gives me:&lt;/P&gt;
&lt;P&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; options sastrace=',,t,d' sastraceloc=saslog;&lt;BR /&gt;4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; proc sql;&lt;BR /&gt;5&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* CONNECT TO DB2(DB=EDW5P1 USER=&amp;amp;RACF PASSWORD=&amp;amp;PASSW READBUFF=200 ); */&lt;BR /&gt;6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* EXECUTE (SET CURRENT QUERY OPTIMIZATION =2) by db2; */&lt;BR /&gt;7&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CONNECT TO DB2 (DB=EDW5P1 USER=&amp;amp;RACF PASSWORD=&amp;amp;PASSW);&lt;BR /&gt;TRACE: Successful connection made, connection id 0 0 1531324028 sqpcon 0 SQL&lt;BR /&gt;TRACE: Database/data source: EDW5P1 1 1531324028 sqpcon 0 SQL&lt;BR /&gt;TRACE: USER=HCD, PASS=XXXXXXX 2 1531324028 sqpcon 0 SQL&lt;BR /&gt;TRACE: AUTOCOMMIT is YES for connection 0 3 1531324028 sqpcon 0 SQL&lt;BR /&gt;8&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; create table TS as&lt;BR /&gt;9&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; select * from connection to db2 (&lt;BR /&gt;10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; select current timestamp as TS1&lt;BR /&gt;11&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; from SYSIBM.SYSDUMMY1&lt;BR /&gt;12&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; WITH UR);&lt;BR /&gt;Prepare stmt: select current timestamp as TS1 from SYSIBM.SYSDUMMY1 WITH UR 4 1531324028 sqprslv 0 SQL&lt;/P&gt;
&lt;P&gt;TRACE: SQL stmt prepared on statement 0, connection 0 is:&lt;BR /&gt;&amp;nbsp; select current timestamp as TS1 from SYSIBM.SYSDUMMY1 WITH UR 5 1531324028 sqprslv 0 SQL&lt;/P&gt;
&lt;P&gt;TRACE: DESCRIBE on statement 0, connection 0. 6 1531324028 sqprslv 0 SQL&lt;BR /&gt;TRACE: Open cursor from statement 0 on connection 0 7 1531324028 sqxextr 0 SQL&lt;BR /&gt;NOTE: Table WORK.TS created, with 1 rows and 1 columns.&lt;/P&gt;
&lt;P&gt;TRACE: Close cursor from statement 0 on connection 0 8 1531324028 sqpclos 0 SQL&lt;BR /&gt;13&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; disconnect from DB2;&lt;BR /&gt;TRACE: Successful disconnection, id 0 9 1531324028 sqpdis 0 SQL&lt;BR /&gt;TRACE: Successful CLI free environment from connection 0 10 1531324028 sqpdis 0 SQL&lt;BR /&gt;ERROR: CLI disconnect failed: Unable to retrieve error message.&lt;BR /&gt;NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements.&lt;BR /&gt;14&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; quit;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for your assistance.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jul 2018 16:39:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477145#M71273</guid>
      <dc:creator>advoss</dc:creator>
      <dc:date>2018-07-11T16:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: PROC SQL disconnect error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477248#M71279</link>
      <description>&lt;P&gt;Has there been any change in your DB2 environment? The only problem seems to be the failure to retrieve an error message.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jul 2018 20:56:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477248#M71279</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-07-11T20:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: PROC SQL disconnect error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477257#M71280</link>
      <description>Not that I am aware of, but that doesn't mean that there hasn't been.  I will pursue that line with our DBAs.</description>
      <pubDate>Wed, 11 Jul 2018 21:26:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/477257#M71280</guid>
      <dc:creator>advoss</dc:creator>
      <dc:date>2018-07-11T21:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: PROC SQL disconnect error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/478667#M71389</link>
      <description>&lt;P&gt;As is often the case, "nothing has changed".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was able to use PROC SQL option NOERRORSTOP to ignore the error.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now it is time to retire SAS8.2 from our tool environment.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2018 14:25:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/478667#M71389</guid>
      <dc:creator>advoss</dc:creator>
      <dc:date>2018-07-17T14:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: PROC SQL disconnect error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/478834#M71410</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13628"&gt;@advoss&lt;/a&gt;&amp;nbsp;- Good to hear you have a workaround. Please mark the post as answered (by you). And yes, time to move on from SAS 8.2. SAS 9.5 is due by year end!&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2018 20:55:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-SQL-disconnect-error/m-p/478834#M71410</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-07-17T20:55:34Z</dc:date>
    </item>
  </channel>
</rss>

