DSXchange

Which is best method to invoke a datastage, from MQ Series Queue when queue has got message?

Rgds,
Chakradhar.

MQ Series Queue needs to invoke DatStage Stage Job on arrival on any message in the Queue.

Is it good plan to have shell script to be used?

Any body any thoughts??

Rgds,

Chakradhar.

Using a shell script is not a good plan. there is no need.
Use the MQ Stage. Why use a shell script? Did you need this to be realtime? No problem. Read the documentation.

throbinson wrote:Using a shell script is not a good plan. there is no need.
Use the MQ Stage. Why use a shell script? Did you need this to be realtime? No problem. Read the documentation.

Thanks for the thought.

i have couple of question added to the above.

1. Which are options to be used in MQ stage to read the message as soon as it is populated in queue by 3rd party application??
2. Can you let me know, Name of PDF file, Which section which is mentioned that?
3. We can invoke other job thru Job Control of the job which has got MQ Stage or do we have better option to do the same?
Pl suggest..

Thanks again and in advance.

Chakradhar.

....been awhile since I've done it, but read up on "trigger queues"....... that is an MQ way to do it....

Ernie

Maybe I'm mis-reading the requirement. I've not done MQ in a while. Why not define a job and have it constantly run waiting for a message from the queue? As soon as a message arrives, it will be delivered to the job and processed. When you want to stop the job, schedule another DataStage job to insert a "stop" message into that same queue that is of a MsgType that triggers the first DataStage job to stop.

mq.pdf in the docs sub directory

Well, i am working with Server Edition, Not Enterprise edition , we don't have MQ Connectors.

What Options for monitoring the Queue for new messages can be used ??

Rgds,
Chakradhar

throbinson is correct...you don't need MQConnector....Server and MQStage can do this also......just having a job waiting endlessly for a message to arrive. Will work perfectly. The only drawback is if the arrival is fairly rare....like once a day or less frequent.....no sense in having the job sit there waiting all that time....... Then it makes sense to have MQ kick off a script that starts a DS job to get the messsages or do anything.

Ernie

"just having a job waiting endlessly for a message to arrive. "

How do we do that that in DataStage verion 8 , server edition??

That is the question?

Thanks,
Chakradhar

"just having a job waiting endlessly for a message to arrive. "

How do we do that that in DataStage verion 8 , server edition??

That is the question?

Thanks,
Chakradhar

Set up your job as a service and set it to "always running".

Thanks Ray for the though.

Can you please get me more information on the services setup for DataStage Job.

Rgds,

Chakradhar.

Yes I could, but so can you. Search (here and IBM) for Information Services Director, SOA and - for older versions - RTI.

WebSphere Information Services Director is typically abbreviated as WISD. All iterations of the product can be discussed in the "SOA Editions" forum.

...this is not an ISD scenario.....

...the MQ Plugin, by default, will "wait endlessly" when used as a Source in your Server (or EE) Job. ...in fact, be careful --- when testing I always use a timeout value of say, 30 seconds, rowlimit of 10, and put in a message type identifier of 9999899 (or some other equally long and unlikely value for a Message Type in the MQ Header) so that I can control the stopping myself. Default is "wait indefinitely".

Ernie