Determining the Db2 code level, catalog level, and function level
Before you can activate a Db2 function level, you must ensure that the Db2 subsystem or data sharing group is at the appropriate code level and catalog level.
Procedure
To determine the code level, catalog level, and
function level of a Db2 subsystem or data
sharing group:
Examples
The following examples show output from DISPLAY GROUP commands in Db2 12:
-DB2A DISPLAY GROUP DETAIL- Example: Data sharing group with coexisting Db2 12 and Db2 11 members
-
In the following example, two members are migrated to Db2 12 and ready for the activation of new function in Db2 12. However, the code level of member DB2B indicates that it is not migrated to Db2 12, which means the group is not ready for activation of function level 500. The DB2 LVL value is 111500, which indicates the code level of Db2 11 in new-function mode.
Also, the migration readiness report shows that the Db2 data sharing group is not ready for migration to Db2 13 due to coexistence with Db2 11.
-DISPLAY GROUP DETAIL 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 IRLMPROC -------- --- ---- -------- -------- ------ -------- ---- -------- DB2A 1 DB2A -DB2A ACTIVE 121500 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 111500 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 121500 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V12R1M500 ....... NO DB2B V11R1M500 ....... NO DB2B V12R1M500 ....... NO --------------------------------------------------------------------- MIGRATION READINESS STATUS: IS NOT READY FOR DB2 13 REASON: COEXISTENCE PRECLUDES MIGRATION TO THE NEXT DB2 RELEASE -------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG -------------------------------------------------------------------- --------------------------------------------------------------------- SCA STRUCTURE SIZE: 12288 KB, STATUS= AC, SCA IN USE: 8 % LOCK1 STRUCTURE SIZE: 12288 KB NUMBER LOCK ENTRIES: 1048576 NUMBER LIST ENTRIES: 23073, LIST ENTRIES IN USE: 7 SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(DSNCAT ) DSN9022I -DB2C DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - Example: Data sharing group with all active members migrated to Db2 12 code, before the activation of function level 500
-
The following DISPLAY GROUP output illustrates a data sharing group with all active members migrated to Db2 12 and ready for the activation of function level 500.
Also, the migration readiness report shows that the Db2 data sharing group is not ready for migration to Db2 13 due to the highest activated function level and not all members have the fallback SPE APAR.
DSN7100I -DB2B DSN7GCMD *** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V12R1M500) CURRENT FUNCTION LEVEL(V12R1M100) HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M100) HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M500) PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNG) -------------------------------------------------------------------- DB2 SUB DB2 SYSTEM IRLM MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC -------- --- ---- -------- -------- ------ -------- ---- -------- DB2A 1 DB2A -DB2A ACTIVE 121500 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 121510 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 121500 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V12R1M510 ....... NO DB2B V12R1M510 PH37108 NO DB2C V12R1M510 ....... NO --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP IS NOT READY FOR DB2 NEXT REASON: HIGHEST ACTIVATED FUNCTION LEVEL NOT V12R1M510 -------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG -------------------------------------------------------------------- SCA STRUCTURE SIZE: 12288 KB, STATUS= AC, SCA IN USE: 9 % LOCK1 STRUCTURE SIZE: 12288 KB NUMBER LOCK ENTRIES: 1048576 NUMBER LIST ENTRIES: 23073, LIST ENTRIES IN USE: 17 SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(DSNCAT ) DSN9022I -DB2B DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - Example: Data sharing group with all active members migrated to Db2 12 after the activation of function level 500
-
The following DISPLAY GROUP output illustrates a data sharing group with function level 500 activated.
Also, the migration readiness report shows that the Db2 data sharing group is not ready for migration to Db2 13 due to the highest activated function level and the missing SPE APAR.
DSN7100I -DB2A DSN7GCMD *** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V12R1M500) CURRENT FUNCTION LEVEL(V12R1M500) HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M500) HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M500) PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNG) -------------------------------------------------------------------- DB2 SUB DB2 SYSTEM IRLM MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC -------- --- ---- -------- -------- ------ -------- ---- -------- DB2A 1 DB2A -DB2A ACTIVE 121500 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 121500 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 121500 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V12R1M500 ....... NO DB2B V12R1M500 ....... NO DB2B V12R1M500 ....... NO --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP IS NOT READY FOR DB2 13 REASON: HIGHEST ACTIVATED FUNCTION LEVEL NOT V12R1M510 -------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG -------------------------------------------------------------------- --------------------------------------------------------------------- SCA STRUCTURE SIZE: 12288 KB, STATUS= AC, SCA IN USE: 9 % LOCK1 STRUCTURE SIZE: 12288 KB NUMBER LOCK ENTRIES: 1048576 NUMBER LIST ENTRIES: 23073, LIST ENTRIES IN USE: 0 SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(DSNCAT ) DSN9022I -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - Example: Db2 12 data sharing group ready for migration to Db2 13
- The example single-member Db2 12 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 -------------------------------------------------------------------- MIGRATION READINESS REPORT --------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V12R1M510 PH37108 YES --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP IS READY FOR MIGRATION TO DB2 13 -------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG -------------------------------------------------------------------- --------------------------------------------------------------------- SCA STRUCTURE SIZE: 12288 KB, STATUS= AC, SCA IN USE: 5 % LOCK1 STRUCTURE SIZE: 12288 KB NUMBER LOCK ENTRIES: 1048576 NUMBER LIST ENTRIES: 23151, LIST ENTRIES IN USE: 0 SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(DSNCAT ) -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL DSN9022I COMPLETION - Example: Db2 12 data sharing group not ready for migration to Db2 13
- The example Db2 12 data sharing group not ready for migration to Db2 13 because of the coexistence with Db2 11.
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 --------------------------------------------------------------------- --------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG --------------------------------------------------------------------- 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 THE NEXT DB2 RELEASE --------------------------------------------------------------------- SCA STRUCTURE SIZE: 12288 KB, STATUS= AC, SCA IN USE: 5 % LOCK1 STRUCTURE SIZE: 12288 KB NUMBER LOCK ENTRIES: 1048576 NUMBER LIST ENTRIES: 23151, LIST ENTRIES IN USE: 5 SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(DSNCAT ) DSN9022I -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - Example: standalone Db2 12 subsystem not ready for migration to Db2 13
-
The example Db2 subsystem has a sufficient code level and the fallback SPE APAR for migration to Db2 13. However, it is not ready for migration to Db2 13 because of its highest activated function level.
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 --------------------------------------------------------------------- --------------------------------------------------------------------- DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH DSNG --------------------------------------------------------------------- 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 --------------------------------------------------------------------- SPT01 INLINE LENGTH: 32138 *** END DISPLAY OF GROUP(........) DSN9022I -DB2A DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - FL 502 Example: Data sharing group with an encryption key label assigned to all members
- If the subsystem parameter ENCRYPTION_KEYLABEL is specified for the members of a data sharing group, issue the following command to display the key label:
-DISPLAY GROUP DETAILThe output is similar to the following:
DSN7100I -DB2C DSN7GCMD *** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V12R1M502) CURRENT FUNCTION LEVEL(V12R1M502) HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M502) HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M502) PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNG) ENCRYPTION KEY LABEL (SYSTEM.KEY01)
What to do next
- If necessary, apply maintenance to the Db2 subsystem or data sharing group members for the code level required by the target function level, and repeat this task.
- Activate the target function level as described in Activating Db2 12 function levels.