Db2 for z/OS and its ecosystem

 View Only

Get a head-start for migration to Db2 13 by activating function level 510 in Db2 12

By Paul McWilliams posted Wed May 05, 2021 01:55 PM


Updated April 5, 2022: this entry is updated to reflect that IBM has announced Db2 13 for z/OS.

By John Lyle and Paul McWilliams.

You can now activate function level 510 (FL 510) in your Db2 12 for z/OS environment, after you apply the PTF for APAR PH33727. The previous function levels in Db2 12 help you control the introduction and use of new capabilities by Db2 applications. However, FL 510 does not introduce any new capabilities in Db2 12. Instead, it helps you verify that you have completed essential pre-migration tasks as you prepare your Db2 12 environment for migration to the Db2 13.

Although Db2 Development has transitioned to continuous delivery of most new capabilities for Db2 for z/OS in the service stream, some kinds of changes still require a new Db2 release. IBM has not yet announced the name, content, or availability dates of Db2 13.  However,  function level 509 is the last function level to deliver new capabilities in Db2 12, and you can now get a head-start on preparing for migration to Db2 13 by activating FL 510, which is the last function level for Db2 12.

When you activate FL 510, you verify that certain required pre-migration activities for Db2 13 are completed in Db2 12. Specifically, FL 510 verifies and enforces the following conditions for migration in your Db2 12 environment:

  • All Db2 12 function levels are activated. 
  • All catalog updates for Db2 12 are applied, and the Db2 catalog is ready for the CATMAINT job for catalog level VnnR1M100 in the next release.
  • All application packages used within the last 18 months are rebound in an appropriate Db2 release (Db2 11 or later) to ensure that they are supported by the next Db2 release.  

Essentially, activation of FL 510 fails if any of these conditions are not met, and activation of FL 510 will be required before you can migrate to Db2 VNext.

It’s important to note that PH33727  does not include the fallback SPE for migration to the next Db2 release, and FL 510 does not verify that the fallback SPE is installed. The fallback SPE is expected be delivered by a future APAR.

How to activate function level 510

To activate function level 510 in preparation for migration to Db2 13, complete the following steps:

  1. If Db2 12 is still at function level 100, activate function level 500 or 501 first. For more information, see Migration step 29: Activate function level 500 or higher.
  2. Check that Db2 is at a sufficient code level by issuing a DISPLAY GROUP command, as described in Determining the Db2 code level, catalog level, and function level. The DSN7100I message indicates the code level and highest function level that can be activated. If the highest function level that can be activated is lower than V12R1M510, apply the PTF for APAR PH33727 and any other required maintenance, so that all members indicate 121510 for DB2 LVL in the DSN7100 message.

     You can apply any PTF at any function level, and it is best to run Db2 at this code level or higher for a period of time before proceeding with activation of the function level. Db2 cannot run at any lower code level after you activate a function level, so you cannot remove any of the required PTFs after activating a function level.

  3. Rebind any packages that are identified by the DSNTIJPE job. The job uses the following query to identify packages that have been used in the last 18 months and were last bound or rebound in a release before Db2 11, and activation of function level 510 succeeds only if this query returns 0 rows. 
                WHERE LASTUSED >= DATE(DAYS(CURRENT DATE) - 548)    
                    AND RELBOUND NOT IN ('P','Q',’R’) 
                    AND VALID <> ‘N’                       
                    AND OPERATIVE <> ‘N’; 

    Important: If the DISABLE_EDMRTS subsystem parameter setting is YES in your Db2 12 environment, the SYSPACKAGE.LASTUSED column is not reliable. Function level 510 activation might succeed even though automatic rebinds remain likely to occur in Db2 13. To avoid such automatic binds from blocking the migration or requiring a fallback, follow the practices described in Rebind old plans and packages in Db2 11 to avoid disruptive autobinds in Db2 12 as you prepare for migration to the next Db2 release.

  4. Tailor the CATMAINT and function level activation jobs by running the installation CLIST: 
    1. In panel DSNTIPA1, specify INSTALL TYPE ===> ACTIVATE. Then specify the name of the output member from the previous function level activation (or migration) in the INPUT MEMBER field, and specify a new member name in the OUTPUT MEMBER field. 
    2. In panel DSNTIP00, specify TARGET FUNCTON LEVEL ==> V12R1M510. The CLIST uses this value when it tailors the ACTIVATE command in the DSNTIJAF job and the CATMAINT utility control statement in the DSNTIJTC job.
    3. Proceed through the remaining CLIST panels, and wait for the CLIST to tailor the jobs for the activation process. The output data set contains the tailored jobs for the activation process.
  5. Run the DSNTIJIC job to take an image copy of the Db2 catalog and directory.
  6. Run the tailored DSNTIJTC job, or run the CATMAINT utility with LEVEL V12R1M510, to update the catalog to the appropriate catalog level, which is catalog level V12R1M509.  If multiple catalog updates are required, the CATMAINT job processes each update in sequential order. If a later update in the sequence fails, the previous successful updates do not roll back, and the catalog level remains at the highest level reached. If that occurs, you can correct the reason for the failure and resubmit the same CATMAINT job.
  7. Optionally, check that Db2 is ready for function level activation by issuing the following ACTIVATE command with the TEST option: 

    Message DSNU757I indicates the results. For more information, see Testing Db2 function level activation.

  8. Run the tailored DSNTIJAF job, or issue the following ACTIVATE command:

After completing the above procedures your subsystem or group is at FL 510, which is required for a future migration to Db2 13. Stay tuned for future announcements about Db2 13. 

Sign in and subscribe to always get the latest news about Db2 for z/OS from the IBM lab: