ERROR: Conversation termination; status=1.

[kumarsandip975]

Hello, Can you please suggest possible reason to get the following error while executing below query. 

%GLOBAL conn_table;
%logon_macro(SSKC, JX123456, {SAS002}2XXXX04E3xxxxxxx2C19BCE799);

rsubmit;

options db2ssid=DVC0 ;

proc sql;

  create table LAND_KD as select *

  from connection to db2(

      select distinct substr(KODE_WD,1,2) as CUSTOMER_COUNTRY_CODE

            ,substr(EN_OMS_TK,1,35) as CUSTOMER_COUNTRY_DESC

      from qera.Cabcdf

      where kode_nm = 'ISO-LAND-KD'

  );

  disconnect from db2;

  quit;

proc download data= LAND_KD; run;

endrsubmit;

ERROR:

NOTE: Remote submit to SSKC commencing.

ERROR: Conversation termination; status=1.

ERROR: A link must be established by executing the SIGNON command before you can communicate with SSKC.

[Patrick]

Problem Note 64599: "ERROR: Conversation termination; status=1" occurs when multiple remote SAS® ses...

[Kurt_Bremser]

The macro you use (%logon_macro) fails to establish the connection to the SAS/CONNECT server.

[kumarsandip975]

@Kurt_Bremser , Ideally this macro definition is %logon_macro correct, there is no issue with macro. That is being called in backend.

[SASKiwi]

This looks suspiciously like a timeout issue on the SAS/CONNECT network connection to me. How long does it run for before the error occurs? Where is the error happening - on the query or the DOWNLOAD? If it is on the DOWNLOAD, try reducing the size of the dataset by say 50% to see if that works.

proc download data = MyData (obs = nnnnnnn); * Change the obs = number to 50% of total obs;
run;

[kumarsandip975]

@SASKiwi It is happening on Query, not on download. I have verified removing download line, but same error.

[Kurt_Bremser]

---

@kumarsandip975 wrote:
@SASKiwi It is happening on Query, not on download. I have verified removing download line, but same error.

---

Then it is possible that the inactivity of the link while the query is running causes a drop of the connection on one of the routers/firewalls. Have your network people take a look at the connection path.

[SASKiwi · Accepted solution]

Do you have other DB2 queries that work OK and this is the only one getting this error? If so what is the maximum elapsed time of the queries that work?