| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DMPMQMCFG removes entries in member when QM is not active |
« View previous topic :: View next topic » |
| Author |
Message
|
| peho11 |
 Posted: Fri Apr 22, 2016 4:02 am Post subject: DMPMQMCFG removes entries in member when QM is not active |
 |
|
Newbie
Joined: 22 Apr 2016
Posts: 1
|
I'm testing DMPMQMCFG for backup purpose but I've seen that when I run the cmd for a QM that is not active it wipe the contents of the member Eg cmd DMPMQMCFG OUTPUT(*MQSC) TOFILE(TECHPLFPRD/QMQSC) TOMBR(MACSFT1)
It creates a member MACSFT1 with 6129 records. I then end the cmd and ran the cmd again and in the log I get the msg "WebSphere MQ queue manager not available" which is true and one could excpect the pgm not to do anything with the member but when I check it's empty...
I can't find any option in the command where I could say "leave member if ont active" or simular.
I would like to be able to run the cmd even though the QM is not active as we have a lot of them and in the test environment we don't have them all active at the same time. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Apr 22, 2016 4:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
not really sure what you mean by 'leave member if not active'.
dmpmqcfg should not delete or stop or otherwise alter the queue manager. If you run the output MQSC file against the queue manager again, you should either get errors that say the object already exists, or the MQSC contains the REPLACE keyword. Then you'll get new objects instead of the old ones. This could remove messages on queues.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Apr 22, 2016 9:06 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
I believe what peho11 is saying is that when your run dmpmqcfg and it encounters an error, it has already opened and removed the existing contents of the file where the output is going, so the result is that you have an empty back up file for the use case of the queue manger being down. I see the same behavior on Linux. The message "AMQ8146: WebSphere MQ queue manager not available." is written to stderr. What we do with our back up script is report whenever a dmpmqcfg results in any records to stderr, and then the administrator would need to act on that to get a good back up. This meets our back up needs, since we also first save off the original back up before running dmpmqcfg. Perhaps, peho11 could consider something similar. This looks like something you will have to handle operationally and outside of the dmpmqcfg program, itself.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 22, 2016 10:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Well.
I guess I would just make sure that it used a different output file every time it needed to be run...
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
