Areas of NonStop-specific configuration

Certain areas of configuration are specific to IBM® MQ on HPE NonStop.

Location and size of Guardian data files

IBM MQ for HPE NonStop V8.1 stores all dynamic data in audited Enscribe files. The data includes dynamically changing persistent queue data and object descriptions (such as channel definitions). The Guardian subvolume of these files and (for queue data files) primary extents, secondary extents, and maxextents can be configured by using runnscnf. See The runnscnf tool for details.

Processes for non-persistent messages

Non-persistent queue messages are kept in main memory and managed by specific processes called cache managers. You can configure multiple per-queue manager cache managers. Cache managers can run on a different CPU than the queue manager, providing some scalability. Each cache manager is responsible for storing non-persistent messages of a configurable set of IBM MQ queues. The relationship between cache managers, IBM MQ queues, CPU, and so on, can be configured by using runnscnf.

Set signal settings

IBM MQ for HPE NonStop V8.1 supports the MQGET SET_SIGNAL feature in the same way as IBM WebSphere® MQ for HP Integrity NonStop Server V5.3. The signal can be used from programs as for IBM WebSphere MQ for HP Integrity NonStop Server V5.3. As the implementation for version 8 is different from version 5.3, there are some settings available from runnscnf. The MQGET SET_SIGNAL feature in IBM MQ V8 is implemented using a new process class called SetSignalManager. Multiple SetSignalManager processes can be configured with one process doing the work for one queue. SetSignalManager processes can run on different CPUs. SetSignalManager processes are configured by using runnscnf.

EMS subsystem

IBM MQ for HPE NonStop V8.1 can optionally issue more, and more detailed, EMS messages than WebSphere MQ for HP NonStop Server V5.3. The extent of EMS messages issued and the collector used can be configured by using runnscnf.

Queue manager global settings

There are certain NonStop-specific settings that are global to the queue manager. These settings include the home terminal being used, the CPU, the priority of certain NonStop-specific processes, tuning parameters, CPU set assignment for each queue manager, settings for fault tolerance, default TCP transport, and so on. All these settings are available by using runnscnf.

User name mapping

User names within IBM MQ have a length limit of 12 characters per name. NonStop user names can be up to 17 characters long. On NonStop, names consist of group name, a dot (‘.’), and a user name, like: MYGROUP1.USER1. Group name and user name can each be up to 8 characters long, so the name of a regular NonStop user can be up to 17 characters long and thus does not fit in the data structures used by IBM MQ to store user identification.

WebSphere MQ for HP NonStop Server V5.3 provided the tools dspmqusr and altmqusr to create a mapping between NonStop-specific user names and names used within IBM MQ. This mapping can be used to establish a one-to-one relationship between IBM MQ internal names and NonStop user names. These tools are available in IBM MQ for HPE NonStop V8.1, with similar syntax and functionality to the WebSphere MQ for HP NonStop Server V5.3 tools. See altmqusr and dspmqusr.

IBM MQ user names are sometimes referred to as Principal Names. The mapping described here is stored in an internal database. The crtmqm command creates this database and adds an entry for the user who ran the installation script (the installation owner). The principal created is always ‘mqm’, for compatibility with other IBM MQ implementations.

After you have created a queue manager, you can create entries in the database for other users of the queue manager.

You can use IBM MQ standard mechanisms to authorize NonStop users outside of the MQM group (which is reserved for IBM MQ administration) to use certain features and/or resources of an IBM MQ queue manager. For this authorization to be effective, the following conditions must be met:

  • A mapping must be present in the internal database.
  • Authorization must be explicitly granted to all resources accessed (see the setmqaut command).

NonStop users within the MQM group (other than the installation owner) can administer (create, start, stop, secure, and so on) any queue manager within the installation. No user name mapping is required to do so.

Applications require a mapping entry to use a queue manager (put, get, browse, and so on). If no mapping entry is found, application access is refused. No explicit or additional authorization (via setmqaut) is required, however.