Hi Bill,
Simplest is to issue CATMAINT for your desired function level (FL). For example, if you specify V12R1M508, CATMAINT will make all the catalog updates for FL 502, FL 503, FL 505 and FL 507. (that's where the catalog changes are up to that point). You might as well start by specifying V12R1M509 and have all Db2 12 catalog updates done; they are very small changes.
Then, you pick where you want your system to be. If there is a reason to 'stop' at FL 505, you can -ACTIVATE FUNCTION LEVEL V12R1M505. Then you will see various system related changes that are not application compatibility-dependent. For example, REBIND phase-in will be active as soon as you activate FL 505, as will the ability to set encryption keys for Db2 system objects using DSNZPARM (came in FL 502) and others.
New SQL behaviors will not automatically be available. Each package that wants/needs to use new SQL behavior would have to be bound with APPLCOMPAT and the appropriate V12R1M5xx value.
Is there a reason to 'stop' at FL 505 and not activate FL 508 right away after the CATMAINT I mention above? I guess that depends on which, and how many, system features (function level-dependent but not APPLCOMPAT-dependent) you want to experience at once.
I do know some shops are planning to go straight from FL 500 (or FL501) to FL 510 after issuing CATMAINT UPDATE LEVEL V12R1M510 (that specification works, even though there are only catalog changes for FL 502, 503, 505, 507 and 509).
I hope this helps.
------------------------------
Mark Rader IBM
Standard disclaimer: opinions are my own.
------------------------------
Original Message:
Sent: Apr 13, 2022 09:49 AM
From: william giannelli
Subject: migrating to next function levels
We are currently at Function Level 500.
What steps, catmaints etc, would be needed to get to FL 505 then FL 508?
thanks
Bill
------------------------------
williamgiannelliMe
------------------------------