Using MQSeries with NonStop Tuxedo 6.5.3

ManualsBrandsHP ManualsServerHP NonStop G-Series

Using MQSeries with NonStop TUXEDO

Disclaimer

The following instructions were developed by a NonStop TUXEDO expert that is an MQSeries

neophyte. Thus statements made about NonStop TUXEDO can be assumed to be correct, but

any comments about MQSeries could be based on lack of MQSeries knowledge. The system

available for testing contained IBM MQSeries for Tandem NonStop Kernel Version 2 Release 2

and Compaq NonStop TUXEDO R6.5 V2. Only native clients and servers written in C using

request/response messages were attempted. This proves the MQSeries and NonStop TUXEDO

libraries can co-exist and it’s assumed that conversational messages will work as well.

Introduction

There were three main obstacles to getting MQSeries and NonStop TUXEDO to co-exist in the

same process. First, MQSeries on the Himalaya uses the Guardian personality while NonStop

TUXEDO uses the OSS personality. Second, MQSeries, at least as configured on the test

system, requires a member of the MQM group to manage and access queues. Third, the

MQSeries sample applications are very sensitive to having an environment variable set, namely

MQDEFAULTPREFIX. However, this might only be the case because the system didn’t use

the default installation disk. Still, without that environment variable set the same programs will

ABEND, even when the correct arguments are supplied.

To verify that NonStop TUXEDO and MQSeries can co-exist in the same process several

MQSeries sample programs (i.e., amqsgbr0.c, amqsget.c, and amqsput.c) were combined with

either simpcl.c or simpserv.c of the NonStop TUXEDO simpapp sample application. This

proved that the MQSeries process can be either a native NonStop TUXEDO client, or a

NonStop TUXEDO server assuming the NonStop TUXEDO administrator can access the

MQSeries queues. A compressed pax file containing several sample clients and servers is

described and included in this document.

Steps for getting MQSeries and NonStop TUXEDO to work

together

The following sections give an overview of what is needed to get the two products to work

together. The sample application provided already includes the steps listed below.

Summary of content (6 pages)

PAGE 1
Using MQSeries with NonStop TUXEDO Disclaimer The following instructions were developed by a NonStop TUXEDO expert that is an MQSeries neophyte. Thus statements made about NonStop TUXEDO can be assumed to be correct, but any comments about MQSeries could be based on lack of MQSeries knowledge. The system available for testing contained IBM MQSeries for Tandem NonStop Kernel Version 2 Release 2 and Compaq NonStop TUXEDO R6.5 V2.
PAGE 2
Step 1: Make parts of MQSeries OSS-friendly Since NonStop TUXEDO uses the OSS personality to build and execute clients and servers the easiest thing to do is copy a small subset of MQSeries files into the OSS name space. It’s likely a build environment could be setup such that the MQSeries files could still reside in the Guardian name space but that wasn’t attempted. First copy the header files from the ZMQSLIB subvolume to an OSS directory (e.g., mqsinc) and make the necessary file name translation.
PAGE 3
simple MQSeries process to ABEND on the test system. Step 3b: Running a NonStop TUXEDO server that accesses an MQSeries queue If a NonStop TUXEDO server is to access an MQSeries queue then the administrator of the NonStop TUXEDO will also have to be able to access the MQSeries queue. On the test system that required that the NonStop TUXEDO administrator be a member of the MQM group. It also requires that the environment variables be included in either the *MACHINES’, *GROUPS’, or *SERVERS’ ENVFILE.
PAGE 4
MQMACHINIFILE and MQDEFAULTPREFIX ubbsimple: *MACHINES’ pmid, GSUBVOL, APPDIR, TUXCONFIG, ENVFILE, mqsgetserv and mqsputserv’s CLOPT (i.e., the queue name and queue manager’s name) 7. Load the environment file: . ./mqs_simpapp_env 8. Load the tuxconfig file: tmloadcf ubbsimple 9. Boot the application: tmboot -y Using the clients and servers The make file builds several MQSeries sample programs: amqsgbr, amqsget, and amqsput that can be used as normal. For example, "amqsgbr SYSTEM.DEFAULT.LOCAL.
PAGE 5
mqsgetcl, tmqsgetcl, and mqsgetserv mqsgetcl and tmqsgetcl use the same source file, however, when the executable is invoked as tmqsgetcl, it starts a transaction before calling the service. Otherwise, the client is basically simpcl.c except it calls the service MQSGETTOLOWER. It can also be forced to abort the transaction it started.
PAGE 6
mqsputcl, tmqsputcl, and mqsputserv mqsputcl, tmqsputcl, and mqsputserv are basically the inverse of mqsgetcl, tmqsgetcl, and mqsgetserv. So instead of retrieving a string off the MQSeries queue and downshifting and returning it to the client, a string argument is taken, up shifted, and added to the MQSeries queue.