System requirements for IBM® Content Manager OnDemand beginning with version 10.5.0.11

Ref:  https://www.ibm.com/support/pages/node/7249695

Abstract
This document describes the system requirements for IBM® Content Manager OnDemand beginning with version 10.5.0.11, which is planned for 3Q2026.

Content
Note:  When a product version is specified as 'or later', it refers to later fix packs of the version that is specified, as well as any later versions (and fix packs) that are not specified. In addition, if a product is not listed, that does not mean that the product is no longer supported. Rather, it means that the prerequisite version of the product will not be changed.
 

IBM z/OS
     3.1 or later

AIX
     7.2 TL5 or later, and 7.3 TL3 or later

Linux (Intel and System z)
     RedHat 8 U10 or later, RH 9 U6 or later, and RH 10 or later
     SUSE 15 SP7 or later, and SUSE 16 or later

Microsoft Windows Server
     Windows Server 2025 or later

Microsoft Windows (for Content Manager OnDemand client programs that run on a workstation)
     Windows 11 or later

IBM Db2 for z/OS
     13 or later

IBM Db2 for Linux, UNIX and Windows
     11.5 or later

Microsoft SQL Server
     2022 or later

IBM Storage Protect
     8.1.26 or later

IBM WebSphere Liberty
     25.0.0.9 or later
 

In addition, the following product components are not planned to ship with Content Manager OnDemand version 10.5.0.11 and later. Note that all of these components have supported 64-bit equivalents that will continue to be provided.
               - OnDemand Windows Client (32-bit)
               - OnDemand Windows Administrator (32-bit)
               - OnDemand Windows Monitor (32-bit)
               - Content Manager OnDemand Web Enablement Kit (ODWEK) Java APIs (32-bit)
               - ARSACIF (32-bit; Multiplatforms only)

This thread is current.

No reported z/OS 3.1 issues found by CMOD.

Note:  CMOD 10.5.0.11 will require z/OS 3.1 or later

CMOD has surfaced the follow Db2 defect:


PH68886: Db2 FOR z/OS ODBC TRACED THE BIGINT VALUE INCORRECTLY

Error description
When BIGINT is in use, the Db2 for z/OS ODBC application trace shows an incorrect value.

At the moment there's only one supported level of CMOD and it's quite mature.

When CMOD V.Next comes out I suspect activity will pick up as people start to migrate to the new version.

Ed Arnold

At a minimum I'd like to see this website continue.

I like the ability to publish items that I think are of interest to the CMOD community.

Ed Arnold

Broadly speaking, I advise *against* using AI/LLM output for anything important.  I've had a few occasions where people have written to me, letting me know that machine generated summaries (of information clearly found on the Forums or Wiki) were not accurate.  I informed them to use the source itself and not summaries, because I can't stop LLMs from generating garbage output.

I will *also* say that many, many folks have moved on -- I haven't counted the full total yet, but I'm going to estimate I have nearly 100 eMail bounces waiting for me to deal with.

EDIT:  About 10% of eMails were bounces, or recipients asked to be removed from the Forums, we've got a little over 800 users, down from a high of around 1100.

-JD.

I have come to the site looking for similar experiences I have, but it is not frequent. I have not played with chatgpt or copiot to see how accurate those are in assessing and resolving questions.

I know every sort of conference and travel suffered a lot with budget constraints. I miss the days of what ODUG started out as but nothing good lasts forever. I know the user group, if it continues, will not be what it once was. I'm not even sure how many of those I met thru the user group are still with ODUG. I would continue to use the forum if it stays around.

There are little to no recourses available when trying to learn CMOD and am very thankful that this forum existed to answer my questions. For that reason, it would be great if it would continue. Of course, it needs to be monitored by those capable of answering questions.

So, it's time to have the discussion...  It's approaching 5 years since our last technical conference...  Five since the last Board of Directors meeting, Three since ODUG ceased to exist according to its Bylaws...  Two years since the old forums went offline suddenly and I managed to recover them from a routine database backup...

ODUG has had a rich history spanning 30+ years... but it's future is currently a blank canvas.  So, with the new year, I ask the question to the community...

What do the Users want to happen to their User's Group?  I'm open to any and all input and feedback, good, bad, and/or ugly.

-JD.

Hey everyone...

While trying to move the Forums to a new cloud provider over the holidays (with a better reputation for mail delivery) and doing some upgrades at the same time, I made a tremendous mistake, and deleted the *real* ODUG Forums, instead of the test machine I *thought* I was working on.  The real catastrophe came when I realized that the backups I was using to do the migration only existed on the real server, and the only offsite copies were several months old.

Unfortunately, we've lost about 5 months of data from the Forums, including posts, replies, and new user memberships...  but also small fixes and improvements I'd made to the server -- tightening firewall rules, database performance tweaks, among others.

To ensure this never happens again, I took a few parts from my old office, and built a 30TB backup server with 3x redundant storage -- 5 disks of ZFS RAIDz3.  Local database backups happen nightly.  Whole-server file-level backups are initiated from the new backup server, which is currently living on my desk.  Offsite copies to a 'tough' USB stick will be rotated out at least monthly.

I've always taken the reliability of ODUG very seriously, and I'm sorry for this lapse that's resulted in data loss.

Having said all that...  ODUG has been extraordinarily quiet lately, and the actual volume of new users / posts / replies has been very low.  That's something I've been meaning to work on as well.  I'll start another thread about that shortly.  :)

-JD.