Hi all,

Is there a way to exclude or pin the RSCT fileset from being updated during an AIX Maintenance Level (ML) upgrade?

Every time we apply the latest ML, the RSCT fileset gets upgraded to a version that is not listed in the IBM Db2 HADR support matrix. This forces us to downgrade the fileset and rebuild the HADR configuration after every upgrade — a time-consuming and repetitive process.

Has anyone found a reliable workaround or best practice to prevent this?

Thanks,
Shanker

While not technically supported you can simply exclude all the rsct filesets from your local AIX update repository before performing the update, i.e. mv ./installp/ppc/rsct* /someotherplace/ ; cd ./installp/ppc ; inutoc .. Just be aware that you might run into dependency issues when you perform the AIX TL/SP update if one of the newer rsct filesets is required by any of the other new bos filesets during the update process.

------------------------------
Chris Gibson
------------------------------

Hi ,

RSCT is part of the AIX base operating system and is automatically upgraded with any ML/TL update, so there is no supported way to exclude or pin it during the upgrade process.

While some administrators temporarily move RSCT filesets from the update repository, this is not supported and may lead to dependency issues.

The recommended approach is to align AIX upgrade levels with the Db2 HADR support matrix or perform a controlled RSCT rollback after the upgrade if required. For long-term stability, it is advisable to validate the target AIX/RSCT level with IBM support before applying the upgrade

Thanks

------------------------------
Anas AlSaleh
IBM Power Systems Software Specialist
Saudi Business Machines ( SBM )
Riyadh
------------------------------