It's been too long since I updated everyone.

The good news is that CMOD is doing very well in the marketplace.  I hope I'm allowed to say that  :-) 

The even better news is because of that the Level 2 team has been expanding.

The z/OS Level 2 team remains the same:

- Larry Fitchett
- Brian Lauther
- Lamies Nesheiwat
- Ed Arnold

The IBM i Level 2 team is:

- Greg Hidalgo
- Leo Gemma
- Jason Anderson

And over on LUW we have a deep team:

- Ted Tan
- Tejaswini (we call her "Tej") Jamakhandi
- Krishna Nagaraja
- Akshay Sai
- Jamie Long
- Tim Wood
- Patricia Virtucio
- Nanping Li
- John Link
- Tam Tran
- Sundar Shunmugam

This only affects customers running ODF and upgrading past Java 8.

So -

IF you run ODF
AND IF you are upgrading your default Java to anything newer than Java 8

THEN

- ODF ships a sample version of ODFProcessDist.java and a ODFProcessDist.class file compiled at java version 8.

- Java made a change after version 8 of mail functions they include with java.

Therefore, if customers want to use a higher level of Java they must do the following:

1) upgrade to CMOD 10.5.0.9 or higher

2) compile the sample version of  ODFProcessDist.java at the level of java they are running

3) copy the class file generated into their ODF jars directory.

Ed

Had a report concerning moving from 2.5 to 3.1 doing LDAP configuration work, received the following:

ICH408I USER(ARSSOCKD) GROUP(U#STT  ) NAME(CONT MGR ON DEMAND )
 CSF1SKE CL(CSFSERV )                     
 WARNING: INSUFFICIENT AUTHORITY - TEMPORARY ACCESS ALLOWED   
 ACCESS INTENT(READ  ) ACCESS ALLOWED(NONE  ) 

If you search here in the ODUG on CSFSERV that message has observed many times.

Contact ICSF or RACF support if this is an issue for your shop.

Ed

Output from my DISPLAY GROUP command:

*** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V13R1M505)
                  CURRENT FUNCTION LEVEL(V13R1M506)           
                  HIGHEST ACTIVATED FUNCTION LEVEL(V13R1M506)
                  HIGHEST POSSIBLE FUNCTION LEVEL(V13R1M506) 
                  PROTOCOL LEVEL(2)                           
                  GROUP ATTACH NAME(....)                     

This is an OAM APAR that affects Db2 Allocations

OA68939: UPDATE OAM'S OBJECT SUPPORT SAMPLE JOBS TO WORK WITH NEW VERSIONS OF DB2

https://www.ibm.com/support/pages/apar/OA68939

Error description
As of APPLCOMPAT V12R1M504, Db2 has deprecated support for the
creation of Segmented (non-UTS) tablespaces. This has caused
OAM Db2 sample jobs to implicitly create PBG tablespaces
instead of segmented which is desired at V12R1M504 and higher.

Within our CBRILOB sample, the LOB tablespace is being created
as PBG, however the auxiliary table space is still defined as
segmented which causes Db2 to return with SQLCODE-769.

CBRILOB requires an update to remain compatible with PBG.
Local fix
If APPLCOMPAT is V12R1M504 or higher, then Add PART clause to
the CREATE AUXILIARY TABLE. This will cause the auxiliary table
to become compatible with the LOB table space which is being
created as PBG at APPLCOMPAT V12R1M504 or higher.

Example:

 CREATE AUXILIARY TABLE osg_hlq.OSM_LOB_AUX_TBL
        IN         osg_hlq.OSMLATS
        STORES     osg_hlq.OSM_LOB_BASE_TBL
        COLUMN     OTOBJ
        PART       1;

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.
 

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)

CMOD V10.5.0.11 will require z/OS V3.1

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

Hello teera_aoo -

When I get an unable to connect message here is what I try first:


1. Ping the arssockd server host from Windows.  Does that work?

2. Next try the port:

Powershell - (failure shown first, then I opened up the firewall and retried successfully)

PS C:\Users\ed.arnold> test-netconnection 10.1.203.52 -port 1447
WARNING: TCP connect to (10.1.203.52 : 1447) failed
WARNING: Ping to 10.1.203.52 failed with status: TimedOut


ComputerName           : 10.1.203.52
RemoteAddress          : 10.1.203.52
RemotePort             : 1447
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.133
PingSucceeded          : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : False



PS C:\Users\ed.arnold> test-netconnection 10.1.203.52 -port 1447


ComputerName     : 10.1.203.52
RemoteAddress    : 10.1.203.52
RemotePort       : 1447
InterfaceAlias   : Ethernet 2
SourceAddress    : 10.111.105.47
TcpTestSucceeded : True

3. If both of these fail it's time for a packet trace to see where the packets are going or not going

Ed Arnold