mqsireportbroker command

Use the mqsireportbroker command to display integration node registry entries.

Purpose

You can use the mqsireportbroker command to view the property values set when you create or change the integration node.

On Windows platforms, Linux, and UNIX systems, the mqsireportbroker command also reports whether an integration node is configured as a WebSphere® MQ service.

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

Usage notes

The following rules apply on the report:
  • You can run this command if the integration node is stopped or running.
  • If values for a password are set, eight asterisks are displayed.
  • Units are shown in the output for all numeric values.

Responses

The following table shows the output returned when you run the mqsireportbroker command.
Property (Units) Notes
brokerName 1
Service userId 2, 3, 4
Service password 2, 3, 4
Queue manager 1
Work path 1
Trusted (fastpath) queue manager application - true 2, 3
Trusted (fastpath) queue manager application - false 3, 5
User LIL path 2
Configuration change timeout (seconds) 2
Internal configuration timeout (seconds) 2
Administration security enabled (true or false) 2
Statistics major interval (minutes) 2
LDAP principal 2
LDAP credentials 2
ICU converter path 2
User exit path 2
Operation mode 2, 3
Fix pack capability level 5
Active user exits 5
Integration node UUID 7
Install path 8
Process ID 7
Notes:
  1. This value is set by the mqsicreatebroker command.
  2. This value is set by the mqsicreatebroker command or later modified by the mqsichangebroker command.
  3. This option is applicable only on distributed systems.
  4. This option is not relevant on Windows, because this value is stored in the service.
  5. This option can be set only by the mqsichangebroker command.
  6. (Not used.)
  7. This value is generated automatically when the integration node is started.
  8. You cannot set this value by using a command.

Authorization

For information about platform-specific authorizations, see the following topics: If you have enabled integration node administration security, you must also set up the authority that is detailed in Tasks and authorizations for administration security.