[UNIX, Linux, Windows, IBM i]

TuningParameters stanza of the qm.ini file

The TuningParameters stanza specifies options for tuning the queue manager.

SuppressDspAuthFail=YES|NO (default)
When set to YES, the queue manager suppresses generation of authorization events and the writing of AMQ8077 error messages to the error log when an authorization check fails, if the connection lacks +dsp authority to an object.
ImplSyncOpenOutput=value
ImplSyncOpenOutput is the minimum number of applications that have the queue open for put, before an implicit syncpoint might be enabled for a persistent put, outside of syncpoint. The default value of ImplSyncOpenOutput is 2.
This has the effect that if there is only one application that has that queue open for a put operation, ImplSyncOpenOutput is switched off.
Specifying ImplSyncOpenOutput=1 means that an implicit syncpoint is always considered. You can set any positive integer value. If you never want an implicit syncpoint to be added, set ImplSyncOpenOutput=OFF.
UniformClusterName=name of cluster
The name of the IBM® MQ cluster that you are using as a uniform cluster.
OAMLdapConnectTimeout=time|0 (default)
The maximum time, in seconds, that the LDAP client will wait to establish a TCP connection to the server. If you are supplying multiple LDAP servers through a connection namelist, the timeout applies to each individual connection attempt, and so a connection to the next entry in the namelist is attempted if this timeout is reached.
time has a maximum value of 3600 seconds, and a value of 0, which is the minimum value as well as the default value, means that the wait is unlimited.
OAMLdapQueryTimeLimit=time|0 (default)
The maximum time, in seconds, that the LDAP client will wait to receive a response to an LDAP request from the server, once a connection has been established, and an LDAP request has been sent.
time has a maximum value of 3600 seconds, and a value of 0, which is the minimum value as well as the default value, means that the wait is unlimited.
[MQ 9.3.2 Feb 2023][MQ 9.3.0.5 Apr 2023]OAMLdapResponseWarningTime=threshold
If a connection to an LDAP server took longer than the threshold number of seconds specified by the OAMLdapResponseWarningTime parameter, then an AMQ5544W message will be written to the error log. The default threshold is 10 seconds.
ExpiryInterval
Indicates the frequency with which the queue manager scans the queues looking for expired messages that have not already been cleaned up by other queue activities. It is a time interval in seconds.
By default, the expiry scanner runs approximately every five minutes on production IBM MQ builds.
CAUTION:
Altering the ExpiryInterval value is not typically required, and you should modify this value only under the guidance of IBM Support.
LivenessHeartBeatLen
Configures the frequency with which the queue manager checks that writes to the log are being made at a reasonable rate. The maximum value for LivenessHeartBeatLen is 600 seconds (10 minutes) and the minimum value is 0, which has the effect of disabling the check altogether.
CAUTION:
In most cases, it is not necessary to change the frequency of these checks. Do not make any changes unless your are advised to do so by IBM Support.
ECHeartBeatLen
Configures the frequency of the queue manager general health checks. The minimum value for ECHeartBeatLen is 10000 milliseconds (10 seconds) and the maximum value is 60000 milliseconds (60 seconds).
CAUTION:
In most cases, it is not necessary to change the frequency of these checks. Do not make any changes unless your are advised to do so by IBM Support.
FileLockHeartBeatLen
Changes the default value for the file lock checks for a multi-instance queue manager that the execution controller periodically performs to make sure that it still holds the exclusive lock on the primary multi-instance file. By default, these file lock checks are made every 20 seconds. The minimum value for FileLockHeartBeatLen is 10 seconds, and the maximum value is 600 seconds (10 minutes).
CAUTION:
In most cases, it is not necessary to change the frequency of these checks. Do not make any changes unless your are advised to do so by IBM Support.

Example stanza

[MQ 9.3.2 Feb 2023][MQ 9.3.0.5 Apr 2023]

TuningParameters:
        SuppressDspAuthFail=NO
        ImplSyncOpenOutput=2
        OAMLdapConnectTimeout=60
        OAMLdapQueryTimeLimit=60
        OAMLdapResponseWarningTime=10
        ExpiryInterval=300