DSXchange

Hi all,

can anybody send me across 'plug-in installation & configuration guide'.Previously MQ plugin was configured for the development project.Now i need to configure it for Test Environment project(Just a new Project).So anybody has any idea regarding configration,please do share with me.

Thanks in advance,

It's called InstConf.pdf and it's to be found on each machine on which DataStage client is installed, at C:\Program Files\Ascential\DataStage7.5\Docs (if you installed into the default location).

Hi all,

Thanks for kind response.
I have gone through the Most of the documents but endup with the gul thing.

If anybody has come across with configuration Or installation of the MQ plug-in,do reply me.all the inputs will be greatly appreciated.

MQ Plugin is already installed and working fine with one of our Project.Now we have craeted a new project and moved all our jobs to this new project,so for this project i need to configure the MQ Plug-in.

Thanks in advance
aquilis,

Do exactly the same things that you did in the first project.

sorry...

Actually that was configured by our DBA previously,but currently i am unable to connect him.thats why?

The error i am facing here is:

'The MQSeries in D_DSSTAGETYPES is not existing.'

In previous project I can see the MQ Plug-in stage in the 'Stage types' Tree in Palette.
But for the New project....... Plugin stage it self is not seen in the palette.
and the above error says the same.
What i want is how to configure the Plug-in stage so that i can view that one in stage types of palette.

Hi all,
Sorry that I didn't go through this post previously.
Needs Plug-in to be registered.
For better understanding:
viewtopic.php?t=96264&highlight=MQ+Plug-in

Hello all,

I was successful to configure/register the MQ PlugIn,but the problem i am facing is ,its not pulling the message from the MQ.So what would be the issue. But in development environment its still working fine.
advise please ,whether i left something undone still.

Thanks....

Is the MQ Series server co-resident (on the same machine as) the DataStage server? This is a requirement if you are using version 7 or earlier of DataStage. At version 8 that requirement is removed; you can get by with just MQ Series client software on the DataStage Server machine.

Ray,

I am working with Version 7.5.1.A.
And you are right ,Both servers should be Co-resident.
and i am having my servers Co-residing.
Then what are all would be the possible solutions otherthan this.

Aquilis.

Check your queue manager, port, or channel of your test environment using either MQ Explorer or from the command line. Your development environment is working fine doesn't mean the MQ in your test environment is going to work the same as development.

lstsaur wrote:Check your queue manager, port, or channel of your test environment using either MQ Explorer or from the command line. Your development environment is working fine doesn't mean the MQ in your test environment is going to work the same as development.

When i execute my jobs from the test environment ,my jobs are getting executed from development environment.test & development environment are two different projects on the same host/server.

I think,when i Run my jobs from test environment, DS executing old executables files created for the same jobs present in the other project. Is his the valid reason.
suggestions required....


Thanks ..........

Your development project and test project are in the same server and sharing the same MQ connection. Development environment jobs are still running with already established connections. If you want to test this check the MQ Manager for active connections on the queue from MQ side.

Aquilis wrote: When i execute my jobs from the test environment ,my jobs are getting executed from development environment.test & development environment are two different projects on the same host/server.

I think,when i Run my jobs from test environment, DS executing old executables files created for the same jobs present in the other project. Is his the valid reason.