ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How to full proof mqsireload command

Post new topic  Reply to topic
 How to full proof mqsireload command « View previous topic :: View next topic » 
Author Message
Beginners
PostPosted: Wed Aug 31, 2016 11:07 am    Post subject: How to full proof mqsireload command Reply with quote

Newbie

Joined: 31 Aug 2016
Posts: 1

Hi,

When we run mqsireload execution group, we get successful commands completion response. But in back end the execution group will stop and start, which takes time. How to ensure that EG reload is successful, apart from checking info logs.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Aug 31, 2016 11:20 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.

Moved to Broker forum.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 31, 2016 11:43 am    Post subject: Re: How to full proof mqsireload command Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Beginners wrote:
When we run mqsireload execution group, we get successful commands completion response.


Because the command has completed. It's successfully issued a command for an EG reload to occur.

Beginners wrote:
But in back end the execution group will stop and start, which takes time. How to ensure that EG reload is successful, apart from checking info logs.


That's how you do it. Same way you verify all the components have started correctly when you use an mqsistart (which actually puts up a little note to remind you to check the log).

It shouldn't be that much of a problem, because you should only need to issue that command occasionally & whoever issued the command can check the logs.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 31, 2016 12:09 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

It's also a good practice (mqsireload or not, IIB or not) to have something monitoring the logs automatically for problems. Most sites have this, so if it's not monitoring for IIB errors you can probably extend it without too much trouble.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Craig B
PostPosted: Mon Sep 19, 2016 9:31 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

In V9 (and below) the mqsireload command would bypass the AdminAgent and put a message direct on to the SYSTEM.BROKER.EXECUTIONGROUP.QUEUE. As such the DFE would just just stop itself without the AdminAgent (bipbroker) knowing. The monitoring withing in bipbroker would see the DataFlowEngine process stop and as such just restart it. Because the command bypassed the admin chain it was simply a fire and forget type request. In IIB V10 the mqsireload request is sent to the AdminAgent and it issues a stop and start on the integration server. Because it sends these as two requests it now actually waits for the integration server to stop before sending the start request. This means that in IIB V10 the mqsireload command does not return until it has issued the asynchronous start. So in IIB V10 when mqsireload returns you know that the integration is server is trying to start back up at this point. As the previous response mentioned this now no different than any other start-up where the approach is taken of "Your request has been honoured to start the resource and that is inflight". At that point the SYSLOG messages of BIP2208 following by the triplet of the BIP2152, BIP2153 and BIP2154 showing a "Start" message has been accepted and completed is the only way to know the whole process is up.
_________________
Regards
Craig
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How to full proof mqsireload command
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.