I posted a library entry with the same title. The link is: https://community.ibm.com/community/user/viewdocument/help-i-need-to-get-to-db2-13?CommunityKey=621c2a2a-01f9-4b57-992f-36ed7432e3bb&tab=librarydocuments

Here's a mostly AI generated summary of what can be found in this article.

Overview: This document outlines a quick-start, seven-step plan for initiating the transition to Db2 13 for z/OS, emphasizing preparation and planning; and focusing on items that can be done whether or not Db2 13 is in house. ​

Setting the Stage

• Db2 13 enhances migration processes, while maintaining key elements like fallback and coexistence with previous versions. ​
• Fallback enables return to previous releases without data loss. ​
• Coexistence allows running different Db2 versions in the same cluster. ​
• Db2 13 supports online migration, minimizing business disruption. ​

What Can I Do Right Now?

• Seven key steps to initiate Db2 13 migration: project planning, requirements, education, assessment, mediation, preparation, and third-party checks. ​

Project Planning

·       Form a project team and designate a project leader. ​

·       Document past migration experiences to improve future efforts.

·       Ensure migration aligns with support timelines, as Db2 12 support ends December 31, 2025. ​

Requirements

·       Verify that Db2 12 subsystems are at the required version (V12R1M510) for migration. ​

·       Check for necessary patches and readiness reports.

Education

·       Utilize resources like IBM Redbooks and online documentation to gain knowledge about Db2 13 features and migration processes. ​

·       Understand the functional inventory of Db2 13 and its continuous delivery updates. ​

Assessment

·       Identify incompatible, deprecated, or removed items in Db2 13. ​

·       Review subsystem parameters and use tools to assess potential issues before migration.

Mediation

·       Manage plans and packages to ensure compatibility with Db2 13. ​

·       Use features like PLANMGMT(EXTENDED) and APPLCOMPAT to mitigate access path changes during migration.

Preparation

·       Conduct integrity checks on Db2 12 systems before migration. ​

·       Utilize provided jobs for catalog consistency and validation.

Third Parties

·       Ensure third-party tools are compatible with Db2 13 and its function levels. ​

·       Document any surprises or issues encountered during migration for future reference. ​

In Summary

A well-structured migration plan can ease the transition to Db2 13, ensuring minimal disruption and leveraging new features effectively. ​