Configuring an ODBC DSN (data source name) on a 64-bit Windows OS for the workgroup server database

book

Article ID: 49099

calendar_today

Updated On:

Products

Nastel AutoPilot for WebSphere MQ

Issue/Introduction

AP-WMQ for Windows is built as a package of 32-bit applications. Thus, the applications, such as the workgroup server (WS), nsqmgr, and the database table make utility, nsqsqlmk, are 32-bit applications, which must interface with a 32-ODBC driver manager and database driver. These, in turn, on a 64-bit Windows OS, must be specified using the Windows 32-bit ODBC Administrator tool accessed from
%windir%\SysWOW64\odbcad32.exe
versus using the usual click-path access method on a 32-bit OS
Windows XP: Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC)
Windows Server 2003/2008: Start > Administrative Tools > Data Sources (ODBC)

When you have the 32-bit ODBC Administrator GUI tool open, you can then define a user or system-wide 32-bit ODBC data source.

Using the wrong bit-type of ODBC Administrator will result in nsqsqlmk failing to connect to the intended database (MS SQL Server, Oracle, MySQL, etc). For example, if a 32-bit nsqsqlmk application attempts to connect to a 64-bit system data source using MS SQL Server, the connection fails with the error:
[Microsoft][ODBC Driver Manager]
The specified DSN contains an architecture mismatch between the Driver and Application

Environment

Release:
Component: AUTPLT