| Author |
Message
|
| andrewrgrayjr |
 Posted: Fri Nov 25, 2011 6:32 am Post subject: saveqmgr V6.1.4.0 (for Websphere MQ 7.1) |
 |
|
Newbie
Joined: 01 Dec 2006
Posts: 7
Location: NY NY (times square)
|
I have been using the saveqmgr (MS03) utility for quite some time with great ressults (I am a huge fan). Red Hat Linux X86_64 rel 4 is the platform and Red Hat X86_64 rel 6 is the new platform.
I am trying to migrate my QM's from 6.0.2.10 to 7.1.0.0 using saveqmgr.
I run saveqmgr 6.0.3 (MQ 6.0.2.10) and the normal output is shown below.......
[mqm@trmqq1 mqm]$ ./saveqmgr.linux -m FOO -f FOO.saveqmgr.trmqq1
SAVEQMGR V6.0.3
Compiled for Websphere MQ V6.0 on Aug 29 2006
Requesting attributes of the queue manager...
Writing Queue Manager definition to FOO.saveqmgr.trmqq1.
Generating attributes for Websphere MQ Release 6.0.0
Generating code for platform UNIX
Requesting attributes of all authinfo objects...
Requesting attributes of all queues...
Requesting attributes of all channels...
Requesting attributes of all processes...
Requesting attributes of all namelists...
Requesting attributes of all listeners...
Requesting attributes of all services...
Writing AuthInfo definitions to FOO.saveqmgr.trmqq1.
Writing Queue definitions to FOO.saveqmgr.trmqq1.
Skipping dynamic queue SAVEQMGR.4ECD623020000703
Writing Channel definitions to FOO.saveqmgr.trmqq1.
Writing Process definitions to FOO.saveqmgr.trmqq1.
Writing Namelist definitions to FOO.saveqmgr.trmqq1.
Writing Listener definitions to FOO.saveqmgr.trmqq1.
Writing Service definitions to FOO.saveqmgr.trmqq1.
I expect this type of output (above). The utility seems to work normally.
With the latest savegmgr - there may be an issue OR I may not be running this correctly.
When I create a QM on MQ 7.1 and run saveqmgr 6.1.4.0 - I see the following output.....
$ ./saveqmgr64.linux -m FOO -f FOO.saveqmgr64.cvgxmqq01
Compiled for Websphere MQ V7.0.1.0 on Oct 9 2011
SAVEQMGR V6.1.4.0
Requesting attributes of the queue manager...
(qmgr.c) Unknown PCF Integer Parameter: 239
(qmgr.c) Unknown PCF Integer Parameter: 240
(qmgr.c) Unknown PCF Integer Parameter: 248
(qmgr.c) Unknown PCF String Parameter: 2119
(qmgr.c) Unknown PCF Integer Parameter: 249
(saveqmgr.c) Unknown CFT_INTEGER_LIST Command Received 2
(qmgr.c) Unknown PCF String Parameter: 2120
(qmgr.c) Unknown PCF Integer Parameter: 243
Writing Queue Manager definition to FOO.saveqmgr64.cvgxmqq01.
Generating attributes for Websphere MQ Release 7.1.0
Generating code for platform UNIX
Requesting attributes of all authinfo objects...
Requesting attributes of all queues...
Requesting attributes of all channels...
Requesting attributes of all processes...
Requesting attributes of all namelists...
Requesting attributes of all listeners...
Requesting attributes of all services...
Requesting attributes of all topics...
Requesting attributes of all subscriptions...
Writing AuthInfo definitions to FOO.saveqmgr64.cvgxmqq01.
(queue.c) Unknown PCF String Parameter: 2119
Writing Queue definitions to FOO.saveqmgr64.cvgxmqq01.
Skipping dynamic queue SAVEQMGR.4ECD5EF120002002
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(queue.c) Unknown PCF String Parameter: 2119
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
Writing Channel definitions to FOO.saveqmgr64.cvgxmqq01.
(channel.c) Unknown PCF Integer Parameter: 1624
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1624
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1624
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1624
(channel.c) Unknown PCF Integer Parameter: 1623
(channel.c) Unknown PCF Integer Parameter: 234
(channel.c) Unknown PCF Integer Parameter: 1640
Writing Process definitions to FOO.saveqmgr64.cvgxmqq01.
Writing Namelist definitions to FOO.saveqmgr64.cvgxmqq01.
Writing Listener definitions to FOO.saveqmgr64.cvgxmqq01.
Writing Service definitions to FOO.saveqmgr64.cvgxmqq01.
(topic.c) Unknown PCF Integer Parameter: 176
(topic.c) Unknown PCF String Parameter: 2110
(topic.c) Unknown PCF Integer Parameter: 234
(topic.c) Unknown PCF String Parameter: 2119
Writing Topic definitions to FOO.saveqmgr64.cvgxmqq01.
(topic.c) Unknown PCF Integer Parameter: 176
(topic.c) Unknown PCF String Parameter: 2110
(topic.c) Unknown PCF Integer Parameter: 234
(topic.c) Unknown PCF String Parameter: 2119
(topic.c) Unknown PCF Integer Parameter: 176
(topic.c) Unknown PCF String Parameter: 2110
(topic.c) Unknown PCF Integer Parameter: 234
(topic.c) Unknown PCF String Parameter: 2119
(topic.c) Unknown PCF Integer Parameter: 176
(topic.c) Unknown PCF String Parameter: 2110
(topic.c) Unknown PCF Integer Parameter: 234
(topic.c) Unknown PCF String Parameter: 2119
(topic.c) Unknown PCF Integer Parameter: 176
(topic.c) Unknown PCF String Parameter: 2110
(topic.c) Unknown PCF Integer Parameter: 234
(topic.c) Unknown PCF String Parameter: 2119
Writing Subscription definitions to FOO.saveqmgr64.cvgxmqq01.
This output tells me that there may be an issue. I know that 7.1 is a very recent release of MQ. Perhaps I need to backtrack to the latest 7.0 release as I plan to migrate and deploy in the next few days.
The file looks ok until you get to the very end.
Perhaps saveqmgr is not yet supported on 7.1.
Has anyone had similar issues?
Thank you |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Nov 25, 2011 7:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There are a significant number of new MQSC/PCF attributes and commands and objects in MQ v7.1 compared to MQ v7.0.x.
Saveqmgr has *not* as yet been updated to support this, at least as of the last release, which came out very shortly *before* 7.1 GAd.
With 7.1 you also have the option of using the new dmpmqcfg command.
You should CONTACT THE MAINTAINER OF saveqmgr and discuss this.
Please MAKE SURE TO READ THE LATEST DOCs. The maintainer *changed* at the last release. Contact Geoff, not Jeff. |
|
| Back to top |
|
|
| mqgeoff |
| Posted: Mon Nov 28, 2011 2:23 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2011
Posts: 4
|
As mqjeff says, V6.1.4.0 has not been upgraded to support MQ V7.1 yet.
I'm considering doing that, but it won't happen this year. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 28, 2011 2:59 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Does dmpmqcfg provide all the features of MS03? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 28, 2011 7:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 28, 2011 7:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Would it be correct to say that is expects all client connected QMs to be listed in the CCDT?
Although many of our backed up QMs are in the CCDT, not all of them are. MS03 allows either CCDT, or explicit connection details. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 28, 2011 7:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zpat wrote: |
| Would it be correct to say that is expects all client connected QMs to be listed in the CCDT? |
I have no idea. |
|
| Back to top |
|
|
| markt |
| Posted: Mon Nov 28, 2011 8:07 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
It would not be correct to say everything is in the CCDT.
dmpmqcfg can take a full client definition on the command line. That's the "-c" flag, where you basically type in exactly the same as you would put on an MQSC command for DEF CHL. For example
| Code: |
dmpmqcfg -m RMTQMGR -c "DEFINE CHANNEL(SYSTEM.DEF.SVRCONN) CHLTYPE(CLNTCONN) CONNAME('idev01.hursley.ibm.com(1414)')"
|
|
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 28, 2011 9:50 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| OK, that's good. Perhaps an unusual format (for a command parameter) - might be worth putting an example like the one above in the infocenter. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 28, 2011 9:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zpat wrote: |
| OK, that's good. Perhaps an unusual format (for a command parameter) - might be worth putting an example like the one above in the infocenter. |
The info center does say
| Quote: |
-c
Force a client mode connection. If the -c parameter is qualified with the option default, the default client connection process is used. If -c is omitted, the default is to attempt to connect to the queue manager first by using server bindings and then if this fails by using client bindings.
If the option is qualified with an MQSC DEFINE CHANNEL CHLTYPE(CLNTCONN) string then this is parsed and if successful, used to create a temporary connection to the queue manager.
|
A more defined example might be useful.
There is a lovely little feedback button at the bottom of the page... |
|
| Back to top |
|
|
| andrewrgrayjr |
| Posted: Tue Nov 29, 2011 9:21 am Post subject: |
|
|
Newbie
Joined: 01 Dec 2006
Posts: 7
Location: NY NY (times square)
|
Thank you for everyone's reply's and comments.
I may downgrade to 7.0.x due to my relatively quick deployment timeframe and my dependancy on the tremendous saveqmgr utility.
Thanks again! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 29, 2011 10:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
what you've said seems to make little sense.
What, exactly, are you dependent on saveqmgr providing for you? Unless it's something very odd, dmpmqcfg should likely fill the need. |
|
| Back to top |
|
|
| andrewrgrayjr |
| Posted: Fri Dec 02, 2011 8:03 am Post subject: |
|
|
Newbie
Joined: 01 Dec 2006
Posts: 7
Location: NY NY (times square)
|
| Saveqmgr saves all the MQ objects in one simple file. I have scripts that run daily. The files give me piece of mind as I can migrate a QM quickly and/or backtrack a change quickly. This is alos useful for Disaster recovery. I rely on this in case something bad happens. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 02, 2011 8:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| dmpmqcfg does the same thing. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 02, 2011 8:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
| dmpmqcfg does the same thing. |
My understanding is this is a server version.
Is there also a client version for it? Or would that then be MS03. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
