mqsideploy command

Use the mqsideploy command to make a deployment request to the Configuration Manager.

Supported platforms

Purpose

Use the mqsideploy command to make deployment requests of all types from a batch command script, without the need for manual interaction.

The default operation is a delta or incremental deployment. Select -m to override the default operation.

mqsideploy does not require a Configuration Manager name parameter because all of the required connection details can be obtained from the -n, -q, -i, and -p parameters.

Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Authorization

On all platforms, the user ID used to run this command must have sufficient authority defined in the Configuration Manager to successfully deploy. The permissions required are the same as the permission required to perform the equivalent task in the Message Brokers Toolkit.

On Linux and UNIX systems, the user ID used to run this command must be a member of the group mqbrkrs. If you do not have mqbrkrs membership, the command fails with the following error message:
mqsideploy -i localhost -p 1414 -q qm2 -b brk2
BIP8081 An exception was caught while processing the command,
'Unable to format an ImbException message for output, ImbException message 
number is BIP2164'.

Responses

This command returns the following responses:
0
(Success) The Configuration Manager issued the deployment request and all of the relevant brokers responded successfully before the timeout period expired.
2
(Failure) The Configuration Manager issued the deployment request and at least one broker responded negatively. See the messages issued from the utility (or the Configuration Manager's event log) for more information.
3
(Initiated) The Configuration Manager has replied, stating that deployment has started, but that no broker responses were received before the timeout occurred.
5
(Submitted) The deployment message was sent to the Configuration Manager, but that no response was received before the timeout occurred.
6
(SuccessSoFar) The Configuration Manager issued the deployment request and some, but not all, of the relevant brokers responded successfully before the timeout period expired; no brokers responded negatively.
98
The Configuration Manager cannot be reached.
99
The arguments supplied to the utility are not valid.
Related concepts
Runtime environment
Related tasks
Deploying
Related reference
ACL permissions
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:34

an09020_