Oninit Logo
The Down System Specialists
+1-913-674-0360
+44-2081-337529
Partnerships Contact
Finderr

-29049 Unable to locate/open Gateway setup file filename.

If you are using IPC-pipe mode to start the Gateway process, you should ensure that the INFORMIXDIR environment variable was set correctly before the application starts.

* For IBM Informix Enterprise Gateway with DRDA:

An error occurred while locating or opening a Gateway ISAM setup file that the gwdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

If you are using network connections, the IBM Informix Enterprise Gateway with DRDA database administrator must ensure that the named file exists in the $INFORMIXDIR/gw/sysinfo directory. If the file is missing, run gwdba to create it. The DBA also must ensure that the INFORMIXDIR environment variable was set correctly at the time that the gwd daemon was started.

* For IBM Informix Enterprise Gateway:

An error occurred while locating or opening an IBM Informix Enterprise Gateway ISAM setup file that the egwdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

If you are using network connections, the IBM Informix Enterprise Gateway DBA must ensure that the named file exists in the $INFORMIXDIR/egw/sysinfo directory. If the file is missing, run egwdba to create it. The DBA also must ensure that the INFORMIXDIR environment variable was set correctly at the time that the egwd daemon was started.

* For IBM Informix Enterprise Gateway Manager:

An error occurred while locating or opening a Gateway ISAM setup file that the egmdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

If you are using network connections, the IBM Informix Enterprise Gateway Manager database administrator must ensure that the named file exists in the "$INFORMIXDIR/egm/sysinfo" directory. If the file is missing, run "egmdba" to create it. The DBA also must ensure that the INFORMIXDIR environment variable was set correctly at the time that the "egmd" daemon was started.