DSN7100I src csect-name display-group-output
Explanation
This message displays output from the DISPLAY GROUP command.
- src
- The command prefix for the DISPLAY GROUP command.
- csect-name
- The name of the control section that issued the message.
- display-group-output
- The DISPLAY GROUP command output formatted on multiple subsequent lines, as described in the following sections:
Output heading
The name of the control section is followed by heading information for the output:
*** BEGIN DISPLAY OF GROUP(text) CATALOG LEVEL(num)
CURRENT FUNCTION LEVEL(text)
HIGHEST ACTIVATED FUNCTION LEVEL (text)
HIGHEST POSSIBLE FUNCTION LEVEL (text)
PROTOCOL LEVEL(n)
GROUP ATTACH NAME(text)
------------------------------------------------------------------
- GROUP (text)
- The name of the data-sharing group.
- CATALOG LEVEL (text)
- The catalog level
of the data sharing group or subsystem. The format is
VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level. - CURRENT FUNCTION LEVEL (text)
- The current function level of the data sharing group or subsystem.The format is
VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level. For example,V13R1M505identifies function level 505. For a list of all available function levels in Db2 13, see Db2 13 function levels. - HIGHEST ACTIVATED FUNCTION LEVEL (text)
- The highest function level that was ever activated for the data sharing group or subsystem. The format is
VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level. - HIGHEST POSSIBLE FUNCTION LEVEL (text)
- The highest function level that can be specified in an ACTIVATE command based on the catalog
level of the group and the code levels of the group members. The format is
VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level.For the code levels of each member, see the DB2 LVL column value in data sharing member information section.
- PROTOCOL LEVEL (num)
- A single numeric character that indicates the current locking protocol that is used in the data-sharing group.
- GROUP ATTACH NAME (text)
- The group attach name for the data-sharing group.
Data-sharing members
The output heading is followed by a section that contains information about the data-sharing members:
Db2 Db2 SYSTEM IRLM
MEMBER ID SUBSYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
-------- --- ---- -------- -------- ----- -------- ---- --------
text num text text text num text text text- DB2 MEMBER text
- The name of the Db2 data-sharing member.
- ID num
- The internally assigned ID for each data-sharing member.
- SUBSYS text
- The subsystem name of the data-sharing member.
- CMDPREF text
- The command prefix of the data-sharing member.
- STATUS text
- The state of the data-sharing member. Expected values are:
- ACTIVE
- The member is up and running.
- AI
- The member is active with more conditions. Indoubt or postponed abort units of recovery are unresolved, so retained locks are held.
- DEACT
- The member is deactivated.
- FAILED
- The member terminated abnormally.
- QUIESCED
- The member is down normally.
- QI
- The member is down with indoubt units of recovery.
- QR
- The member is down with resynchronization responsibility.
- QC
- The member is down with group buffer pool castout responsibility.
- QCR, QIC, QIR, or QICR
- Possible combinations of the quiesced states (QI, QR, and QC):
- QCR is the equivalent of QC and QR.
- QIC is the equivalent of QI and QC.
- QIR is the equivalent of QI and QR.
- QICR is the equivalent of QC, QI, and QR.
- DB2 LVL num
- A 6-character string that identifies the code level of the Db2 subsystem or member. The format is vvrmmm, where vv is the version, r is the release, and mm is the modification level. Each member of the group can have a different code level but it is always at or higher than the function level of the data sharing group.
- SYSTEM NAME text
- The name of the z/OS® system on which the data-sharing member runs.
- IRLM SUBSYS text
- The accompanied IRLM's subsystem name for this Db2 member.
- IRLMPROC text
- The accompanied IRLM's startup procedure name.
Migration readiness
If the DISPLAY GROUP Command is issued with the DETAIL option, migration readiness information is provided:
MIGRATION READINESS REPORT
--------------------------
DB2 CODE SPE MIGRATION
MEMBER LEVEL APAR ELIGIBLE
-------- --------- ------- ---
text text text text
MIGRATION READINESS STATUS: text
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.
Subgroup attachment
If the DISPLAY GROUP command is issued with the DETAIL option, subgroup attachment information is provided:
DISPLAY SUBGROUP ATTACH INFORMATION FOR GROUP ATTACH text
------------------------------------------------------------------
MEMBERS OF SUBGROUP ATTACH text
text text text text text text text text - GROUP ATTACH text
- The name of the group attachment group for the data-sharing member that is printing the output.
- MEMBERS OF SUBGROUP ATTACH text
- The name of the subgroup attachment group, followed by one or more lines that list the members of the subgroup. Each line contains up to eight members.
If more than 105 subgroup attachment groups are found, the following message is displayed:
MAXIMUM NUMBER OF SUBGROUP ATTACH GROUPS DISPLAYEDIn this case, no additional groups are reported.
Shared communications area
The output provides the following information about the shared communications area (SCA):
SCA STRUCTURE SIZE: num KB, STATUS = tx, SCA IN USE: num %
- STRUCTURE SIZE num
- The size of the shared communications area (SCA), measured in kilobytes (KB).
- STATUS tx
- A 2-character indicator of the status of the shared communications area. Possible values are:
- AC
- The SCA is active.
- CC
- The SCA rebuild connect function completed.
- CS
- The SCA rebuild connect function started.
- DS
- The SCA loss of connectivity, delayed action started.
- DC
- The SCA loss of connectivity, delayed action completed.
- EC
- The SCA rebuild stop complete function completed.
- ES
- The SCA rebuild stop complete function started.
- IN
- The SCA is in initialization phase.
- LC
- The SCA rebuild cleanup function completed.
- LS
- The SCA rebuild cleanup function started.
- OC
- The SCA rebuild connect complete function completed.
- OS
- The SCA rebuild connect complete function started.
- PC
- The SCA rebuild process complete function completed.
- PS
- The SCA rebuild process complete function started.
- QC
- The SCA rebuild quiesce function completed.
- QS
- The SCA rebuild quiesce function started.
- RC
- The SCA rebuild resource manager invocation completed.
- RS
- The SCA rebuild resource manager invocation started.
- SC
- The SCA rebuild stop function completed.
- SS
- The SCA rebuild stop function started.
- TE
- The SCA is in termination phase.
- UC
- The SCA rebuild resource manager invocation completed.
- US
- The SCA rebuild resource manager invocation started.
- VC
- The SCA volatility change function completed.
- VS
- The SCA volatility change function started.
- SCA IN USE num
- Either
the percentage of the number of entries that are in use in the SCA or the percentage of the number
of elements that are in use in the SCA, whichever is larger. If the SCA structure is very large or
if only a small number of SCA entries are in use, the percentage that is in use might be less than
1%. In this case, the percentage is indicated
as:
SCA IN USE: < num %
LOCK1 structure
The output provides the following information about the LOCK1 structure:
LOCK1 STRUCTURE SIZE: num KB
NUMBER LOCK ENTRIES: num
NUMBER LIST ENTRIES: num, LIST ENTRIES IN USE: < num- STRUCTURE SIZE num
- The size of the LOCK1 coupling facility structure, measured in kilobytes (KB).
- LOCK ENTRIES num
- The maximum number of lock table entries in the LOCK1 coupling facility structure.
- LIST ENTRIES num
- The maximum number of modify lock list entries in the LOCK1 coupling facility structure.
- LIST ENTRIES IN USE num
- The number of modify lock list entries in the LOCK1 coupling facility structure that are currently in use. These entries are sometimes referred to as record data.
SPT01 table space information
The output contains information about the inline length of BLOB column SPTSEC_DATA in the SPT01 table space.
If the SPT01 table space is available, the following output is displayed:
SPT01 INLINE LENGTH: num- SPT01 INLINE LENGTH num
- The current inline length of the SPTSEC_DATA column.
If the SPT01 table space is unavailable when DISPLAY GROUP is issued on a subsystem or data sharing member that is in conversion mode, the following output is displayed:
SPT01 INLINE LENGTH INFORMATION NOT AVAILABLE
REASON reason-code
TYPE resource-type
NAME reason-nameIf the SPT01 table space is unavailable when DISPLAY GROUP is issued on a subsystem or data sharing member that is in enabling-new-function mode, the following messages are displayed:
TABLE SPACE NEW FUNCTION ENABLEMENT INFORMATION NOT AVAILABLE
REASON reason-code
TYPE resource-type
NAME reason-name
SPT01 INLINE LENGTH INFORMATION NOT AVAILABLE
REASON reason-code
TYPE resource-type
NAME reason-name- REASON reason-code
- The Db2 reason code value that indicates the reason for the failure. For explanations of reason codes, see Db2 reason codes.
- TYPE resource-type
- The type of resource. For an explanation of resource-type and resource-name values, see Resource types.
- NAME resource-name
- The resource name. For an explanation of resource-type and resource-name values, see Resource types.
End of output
The output normally ends with the following message:
*** END DISPLAY OF GROUP(text)- GROUP
- The name of the group that the preceding lines of the output refer to.
If the output exceeds the maximum length, the following message marks the end of the output instead:
DISPLAY TERMINATED DUE TO INSUFFICIENT MESSAGE SPACE.System action
Processing continues.
User response
No action is required.
Examples
The following examples show output from DISPLAY GROUP commands in Db2 13:
-DB2A DISPLAY GROUP DETAIL- Example: Data sharing group with coexisting Db2 13 and Db2 12 members
-
In the following example, two members are migrated to Db2 13 and ready for the activation of new function in Db2 13. However, the code level of member DB2B indicates that it is not migrated to Db2 13, which means the group is not ready for activation of function level 500.
The DB2 LVL value for DB2B is 121510, which indicates that all Db2 12 function levels are activated.-DISPLAY 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(V13R1M100) PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNG) -------------------------------------------------------------------- DB2 SUB DB2 SYSTEM IRLM MEMBER ID SYS CMDPREF ELIGIBLE LVL NAME SUBSYS IRLMPROC -------- --- ---- -------- -------- ------ -------- ---- -------- DB2A 1 DB2A -DB2A ACTIVE 131501 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 121510 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 131501 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V13R1M501 ....... N/A DB2B V12R1M501 PH37108 YES DB2B V12R1M501 PH37108 YES --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP MIGRATION IN PROGRESS TO DB2 13 REASON: ALL REMAINING MEMBERS ARE READY FOR DB2 13 -------------------------------------------------------------------- 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: Running a DISPLAY GROUP command run on a Db2 12 member during coexistence with Db2 13
-
The following example output shows the result of running the following command on a Db2 12 member in the data sharing group from the previous example:
-DB2B DISPLAY GROUP DETAILBecause the command was run on a Db2 12 member, the highest possible function level indicates V12R1M510, which is the highest level that you can activate by issuing an ACTIVATE command. However, the current function level indicates V13R1M100 because at least one member has been migrated to Db2 13.
-DISPLAY GROUP DETAIL DSN7100I -DB2B 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 IRLMPROC -------- --- ---- -------- -------- ------ -------- ---- -------- DB2A 1 DB2A -DB2A ACTIVE 131501 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 121510 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 131501 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V13R1M501 ....... N/A DB2B 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 -------------------------------------------------------------------- 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 -DB2B DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION - Example: Data sharing group with all active members migrated to Db2 13 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 13 and ready for the activation of function level 500.
DSN7100I -DB2B DSN7GCMD *** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V13R1M100) CURRENT FUNCTION LEVEL(V13R1M100) HIGHEST ACTIVATED FUNCTION LEVEL(V13R1M100) HIGHEST POSSIBLE FUNCTION LEVEL(V13R1M500) 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 131501 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 131501 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 131501 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V13R1M501 ....... NO DB2B V13R1M501 ....... NO DB2C V13R1M501 ....... NO --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP IS NOT READY FOR DB2 NEXT REASON: NO NEXT RELEASE OF DB2 IS CURRENTLY AVAILABLE -------------------------------------------------------------------- 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 13 after the activation of function level 500
-
The following DISPLAY GROUP output illustrates a data sharing group with function level 500 activated.
DSN7100I -DB2A DSN7GCMD *** BEGIN DISPLAY OF GROUP(DSNCAT ) CATALOG LEVEL(V13R1M500) CURRENT FUNCTION LEVEL(V13R1M500) HIGHEST ACTIVATED FUNCTION LEVEL(V13R1M500) HIGHEST POSSIBLE FUNCTION LEVEL(V13R1M500) 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 131501 MVSA DJ2A DB2AIRLM DB2B 2 DB2B -DB2B ACTIVE 131501 MVSB DJ2B DB2BIRLM DB2C 3 DB2C -DB2C ACTIVE 131501 MVSC DJ2C DB2CIRLM -------------------------------------------------------------------- MIGRATION READINESS REPORT -------------------------- DB2 CODE SPE MIGRATION MEMBER LEVEL APAR ELIGIBLE -------- --------- ------- --- DB2A V13R1M501 ....... NO DB2B V13R1M501 ....... NO DB2B V13R1M501 ....... NO --------------------------------------------------------------------- MIGRATION READINESS STATUS: GROUP IS NOT READY FOR DB2 NEXT REASON: NO NEXT RELEASE OF DB2 IS CURRENTLY AVAILABLE -------------------------------------------------------------------- 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: 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(V13R1M500) CURRENT FUNCTION LEVEL(V13R1M500) HIGHEST ACTIVATED FUNCTION LEVEL(V13R1M500) HIGHEST POSSIBLE FUNCTION LEVEL(V13R1M500) PROTOCOL LEVEL(2) GROUP ATTACH NAME(DSNG) ENCRYPTION KEY LABEL (SYSTEM.KEY01)
Examples for checking migration readiness
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 COMPLETIONNotice 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