ALERT: Beware CMOD V10.5.0.8 FixPack BUG

Previous topic - Next topic

JeanineJ

I found out last week from IBM support that a bug has been introduced in the V10.5.0.8 fixpack where the 30 minutes arssockd check is not writing the 201  to the CMOD system log. From my ticket:

"A few months ago we realized that CMOD 10.5.0.8 does not generate the 201 message (as it should). This was an oversight on our part.
Its been corrected in the next fixpack (10.5.0.9) yet to be released."

I found the issue after migrating my sandbox server from RHEL7 V10.5.0.6 to RHEL8 V10.5.0.8.

I'm going to be getting the 10.5.0.7 fixpack for my next server migrations if IBM doesn't have the fix ready for production when I need it.

Figured to let the community know.