The
following steps show you how to modify a Configuration
Manager's
service user ID, service password, database password, User Name Server queue
manager, and the maximum JVM heap size, on Windows:
- Stop the Configuration
Manager using the mqsistop command.
- Enter the mqsichangeconfigmgr with the parameters you want to change:
mqsichangeconfigmgr configmgrName <<-i ServiceUserID> -a ServicePassword>
<-p DatabasePassword> <-s UserNameServerQueueManagerName> <-j MaxJVMHeapSize>
where:
- configmgrName
- Is the Configuration
Manager name. This is optional.
- -i
- Is the service user ID that is used to run the Configuration
Manager.
- -a
- Is the password for the Configuration
Manager user
ID.
- -p
- If an existing DB2 database
from a pervious version of the product has not yet been migrated, use this
option to set the password used to access the database.
- -s
- Is the WebSphere
MQ queue manger for the User Name Server.
- -j
- Is the maximum Java virtual machine heap size, in megabytes (minimum 64).
For example, to modify the
Configuration
Manager so
that it can communicate with the
User Name Server,
enter the following command at the command prompt:
mqsichangeconfigmgr CMGR01 -s WBRK_UNS_QM
- Restart the Configuration
Manager using the mqsistart command.
The Configuration
Manager restarts with the new properties.
If you cannot change a property, delete the Configuration
Manager then create a new one with the new property.
Creating a new Configuration
Manager does not cause any
loss of data as long as the previous Configuration
Manager's
database tables were not deleted (for example, by specifying the -n parameter
on the mqsideleteconfigmgr command).