You must have a Version 6.0 installation of the product with the required component code installed, that is, the broker component is installed if it is needed, and so on.
Before starting migration, stop any debugging sessions in the Control Center. It is not possible to migrate message flows that are being debugged.
The mqsimigratecomponents command updates your registry and file system, WebSphere MQ definitions, and database definitions. If the user who is issuing the command does not have the authority to perform all of these steps, the command can be run one part at a time. Different users can run the part for which they are authorized in order to achieve the overall result. This is referred to as split migration and is performed using the -1, -2 and -3 parameters.
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.
mqsimigratecomponents FIRSTBROKER -t 6.0.0.1
mqsimigratecomponents BROKERB -1 -2
mqsimigratecomponents BROKERB -1 mqsimigratecomponents BROKERB -2
The migration check can be run against a running component. This does not impact the component, except for imposing a slight performance penalty. Note that on UNIX systems, the odbc.ini file needs to be migrated (that is, a new-format odbc.ini file needs to be created with the same set of data sources as the old one) before the check can be run, because the checking command needs to be able to access the broker database.
The check command either succeeds or fails, and prints a message about whether or not the migration should succeed, but no modifications are made during the process.
This command can produce a large number of possible responses,
depending on the results of the various operations. Note that this command
differs from other commands in the way it produces messages – they are displayed
as needed, rather than being produced in a batch at the end of the program.
When migrating database tables, z/OS produces
more output than distributed systems.
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:
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 illustrates 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 illustrates 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
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an26150_ |