Informix Enterprise Gateway Manager Error

Hi All, I am testing connecting to the mssql server through egm. When connecting to the mssql data source using dbaccess directly as shown below, sql runs fine. Instead, when using in the form of distributed query as shown below, a 908 error occurs and the egmd process crashes. Is there any way to see if this is happening for some reason? The EGM is version 7.31.UD4, and the environment variable GWDIRECTMODE is set to 1. I also tried setting GWDEBUG=121,122,123 but there was no debug message when the egmd process was down. Thanks for reading. ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------ #Informix

Hi S angGyu, Seems like process was not running. Anything logged in online.log or in egm.log. -908 Attempt to connect to database server (servername) failed.The program or application is trying to access another database server but has failed. Note the server name in the current statement. ------------------------------ Gaurav Kumar ------------------------------

Thanks for reply Gaurav, When the egm process goes down, there are no messages at all in online.log and egm.log. Even odbc trace or mssql server does not generate log messages. Does this happen because the sql server version is 2017? ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------

Hi SangGyu, I would suggest you to open a new case for this. And BTW what is the length of your saved password? ------------------------------ Gaurav Kumar ------------------------------

Thanks for the quick response. I personally built a system for testing, so I don't think I can open the case. Password length is 8 characters. ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------

Hi SangGyu, Okay so if you are testing it for personal use then test it with latest version of MS SQL SERVER. Your second query also looks good to me. Something to investigate SQLHOSTS file and odbc.ini Can you access your msql@egm731ud4 through dbaccess and access the tables ------------------------------ Gaurav Kumar ------------------------------

Hi SangGyu , My guess is you have different sqlhosts configuration there. On the sqlhosts of your database you don't set the egm731ud4 host. Using the direct mode, the dbaccess will use the local SQLHOSTS. BTW, here I'm using EGM 7.31.ud4x1 to connect SQLSERVER versions 2000, 2008, 2008 R2, 2014, and all works fine. The unique issue I have with it is a huge flaw on the Datadirect ODBC when you interrupt a statement, they don't interrupt on the SQLSERVER, your EGM will receive 100% of the data. So if you have a SELECT which returns 1 million records and you fetch only the first record and close the cursor, your session will freeze waiting for the EGM receiving the rest of the 999.999 records to free your cursor... so, beware. We use with EGM accessing Oracle databases and this issue doesn't happen. Regards Cesar

Thanks you for reply Cesar, In short, all components are on the same host as shown below. I will try again with a lower version of SQL SERVER. Informix 14.10.FC4W1DE (dbaccess) ===> EGM 7.31.UD4 / DataDirect ODBC ===> SQLSERVER 2017 sqlhosts (Informix 14.10) ol_informix1410_2 onsoctcp db2 ol_informix1410_2 dr_informix1410_2 drsoctcp db2 dr_informix1410_2 lo_informix1410_2 onsoctcp 127.0.0.1 lo_informix1410_2 egm731ud4 onsoctcp db2 9660 sqlhosts (EGM) egm731ud4 onsoctcp db2 9660In addition, thank you for sharing your issues. ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------

One correction, here we access sqlserver 2017 too, without any issues. What you can do to try to identify what happens is uncomment at informix.rc the line GWDEBUG 121,122,123 Don't need to restart the EGM. Just rerun your sql Then you will see a file at /tmp/egmt.* Take a look, maybe you able to identify something there.

ouch, I just remember; you probably get into a defect. I just remember that I got an issue like this. I have an SB were solved this and the problem is on version 14.10.FC3W1 My SB is 14.10.FC4W1X3 Maybe you need to wait for the FC4W2 , FC5 os ask for an SB to your environment. The defect : APAR IT33397 - FRONT END VERSION (FEVERS) IS SENT AS '14.10' RATHER THAN '9.59' THE SQL VERSION (SQVERS)

correction: I have an SB were solved this and the problem is on version 14.10.FC4W1

Thank you Cesar, The GWDEBUG environment variable is set, but in my case, the /tmp/egmt.** file was not created when the egm process was down. And thank you for sharing information on APAR IT33397. It seems that it is not a version problem as it is used well in SQL SERVER 2017. I should review the EGM configuration procedure to make sure there are no mistakes. ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------

if you can, test using version 12.10 .. all works fine with it.

Hello Cesar, Due to laziness, sharing of test results was late. When I used the odbc driver manager included in 7.31.ud4, I could not use distributed sql in the sql server and oracle, but when I used the odbc driver manager of 7.31.ud3, it worked well. It seems to be a problem with odbc configuration rather than an egm version problem. Thank you again for your advice in various ways. ------------------------------ SangGyu Jeong Software Engineer Infrasoft Seoul Korea, Republic of ------------------------------