The table below lists and explains names and meanings of the MQ parameters. These values are tuned by editing the /etc/default/LifeKeeper configuration file.
| Parameter Name | Meaning | Setting Value | Default Value | When to Apply | Notes |
|---|---|---|---|---|---|
| MQS_QUICKCHECK_TIMEOUT_SC | Timeout in seconds for the server connect check. | Integers | 10 | As required (takes effect immediately) | |
| MQS_QUICKCHECK_TIMEOUT_CC | Timeout in seconds for the client connect check. | Integers | 10 | As required (takes effect immediately) | |
| MQS_QUICKCHECK_TIMEOUT_PUTGET | Timeout in seconds for the PUT/GET check. | Integers | 10 | As required (takes effect immediately) | |
| MQS_QUICKCHECK_TIMEOUT_PS | Timeout in seconds for checking whether publish/subscribe is in use. | Integers | 5 | As required (takes effect immediately) | |
| MQS_QUICKCHECK_TIMEOUT_CLUSTER | Timeout in seconds for checking whether the queue manager is part of an WebSphere MQ cluster or not. | Integers | 5 | As required (takes effect immediately) | |
| MQS_QUICKCHECK_TIMEOUT | Timeout in seconds for the quickCheck script. | Integers | 40 | As required (takes effect immediately) | If the value is less than 10 seconds, it will be set to the default. |
| MQS_QMGR_START_TIMEOUT | Timeout in seconds for the queue manager start command to complete. | Integers | 60 | As required (takes effect immediately) | |
| MQS_CMDS_START_TIMEOUT | Timeout in seconds for the command server start command to complete. | Integers | 30 | As required (takes effect immediately) | |
| MQS_LISTENER_START_TIMEOUT | Timeout in seconds for the listener start command to complete. | Integers | 30 | As required (takes effect immediately) | |
| MQS_LISTENER_LIST_TIMEOUT | Timeout in seconds for the listener list command to complete. | Integers | 10 | As required (takes effect immediately) | |
| MQS_CHECK_TIMEOUT_ACTION | The action in case a server connect check or client connect check times out. | ignore: a message about the timeout is logged, but no recovery is initiated sendevent: local recovery is initiated in case a server connect check timed out |
ignore | As required (takes effect immediately) | |
| MQS_LISTENER_CHECK_DELAY | Time in seconds between the start of the listener and the check for the successful listener start. The default of 2 seconds should be sufficient to detect port in use conditions. | Integers | 2 | As required (takes effect immediately) | If the value is less than 2 seconds, it will be set to the default. |
| NO_AUTO_STORAGE_DEPS | Determines if the shared storage checks and file system resource creation step are performed for the queue manager and log storage directories during MQ resource hierarchy creation. A value of 0 indicates these tasks will be perform. A value of 1 will bypass these tasks. | 0 or 1 | 0 | As required (takes effect immediately) | |
| MQS_DSPMQVER_TIMEOUT | Timeout in seconds for the dspmqver command (needed to find out the version of WebSphere MQ), must be at least 2 seconds. | Integers | 5 | As required (takes effect immediately) | |
| MQS_SKIP_CRT_MISSING_Q | Determines if missing test queue is automatically created. A value of 0 indicates missing test queues will automatically be created. A value of 1 indicates this process will be skipped. | 0 or 1 | 0 | As required (takes effect immediately) | |
| MQS_ALT_USER_NAME | The alternate user name to use for all WebSphere MQ commands. By default the user mqm is used. If set the alternate user must have its primary group set to the group mqm or must have secondary membership in that group. | Character string | mqm if not set or the user does not have membership in the “mqm” group. | As required (takes effect immediately) | Should only be set if a WebSphere MQ addon package requires a user other than “mqm” |
Post your comment on this topic.