Start of change

Setting your environment to access databases

When you have configured your ODBC data source names, you must also configure the environment for issuing console commands, and for running the broker, so that it can access the required database libraries. For example, if you have a DB2 broker database, you must add the DB2 client libraries to your library search path.

On Windows platforms, this is likely to have been done for you when you installed the database product. On UNIX systems, and Linux, you need to run a profile for each database you need to access. For example, on DB2 you must run db2profile; other database vendors have similar profiles.

If you are using a 64-bit DB2 instance, ensure that you add <DB2 instance directory>/sqllib/lib32 to the start of the library search path environment variable after running db2profile. If you are using a 64-bit Oracle instance, ensure that you add $ORACLE_HOME/lib32 to the start of the library search path environment variable. If you are using 64-bit execution groups, ensure that you set the environment variable MQSI_LIBPATH64 to include the regular 64-bit database libraries.

Additionally, ensure that you access the correct set of libraries (32-bit) because this might not be the default.

If you are using WebSphere MQ Version 6, refer to the section 'Implications of a 64-bit queue manager' in WebSphere MQ Quick Beginnings for your operating environment.

End of change