Rob, good points! but then you are doing the pre-Problem detirmination for your 'business' user who is expecting something and working from taget to source.
I always tell my 'business' user if they did not get what they expected to call their 'business' user supplier (aka the sender party) and track the message from the source to the target. 99% of the cases it's a situation like 1) and 2) you described only this time it's the companies 'business' user calling their own helpdesk or support group and he/she often is known to that group. AND most importantly keeps my support group free of unneccessary calls as often they can't do anything but just 'narrowing' down the problem and passing on the call... Michael -----Oorspronkelijk bericht----- Van: MQSeries List [mailto:[EMAIL PROTECTED] Wyatt, T. Rob Verzonden: vrijdag 12 maart 2004 2:04 Aan: [EMAIL PROTECTED] Onderwerp: Re: RCVR versus RQSTR channels Peter, We have connections to a number of service bureaus and business partners. Sometimes the users call to say an expected message is overdue and we see the channel is down. This can mean any number of things that generally fall into two categories - 1) triggering is broken or 2) the app is broken. Either way we call the 3rd party's help desk and work our way from Tier 1 Support up. This can take a while, especially if we escalate to MQ Support for an application problem or vice versa. Starting the channel does two things. First, this narrows down the problem. If the channel starts and no message is received, we escalate to the app support group at the third party site. If we get a message when the channel starts, it's a triggering problem and we get the MQ folks on the line. In the second case we can keep the channel up manually until the third party's MQ support team come on the line. Some of our interfaces are time-sensitive and failure to deliver messages before the daily cutoff date results in potential fines, interest and contractual penalties. In at least a couple of instances starting the RQSTR channel has kept us from missing the deadlines and incurring the financial consequences. Not bad for some free advice I picked up off this list years ago! -- T.Rob -----Original Message----- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 6:02 PM To: [EMAIL PROTECTED] Subject: Re: RCVR versus RQSTR channels T.Rob, I am curious. Exactly in what situation do you take advantage of the fact that you can start the third parties SNDR to you? If your RQSTR (or RCVR) is Inactive, and you can't see the other side, don't you have to assume there is no channel problem? At what point do you say to yourself "Let's try and start their SNDR for them."? Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
