I find ODUG to be a helpful resource. There is information here that you can't find elsewhere/AI. I don't post, but I come here looking for information and would certainly like to see it continue. Thanks.

I am in a similar position as others in this thread. While I do not contribute much myself, I have been able to solve many issues or at least get some relevant details about some questions/concerns thanks to this forum. AI searches on OnDemand topics have been really horrible for me as well.

I have really appreciated this forum and would love to see it continue.

I would like to see this website continue. Although, I do not post much on the site, I have found a lot of answers to issues I have faced over the years on the site.

John Kyle

The end result determined that when the number of documents in a batch was increased (up to 12000) the RESTYPE=ALL created very large resource files. Per IBM when resource files approach 500MB, there's increased search overhead to search a large resource file by arspdump to rebuild the documents when retrieved. We changed RESTYPE=NONE and haven't seen this issue since but that increases our storage footprint for the documents.

I did get a few "Hey, I can't reach ODUG" eMails and texts over the past two weeks...  :D

-JD.

It's decent reference source when one can't get direct answers from IBM or when IBM says sorry that's a Lab Services issue/problem/function. Like last week when I needed to interrogate a CMOD appgroup for documents greater than 5MB for a project. I eventually figured out how to do it.

I thought I was losing my mind last week when I went to reference odug for something CMOD and couldn't get it.  I'm glad you're back.

This forum is still a very important source of information. I've tried asking AI about IBM CMOD or other IBM products,
but the answers are often just guesses because the AI doesn't know the exact product details (and it also takes time to remove sensitive information).

I understand that running seminars requires a lot of resources, so focusing on Q&A discussions in the forum makes sense.

I also agree that when the next CMOD version is released, more people will likely join this community.

One issue I've noticed is that the website sometimes loads very slowly. Not sure if this is only happening in my region or if others see the same thing.

Cheers,
TW.

Statement of direction
IBM intends to provide Technotes for the following:

System requirements for Content Manager OnDemand beginning with version 10.5.0.11 is planned for 3Q 2026.

System requirements for Content Manager beginning with version 8.7.0.6 is planned for 4Q 2026.

IBM intends to deprecate the current Full Text Search engine technology in a future Content Manager OnDemand 10.5 fix pack.

Note: The intended replacement search engine technology for Content Manager OnDemand Full Text Search is Elasticsearch and OpenSearch.

Subject: Deprecated DB2 TABLE/TABLESPACES regarding ARS INDEX TABLES

Problem Description:
This week, the DB2 DBA's brought up the topic of old Tablespace constructs being deprecated.  Looks like all of the recently defined Index Data tables are being defined with Supported constructs.  Older Index Data tables were defined with constructs identified as Deprecated. 
Will this Impact Production Support without Upgrading these Objects?  Do they need to be upgraded to be properly supported?  Same with the Indexes associated to these Tables/Tablespaces.

Note:  This answer was provided by Db2 Support.  If you have a question contact Db2 support, not CMOD support.

Note:  This is all unofficial information unless promulgated via an IBM announcement

If you create the objects with APPLCOMPAT  level V13R1M503 or lower then you can create deprecated objects.  If you are using SPUFI or DSNTIAD or DSNTEP2 then you would need to bind those plans with APPLCOMAT(V13R1M503)  or lower.



Note, however,  that Db2 VNext will not support the following:

Simple, segmented or classic partitioned tablespaces;

BRF or basic (6 byte) format pagesets;

hash pagesets;

synonyms;

VTAM connectivity.



You have till approx. 2031 till V13 will be out of support.

_________________________________________________

Follow-on question:

All of the Index tables after 2019 seem to be created ok(partition by growth), but we have 2900+ tables that are Simple tables (TYPE of SPACE).  39 of them are ARS* SYSTEM TABLES.   All need to be converted before 2031, right?  Don't want to wait until the "last minute".
_________________________________________________

Reply from Db2:

>  All need to be converted before 2031, right?

Yes.