| Author |
Message
|
| aboggis |
 Posted: Tue Jul 06, 2004 9:49 pm Post subject: Problems with saveqmgrc (MS03) |
 |
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I am now having problems running the saveqmgrc binary in supportpac ms03. This previously worked on my Windows environment (Windows 2000 SP4, WMQ 5.3 CSD07). I get the following:
| Code: |
C:\Tmp>saveqmgrc -m CLUSTER2B.AR1.MANAGER -f x
SAVEQMGR V5.3.3a
Compiled for Websphere MQ V5.3 on Mar 22 2004
With no client connection information specified.
Requesting attributes of the queue manager...
Writing Queue Manager definition to x.
Generating attributes for Websphere MQ Release 5.3.0
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...
Writing AuthInfo definitions to x.
Writing Queue definitions to x.
Skipping dynamic queue MQMON.aboggis.40E5997E201C8A01
Skipping dynamic queue SAVEQMGR.40E5997E201C8B01
Writing Channel definitions to x.
Writing Process definitions to x.
Writing Namelist definitions to x.
Error: Received parameter block is of an unrecognised type.
Error: Received parameter block is of an unrecognised type.
Error: Received parameter block is of an unrecognised type.
Error: Received parameter block is of an unrecognised type.
Error: Received parameter block is of an unrecognised type.
Error: Received parameter block is of an unrecognised type.
.
.
. |
Those last lines just repeat ad infinitum.
Has anyone else experienced this? Is it CSD07 on the Window side? The MQ queue manager I am connecting to is on a Solaris host and it's WMQ 5.3 CSD05. |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Wed Jul 07, 2004 8:28 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Get the latest release of MS03 (saveqmgr) because CSD06 introduced new queue attributes.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| aboggis |
| Posted: Wed Jul 07, 2004 8:52 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
| That is the latest. I got the supportpac yesterday. The binaries in the ZIP file are dated 3/22/2004. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jul 07, 2004 9:18 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Well, I wonder if CSD07 added even more new queue attributes (or attributes to other MQ objects)??
Maybe I'll do a Windows MQ CSD upgrade later today to see what happens. 
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jul 07, 2004 2:11 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Ok, I did the WMQ v5.3 CSD07 upgrade this afternoon on Win2000 SP4 box.
Then I ran the current version of saveqmgr against a local queue manager and it worked just fine. Here's the command I used:
| Code: |
| saveqmgr -m MyQMgr -f MyQMgr.mqsc -s |
One question: Did you reboot your PC after the CSD upgrade? I know it doesn't request it, but it is always a good idea with Windows.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| aboggis |
| Posted: Wed Jul 07, 2004 2:29 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
Yes. Several times  This is windows after all. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jul 07, 2004 2:50 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
I just noticed that you are using the client version connecting to a Solaris queue manager. I completely missed that. 
Anyway, I set MQSERVER (same PC) to point to a queue manager on Solaris 8 / WMQ v5.3 CSD03 and then ran saveqmgrc as follows:
| Code: |
| saveqmgrc -m RemoteQMgrName -f x |
and it worked just fine.
Very strange. Maybe you need to look at the code for saveqmgr.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
