The runnscnf tool

runnscnf is a tool that is used to change all kinds of different settings based on a common concept.

The tool uses the following terminology:


The term “class” means a set of objects of the same kind that have a common set of properties. By knowing the class of an object, runnscnf knows which changeable or viewable properties are available for the object, so only valid properties for that object and only valid values for the properties of an object can be entered. For supported classes and their properties see Classes. Class names are not case sensitive, so you can enter a class name in lowercase, uppercase, or any mixture of cases. Classes are defined by IBM® MQ, you cannot introduce new classes or delete existing classes.


An “object” within runnscnf is the name of a member of the appropriate class. Examples of objects are instances of the CacheManager (a type of process that stores non-persistent messages in main memory), named QueuePatterns (allowing rules for file size and file placement in the Guardian space), and so on. Names of objects are typically chosen by the user. In general, names of objects are case sensitive. For certain classes there is a fixed set of object names supported. See Classes.

Objects exist only as long as there is at least one configured or system maintained property for this object. When you set a property for an object, this object exists in the database maintained by runnscnf. When you delete the last property of an object, the object is also deleted.

If you want to use special characters in object names (like _, -, &, + and so on), the object name must be quoted in runnscnf. Without quoting, object names can consist only of characters and digits.

Each object has a set of named properties that can be changed and viewed by using runnscnf. A property of an object has a name and a value. For example, a property of the CacheManager CacheMan1 object is the CPU where the process is supposed to run. In that example, the class of the Object is “CacheManager”, the name of the object is “CacheMan1”, the name of the property is “CPU”, and the value of the property is the CPU where the process is supposed to run. All objects of a given class have the same set of available properties. The values of the properties always have a default, which can be overwritten by using runnscnf. runnscnf only shows values that are explicitly set by the user.

This concept allows a common, simple way of changing properties for different objects in a common, unified way.

runnscnf has two different modes of operation, local and global. In global mode, properties are set for all queue managers within a given installation. In local mode, a specific queue manager must be specified, and settings apply only to that queue manager. If a setting is given for a specific queue manager, it overwrites any potential global setting of the same property. The mode can be switched between local and global at any time.

Settings made in runnscnf do not work on existing objects, the settings apply only to newly created objects. So, for example, runnscnf cannot be used to change attributes of an existing queue file, it can only be used to set parameters for a new queue file to be created. All settings made with runnscnf are persisted in a file. Settings remain even after the queue manager is deleted, so if you recreate a queue manager with a name known to runnscnf, the previous settings remain in effect. If you want to delete the settings completely, you must use dltmqm with the -c option.