WDI 3.2 triggering, not working with MQ 6.0, or when migrating WDI 3.2 to 3.3 on AIX 64 bit operating system.

Answer

Step 1:
To resolve the error:"0509-124 The program is a discontinued 64-bit object file"
You must remove the symbolic links ( Soft Links ) in /usr/lib that point to the 64 bit libraries for WMQ 6.0

Step 2:
To resolve the error: "Unable to open module: edimqs"

WDI 3.2 or 3.3 temporary solution to the problem:
To work around this problem you can modify the Application Identifier field in the WMQ Process Definition for WDI.PROC to look like this:

WDI 3.2 -WDI.PROC



WDI 3.3 - WDI.PROC



By adding the LIBPATH=/usr/mqm/lib:$LIBPATH to the Application ID field when the runmqtrm executable creates a new shell and executes the WDIAdapter program the LIBPATH environment variable will contain the correct paths to locate the MQ libraries but will not interfere with the MQ commands.


Setting LIBPATH to Include MQ Library Directory:
Because of the way WebSphere MQ locates its modules, updating the LIBPATH to include the /usr/mqm/lib directory in a shell where MQ Series commands are going to be executed will cause errors. The MQSeries commands need to be run in a shell where LIBPATH has not been updated to include this path. If you set LIBPATH in a shell where you will be running an MQ command you will see this error.

exec(): 0509-036 Cannot load program /usr/bin/runmqtrm because of the following errors:

0509-150 Dependent module /usr/mqm/lib/libmqmcs_r.a(shr.o) could not be loaded.
0509-124 The program is a discontinued 64-bit object file.

This is why in the above solution we modified the Application ID field. This will set the proper LIBPATH environment for WDI to run but will not interfere with the MQSeries environment.



WDI 3.3 permanent solution to the problem:
In the future, the WebSphere Data Interchange 3.3 build environment will be modified as an APAR fix, so that LIBPATH includes /usr/mqm/lib. By doing this, the WDI system will automatically include /usr/mqm/lib in the search as edimqs is loaded. Once this change is put into effect step two of this document will not be needed.