Before making Db2 12 operational, ensure that all work is stopped on
the Db2 11 subsystem.
Before you begin
If you do not stop work on the Db2 11 subsystem
or data sharing member that you are migrating, fallback procedures
might fail.
Procedure
To stop work on the system that you are migrating:
- Issue the following command, where -DSN1 is
the subsystem command prefix that is defined for Db2.
You must have system administrator (SYSADM) or system operator
(SYSOPR) authority to issue this command.

-DSN1 STOP DB2 MODE(QUIESCE)

The QUIESCE keyword allows
Db2 to complete
the processing of programs that are currently executing. This might
require some processing time.
- Issue the following command to allow only the
system administrators and system operators that were defined during
installation to access Db2:

-DSN1 START DB2 ACCESS(MAINT)

If
Db2 does
not start properly, it usually abends with a reason code that indicates
where the error occurred. To find the error, check the set of definitions
for the associated resource. For example, if the bootstrap data set
(BSDS) does not match the subsystem parameter values, ensure that
the correct jobs were run for DSNTIJUZ. Ensure that you started
Db2 with
the correct subsystem parameter option.
-
Follow these steps to ensure that all Db2 11 work is stopped:
-
Stop Db2by issuing the following
command:

-DSN1 STOP DB2 MODE(QUIESCE)

A user with
installation system administrator (installation SYSADM) or installation system operator
(installation SYSOPR) authority must enter this command.

What to do next
If
you have not already converted the BSDS to extended format, you must complete the conversion, as
described in Convert the BSDS, Db2 catalog, and directory to 10-byte RBA and LRSN format , before you begin Migration step 18: Start Db2 12.