ActiveX and Remote Queue Managers

[klamerus]

I'm working on a web site (IIS with VBScript) from which we want to be able to check in on some queue managers on remove systems.

So, we need to use the COM/ActiveX interface on a Windows 2000 platform to talk to several remote queue manages.

We've been asking questions all over the place and searching the web and IBM documentation and have been unable to find any examples of VB or VBScript talking to queue managers on remote queues. We can't rely upon environment variables because there are several queues we need to check on.

Can anyone provide a code snippet of even just the part of some code that would connect to a single remote queue manager?

 

[MQdude]

I would first ask is this the solution that is best for you? Do you want to monitor those queue managers, or pole to find out if there is any data that you should be pulling?

You might want to tell us what your doing so we can advise you if that is the right thing to do.

Here is an answer anyways. It's an easy, low tech, low research, alternative.

Use VBscfipt to run a batch file as follows.

Inside a bat file
set MQSERVER SYSTEM.DEF.SVRCONN/TCP/999.99.99.131(1414)
runmqsc qmgrname <mqcmdin.txt >mqcmdout.txt
set MQSERVER SYSTEM.DEF.SVRCONN/TCP/999.99.99.131(4500)
runmqsc qmgrname2 <mqcmdin2.txt >mqcmdout2.txt

You can change the environment variable inside a batch file as many times as you like. It overrides any machine setting but doesn't change your permanent evironment variables settings. 4500 is a mainframe port number 1414 is used on most other platforms.

Now use VBscript to parse and analyse the result files mqcmdout*.txt

 

[klamerus]

Sorry for the delayed response. I was in one of my infrequent vacations.

The following is an "as brief as possible" description of whta we're trying to do.

We have a custom application that uses WebSphere MQ (I'll just call it MQ). Work is routed to this application through these queues and it performs various services on those messages, which contain documents. Some of those services are to mail the document, fax it, print it, archive it (in a repository), etc. These individual requests are performed by a set of applications running on our servers that we call agents. Any way request to the system overall might ask for several of these individual steps as part of an overall workflow. The final results are logged in a database.

This system processes tens of thousands of requests daily and is running on Windows 2000. These requests come from a number of other systems in batches (jobs in SAP being the biggest source, but hundreds of others as well). These applications are all on remote systems and various operating systems. Our system is the central processing hub for these.

Since the batches of requests can be so large, it can take hours to process all of them. People being people, the owners of the applications sending the requests become concerned if our system is working or not. What we're looking to do is provide them a means of checking on the status of the system through a web site (which we would like to put on the database server, which is only hosting the database at this time). We want them to be able to see how deep the queues are, how many outstanding requests they have, how long has the old job been on the queue, etc.

This would require a number of interactive queries by end-users who be able to query against the MQ data as well as the database where we record the performance of work done (we use it to keep data on transactions completed).

Basically, an interactive web site that can be a kiosk for end-users who don't have the access or skills (nor do we want them to) to see how their work is going (or went).

 

[klamerus]

Also sorry for the very choppy response. My English is actually generally quite good. Didn't get much sleep last night though