Merge branch 'stable' into monthlyupdate

Author: prveenkumr

src/mas/devops/data/catalogs/v9-260827-amd64.yaml

@@ -219,8 +219,9 @@ editorial:
     - IBM Maximo AI Service [v9.1.18](https://www.ibm.com/support/pages/node/7284133) and [v9.2.2](https://www.ibm.com/support/pages/node/7284134)
     - IBM Truststore Manager v1.7
     - IBM Suite License Service v3.13
-    - CP4D: 5.3.1
-    - OCP: 4.22
-    - Mongo: 8.0.29
+    - 'CP4D: 5.3.1'
+    - 'OCP: 4.22'
+    - 'Mongo: 8.0.29'
+    - 'db2u: 120105.0.1'
   known_issues:
     - title: During upgrades from MAS Manage 9.0.x to 9.1.x using the online-offline upgrade process, some environments may fail during the offline phase because the PLGCOUNT table does not contain the expected MAXPRODUCTID column. This issue is upgrade-blocking and was identified late in the release validation cycle. Due to the August 27, 2026 GA release timeline, MAS Manage 9.1.x was released with this documented as a known limitation. A corrective fix has been developed, and an Interim Fix (IFIX) release is being prepared. Customers encountering this issue should contact IBM Support and reference the [technote](https://www.ibm.com/support/pages/node/7285399)

src/mas/devops/data/catalogs/v9-260827-ppc64le.yaml

@@ -78,8 +78,9 @@ editorial:
     - IBM Maximo Manage [v9.0.29](https://www.ibm.com/support/pages/node/7284559),[v9.1.21](https://www.ibm.com/support/pages/node/7284558) and [v9.2.2](https://www.ibm.com/support/pages/node/7284557)
     - IBM Truststore Manager v1.7
     - IBM Suite License Service v3.13
-    - CP4D: 5.3.1
-    - OCP: 4.22
-    - Mongo: 8.0.29
+    - 'CP4D: 5.3.1'
+    - 'OCP: 4.22'
+    - 'Mongo: 8.0.29'
+    - 'db2u: 120105.0.1'
   known_issues:
     - title: During upgrades from MAS Manage 9.0.x to 9.1.x using the online-offline upgrade process, some environments may fail during the offline phase because the PLGCOUNT table does not contain the expected MAXPRODUCTID column. This issue is upgrade-blocking and was identified late in the release validation cycle. Due to the August 27, 2026 GA release timeline, MAS Manage 9.1.x was released with this documented as a known limitation. A corrective fix has been developed, and an Interim Fix (IFIX) release is being prepared. Customers encountering this issue should contact IBM Support and reference the technote [technote](https://www.ibm.com/support/pages/node/7285399)

src/mas/devops/data/catalogs/v9-260827-s390x.yaml

@@ -78,9 +78,10 @@ editorial:
     - IBM Maximo Manage [v9.0.29](https://www.ibm.com/support/pages/node/7284559),[v9.1.21](https://www.ibm.com/support/pages/node/7284558) and [v9.2.2](https://www.ibm.com/support/pages/node/7284557)
     - IBM Truststore Manager v1.7
     - IBM Suite License Service v3.13
-    - CP4D: 5.3.1
-    - OCP: 4.22
-    - Mongo: 8.0.29
+    - 'CP4D: 5.3.1'
+    - 'OCP: 4.22'
+    - 'Mongo: 8.0.29'
+    - 'db2u: 120105.0.1'
   known_issues:
     - title: During upgrades from MAS Manage 9.0.x to 9.1.x using the online-offline upgrade process, some environments may fail during the offline phase because the PLGCOUNT table does not contain the expected MAXPRODUCTID column. This issue is upgrade-blocking and was identified late in the release validation cycle. Due to the August 27, 2026 GA release timeline, MAS Manage 9.1.x was released with this documented as a known limitation. A corrective fix has been developed, and an Interim Fix (IFIX) release is being prepared. Customers encountering this issue should contact IBM Support and reference the technote [technote](https://www.ibm.com/support/pages/node/7285399)