Author |
Message
|
kevinf2349 |
Posted: Mon Nov 24, 2003 10:28 am Post subject: Starting Stopped Channels |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Hi folks,
I have been bitten a couple of times by our PC folks going into MQ and manually issuing a stop command for a channel. The channel goes, as one would expect, into a STOPPED state...which is fine.
The problem is that this seems to prevent the channel from starting up via triggering and we need a solution that will allows us to start the channels 'automatically' should the PC people forget to restart the channel when they have finished. Any ideas? |
|
Back to top |
|
 |
JasonE |
Posted: Mon Nov 24, 2003 1:55 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Do channel events help here (isnt there an event for manual stop - Doing this from memory with no manuals to hand, sorry!)
Alternatively, you could write a program which polls for stopped channels using PCF commands and then uses PCF commands to start them - This could be launched using custom services for when the qmgr is up and running.
Note: You could parse runmqsc output for stopped channels, but dont issue runmqsc START CHANNEL on windows, as the channel pgm will get terminated if the signed on user logs off. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Nov 24, 2003 6:19 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Why are they stopping the channels? Should they be allowed to?
If no, then you have to implement the security to prevent them.
If yes, they should have the ability / smarts / responsability to restart them when they are done mucking around, no? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
tkaravind |
Posted: Mon Nov 24, 2003 9:28 pm Post subject: |
|
|
Acolyte
Joined: 24 Jul 2001 Posts: 63
|
Folks,
Yes. We never allow someone to stop the channels in our production region over here. A better idea would be to set an appropriate "disconnect interval" and the channel goes into an INACTIVE state when that expires.
There is not much of a difference between the STOPPED & INACTIVE states except that with the latter you could auto-start the channel through the initiator.
IBM manual clearly states that the channel initiator cannot be used on STOPPED channels.
As a last resort you could go for programmed start through simple mqs scripts or PCF commands but these make it a bit more complicated.
Aravind |
|
Back to top |
|
 |
kevinf2349 |
Posted: Tue Nov 25, 2003 7:27 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Peter et all,
Unfortunately they do have the ability and authority to start and stop channels. Under normal operation the channels are triggered and have a disconnect interval set at 10 minutes.
The issue is really only when they forget to restart the channels when they have finished doing whatever it is they do on those wintel boxes.
The really annoying thing is that our PC group seem to no accountability and the clients come running to me claiming that 'MQ isn't working' whenever they leave things disjointed. I have no access to the server to restart the channels so I have to wait for the PC bods to come in and correct their mistakes. I guess what I am really seaching for is a solution that takes the PC bods out of the loop and will allow me to start the channel 'automatically' even from a stopped state. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Nov 25, 2003 7:38 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Do you have MQ connectivity to these QMs? If so, is there a XMIT queue back to your QM that is named exactly like your QM?
If yes, and their security is not clamped down, you could use the MO71 support pac to look at all the MQ objects and do anything you want to them.
You will use MO71 to connect to your QM, and pass commands via MQ to their QM, which will send the replies back to you via the XMIT queue named after your QM.
Cooool!!!  _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|