| Author |
Message
|
| anantha sreenivasan |
 Posted: Thu Jul 17, 2008 11:19 am Post subject: mqsideploy fails with BIP8041E |
 |
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
I'm trying to delete a message flow. This message shows as deleted from toolkit but it exists when I issue an mqsilist command
Following are the details
Broker Name: BROKER_TEST
Execution Group: TEST_EG
Message Flow: TEST_MSGFLOW
$ mqsilist BROKER_TEST -e TEST_EG
BIP8131I: MessageFlow: TEST_MSGFLOW
Now when I issue mqsideploy to delete the message flow, I get the following error
mqsideploy -n CONFIGMGR_TEST -b BROKER_TEST -e TEST_EG -d TEST_MSGFLOW.cmf
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1046E: Unable to connect with the Configuration Manager (BIP8041E: Unable to open the selected file 'CONFIGMGR_TEST'.
The file selected could not be opened for read or write.
Ensure that, if specified as input, the file exists and not also for output; and that the file path is valid in any cases. Also ensure that the file is not locked by another user.).
The utility encountered a problem while attempting to connect to the Configuration Manager's queue manager to put a message to its request queue.
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the Configuration Manager's queue manager is running and that the current user is able to put messages to its SYSTEM.BROKER.CONFIG.QUEUE. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 17, 2008 11:25 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You have not specified all the mandatory parameters.
an
mqsideploy -h
will help
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| sridhsri |
| Posted: Thu Jul 17, 2008 12:13 pm Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
You could try using the command
mqsideploy -i ipaddress -p cfgmgr qmgr's port -q cfg qmgr -b broker name -e eg name -d flow name
if that doesn't work, use the -v parameter. this will enable trace. the trace file should give you more details. |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Fri Jul 18, 2008 10:14 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
| I ran a trace using -v option. How to interpret and analyze the trace file for required details? |
|
| Back to top |
|
|
| masuluris2k8 |
| Posted: Fri Jul 18, 2008 10:45 am Post subject: |
|
|
Newbie
Joined: 08 Apr 2008
Posts: 1
|
| Check the information you have provided in CONFIGMGR_TEST file to connect to the configuration manager. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jul 18, 2008 9:50 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are TWO wys to specify the CONFIG MANAGER in broker ( from 6.0 that is)
1) to supply the full path including extension of the file that gets created when you connect a toolkit to the config mgr.
i.e. Where you specify the Queue Manager Name, IP Address & Port.
You can get the full path name of this file using the toolkit itself.
2) To supply the Queue Manager Name, IP Address & Port of the Queue Manager Listener in the mqsideploy command. This is as per a previous reply to your question.
Please try these commands and post the output here.
This does work. I use it on at least 10 different broker/config mgr systems.
To quote a 1970's TV Series,
'Patience Grasshopper'.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| hany77eg |
| Posted: Fri Jul 18, 2008 10:59 pm Post subject: |
|
|
Newbie
Joined: 15 Jul 2008
Posts: 5
|
As i understand from your post you face two problems:
1- The flow still exists although you delete it
2- Config File can't be found/read when issue the mqsideploy command.
for the first issue:
Sometimes when there is a connection opened between the flow and DB for example an instance will be found when issuing the mqsilist command even after deleting the flow from the execution group; the solution is to kill the process and delete the execution group and recreate it again.
For the second problem:
First be sure you issue the command from the same location of the file
second be sure that the file is will formed and its contents are valid
i hope that this will help  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jul 19, 2008 9:21 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
[quote]BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1046E: Unable to connect with the Configuration Manager (BIP8041E: Unable to open the selected file 'CONFIGMGR_TEST'. [/quote]
I think this indicates that the errors are related to actually connecting to the Configuration Manager.
My previous replies on this topic have shown the way the errant command needs to be modified to actually specify the connection properties of the configuration manager Queue Manager ( IP Address, Port & QM Name).
Lets see the output from a revised command that actually specifies the Config Manager connection details. Then we can help the poster further.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
