CMOD 10.5 Release Notes

[Ed_Arnold]

For everyone upgrading to 10.5 on z/OS - make sure you're referring to the z/OS 10.5 Upgrade Readme file located here:

https://www.ibm.com/support/pages/ibm-content-manager-ondemand-zos-v105-readme

This is separate from the multiplat server and client readmes which are published one-for-every-fixpack available here:

https://www.ibm.com/support/pages/ibm-content-manager-ondemand-multiplatforms-version-105-readme-files

Ed

[Ed_Arnold]

The arsmaint program has always been designed to be initiated on the server. 

Prior to fixpack 10.5.0.6 this restriction was not enforced. 

Starting with 10.5.0.6 this restriction is being enforced. 

This can result in arsmaint failing in two different cases.

1.)    If arsmaint is not being initiated on the server, the solution is to run arsmaint on the server,

2.)    If arsmaint is  being initiated on the server, the server may not be resolving localhost correctly. Check to ensure the domain name localhost is resolved correctly.

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

[Ed_Arnold]

Had a couple reports of the 10.5.0.7 PTF not APPLYing.

Solution is to APPLY everything up to and including 10.5.0.6 first.

In other words, 10.5.0.6 is the keyhole that service application has to pass through before APPLYing 10.5.0.7.

Ed

[Ed_Arnold]

IF you're configuring ICN for Single Sign-On on z/OS

THEN you need to be at 10.5.0.6.

HOWEVER - I am told that if you're not running arsusec as shipped, right out of the can, then there are no guarantees as to whether SSO will work.

Ed

[Ed_Arnold]

Specifying an index parameter two different ways is unsupported.

Specifically, in this instance, the problem was specifying job_name index created from two different sources: (INDEX1= and -b/-B).

After upgrading from 10.1 to 10.5 the symptom was reports that failed to load, despite having loaded successfully at 10.1.

In these cases, the 88-type record simply indicates an error of RC = 6.   

The desire was for -b/-B to win, overriding what ACIF (or any of the indexers) might have found in the report.   

However, that is  not supported. 

Remove one of the specifications.

[Ed_Arnold]

At 10.5.0.7 the default TLS (SSL) level for both clients and the server flips from TLS V1.2 to TLS V1.3.

If implementing TLS for the first time, things might be easier if all of CMOD, clients and servers, are at 10.5.0.7 first.