Use the mqsimigratecomponents command to migrate a component from a previously installed version of the product to another version on the same computer to prepare it for participation in the broker domain of the target version.
You can also use this command to return a component from a later version to an earlier one to reverse the effects of forward migration.
You must run this command from whichever version of the installed product is the later, regardless of whether it is the source version or the target version.
You must have an installation of the product at the required version, with the required component code installed, to issue this command successfully.
Before you start migration, stop any active debug sessions in the Message Brokers Toolkitor the Version 2.1 Control Center. You cannot migrate message flows that are being debugged.
1> use master 2> go 1> sp_dboption "BROKER1","ddl in tran",TRUE 2> go Database option 'ddl in tran' turned ON for database 'BROKER1'. Run the CHECKPOINT command in the database that was changed. (return status = 0) 1> use BROKER1 2> go 1> checkpoint 2> gowhere BROKER1 is the name of the Sybase broker database.
You can check a running component. The check does not affect the component, apart from a slight impact on performance. On Linux and UNIX systems, you must migrate the ODBC configuration file (the file in which you have defined the data sources, for example .odbc.ini) before you run the check, because the checking command must be able to access the broker database.
The check command either succeeds or fails, and prints a message about whether the migration will succeed, but no modifications are made during the process.
If a broker that you are migrating shares a database schema with another broker, warning message BIP8678 is issued and the check fails. In this case, all the brokers that share a database schema must be migrated together.
mqsimigratecomponents FIRSTBROKER -t 6.0.0.1
mqsimigratecomponents BROKERB -1 -2
mqsimigratecomponents BROKERB -1 mqsimigratecomponents BROKERB -2
The mqsimigratecomponents command updates your registry and file system, WebSphere MQ definitions, and database definitions. If the user ID used to run this command does not have the authority to perform all of these steps, you can run the command one part at a time. Different users can run the part for which they are authorized in order to achieve the overall result. This approach is referred to as split migration, and is performed using the -1, -2, and -3 parameters.
If you run split migration, your user ID must always have the ability to read from the registry for the product, and also have specific authorization for each step to succeed:
This command can produce a large number of possible responses, depending on the results of the various operations. This command differs from other commands in the way it produces messages: they are displayed as generated, rather than being reported in a batch at the end of the program. When you migrate database tables, z/OS produces more output than distributed systems. Use the -q parameter to reduce the number of messages displayed.
The following example checks for migration of BROKER1 from Version 2.1 to Version 6.0:
mqsimigratecomponents –c BROKER1
BIP8849I: Broker 'BROKER1' (Version 2.1) with Queue Manager 'brkqm1' and Data Source 'brkdb1' specified for migration.
BIP8791I: Duplicate rows check started.
BIP8794I: Table BRMINFO has no duplicated rows.
BIP8794I: Table BRMRTDDEPINFO has no duplicated rows.
BIP8794I: Table BROKERRESOURCES has no duplicated rows.
BIP8794I: Table BRMRTDINFO has no duplicated rows.
BIP8794I: Table BRMWFDINFO has no duplicated rows.
BIP8792I: Duplicate rows check passed.
BIP8791I: Duplicate rows check started.
BIP8800W: No invalid topic syntax was detected in table BSUBSCRIPTIONS.
BIP8800W: No invalid topic syntax was detected in table BPUBLISHERS.
BIP8800W: No invalid topic syntax was detected in table BRETAINEDPUBS.
BIP8797I: Topic syntax check succeded
BIP8680I: Pre-migration check succeeded.
BIP8071I: Successful command completion.
The following example does automatic migration of BROKER1 from Version 2.1 to Version 6.0 on Windows:
mqsimigratecomponents BROKER1
BIP8849I: Broker 'BROKER1' (Version 2.1) with Queue Manager 'BROKER1' and Data Source 'BROKERDB' specified for migration.
BIP8755I: Copied value 'QueueManagerName' into the new location
BIP8755I: Copied value 'DataSourceName' into the new location
BIP8755I: Copied value 'DataSourceUserId' into the new location
BIP8755I: Copied value 'DataSourcePassword' into the new location
BIP8755I: Copied value 'LilPath' into the new location
BIP8755I: Copied value 'ConfigurationTimeout' into the new location
BIP8755I: Copied value 'ConfigurationDelayTimeout' into the new location
BIP8755I: Copied value 'MigrationNeeded' into the new location
BIP8755I: Copied value 'MQTrustedQueueManager' into the new location
BIP8755I: Copied value 'UserNameServerQueueManagerName' into the new location
BIP8755I: Copied value 'BrokerUUID' into the new location
BIP8755I: Copied value 'AdminAgentPID' into the new location
BIP8763I: Deleted value 'QueueManagerName' from the old location
BIP8763I: Deleted value 'DataSourceName' from the old location
BIP8763I: Deleted value 'DataSourceUserId' from the old location
BIP8763I: Deleted value 'DataSourcePassword' from the old location
BIP8763I: Deleted value 'LilPath' from the old location
BIP8763I: Deleted value 'ConfigurationTimeout' from the old location
BIP8763I: Deleted value 'ConfigurationDelayTimeout' from the old location
BIP8763I: Deleted value 'MigrationNeeded' from the old location
BIP8763I: Deleted value 'MQTrustedQueueManager' from the old location
BIP8763I: Deleted value 'UserNameServerQueueManagerName' from the old location
BIP8763I: Deleted value 'BrokerUUID' from the old location
BIP8763I: Deleted value 'AdminAgentPID' from the old location
BIP8768I: Finished registry migration for component 'BROKER1'.
BIP8654I: Moving filesystem artefacts from '' to 'C:\Documents and Settings\AllUsers\Application Data\IBM\MQSI'
BIP8670I: Database migration started
BIP8663I: Creating temporary new tables
BIP8664I: Migrating from existing tables to temporary new tables
BIP8665I: Dropping existing tables
BIP8666I: Creating new tables
BIP8667I: Copying all rows from temporary new tables to new tables
BIP8668I: Dropping temporary new tables
BIP8669I: Database migration successful
BIP8785I: Starting WebSphere MQ queue migration for component 'BROKER1'.
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.AGGR.REQUEST'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.AGGR.CONTROL'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.AGGR.REPLY'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.AGGR.TIMEOUT'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.AGGR.UNKNOWN'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.TIMEOUT.QUEUE'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.WS.INPUT'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.WS.REPLY'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.WS.ACK'
The setmqaut command completed successfully.
BIP8786I: Created WebSphere MQ queue 'SYSTEM.BROKER.IPC.QUEUE'
BIP8787I: Cleared WebSphere MQ queue 'SYSTEM.BROKER.ADMIN.QUEUE'
BIP8787I: Cleared WebSphere MQ queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE'
BIP8787I: Cleared WebSphere MQ queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY'
BIP8787I: Cleared WebSphere MQ queue 'SYSTEM.BROKER.IPC.QUEUE'
BIP8789I: Finished WebSphere MQ queue migration for component 'BROKER1'.
BIP8071I: Successful command completion.
The following example shows a split migration from Version 2.1 to Version 6.0:
mqsimigratecomponents BROKER -1 mqsimigratecomponents BROKER -s 2.1.0.8 -2 mqsimigratecomponents BROKER -s 2.1.0.8 -3
The following example shows a split migration from Version 6.0 to Version 2.1:
mqsimigratecomponents BROKER -t 2.1.0.8 -2 mqsimigratecomponents BROKER -t 2.1.0.8 -3 mqsimigratecomponents BROKER -t 2.1.0.8 -1