By John Lyle and Paul McWilliams.
After you apply the PTF for APAR PH50072 (available since June 2023), you can issue a DISPLAY GROUP command with the DETAIL keyword to quickly get a report about the readiness of your Db2 for z/OS subsystems and data sharing groups for migration to Db2 13.
As we mentioned in our previous post in this blog, before you can migrate your Db2 12 environments to Db2 13, they must meet the following basic requirements (and their implied prerequisites): the highest-activated function level is function level V12R1M510, and the PTF for the fallback SPE (PH37108) is applied on every data sharing member.
Before this APAR, DBAs often have difficulty determining if all Db2 data sharing members have on the required code levels, and the more members that a data sharing group has, the more time-consuming the migration readiness determination process can be. The gathering of this fallback SPE information can take a very long time and be error prone. The dynamic nature of Db2 maintenance can also mean that gathered fallback SPE information can be out of date before the information gathering process even completes. So, customers have often requested functionality to make the Db2 release migration readiness determination a much quicker and more reliable process.
With this new migration readiness capability, a report in the DISPLAY GROUP DETAIL output in the DSN7100I message indicates whether your environment is ready for migration to the next release of Db2.
If your Db2 12 environment ready for migration to Db2 13, you will see a report like the following example output message:
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
---------------------------------------------------------------------
The migration readiness report can also indicate that migration of a data sharing group is already in progress. In the following example, both members indicate the MIGRATION ELIGBLE field shows yes for both members, and the CODE LEVEL field for DB2B shows that it is already running Db2 13, so the MIGRATION READINESS status field shows GROUP MIGRATION TO DB2 13 IN PROGRESS:
-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 PH37108 YES
MIGRATION READINESS STATUS: GROUP MIGRATION TO DB2 13 IN PROGRESS
REASON: ALL MEMBERS ARE READY FOR DB2 13
---------------------------------------------------------------------
However, if your Db2 environment is not ready for migration, the report indicates that, and it also indicates one of the following reasons:
- A next release of Db2 release is currently not available (Db2 13 has been available since May 2022, but the report would flag this reason if you are already in Db2 13, since no next release of Db2 has currently been announced.)
- Coexistence with any data sharing members on an earlier release of Db2 prevents migration to the next Db2 release. Coexistence with Db2 11 prevents migration to Db2 13.
- The highest activated function level is not sufficient. As mentioned above, you must activate function level 510 in Db2 12 before you can migrate to Db2 13.
- The PTF for fallback SPE APAR is not applied on any every data sharing member. In Db2 12, you must apply the PTF for APAR PH37108 on every member before you can migrate to Db2 13.
For example, the following migration readiness report indicates that a Db2 12 subsystem has a sufficient code level (V12R1M510) and the fallback SPE (PH37108) is applied, so the report does indicate YES in the MIGRATION ELLIGIBLE column. However, the catalog level (V12R1M500) and highest activated function level (V12R1M100) are not sufficient, and the function level is reported in the REASON field. As mentioned above, you must activate function level 510 in Db2 12 before you can migrate to Db2 13.
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
---------------------------------------------------------------------
Here’s another example, where the data sharing group is not ready for migration to Db2 13 because member DB2B is still running Db2 11, and such a coexistence situation of course prevents migration to Db2 13:
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
---------------------------------------------------------------------
Notice that the migration readiness report only reports one reason that the group is not ready for migration. So, if you stopped member DB2B in the preceding example, the migration readiness report would now indicate a different reason, namely the insufficient function level.
For more information about and examples of this new capability, see Check readiness for migration to Db2 13.
#Db2forz/OS #db2z13 #Db2Znews