Class QueueManager

CurrentQMGR object

Table 1. QueueManager properties for object CurrentQMGR

Name	Datatype	Meaning
EmitEMSforExpiry	Bool	Control whether to emit EMS messages about processed expired messages.
EMSCounterForExpiredMsgs	Number	Specify how many messages have to expire for each EMS message.
AuditRefreshInterval	Number	Specify how often to check for changes to queue manager .ini files or SSL files so changes can be replicated to the passive node in a disaster recovery configuration. The interval is given in seconds.
RecoverSSLFiles	Bool	Set this to T to specify that SSL files located in OSS ssl directory are checked and recovered from Guardian MQ catalog file (AMQOBJMQ) on queue manager startup if required. Defaults to F.
ConfiguredEnvOnly	Bool	Set to T to specify that environment variables are taken only from what is configured using runnscnf. Set to F to specify that environment variables are taken from the runnscnf settings, but also from the shell if not set by runnscnf.

Set the value of EmitEMSforExpiry to t to enable the EMS messages, set it to f to disable EMS messages. Changing EmitEMSforExpiry takes effect after a queue manager restart. The EMS message has the event number 5 and the unique id EMS_probeId_1050.

EMS messages can be generated to indicate there are expired messages on a specified queue. If EMS messages are enabled, messages are emitted if one of the following conditions occur:

• At least one message has expired within the configured time interval.
• The configured number of messages have expired.

The time interval is configured by setting ExpiryInterval in stanza TuningParameters in the queue manager-specific configuration file qm.ini. The value ExpiryInterval is also used for the expiry task. The default time interval is 300 seconds.

The number of messages expired is configured by setting the EMSCounterForExpiredMsgs for this class. The default number of messages is 10,000.

The settings are configured on a queue manager basis, but expired messages are reported per queue.

The property RecoverSSLFiles must be set on the active node in a disaster recovery configuration that is replicated to passive node along with the Guardian MQ catalog file containing the archived ssl files. The ssl file recovery procedure is invoked on each node if RecoverSSLFiles if set to T.

Environment object

You can use the Environment object to set values for environment variables. The properties for this object are environment variable names. An environment variable can have any name and be set to any value. The name is case sensitive, for example, MYVARIABLE is a different variable to MyVariable.

If you set an environment variable by using runnscnf in global mode, that environment is used for all queue managers. If you set an environment variable by using runnscnf in local mode, that environment is used only for the specified queue manager. Settings made for a specific queue manager override those made for all queue managers.

The ConfiguredEnvOnly property of the CurrentQMGR object is used to specify how a queue manager's environment is derived. Set ConfiguredEnvOnly to T to specify that only settings made by runnscnf are used, and any environment variable settings made in the shell are ignored. If ConfiguredEnvOnly is set to F, the environment is derived from the shell, but any environment variables set in runnscnf override any that are set in the shell.

ActualEnvironment object

You can use the ActualEnvironment object to view the environment that is currently set for a queue manager. The properties are the environment variables and their settings. Note that the environment displayed might not be the environment that the queue manager is currently running in. If you change the environment, the ActualEnvironment reflects that change, but the queue manager does not pick up that change until it is restarted.