MQSeries.net :: View topic - Recompiling (NEON) user exits ( MQSIv2.0.1 -> WMQIv2.1)

babanet

Recompiling user exits ( MQSIv2.0.1 -> WMQIv2.1)

The following is what IBM documentation suggests in order to recompile customized user-exits and make them work as before:

User exits from previous versions have to be recompiled as multi-threaded objects (and linked with thread-safe libraries). Follow the separate procedure to ultimately generate the nnuserexit.dll and incorporate the table bind files and the nnuserexit.dll into the new WMQI environment.

Due to the change in naming conventions (NNSY replaces NEON), the following adjustments have to be made to the following files:

1. Update customized code that uses the following header files:
Current C++ Header File: Updated C++ Header File:
---------------------------------- -----------------------------------
NEON.h NNSY.h
NEONETRELEASE.h NNSYFRELEASE.h
INFR/NEONObjects.h INFR/NNSYObjects .h
NNGLOBAL/NEONDefinedMessageProperties.h NNGLOBAL/NNSYDefinedMessageProperties.h

Example
#include <INFR/NEONObjects.h> changes to
#include <INFR/NNSYObjects.h

2. Update the following global compiler names (where applicable):
Current Global Compiler Name: Updated Global Compiler Name:
---------------------------------- -----------------------------------
USING_NAMESPACE(NEON) USING_NAMESPACE(NNSY)
NEON_NAMESPACE NNSY_NAMESPACE

[ Note: I think there is a bit of unclarity in this procedure . No specific instructions are provided in any of the known IBM or Sybase websites or in any one of the WMQI manuals as to how to “recompile the customised user exits as multi-threaded objects (and linked with thread-safe libraries)”, in order to make them work as they did before the migration. This particular issue is of immense importance and will be of great concern to the MQSI team.

On a trial machine (not cluster), I tried performing this step as it ‘reads’ i.e. recompiling the user exits as multi-threaded objects. I then tested the setup with two interfaces with customised user exits, one of them performing a database lookup. I found that when the interface user exit does not perform a database lookup, it works fine. However, when a database lookup is involved, the reformating fails when it tries to call the routine to perform the lookup. (Also in the Visual Tester tool, the same problem occurs, with an error message about incorrect memory address reference!) ].

The question is: How exactly does one perform this procedure (in the Microsoft Visual C++ environment) in order to achieve the desired purpose? Do I have to recompile all static library projects or is it just the nnuserexit.dll, and in any case, how exactly do I perform this recompilations within Visual C++ such that the user exits would now be compatible with WMQIv2.1 environment?