mqsistart command

Use the mqsistart command to start the specified integration node, integration servers managed by the specified integration node, or any components that have been deployed to an integration server managed by the specified integration node. The command can also be used to start any components that have been deployed to an independent integration server.

Purpose

The mqsistart command:

  • Checks that the integration node environment is set up correctly; for example, that the installed level of Java™ is supported.
  • On Linux and AIX systems, where the mqsisetdbparms command was used to associate the data source with the integration node, the mqsistart command checks integration node connectivity to, and performs tests against, any user data sources where the IBM App Connect Enterprise Database Extender SupportPac is being used for extended database support.

    If any issues are identified, a warning is reported to the system log and command line. However, this step does not prevent the integration node from starting cleanly.

  • If the integration node has a queue manager, and that queue manager that is not running, the command returns an error.

  • Checks the publish/subscribe mode (attribute PSMODE) of the queue manager that is associated with the integration node. If the PSMODE is set to DISABLED, it is changed to COMPAT and this is reported to the system log. If the PSMODE is already set to COMPAT or ENABLED, the setting is not changed.
  • Depending on which parameters you specify with the command, you can start one, or all of the integration servers, applications, or message flows under the integration node.
  • The mqsistart command cannot be used to start an independent integration server. To start an independent integration server, use the IntegrationServer command. For more information, see Starting an integration server.
Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Authorization

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

The integration node starts only if the user ID under which it will run is authorized to access both the following locations. On Windows systems, the user ID is defined by the ServiceUserID specified on the mqsicreatebroker command; on Linux and AIX systems, it is the user ID with which you run this command:

  • Home directory, where IBM App Connect Enterprise has been installed.
  • Working directory, if specified by the -w flag on the mqsicreatebroker command.