Use the mqsideploy command on z/OS® to make a deployment request to a local broker.
>>-mqsideploy--| brokerSpec |-----------------------------------> >-- -e --integrationServerName--+- -a --BARFileName--+------+-+--> | '- -m -' | '- -d --deployedObjects-------' >--+-------------------+--+---------------------+-------------->< '- -w --timeoutSecs-' '- -v --traceFileName-' brokerSpec |--+- brokerName ----------------+------------------------------| +- -n --brokerFileName--------+ | .-------------------------. | | V | | '-----+- -i --ipAddress-+---+-' +- -p --port------+ '- -q --qMgr------'
Synonym: dp
>>-+-deploy-+---------------------------------------------------> '-dp ----' >-- e=integrationServerName --+- a=BARFileName --+---------+-+--> | '- m=yes -' | '- d=deployedObjects ----------' >--+------------------+--+-------------------+----------------->< '- w=timeoutValue -' '- v=traceFileName -'
Use this option if multiple users want to connect to the same broker, or if you are using advanced connection parameters such as SSL.
To create this file, right-click the broker in the IBM® Integration Explorer and select Export *.broker file. When prompted, navigate to the location in which you want to save the file and enter the file name; the extension .broker is appended automatically when you click Save. Include the location (path) and file name when you specify this parameter. You must ensure that the location is accessible when you run this command.
If you want to run a command that uses SSL to administer a remote broker over a secured channel, you must specify the keystore and truststore password for the connection using the IBM_JAVA_OPTIONS environment variable. See Resolving problems when running commands for further information.
If you choose this option, you must specify at least one of these three parameters; the order in which you specify them is irrelevant. You cannot specify each parameter more than once.
Parameters that you omit assume default values:
The BAR file can be in a local or remote file system, if the user ID or the broker that is running the command can access the file and read it.
You can specify objects of all types, but if you specify an ambiguous object name (for example, "top", when both "top.dictionary" and "top.cmf" are deployed to the same integration server), the entire command fails with the message BIP1089. In these circumstances, you must specify the fully qualified name of the objects to remove; for example, "top.dictionary:top.cmf".
The default operation is a delta or incremental deployment. Use the -m parameter to override the default operation and run a complete deployment.
You can set this parameter to a value in the range 1 - 2 145 336 164. If you do not provide a timeoutValue value, or you set a value less than 1 or greater than 2 145 336 164 is specified, an error is returned.
Set this parameter to a value greater than the sum of the configuration timeout parameters ConfigurationChangeTimeout and InternalConfigurationTimeout that you specified for the broker, if you want to ensure that a response is received within the timeoutValue period. If you set a smaller value, the response returned might indicate that the state of the deploy request is unknown.
If you try to connect to a remote broker by specifying the i, p, and q parameters, or by using a connection parameter file (.broker), the command attempts to use WebSphere® MQ Java™ client code. This option is not supported on z/OS, and returns the following error:
BIP1046E: Unable to connect with the broker (name)
The reported reason code is MQRC_ENVIRONMENT_ERROR. You must specify a local queue manager.
The following examples show the use of the -n parameter to define the connection parameters for the broker. If the broker is on the local computer, you can specify it by name.
mqsideploy -n broker1.broker -e default -a mybar.bar -m -w 600
mqsideploy –n b1.broker –e default –d top.cmf:bar.dictionary
F MQ01BRK,dp e=default,a=flows.bar