%META:TOPICPARENT{name="ErrorMessagesN"}%
==Error Messages (N)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

    
===No <nop>OpenLink ODBCINST.INI file found===

The "No <nop>OpenLink ODBCINST.INI file found" error message suggests that the ODBCINSTINI environment variable has not been set. If you receive this error, take the following action:

1. cd into the root directory of your <nop>OpenLink client components installation. For example:

{{{
$ cd /usr/openlink
}}}

2. Run the command which corresponds to your Unix shell. For example:

{{{
$ . ./openlink.sh // Bourne, Korn, and Bash Shells
$ source openlink.csh //C Shells
}}}

3. Run set. Insure that ODBCINI, ODBCINSTINI, and UDBCINI are set. For example:

{{{
$ set
SHLIB_PATH=:/home/openlink/32bit/lib
TERM=vt100
TMOUT=0
TZ=EST5EDT
UDBCINI=/home/openlink/32bit/bin/udbc.ini
}}}

4. Test.

If your variables are not set, use a text editor to open the openlink.sh or openlink.csh script. Take note of the environment variables. Then, try to set them on the command line. For example:

{{{
$ cd /usr/openlink
$ vi openlink.sh

UDBCINI=/home/openlink/32bit/v40/bin/udbc.ini
ODBCINI=/home/openlink/32bit/v40/bin/odbc.ini
ODBCINSTINI=/home/openlink/32bit/v40/bin/odbcinst.ini
:q!

$ export UDBCINI=/home/openlink/32bit/v40/bin/udbc.ini
$ export ODBCINI=/home/openlink/32bit/v40/bin/odbc.ini
$ export ODBCINSTINI=/home/openlink/32bit/v40/bin/odbcinst.ini
}}}    

===Evidence===

Name of .taz files
Output of set
uname -a