Home
Changing DB2 configuration parameters
For each DB2 database that the queue manager is coordinating, we need to:
- Set database privileges
- The queue manager processes run with effective user and group mqm on UNIX systems. On Windows systems, they run as the user that started the queue manager. This can be one of:
- The user who issued the strmqm command, or
- The user under which the IBM MQSeries Service COM server runs
By default, this user is called MUSR_MQADMIN.
If you have not specified a user name and password on the xa_open string, the user under which the queue manager is running is used by DB2 to authenticate the xa_open call. If this user (for example, user mqm on UNIX systems) does not have minimal privileges in the database, the database refuses to authenticate the xa_open call.
The same considerations apply to your application process. If you have not specified a user name and password on the xa_open string, the user under which your application is running is used by DB2 to authenticate the xa_open call that is made during the first MQBEGIN. Again, this user must have minimal privileges in the database for this to work.
For example, give the mqm user connect authority in the mydbname database by issuing the following DB2 commands:
db2 connect to mydbname db2 grant connect on database to user mqmSee Security considerations for more information about security.- Change the tp_mon_name parameter
- For DB2 for Windows systems only, change the TP_MON_NAME configuration parameter to name the DLL that DB2 uses to call the queue manager for dynamic registration.
Use the command db2 update dbm cfg using TP_MON_NAME mqmax to name MQMAX.DLL as the library that DB2 uses to call the queue manager. This must be present in a directory within PATH.
- Reset the maxappls parameter
- You might need to review your setting for the maxappls parameter, which limits the maximum number of applications that can be connected to a database. Refer to Database connections.
Parent topic:
DB2 configuration
fa13610_
Home