Db2 V12 Add Column HIGH_POSS_FUNCTION_LVL To SYSIBM.SYSLEVELUPDATES

Hi,

I want to withdraw my request.

Thanks,

Stephen

Hi Stephen,

The Highest Possible Function Level is just that: the highest function level that can be activated based on all of the currently active members in data sharing. The HPFL can change if a new member starts up or another member comes down. Maybe an example would help illustrate this concept. Lets say there are two members up in a data sharing group at FL 500. They both have on a 501 level of code and all the prereqs done. So...in this case their HPFL would be 501. But lets say another member comes up and it's code level is 500. So the HPFL in this case becomes 500 because one of the active members doesn't yet have the 501 code on. So the HPFL value can be fluid as the members come up and down. This was what I meant when I said we could add the HPFL value to the SYSLEVELUPDATES catalog table....but that the value could change (up or down) right after we inserted the value.

Hope this helps! Let us know if you'd like to further discuss.

John

I need some clarification please. In message DSN7100I, what is the definition of HIGHEST POSSIBLE FUNCTION LEVEL

DSN7100I -DB2L DSN7GCMD
*** BEGIN DISPLAY OF GROUP(DB2GR0W ) CATALOG LEVEL(V12R1M500)
CURRENT FUNCTION LEVEL(V12R1M100)
HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M100)
HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M501)
PROTOCOL LEVEL(2)
GROUP ATTACH NAME(GR0W)

Hello Stephen, Db2 for z/OS development has reviewed this idea and would like to share the following with you: Adding this function would not be difficult. But that HIGHEST_POSSIBLE_FUNCTION _LEVEL value is determined based on the members that are active in a data sharing group at the time SYSLEVELUPDATES is updated. So we might put a particular value in there during a SYSLEVELUPDATES update....and in 5 minutes another Db2 starts up that would cause HIGHEST_POSSIBLE_FUNCTION_LEVEL to change. So this new column value might not match the current value at a later point in time.