Check readiness for migration to Db2 13

You can check the readiness of your Db2 12 environment for migration to Db2 13.

Before you begin

Complete the following tasks:

Apply the PTF for APAR PH58761 in Db2 12. In data sharing, apply these APARs on any Db2 12 members where you plan to run the DISPLAY GROUP command to check migration readiness.
Apply required maintenance in Db2 12. See Required maintenance for Db2 13 installation or migration.
Verify premigration activities and activate function level 510 in Db2 12. See Verify Db2 13 premigration activities and activate function level 510 in Db2 12.

Procedure

To check the readiness of your Db2 12 environment for migration to Db2 13, complete the following steps:

Issue a DISPLAY GROUP command with the DETAIL option in Db2 12.
```
-DIS GROUP DETAIL
```
Check the MIGRATION READINESS REPORT report section in the DSN7100I message output.
The the migration readiness report has the following format:
```
MIGRATION READINESS REPORT
--------------------------
DB2       CODE       SPE      MIGRATION
MEMBER    LEVEL      APAR     ELIGIBLE
--------  ---------  -------  ---                        
text      text       text     text                                   
MIGRATION READINESS STATUS: type-text readiness-text                                                  
REASON: reason-text                                                          
--------------------------------------------------------------------- 
```
DB2 MEMBER text

The name of the Db2 data sharing member.

CODE LEVEL text

The current code level of the data sharing member or subsystem.The format is VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level.

SPE APARtext

The fallback SPE APAR value for this data sharing member or subsystem. If the value is not initialized to a fallback SPE APAR number, '.......' is displayed.

MIGRATION ELIGIBLE text

Indicates whether the data sharing group member or subsystem has on the fallback SPE for the next Db2 release. The value is YES, NO, or N/A.

N/A indicates a Db2 13 member that is already migrated in coexistence with Db2 12.

MIGRATION READINESS STATUS: type-textreadiness-text

GROUP for data sharing or SUBSYSTEM for a standalone Db2 subsystem
type-text

GROUP or SUBYSTEM.

readiness-text

One of the following status indicators:

IS NOT READY FOR DB2 nn

IS NOT READY FOR DB2 NEXT

IS READY FOR DB2 nn

GROUP MIGRATION IN PROGRESS TO DB2 nn
REASON: reason-text
Indicates one of the following reasons that the subsystem or data sharing group is not yet ready to migrate to the next release of Db2:
- NO NEXT RELEASE OF DB2 IS CURRENTLY AVAILABLE
- COEXISTENCE PRECLUDES MIGRATION TO NEXT DB2 RELEASE
- ALL REMAINING MEMBERS ARE READY FOR DB2 nn
- HIGHEST ACTIVATED FUNCTION LEVEL NOT VnnR1Mnnn, where VnnR1Mnnn is the expected highest available function level.
- REQUIRED FALLBACK SPE APAR MISSING: PHnnnnn, where PHnnnnn is the expected fallback SPE APAR number.

Examples

You might see the following examples when you issue the following DISPLAY GROUP command with the DETAIL keyword in Db2 12.

-DIS GROUP DETAIL

Db2 12 data sharing group that is ready for migration

The following example migration readiness report shows that member DB2A, which is the only active member, has a highest activated function level of V12R1M510 and has the fallback SPE APAR applied, so the data sharing group is ready for migration to Db2 13.

DSN7100I  -DB2A DSN7GCMD                                             
*** BEGIN DISPLAY OF GROUP(DSNCAT  ) CATALOG LEVEL(V12R1M509)        
                  CURRENT FUNCTION LEVEL(V12R1M510)                  
                  HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M510)        
                  HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M510)         
                  PROTOCOL LEVEL(2)                                  
                  GROUP ATTACH NAME(DSNG)                            
---------------------------------------------------------------------
DB2          SUB                     DB2    SYSTEM    IRLM           
MEMBER   ID  SYS  CMDPREF   STATUS   LVL    NAME      SUBSYS PRLM2171
DB2A       1 DB2A -DB2A     ACTIVE   121510 UTEC5     PR21   PRLM21  
DB2B       2 DB2B -DB2B     QUIESCED 111500 UTEC5     QR21   QRLM21  
---------------------------------------------------------------------
MIGRATION READINESS REPORT                                           
--------------------------                                           
DB2       CODE       SPE      MIGRATION                              
MEMBER    LEVEL      APAR     ELIGIBLE                               
--------  ---------  -------  ---                                    
DB2A      V12R1M510  PH37108  YES                            
MIGRATION READINESS STATUS: GROUP IS READY FOR DB2 13
---------------------------------------------------------------------
DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG            
---------------------------------------------------------------------
...
*** END DISPLAY OF GROUP(DSNCAT  )                                   
-DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL DSN9022I  COMPLETION

Notice that member DB2B is quiesced at the time the DISPLAY GROUP DETAIL command is executed on DB2A. If the DB2A member migrates to Db2 13 while DB2B is quiesced, then the DB2B member is no longer be able to start on Db2 11. The reason is that coexistence between Db2 11 and Db2 13 is not supported. DB2B can start on Db2 12 if it was running with Db2 12 code with the fallback SPE (PH37108) applied.

