I have been trying to install a rpm.rte file-set update on AIX 7.2 and AIX 7.3 , I am trying to install as applied mode so that backout plan could be just rejectig it and rolling back to older version . I have used smitty with Commit - NO and Save replaced file - Yes , installp -aXYd . rpm.rte and both the time the fileset installas as APPLIED but when i check lslpp it shows as COMMITED . I have checked all the places and methods and none seems to work . Is there a solution to this ?

------------------------------
Shadab Sayeed
------------------------------

Hi Shadab,

Which version of rpm.rte are you updating from?

There are changes to the database used by rpm between levels, once you've upgrade, you can't reject and rollback, the old version will no longer be able to read the database.  This is why it may have gone straight to commit.

Phill.

------------------------------
Phill Rowbottom
Unix Consultant
Service Express
Bedford
------------------------------

The behavior you're seeing is expected. rpm.rte cannot remain in APPLIED state because AIX treats it as a core prerequisite fileset. Even if you install it with Apply Only, the system will immediately commit it since rollback isn't supported for this component.
IBM documents this behavior for base/system filesets that always commit automatically.

------------------------------
[Nawaf] [Alsabah]
Network and Computer Engineer
Nawaf
------------------------------

Here is a cleaner and more professional rewrite:

---

If it's a base image, it will always be in a committed state. The apply state appears only for updated images.

# installp -L -d . | grep rpm.rte
rpm.rte:rpm.rte:4.20.1.2001::I:C:::::N:RPM Package Manager::::0::

Here, I indicates it is a base image.

---

------------------------------
Srikanth Thanneeru
------------------------------

HI 

rpm.rte is a base operating system prerequisite fileset meaning It cannot be applied in apply mode ,it's always committed state.

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

The unexpected COMMITTED state of your  rpm.rte  fileset is likely caused by RPM Package Manager auto-commit behavior in AIX, which overrides the  installp   Commit = NO  flag for RPM-dependent packages. Here's how to resolve it:
 
​
1. Roll back the committed fileset with  installp -r rpm.rte <old_version>  (replace  <old_version>  with your original version from  lslpp -l rpm.rte ).
​
2. Reinstall with explicit commit disable:
 installp -a -X -Y -d /export/suma/rpm_new/rpm_7.3 -C NO -S YES rpm.rte 
This forces  rpm.rte  to stay in APPLIED state by bypassing RPM's auto-commit.

------------------------------
djj d
------------------------------

The unexpected COMMITTED state of your  rpm.rte  fileset is likely caused by RPM Package Manager auto-commit behavior in AIX, which overrides the  installp   Commit = NO  flag for RPM-dependent packages. Here's how to resolve it:
 
​
1. Roll back the committed fileset with  installp -r rpm.rte <old_version>  (replace  <old_version>  with your original version from  lslpp -l rpm.rte ).
​
2. Reinstall with explicit commit disable:
 installp -a -X -Y -d /export/suma/rpm_new/rpm_7.3 -C NO -S YES rpm.rte 
This forces  rpm.rte  to stay in APPLIED state by bypassing RPM's auto-commit.

------------------------------
djj d
------------------------------