Supported MQCONNX parameters


The Agentless Services support the following IBM MQ MQCONNX parameters:

  • ChannelName
  • ConnectionName
  • RemoteQueueManagerName
  • SecurityExitName
  • SecurityUserData
  • CipherSpecName
  • KeyRepository
  • OCSPResponderURL
  • QmgrAuthType
  • QmgrAuthUserName
  • QmgrAuthPassword
  • CCDTURL (Client Channel Definition Table URL)

Refer to the IBM MQ documentation for specific details on their meaning. If the parameters have been specified for a particular queue manager, then they are used in the MQCONNX call when the Agentless Services are connecting to that queue manager.

At a minimum, you must specify the ConnectionName. If ChannelName is not specified, the channel name "SYSTEM.ADMIN.SVRCONN" is used, which might or might not be valid in your configuration.

When configuring an agentless connection to a queue manager, you might also want to specify the name of the Model Reply Queue Definition to use. This setting can be specified when using local queue manager connections also. This setting can be set individually for the IBM MQ Monitor and the IBM MQ Configuration extensions, as needed.

The following example changes both extensions to use the Model Reply Queue Definition named "MyModelQ".

Information
Example
agentpref --set "WebSphere MQ Monitor" DefaultModelQueue MyModelQ --set "WebSphere MQ Configuration " DefaultModelQueue MyModelQ --notify "WebSphere MQ Configuration" --notify "WebSphere MQ Monitor"
Warning

Important

It is not formally required that the DefaultModelQ for the IBM MQ Monitor and IBM MQ Configuration be the same, but to avoid confusion, BMC recommends that the same model queue be used unless there is a specific reason based upon your environment.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView Middleware Monitor 9.2