Db2 12 data sharing group not ready for migration to Db2 13

In the following example, the data sharing group is not ready for migration to Db2 13 because of the coexistence with member DB2B, which is an active member that is still on Db2 11.

The SPE Value for the Db2 11 DB2B member is undefined (hexadecimal zeroes), which is the reason that the SPE value appears as a series of dots ('.......’) with the indication that it is not eligible for a migration to Db2 13. This new functionality does not exist on Db2 11 and so the SPE value is not undefined. The same is expected for any members that do not yet have PH50072 applied.

DSN7100I  -DB2A DSN7GCMD                                             
*** BEGIN DISPLAY OF GROUP(DSNCAT  ) CATALOG LEVEL(V12R1M500)        
                  CURRENT FUNCTION LEVEL(V12R1M100)                  
                  HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M100)        
                  HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M100)         
                  PROTOCOL LEVEL(2)                                  
                  GROUP ATTACH NAME(DSNG)                            
---------------------------------------------------------------------
DB2          SUB                     DB2    SYSTEM    IRLM           
MEMBER   ID  SYS  CMDPREF   STATUS   LVL    NAME      SUBSYS PRLM2171
DB2A       1 DB2A -DB2A     ACTIVE   121510 UTEC5     PR21   PRLM21  
DB2B       2 DB2B -DB2B     ACTIVE   111500 UTEC5     QR21   QRLM21  
---------------------------------------------------------------------
MIGRATION READINESS REPORT                                          
--------------------------                                          
DB2       CODE       SPE      MIGRATION                              
MEMBER    LEVEL      APAR     ELIGIBLE                               
--------  ---------  -------  ---                                    
DB2A      V12R1M510  PH37108  YES                             
DB2B      V11R1M500  .......  NO                 
MIGRATION READINESS STATUS: GROUP IS NOT READY FOR DB2 13
REASON: COEXISTENCE PRECLUDES MIGRATION TO NEXT DB2 RELEASE 
---------------------------------------------------------------------
DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG            
---------------------------------------------------------------------
...
*** END DISPLAY OF GROUP(DSNCAT  )                                   
DSN9022I  -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION

Db2 12 subsystem not ready for migration to Db2 13

In the following example, the standalone Db2 subsystem is not ready to for migration to Db2 13 because the highest activated Db2 12 function level is not V12R1M510.


DSN7100I  -DB2A DSN7GCMD                                             
*** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M500)        
                  CURRENT FUNCTION LEVEL(V12R1M100)                  
                  HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M100)        
                  HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M501)         
                  PROTOCOL LEVEL(2)                                  
                  GROUP ATTACH NAME(....)                            
---------------------------------------------------------------------
DB2          SUB                     DB2    SYSTEM    IRLM           
MEMBER   ID  SYS  CMDPREF   STATUS   LVL    NAME      SUBSYS PRLMPR21
-------- --- ---- --------  -------- ------ --------  ----   --------
........   0 DB2A -DB2A     ACTIVE   121510 UTEC6     PR21   PRLMPR21
---------------------------------------------------------------------
MIGRATION READINESS REPORT                                          
---------------------------                                          
DB2       CODE       SPE      MIGRATION                              
MEMBER    LEVEL      APAR     ELIGIBLE                               
--------  ---------  -------  ---                                    
........  V12R1M510  PH37108  YES                             
MIGRATION READINESS STATUS: SUBSYSTEM IS NOT READY FOR DB2 13
REASON: HIGHEST ACTIVATED FUNCTION LEVEL NOT V12R1M510                
---------------------------------------------------------------------
...
*** END DISPLAY OF GROUP(........)                                   
DSN9022I  -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION

Example for DISPLAY GROUP run on a Db2 12 member in coexistence with Db2 13

-DIS GROUP DETAIL
DSN7100I -DB2A DSN7GCMD
*** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V13R1M100)
CURRENT FUNCTION LEVEL(V13R1M100)
HIGHEST ACTIVATED FUNCTION LEVEL(V13R1M100)
HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M510)
PROTOCOL LEVEL(2)
GROUP ATTACH NAME(DSNG)
---------------------------------------------------------------------
DB2 SUB DB2 SYSTEM IRLM
MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS PRLM2171
DB2A 1 DB2A -DB2A ACTIVE 121510 UTEC5 PR21 PRLM21
DB2B 2 DB2B -DB2B ACTIVE 131503 UTEC5 QR21 QRLM21
---------------------------------------------------------------------
MIGRATION READINESS REPORT                                          
--------------------------                                           
DB2       CODE       SPE      MIGRATION                              
MEMBER    LEVEL      APAR     ELIGIBLE                               
--------  ---------  -------  ---                                    
DB2A      V12R1M510  PH37108  YES
DB2B      V13R1M501  .......  N/A
MIGRATION READINESS STATUS: GROUP MIGRATION IN PROGRESS TO DB2 13
REASON: ALL REMAINING MEMBERS ARE READY FOR DB2 13
---------------------------------------------------------------------
...
*** END DISPLAY OF GROUP(DSNCAT )
DSN9022I -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION