Migrating a Version 2.1 User Name Server to Version 6.0 on z/OS

Before you start
  • Ensure that you are familiar with the steps involved in creating a User Name Server on z/OS.
  • The JCL uses the mqsimigratecomponents command to migrate a User Name Server on z/OS. This command takes many parameters, which you must understand fully before attempting to migrate the User Name Server.

If you have a User Name Server in your Version 2.1 domain, you must migrate it to Version 6.0 when you migrate the Configuration Manager for that domain. This applies if the Configuration Manager and User Name Server are on the same computer, or different computers. This does not affect the migration of brokers, which can be migrated after the User Name Server and Configuration Manager have been migrated.

  1. Stop the Version 2.1 User Name Server.
  2. Create a new User Name Server PDSE.
  3. Copy all User Name Server JCL from the Version 6.0 installed SBIPPROC/SBIPSAMP PDSEs to the new User Name Server PDSE and customize them all. See Customizing the User Name Server JCL for more information.

    When you customize the new Version 6.0 JCL for this migration, do not make the ++HOME++ JCL variable the same value as the existing Version 2.1 component directory, otherwise the previous ENVFILE will be overwritten when you submit the BIPGEN job. Set the ++HOME++ variable to the Started Task user ID home directory (for example, /u/mq01uns).

    1. Customize the BIPEDIT file using values that are defined in the User Name Server's Version 2.1 mqsicompcif file. Equivalent customization variables in mqsicompcif and BIPEDIT lists the customization variables that are used in the Version 2.1 mqsicompcif file, and the equivalent variables in the Version 6.0 BIPEDIT file.
    2. Copy any additional changes that you have made to the environment file, ENVFILE, to BIPUPROF in the component data set. Submit the BIPGEN job to create the environment file ENVFILE.
    3. Customize and submit the BIPMGCMP job.
  4. Copy the started task JCL (BIPUNSP) to the procedures library. When you copy the started task, keep a second copy of the original in a safe place for backup purposes.
  5. The verification program runs when you start the Version 6.0 User Name Server.

When you have migrated your User Name Server, migrate the broker.

Related tasks
Backing up Version 2.1 resources
Creating a User Name Server on z/OS
Creating the User Name Server PDSE
Customizing the User Name Server JCL
Copying the User Name Server started task to the procedures library
Planning for migration from Version 2.1
Migrating the tooling
Migrating a Configuration Manager from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating the broker
Related reference
Equivalent customization variables in mqsicompcif and BIPEDIT
Sample BIPEDIT file
mqsimigratecomponents command