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.
To migrate a Version
5.0User Name Server to Version 6.0 on z/OS,
complete the following steps:
Stop the Version
5.0User Name Server.
Create a new User Name Server PDSE.
Copy all User Name Server JCL from the Version 6.0 installed SBIPPROC and SBIPSAMP PDSEs
to the new User Name Server PDSE and customize them
all.
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
5.0 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).
Customize the BIPEDIT file using values that are defined in the User Name Server's Version
5.0mqsicompcif file. Equivalent customization variables in mqsicompcif and BIPEDIT lists the customization
variables that are used in the Version
5.0 mqsicompcif
file, and the equivalent variables in the Version 6.0 BIPEDIT
file.
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.
Customize and submit the BIPMGCMP job.
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.
The verification program runs when you start the Version 6.0User Name Server.
When you have migrated the User Name Server,
ensure that you have migrated the rest of the components: