DB2 - Problem description
Problem IC89691 | Status: Closed |
ENABLE_MQFUNCTIONS UTILITY SHOWS UNSUPPORTED PARAMETER "-Q" IN USAGE MESSAGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using enable_MQFunctions executable you may see usage message as below: ============================================================ Usage: enable_MQFunctions -n dbName -u uID -p password [-q queuemanager] [-v 0pc|1pc|all] [-novalidate] [-echo] [-force] [-c clobSize] ============================================================ But actually Federation Server does NOT support parameter [-q queuemanager] on v95 or later versions. You can not specify queue manager name to enable your MQ UDF. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * The users who want to enable MQ UDF using their own queue * * manager instead of the * * default one. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Federation Server Version 9.7 and Fix Pack 8. * **************************************************************** | |
Local Fix: | |
To enable MQ UDF using your own queue manager instead of the default one: 1. Create your own queue manager, create at least a receive queue in it, active it. 2. Run enable_MQFunctions(without -q option) to enable MQ UDF using the default queue manager. 3. Run below SQLs to update the config table to use your own queue manager: 1) UPDATE DB2MQ."MQSERVICE" SET QUEUENAME='<QUEUE_NAME>',QUEUEMGRNAME='<QUEUE_MGR_NAME>' WHERE SERVICENAME='DB2.DEFAULT.SERVICE' 2) UPDATE DB2MQ."MQHOST" SET QUEUEMGRNAME='<QUEUE_MGR_NAME>' 3) ALTER SERVER MQ OPTIONS(SET AMI_QUEUE_MGR_LIST '<QUEUE_MGR_NAME>') NOTE: Where <QUEUE_MGR_NAME> is the queue manager name, <QUEUE_NAME> is name of the queue managered by <QUEUE_MGR_NAME> | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
The problem is firstly fixed in Federation Server V97fp8. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 02.04.2013 02.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7., 9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |